Attribution you can make budget decisions on, built in your own warehouse
You keep your data in your environment, and your data team owns every pipeline. Your marketing team gets journeys, attribution and reports to decide where budget goes, built with a team that has done it many times.
- Ingestion
- Tool setup
- Conversion events
- Customer journeys
- Attribution models
- Reporting
- Handover
Owning your data shouldn’t slow down your marketing decisions
Data that has to stay with you
Regulation or company policy means customer and revenue data stays in your own cloud, under your own contracts.
Marketing waiting for answers
Marketing needs to know which channels bring customers. Until then, budget runs on last-click.
Choices that change the numbers
How journeys join up across systems, how channels are grouped, and how credit is shared. Each one takes time to get right.
Before anything is built, you know what it takes
We usually start with a four-week scoping engagement. A workshop with marketing and one with data, then a review of your data and systems, with weekly check-ins. You keep everything, whether you build it with us or on your own.
Your gaps, ranked
Where your data, identity and attribution logic fall short, rated by impact on budget decisions.
How it holds up as you grow
What breaks with more spend, new channels, new markets or app campaigns.
The target design
Which parts of your setup to keep, extend or replace.
A build plan
Components, order and effort, plus quick fixes you can make straight away.
An operating plan
Who runs it after the build, and the skills it needs.
A readout
The findings, presented to your stakeholders.
| Component | Keep, extend or build | When | Effort |
|---|---|---|---|
| Web events in the warehouse | Build | First | M |
| Identity across web, app and payments | Extend | First | L |
| Attribution model | Replace | First | L |
| Survey answers in the journey | Build | Later | S |
| Signals to ad platforms | Build | Later | M |
| Quick fixes for your team this week: 2 | |||
Built in your accounts, with your data team
Everything runs in your own cloud, warehouse and BI tool, under your contracts. We start from the tracking and data you already have, so there’s no new tag to add and no history to start over.
Your data team works with us through the build. By the time we’re done, they know how every part works, so there’s no separate handover project at the end.
What we build, and what you get from it
We build it in this order, starting with the parts that affect budget decisions most.
- 1
Ingestion
What we buildPipelines for ad spend, website and app events, CRM or revenue data, and survey answers if you collect them, through your ETL
What you getThe data marketing decisions depend on, in one place in your warehouse
- 2
Tool setup
What we buildAny tool the foundation still needs, chosen with you and set up
What you getNo gaps in what the measurement needs
- 3
Conversion events
What we buildThe milestones from signup to revenue, agreed with marketing and modelled in your warehouse
What you getOne definition of each conversion, used in every report
- 4
Customer journeys
What we buildTouchpoints joined across web, app and CRM, into one record per customer
What you getThe path each customer took to revenue, not only the last click
- 5
Attribution models
What we buildChannel groups and credit rules, built in dbt and written up in plain language
What you getChannel credit you can trace back to a rule, and change when your marketing changes
- 6
Reporting
What we buildReports in your BI tool, built around the budget questions marketing asks
What you getWhere to spend, read where the rest of the company already works
- 7
Handover
What we buildDocumentation, walkthroughs with your data team, and a list of what would improve the setup next
What you getA team that can run and extend it without us
Every rule, written up in plain language
Marketing can read why a channel got credit. Your data team can see where the rule lives and change it.
When the project ends, your team owns all of it: pipelines, models, reports and documentation. Nothing runs on a Propel account.
- Rule
- Paid social credit
- In plain language
- A Meta or TikTok ad click gets credit if it happened in the 28 days before signup.
- Why
- Agreed with marketing in discovery, because most trials start within four weeks of a first visit.
- Changes go through
- Your data team
We’ve built this many times, so your team gets there faster
We start from a foundation
We adapt what we’ve built before to your data and your stack, instead of starting from zero.
We’ve solved these problems before
Joining journeys, grouping channels, sharing credit. Less trial and error, because we’ve done it many times.
We start with what matters
We build the parts that affect budget decisions first, so marketing can use the numbers early.
More than half of Zeffy’s signups showed up as direct or referral, and off-the-shelf tools didn’t fit their self-serve funnel. We combined their Amplitude data, signup survey answers and ad platform data into one attribution model their team owns. Read how in the Zeffy case study.
“Now we have something flexible. We can play around with the rules, add new channels, and actually see the impact of what we’re doing.”
Alexandre Piron, Paid Marketing Specialist, Zeffy
Who you work with

Timo Dechau
Builds the data systems marketing teams rely on, for companies like Amplitude, Shimano, Cricut and Audible.
Barbara and Timo work on every project. We take on at most six clients at a time.
Is it a fit?
A good fit if
- You have a data team with the time and mandate to take this forward
- You need to own the stack and pipelines, for example for regulation
- Your tracking is in reasonable shape
- Marketing is happy to request rule changes through the data team
Probably not the best fit if
- Cost is the main reason. Building in your environment is more complex and takes longer
- Your tracking has big gaps. We build on what’s there, so those are worth fixing first
- Marketing wants to change rules often. After handover, changes go through your data team
- Your data team is stretched. Handovers to teams without time tend to stall
If ownership isn’t the main reason, a team that runs it for you is usually the better fit. We’ll tell you on the first call.
Questions data and marketing teams ask
Which warehouses and tools do you work with?
We usually build on BigQuery, dbt and Fivetran, and work with other warehouses and ETL tools case by case. We confirm the fit during scoping.
Do we need new tracking?
No. We build on the tracking you have and point out the gaps worth closing. Your team or agency makes any tag changes.
How long does the build take?
It depends on your sources, how custom they are, and how much time your data team has. The build plan from the scoping gives you the estimate.
How much of our data team’s time does it take?
They work alongside us through the build. That keeps the handover short, and it’s why a setup stalls when the team has no time for it.
Can you send conversion data back to the ad platforms?
Yes, if it’s in scope. We set up the events and values each platform receives, from your warehouse.
Can marketing change the rules after handover?
Yes, through your data team. Every rule is written up in plain language, so it’s clear what to change and why. If marketing wants to change rules on its own, that needs us to host the data.
Does our data leave our environment?
No. We build in your accounts, with the access you give us. We share a DPA, a security overview and our GDPR basis.
