Product
How attribution works
Attribution connects an install, and later purchases, to the creator who caused it. That is influencer app tracking for a creator program. Production and Sandbox are separate environments, so live payouts use production traffic only.
Path 1: the tracking link
New links use a 7-day window. A first open after that window stays unmatched.
Android
Play Store destinations can carry a referrer token. The SDK sends that token on install for a deterministic match. Direct APK / ADB installs often have no referrer; use internal testing or a physical device that installed through Play.
iOS and other platforms
The click stores coarse device, locale, and network signals. First open is scored against recent unmatched clicks in the same environment. The SDK works without IDFA and without an ATT prompt. That score is best-effort: concurrent installs on similar devices or networks can miss or collide. When the link match misses, use Path 2 (applyCode()).
Path 2: the discount code
When click matching misses, applyCode() attributes the customer to the creator who owns that discount. Discount codes is the full guide.
What you will see
- Clicks on go.tapapplink.com (or the sandbox host)
- Matched installs in Attribution
- Code redemptions on the creator and discount views
- Revenue events once the webhook is connected