Mobile App Attribution

Store redirect

GET /app?device=android&affiliate=AFF1024&campaign=FB_CY_01

device must be android or ios. The endpoint resolves the brand from the request host, records an app-click touch, and returns HTTP 301 with the configured store URL.

For Android, the URL contains an encoded Install Referrer with click_id, affiliate, and campaign values. For iOS, the configured Apple pt, ct, and mt=8 parameters are used.

First application launch

POST /app/activate
Content-Type: application/json

Android request:

{
  "installation_id": "4c0b68c8-3c90-46dc-a0dc-e092f879dd80",
  "install_referrer": "click_id=87b1d8d2-90aa-4e1e-b7c7-cc97f930b966&affiliate=AFF1024&campaign=FB_CY_01"
}

iOS request:

{
  "installation_id": "4c0b68c8-3c90-46dc-a0dc-e092f879dd80"
}

Matched response:

{"matched":true,"campaign":"FB_CY_01","affiliate":"AFF1024"}

An unmatched activation is not an API failure:

{"matched":false}

Android matching is deterministic when Install Referrer returns click_id. iOS uses a time-limited fingerprint/IP-hash fallback and is therefore probabilistic. A future MMP or deferred-deep-link integration can replace this fallback without changing customer registration.

Registration

After activation, the app passes the same installation_id to POST /customer/registration. The server resolves the bound touch and stores its campaign and affiliate snapshots in the new customer.