Marketing Attribution in a Cookieless, AI-Search World

Three layers, one number

Layer 1: deterministic. Self-reported ("how did you hear"), UTM-tagged conversions, PLG signup events. This is the ground truth.

Layer 2: statistical. Media mix modeling (MMM) on spend + pipeline, refreshed quarterly. This is what tells you channel efficiency at spend-level granularity.

Layer 3: qualitative. Rep-reported source per closed-won, sales debrief. This catches what the models miss.

Blend them into one dashboard, and the CFO gets a defensible number without pretending you can precisely attribute individual users.

AI search: the new dark funnel

Perplexity, ChatGPT search, and Google's AI overviews increasingly answer questions without a click. Track branded search share of voice, direct traffic trend, and self-reported source — those are the leading indicators that AEO investment is working.

Measurement that survives a board review

Activity metrics — messages handled, tasks executed, hours "saved" — are the metrics of a project that is about to be cancelled. They rise regardless of whether the work was any good. Replace them with outcome metrics measured against a holdout: a slice of traffic deliberately handled the old way so you always have a live control group rather than a historical one.

The four numbers we hold ourselves to on cookieless attribution engagements are resolution or completion rate without human touch, quality as judged by a blind human review of a weekly sample, cycle time from trigger to resolved, and cost per case fully loaded including inference and engineering amortisation. Report all four together. Any one of them in isolation can be gamed, and the combination cannot.

Publish the numbers weekly to a channel that includes sceptics. Programmes die in silence, not in criticism — and the fastest way to earn the budget for phase two is a four-week chart that a CFO can read without a translator. Our revenue operations team ships this dashboard as a deliverable in week one, before the first line of production logic is written.

• Autonomous resolution rate against a live holdout
• Blind quality score on a weekly random sample
• Cycle time, median and 90th percentile
• Fully loaded cost per case, including inference
• Escalation reasons, grouped and trended

Governance, risk and the things auditors ask

Assume from day one that someone will ask you to reconstruct a specific decision from six months ago. That single requirement drives most of the design: immutable logs of every input, every retrieved source, every tool invocation with its arguments, every output, and the identity of any human who reviewed it. Retention should match your existing records policy, not a default someone picked in a console.

Access control is the second pillar. The system should hold the narrowest possible credentials, scoped per tool, rotated on a schedule, and never shared with a general-purpose account. Anything that moves money, changes entitlements, deletes records or communicates a legal position belongs behind an explicit human approval regardless of how confident the model is. Confidence is not authority.

Third, write down what the system is not allowed to say or do, and test it. A short adversarial suite run on every deployment — prompt injection attempts, out-of-scope requests, hostile inputs, edge-case identities — catches regressions that unit tests never will. This is standard practice on every build we ship, and it is the reason our clients pass procurement security reviews without a remediation round.

• Immutable, queryable audit trail per decision
• Least-privilege, per-tool, rotated credentials
• Mandatory human approval for money, entitlements and deletions
• Adversarial regression suite in the deployment pipeline
• Documented data retention aligned to existing policy

Cost model and total ownership

Budget in three buckets and you will not be surprised. Build is a one-off: discovery, integration work, evaluation harness, and the control plane. Run is monthly: inference or platform fees, infrastructure, and observability. Improve is the bucket teams forget — the standing allocation for prompt and policy maintenance, new categories, and responding to upstream API changes. A programme with no improve budget degrades quietly within two quarters.

On the run line, the largest controllable cost is almost never the headline model price. It is unnecessary context. Retrieving twelve documents when three would do, replaying full conversation history on every turn, and re-deciding cases that a cache could answer are the three habits that inflate bills by an order of magnitude. Caching, tiered routing to smaller models for classification, and tight retrieval budgets typically cut spend 60–80% with no measurable quality loss.

Compare against the honest alternative, not against zero. The counterfactual for cookieless attribution is usually additional headcount, an outsourced team, or continued lost revenue from slow response — all of which carry their own ramp, management and quality costs. When you price it that way, the payback window on a well-scoped wedge is normally two to four months.

• Build: discovery, integration, evals, control plane
• Run: inference, infrastructure, observability
• Improve: standing budget for policy and coverage growth
• Optimise: caching, tiered routing, retrieval budgets
• Compare to headcount and lost revenue, not to zero

Team, ownership and change management

The staffing pattern that works is small and cross-functional: one engineer who owns the integrations and control plane, one domain expert who owns the policy and reviews the weekly sample, and one accountable owner with the authority to change the underlying process. Three people with clear decision rights consistently outperform a large steering committee, because most of the work is judgement calls that need to be made in hours rather than at the next fortnightly meeting.

Change management is 40% of the outcome and gets 5% of the planning. Bring the operators in during discovery, not at launch. Show them that the first release drafts their work rather than grading it. Give them a one-click override and treat every override as a bug report against the policy, not as user error. Teams that do this see adoption in weeks; teams that announce the system by email see quiet sabotage for months.

Finally, decide up front who owns the system after go-live. An unowned automation is a liability the moment an upstream API changes. If you do not have internal capacity, that is a legitimate reason to use a managed partner — our revenue operations practice runs post-launch operations for clients in exactly that position, and Evron Desk covers the frontline support layer alongside it.

• One engineer, one domain owner, one accountable executive
• Involve operators during discovery, not at launch
• Treat every override as a policy bug
• Name a post-launch owner before you go live

Frequently asked questions