The short answer. Attribution software assigns credit for a conversion across the touchpoints that preceded it. Every tool in the category runs the same handful of models on whatever events it receives. The models are close to interchangeable. What separates good reporting from confident nonsense is how completely the tool collects conversions in the first place.
We pulled the US search results for “attribution software” on September 22, 2026. Ignoring the AI Overview, the first page is two vendor homepages, four roundups promising 10, 12, 19 or more tools reviewed, one FAQ page defining the term, and at position three, a Reddit thread in r/PPC titled “What attribution tools/software are you guys using?” with no settled answer underneath it.
That shape tells you something. The buyers doing the searching are not short of vendor lists. They are short of a way to tell whether any of it will report numbers they can act on. The roundups all compare the same axes: supported models, integrations, pricing tier, whether there is a B2B CRM connector. Not one of them asks the question that decides the answer.
Here it is. Attribution software is a math layer sitting on a data layer, and almost nobody sells you the data layer. If the events arriving at the model are missing a third of your conversions, a better model does not rescue you. It gives you a more sophisticated, more confident, more expensively licensed version of the wrong answer.
What attribution software actually does
An attribution tool takes a stream of marketing touchpoints (ad clicks, organic sessions, email opens, direct visits) and a stream of conversions (purchases, signups, qualified leads), stitches them into per-user journeys, and applies a rule that decides how much credit each touchpoint gets. It then rolls that credit up by channel, campaign, ad group, and creative so you can compare return on spend across things that are not otherwise comparable.
Three jobs, in order of how often they break:
- Collect the touchpoints and conversions.
- Stitch them into journeys belonging to the same person or account.
- Assign credit using a model.
Vendor marketing is almost entirely about step three. Step one is where the money leaks.
The four models, in one table
This is the comparison every roundup leads with, so here it is compressed, and then we can move on to the part that matters.
| Model | Credit goes to | Honest use case |
|---|---|---|
| First touch | The first recorded interaction | Judging top-of-funnel demand generation |
| Last touch | The final interaction before converting | Fast, defensible, what most ad platforms report by default |
| Linear or time decay | Split across all touchpoints, evenly or weighted toward recent ones | Multi-session considered purchases |
| Data-driven or algorithmic | Distributed by modeled incremental contribution | Only credible at high conversion volume |
Two things worth saying plainly about this table. First, the differences between these models are smaller than the differences between two tools’ collection methods. Swapping last touch for time decay moves your channel mix report by a modest amount. Losing 35 percent of your conversions moves it by a lot more, and in a direction you cannot predict, because the loss is not evenly distributed across channels.
Second, data-driven attribution needs volume. If you are running a few hundred conversions a month, an algorithmic model is fitting noise and presenting it in a nice chart. Last touch plus complete data beats data-driven plus partial data at that scale, every time.
The input problem nobody puts in the comparison table
Browser-based conversion tracking loses 30 to 40 percent of conversions. That number is not controversial among people who have measured it, and it comes from four stacked causes:
- Ad blockers and privacy extensions drop the tracking script before it ever loads. This is the largest single bucket and it skews heavily toward technical and younger audiences, which means it skews by channel. More on the mechanics in our guide to ad blocker tracking.
- Safari Intelligent Tracking Prevention caps cookies set by JavaScript at seven days. Any consideration window longer than a week loses its identifier.
- Firefox Enhanced Tracking Protection blocks cross-site tracking cookies by default, and blocks known tracking scripts outright in strict mode.
- Cookie expiry and cross-device journeys break the stitch in step two even when collection in step one succeeded.
Now put that next to the thing attribution software is for. You are comparing channels. If Channel A’s audience blocks trackers at twice the rate of Channel B’s, your attribution tool is not measuring performance. It is measuring ad blocker penetration, dressed as performance, and you are about to move budget on the basis of it.
This is why two tools running the identical model on the same business can produce channel reports that disagree by double digits. They are not disagreeing about math. They are receiving different events.
Three collection architectures, and what each one costs you
When you evaluate attribution software, this is the axis to sort on. Every tool in the category sits in one of three places.
| Architecture | How events are collected | What it loses |
|---|---|---|
| Browser pixel | A script on your site fires on conversion | Everything a blocker, an extension, or a failed script load prevents. Cookie lifetime capped by the browser. |
| Browser plus tag manager | Same, routed through a container | The same losses. A tag manager reorganizes tags, it does not change who is allowed to fire them. |
| Server-side collection | Your server sends the conversion to the ad platform APIs directly | Far less. The event originates somewhere the browser cannot veto and cookies can be set in an HTTP response. |
That middle row is the expensive misunderstanding. Moving your tags into a container, or even into a server container you administer yourself, is a deployment change. It is worth doing for page speed and governance. It does not recover a conversion that a blocker stopped from firing, because the trigger still lives in the browser. We unpack the distinction in detail in what server side tracking is and compare the two paths directly in client side vs server side tracking.
If you want the fuller version of the leak, with the causes ranked, why you’re losing conversion data covers it.
MTA and MMM are answering different questions
This comes up constantly in the buyer research, so it is worth thirty seconds.
Multi-touch attribution (MTA) works bottom-up. It observes individual journeys, stitches them, and assigns credit per touchpoint. It is granular, it is actionable at the campaign level, and it degrades exactly as described above when collection is incomplete.
Marketing mix modeling (MMM) works top-down. It regresses aggregate spend against aggregate outcomes over time, with no user-level data at all. It is immune to the identity and blocking problems, it handles offline and brand channels that MTA cannot see, and it needs years of history plus meaningful spend variation to say anything reliable. It will not tell you which ad group to pause on Thursday.
Most teams buying attribution software want MTA. The correct reason to add MMM is that you have channels MTA structurally cannot observe, not that your MTA numbers look wrong. If your MTA numbers look wrong, fix the collection layer first, because an MMM built on the same misreported conversions inherits the problem at a different altitude.
Six questions to ask before you compare models
This is the evaluation checklist we have not seen published anywhere in the category. Ask these before you look at a single feature matrix.
- Where does a conversion event originate? Browser, or your server? If the answer is browser, everything below is capped by the blocker rate of your audience.
- What is the measured match rate? Not the model’s confidence score. The share of real conversions the tool can tie to a click identifier. Ask for the number and ask how it was measured.
- What happens to click IDs after seven days? If they live in a JavaScript-set cookie, Safari deletes them. If they are stored server-side, they survive the consideration window.
- Does it send conversions back to the ad platforms, or only report on them? A dashboard tells you what happened. Feeding accurate conversions back into the platform APIs is what changes bidding, and bidding is where the money is.
- How long does deployment take, and who does it? A tool that needs a developer sprint and a tagging audit has a real cost that is not on the pricing page.
- What does it do when the identifier is missing entirely? Discard the conversion, guess, or flag it? All three are defensible. Silently guessing is not, and it is the most common answer.
Question four is the one that separates reporting tools from tracking tools, and buyers routinely conflate them. An attribution dashboard that never writes back to Google Ads leaves the platform optimizing against its own incomplete pixel data, which is the original problem.
Measure your own gap before you shortlist anything
You do not need a trial or a sales call to find out how bad the input problem is on your own site. Take last month and put two numbers side by side.
The first is conversions as your ad platforms and analytics report them. The second is the count of real, completed orders or qualified leads from the system of record that finance trusts, filtered to the same date range. A payment processor, a CRM, an order table. Somewhere the number is not negotiable.
The gap between those two figures is the ceiling on what any attribution software can tell you. If it is under 10 percent, your collection layer is healthy and buying for modeling features is a reasonable decision. If it is 25 percent or more, model selection is not your problem and no vendor on the first page of search results will fix it by being better at math.
Then run the same comparison one channel at a time. Uneven gaps across channels are the finding that should stop a purchase, because that is the pattern that makes cross-channel comparison actively misleading rather than merely incomplete.
Where Convultra fits
Convultra is server-side conversion tracking, which means it sits at the collection layer rather than the modeling layer. It installs as one line of JavaScript, with no tagging server to administer and no developer sprint. It captures gclid, gbraid, wbraid, fbclid and msclkid at first touch with a 90-day retention window, persists gclid, fbclid and msclkid server-side (gbraid and wbraid stay in the browser’s click history), and delivers conversions to Google Ads and OpenAI Ads today, with Meta, Microsoft Ads and TikTok coming soon. Match rate is about 98 percent on the conversions it captures, against the 60 to 70 percent a browser pixel manages once blockers and ITP have taken their cut.
The honest positioning: if you already own an attribution platform and its numbers look thin, you probably do not need a second attribution platform. You need the events reaching the one you have to be complete. If you do not own one yet and your reporting question is “which campaigns actually produced revenue,” accurate server-side collection feeding the ad platforms directly may be the whole answer.
For measuring the gap before you buy anything, our guide to conversion tracking accuracy walks through how to quantify what you are currently losing.
So what should you actually shortlist
Not a list of nineteen. Sort the category by what it is for:
- Ad platform native reporting (Google Ads, Meta Ads Manager). Free, blind to everything outside its own walls, and running on the same browser pixel data as everyone else. Fine as a baseline, useless as a referee between channels.
- Attribution and analytics platforms. Strong modeling, dashboards, CRM stitching for B2B. Buy for the reporting. Check question one before you assume the inputs are sound.
- Server-side tracking tools. Focused on collection and on delivering conversions back to the ad platforms. Our roundup of the best server side tracking tools covers the current field, and if you are weighing a self-hosted tagging server against a managed product, the Stape alternative comparison lays out that specific trade-off.
The order matters more than the shortlist. Fix collection, then choose a model. Doing it the other way around is how teams end up with a beautifully modeled picture of two thirds of their business.
FAQ
What is attribution software?
Attribution software assigns credit for a conversion across the marketing touchpoints that preceded it. It collects ad clicks and sessions, stitches them into per-user journeys, applies an attribution model to distribute credit, and reports return on spend by channel and campaign. Its accuracy depends far more on how completely it collects conversions than on which model it applies.
What are the four types of attribution?
First touch credits the first recorded interaction. Last touch credits the final interaction before the conversion. Linear or time decay splits credit across every touchpoint, either evenly or weighted toward recent ones. Data-driven or algorithmic attribution distributes credit by modeled incremental contribution, and it only produces reliable output at high conversion volume.
What is the difference between MTA and MMM?
Multi-touch attribution works bottom-up from individual user journeys and is actionable at the campaign level, but it degrades when conversion collection is incomplete. Marketing mix modeling works top-down by regressing aggregate spend against aggregate outcomes, needs no user-level data, and can see offline and brand channels, but it requires years of history and will not tell you which ad group to pause today.
Why do two attribution tools report different numbers for the same campaign?
Usually because they are receiving different events, not because they disagree about math. Browser-based collection loses 30 to 40 percent of conversions to ad blockers, Safari Intelligent Tracking Prevention, Firefox Enhanced Tracking Protection and cookie expiry, and that loss is not distributed evenly across channels. Two tools with different collection architectures will therefore produce channel reports that disagree by double digits.
Does moving to a server-side tag manager fix attribution accuracy?
Not on its own. A server-side tag container changes where tags execute, but the trigger that fires the conversion still lives in the browser, so an ad blocker that prevents the script from loading still prevents the event. Recovering those conversions requires the event to originate on your own server rather than in the visitor’s browser.
What should I ask an attribution software vendor before buying?
Ask where a conversion event originates, browser or server. Ask for a measured match rate and how it was measured. Ask what happens to click identifiers after seven days, given Safari’s cookie cap. Ask whether the tool sends conversions back to the ad platform APIs or only reports on them. Ask how long deployment takes and who performs it. Ask what the tool does when an identifier is missing entirely.
Find out what your current stack is missing
Convultra installs with one line of JavaScript and shows you the conversions your pixel never recorded, usually within a day. Start your free trial.