API Reference · Attribution
Tracking
Resolve AON click redirects without losing attribution; conversions are reported by Partners through the postback route.
Operations
GET
/v1/track/click/{aon_id}PublicRedirect tracked click
Public operationPath Parameters
Route identifiers embedded in the request path.
Fields
1·1 required
Showing the complete documented schema.
aon_idstringAON click tracking identifier.
example: trk_tokyo_001Redirect to the partner destination.
Fields
1·1 required
Showing the complete documented schema.
LocationstringRedirect target resolved for the tracked click.
example: https://partner.example.com/travel/tokyo-weekend?aon_id=trk_tokyo_001format: uriErrors and failure modes
Tracking identifier not found.
Behavior, compatibility, and source notes
Resolve a tracked click and redirect to the final destination while recording attribution.
- This route returns an HTTP redirect rather than a JSON body.
- Your integration should keep the AON tracking link intact so attribution can be recorded before redirecting to the advertiser destination.
Implementation checklist · 2 items
- Keep AON tracking URLs intact until the click redirect resolves.
- Have the Partner report conversions through POST /v1/postback/{partner_id} with the tracking identifier from the click flow.