New-visitor event view
Connect GA4 and related event records so the team can distinguish a recognized first visit from later observed activity, while keeping identity gaps visible.
Brinker Analytics / Attribution systems
A custom MTA system can connect events, return visits and order records. That way your team can see the path a buyer took, know how the method works, and keep the judgment.
Talk through your attribution foundation
The decision
When a buyer encounters paid social, search, email, and affiliate links before purchasing, the order record alone hides useful context. The aim is a traceable view of the touchpoints your business can observe, with the order-management system retained as a check.
If the real decision is whether more spend created more total sales, MTA is a starting hypothesis—not the proof. That is where a well-designed incrementality test or a broader MMM belongs.
A strong fit
Start elsewhere
Without third-party cookies
Yes, but not without your own records.
MTA's core job is to notice that a click today and a click two weeks ago came from the same person. That's hard, because cookies get cleared. Safari and other browsers shorten or block them. People switch phones and laptops.
When those records get wiped, the system has “goldfish memory.” It sees a returning buyer as new. First-click collapses into last-click, and the MTA tells you nothing you didn't already have.
First-party event data. That's site activity recorded from your own domain, not a third-party call. It can keep more continuity, subject to browser controls (Safari, for example, deletes script-set storage after seven days without a visit) and the shopper's consent. It doesn't get around consent, and privacy rules depend on where you sell and how it's built.
On top of that sits identity resolution. A partner uses signals like hashed email addresses, to link visits that likely belong to the same person across devices. It will never be perfect, but it gives you a more complete record of the journey you can see.
My working target before I'd lean on MTA: first-party tracking that captures more than about 90% of sales and sessions. That's not a universal line, and standard GA4 alone, triggered by third-party code, isn't enough in my view.
Also clean up two things first. Deduplicate browser and server events (Meta matches them on a shared event ID and event name), or you'll count too many touchpoints. And keep UTM rules consistent so each touch lands in the right channel.
Build it first, in-house, with a developer, or with a partner. Until then, ordinary platform reporting plus an MMM, a platform lift study, or a geo test will usually serve you better than a weak MTA.
And if you're short on history, an MTA built on first-party data can still work. It doesn't need 12 months of data to start showing useful paths.
Across channels
On this site, cross-channel attribution is multi-touch attribution (MTA). It spreads credit across the channels you can see in first-party journeys, like paid social or search. Then it ties each path to an order in your own record.
Which channels show up together on the way to a purchase, and in what order.
That's useful. It's where a lot of my best budget questions start.
Whether one channel caused sales in another. Credit isn't cause. An MTA hands out a fixed pool of order credit across the clicks it can see. And the more identity it loses, the more it starts to look like last click.
Last click undervalues upper-funnel channels. A video or podcast ad can create the demand and rarely be the last click. TV and radio never get a click at all.
Because each platform counts the conversions it touched, by its own rules. Google Ads defaults to data-driven attribution for most conversion actions. GA4 has its own attribution settings too. Add the reports together and you can get more sales than your business made.
That's overlap. It isn't cross-channel attribution.
From a test. If you can measure each other channel's sales by region, a geo test can compare them in the test and control regions. That shows whether changing one channel changed what another one sold. Total sales stay the bottom line. That's how you test whether one channel lifts another. It helps to know what each measurement method can see.
Think approaches, not brands. Platform reporting and GA4 attribution are the usual starting points. A custom MTA built on your own order record is the next step up. For the rules themselves, see first-touch, last-touch and multi-touch rules. Wondering why the models argue? Read why MTA and MMM disagree.
No model owns the truth.
If you're deciding whether cross-channel credit is enough to move budget, talk through the decision.
The approach
The implementation follows the available records and the decision they need to serve. It does not begin by declaring a favorite attribution model.
Identify the event sources, IDs, handoffs, channel taxonomy, and the system that owns the order truth.
Link sessions and touchpoints to purchase records where the data permits, then explain material gaps against the OMS and other reporting systems.
Document which attribution rule serves each operating question, what it misses, and when a test or MMM should take over.
Three upgrades worth investigating
Connect GA4 and related event records so the team can distinguish a recognized first visit from later observed activity, while keeping identity gaps visible.
Connect the order platform to identify new and returning customers where the records support it, then reconcile that view to the system of record.
Where a geo incrementality test is comparable, use it to calibrate how last-click patterns are interpreted. A calibration factor applies only to the conditions tested; it is not a permanent multiplier or causal proof for every channel.
An LLM can help surface hypotheses—such as whether lower-funnel channels are receiving more observed credit than their tested incremental effect supports—but a person still has to review the records, test conditions, and decision.
Keep reading
Attribution rules are reporting conventions. The useful one depends on whether the team is reconciling a last click, studying entry paths, or deciding what requires a causal test. If the order, event, and campaign records cannot yet be compared, begin with the data foundation rather than forcing an attribution view.
Questions before committing
It connects the customer activity your systems can observe to orders and makes the resulting journeys available for investigation. The work begins with the event, identity, and order records—not an attribution rule.
No. An observed path can support a useful hypothesis, but it cannot establish that every visible touchpoint caused an order. A material causal claim needs a credible test when one is feasible.
Yes. A data lake or reliable website-event stream is a practical starting point. If neither exists, the first scope is usually the capture, ownership, and reconciliation work needed to make later attribution credible.
Yes, on this site. Both give credit across the channels you can see in first-party journeys, tied to your own orders. Neither proves that one channel caused sales in another. For that, you need a test, like a geo test that compares each channel's sales in the test and control regions, where those sales can be measured by region.
A practical first conversation
We can determine whether a custom MTA build, data-foundation work, a test, or a different measurement path is the next useful move.
Talk through your attribution foundation