Marketing attribution assigns credit for an outcome to one or more preceding interactions under a defined model.
Agentic offer attribution applies that principle at the Offer level by correlating a dispatched Offer, a recorded click, and a later commercial outcome reported by an approved supply partner through the configured event path. It extends familiar affiliate attribution and conversion tracking to AI-agent workflows by preserving Offer and dispatch identity in addition to click and partner outcome evidence. In that sense, affiliate attribution for AI agents must preserve the AI-product surface and the particular served Offer, not only a generic referral source. The evidence chain establishes a traceable relationship; it does not by itself prove that the Offer caused the outcome, define a universal attribution window, or guarantee that commission is payable.
From offer interaction to attributed outcome
Return a dispatched offer
AON associates the response with a stable offer ID and a per-dispatch offer-instance ID.
Follow the documented handoff
When tracking is enabled, the executable URL defined by the selected AON contract records the click before handing off to the merchant.
Preserve click context
The redirect carries per-click and per-dispatch identifiers into the downstream flow.
Receive a reported outcome
A supply partner reports a conversion through its configured server-to-server postback route.
Validate attribution and commission
AON resolves the stored evidence chain, deduplicates the outcome, and applies goal, pricing, risk, and reconciliation rules.
Identifiers in the AON attribution chain
Offer, dispatch, click, and outcome identifiers represent different stages of the attribution evidence chain.
- 01Offer identity
offer_id identifies the stable offer in inventory across multiple dispatches.
- 02Dispatch identity
offer_instance_id identifies one delivery of that offer and can later be carried as aon_tracking_id.
- 03Click identity
click_id or aon_click_id identifies a specific recorded click after the user follows the documented click URL for the selected AON contract.
- 04Outcome identity
A partner order or event identifier supports deduplication and reconciliation without replacing the tracked origin.
- Attribution models, lookback windows, consent, and retention rules can differ by system and commercial agreement.
- AON evaluates a Partner postback against the Goal declared by the attributed Offer. An exact Goal match is required for billing evaluation; a valid unmatched event can still be recorded as a non-billing event.
Offer attribution vs AI traffic attribution
AI traffic attribution classifies visits or conversions from an AI channel. Agentic offer attribution is narrower: it resolves a specific structured offer dispatch and tracked interaction to a reported downstream outcome. See the Attribution layer definition.
Example in practice
An AI career coach presents an eligible online-course offer and opens the documented click URL for its selected AON contract. The tracked handoff records the click and sends the user to the course provider. If an approved supply partner later reports a qualifying enrollment with the preserved tracking context, AON can connect the enrollment to the dispatched offer and originating publisher before applying settlement rules.
Common questions about agentic offer attribution
Is a tracked click the same as a conversion?
No. A click records an interaction with the offer, while a conversion is a later qualifying outcome reported through the documented partner event path.
Which identifier ties attribution to a specific offer delivery?
offer_instance_id identifies the particular delivery used in the attribution chain. offer_id identifies stable inventory, but it cannot by itself distinguish which response or tracked interaction preceded an outcome.
What happens when a reported outcome has no matching tracking context?
A reported outcome without matching tracking context cannot be reliably attributed to a specific AON offer interaction. The outcome remains unmatched or fails attribution validation because offer_id alone does not identify a specific dispatch.
What tracking information should an AI product retain from recommendation through conversion?
Preserve the documented action and the identifiers required by the selected delivery and tracking contract, then use the supported event and reporting paths rather than inventing a new identifier scheme. In AON, stable Offer identity, per-dispatch identity, and click context serve different purposes and are not interchangeable.
Does attribution prove that an AI recommendation caused the purchase?
No. Attribution assigns credit from observable touchpoints under defined rules. Proving causal lift requires a different measurement design, such as controlled incrementality analysis.
How is conversion tracking for AI agents different from ordinary affiliate attribution?
The underlying purpose is similar: connect a downstream outcome with an earlier attributed interaction. Agentic offer attribution can additionally preserve structured Offer identity, a particular served instance, and the originating AI-product surface before a partner reports the conversion.
Does successful attribution guarantee commission payment?
No. Attribution establishes the evidence chain. Goal matching, pricing, risk, deduplication, reconciliation, and other settlement eligibility rules can still affect whether commission becomes payable.
Sources
- AON Tracking APIAON documentation
- AON Partner postbacksAON documentation
- UCP attribution specificationRelated standard
- Google Analytics attribution overviewIndustry source