Skip to content

docs(affiliate): calling a tracking link from your server with ip/ua (LIN-3814) - #292

Open
RathodDarshil wants to merge 3 commits into
mainfrom
darshil/lin-3814-tracking-link-s2s
Open

RathodDarshil wants to merge 3 commits into
mainfrom
darshil/lin-3814-tracking-link-s2s

Conversation

@RathodDarshil

@RathodDarshil RathodDarshil commented Oct 17, 2026 •

Copy link
Copy Markdown
Collaborator

Documents how an affiliate whose server calls the tracking link passes the user's device IP and user agent (ip / ua, with the AppsFlyer af_ip / af_ua names accepted), what redirect=false returns, and what the advertiser's S2S switch now covers. Merge only after hazelnut#914 is deployed, because the behaviour it describes is not live yet.

Part of LIN-3814. Triggered by CASHe / Mobrand, whose server-side clicks recorded Mobrand's server IP and never matched an install.

Changes

  • Tracking Links: new section "Calling the link from your server": parameters, the redirect=false response (200 accepted, 503 retry, ignored reasons with fixes), and the advertiser opt-in. Plus one troubleshooting entry.
  • Turn On S2S Clicks for a Partner (advertiser-facing):
    • The switch now also covers tracking links a partner's server calls (intro, "Before you start", the capabilities table).
    • The token sentence is scoped to the S2S click API. It also says tracking-link calls carry no token, and that this only affects the partner's own campaigns.
    • Propagation is "within 6 minutes": the gateway reloads opt-ins every 5 minutes, and the overseas edge adds up to 1 more.
    • "Turn it off" says tracking links go back to recording the caller's IP. Plus a troubleshooting entry.
  • Server-to-Server Clicks: a tip for partners already calling the tracking link from their server, and why the S2S API is still the better choice for a new integration.
  • Getting Started: the server-called link option in the setup steps, and the AppsFlyer template FAQ now covers af_ip / af_ua / redirect=false on tracking links.
  • The ip_adress typo alias is deliberately undocumented.

Testing

  • npm run check:routes -- origin/main (routes valid) and npm run check:agents (9 pass).
  • Previewed every changed page locally with mintlify dev. Sections, tables, tips and warnings render correctly.
  • Behaviour checked against the hazelnut#914 branch: unit tests plus a local e2e (14/14) through the gateway into ClickHouse.
  • Not verified: behaviour on production, because hazelnut#914 is not deployed yet.

🤖 Generated with Claude Code

RathodDarshil and others added 3 commits October 17, 2026 15:57
…er with ip/ua (LIN-3814)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…N-3814)

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…alled tracking links (LIN-3814)

- Turn On S2S Clicks: the switch now also covers tracking links a partner's
  server calls; token wording scoped to the S2S API; 6-minute propagation;
  turning it off; a troubleshooting entry.
- Server-to-Server Clicks: tip for partners already calling the tracking link.
- Getting Started: the server-called link option and the AppsFlyer af_ip/af_ua
  template answer.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant