Attribution Reporting API

Data & Tracking

Also: ARA · Chrome Attribution Reporting API

What it isBrowser-native way to measure ad clicks to conversions

Trade-offPrivacy first, precision second

Built byGoogle, part of Privacy Sandbox

Watch forNoisy, delayed, aggregated data

Quick definition

The Attribution Reporting API (ARA) is a Chrome browser feature that lets advertisers measure whether an ad click or view led to a conversion, without using third-party cookies. It's part of Google's Privacy Sandbox and reports results in a delayed, aggregated form rather than per-user detail.

How it varies across Australia

Adoption of privacy-preserving measurement tools like ARA is still uneven across Australian advertisers. Larger businesses with dedicated data teams are testing it alongside server-side tracking and Consent Mode. Smaller businesses are mostly unaware it exists, which means their attribution gaps will widen faster once third-party cookies fully disappear.

See data and tracking maturity across Australian industries →

What it actually means

For years, attribution ran on third-party cookies. A cookie followed a person from ad click to purchase, and the advertiser stitched the journey together at the individual level. The Attribution Reporting API (ARA) breaks that model deliberately.

Instead of tracking a person, the browser itself records that a click happened and, later, that a conversion happened on the same device. It then reports the match back to the advertiser in a delayed, aggregated and deliberately noisy form. No single ad click can be tied to a single named customer. You get a statistically useful signal, not a certain answer.

This matters because it changes what attribution can promise. Last-click and multi-touch attribution models assumed clean, user-level data. ARA assumes privacy by default and asks marketers to accept some uncertainty in exchange. It sits alongside server-side tracking, first-party data collection and Consent Mode as part of the post-cookie measurement toolkit.

Most marketers have never touched it directly. Ad platforms like Google Ads and Meta implement it under the hood and abstract the complexity away. But understanding what it does explains why conversion numbers have grown fuzzier industry-wide, and why chasing perfect attribution is a losing game now.

The Attribution Reporting API doesn't tell you who converted. It tells you enough to keep optimising without knowing who anyone is.

How it shows up

ARA shows up indirectly, through the ad platforms that implement it. Google Ads conversion reporting increasingly blends modelled and API-based signals rather than raw cookie-based tracking. Reported conversion counts become smoother and slightly delayed. Attribution windows shrink. Cross-device matching gets less reliable. If your conversion numbers have felt harder to reconcile against your CRM lately, ARA and its Privacy Sandbox siblings are part of the reason.

The Australian context

Australian businesses face this shift from two directions at once. Chrome's move away from third-party cookies affects tracking globally, but the Privacy Act reforms and ACMA's tightening spam and consent rules push in the same direction locally. Businesses that treat ARA as a Google problem to wait out are missing that the underlying trend, less individual tracking, more aggregated and consented measurement, is where Australian privacy law is heading regardless of what any single browser does.

Where people get this wrong

Assuming ARA is optional because 'my agency handles tracking'.The API changes what data is available at all, not just how it's collected. If the ad platform doesn't support it well for your setup, no amount of agency effort recovers the missing precision.

Expecting ARA to replace cookies with equivalent accuracy.It's designed to be less precise on purpose. Noise and aggregation are privacy features, not bugs to be engineered around.

Ignoring it because it 'only affects Chrome'.Chrome holds a majority share of the Australian browser market. Other browsers are shipping comparable privacy-preserving measurement approaches, so the direction is universal even if the mechanics differ.

Common questions

Is the Attribution Reporting API the same as Google Analytics?

No. Google Analytics 4 (GA4) is a full analytics platform. ARA is a lower-level browser API that ad platforms use to measure ad conversions without third-party cookies. GA4 can incorporate signals influenced by it, but they're separate systems.

Do I need to set up the Attribution Reporting API myself?

Usually not directly. Ad platforms like Google Ads implement it on your behalf. Your job is making sure your conversion tracking, consent settings and server-side setup are configured well enough for the platform to use it effectively.

Why do my conversion numbers look different since this rolled out?

ARA and related Privacy Sandbox changes report conversions in delayed, aggregated and slightly noisy batches instead of clean per-click matches. Expect small discrepancies between platforms and a short reporting delay rather than instant, exact figures.

Does this mean third-party cookies are already gone?

Not entirely, but the direction is set. Chrome has moved slowly on full removal, but the industry, including Australian privacy regulation, is converging on less individual-level tracking regardless of the exact cookie timeline. Building measurement around first-party data is the safer bet either way.

Debrief

Get the next one

No spam. No fluff. Just the next article, straight to your inbox.

Keep exploring

About New Rebellion

New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.

How we think →