What It Is
If your apps already report through AppsFlyer, Adjust, Branch, Kochava, Singular or Apptrove, keep using those integrations — see the MMP guides in this section. Affclix Mobile Attribution is for app owners who want AffClix itself to be the measurement partner.
Mobile Attribution is switched on for each account individually. If you don't see Mobile Attribution → Mobile Apps in your menu, contact support to have it enabled. Team members also need the MMP integration permission.
Setting Up an App
Register the app
Open Mobile Attribution → Mobile Apps and add the app with its platform (Android, iOS or both), bundle ID, store URL, currency and timezone. Reports count days in the app's timezone.
Install the SDK
On the SDK & Links tab, copy the app key and SDK signing secret, then follow the code for Android (Kotlin), iOS (Swift), or React Native, Flutter and Unity. Installs and sessions are tracked automatically. Keep the signing secret out of source control and inject it at build time.
Log in-app events
Define events such as sign-up or purchase under Settings → Events, then log them from the app with their event token.
Follow the setup checklist
The checklist on SDK & Links ticks off each step as data arrives: SDK sending data, first install, first in-app event, test device registered, a campaign pointing at the app, and the first attributed install.
Attribution Links
To credit installs to affiliates, create an app-install campaign and set its destination URL to the app's attribution link, shown on the SDK & Links tab. It looks like this:
https://<tracking-domain>/m/c?ak=<app_key>&click_id={click_id}&c={campaign_id}&a={affiliate_id}&gaid={gaid}&idfa={idfa}&redirect=<store_url>Always copy the link from the console — it already contains your app key and store URL. Affiliates keep using their normal AffClix tracking links; the click passes through to the store and the install is matched back to it.
Under More link types you will also find an impression (view-through) URL and branded deep links that open a specific screen.
Attribution Windows
| Setting (app Settings tab) | Meaning |
|---|---|
| Click lookback window | How many days (1–90) after a click an install can still be credited to it. |
| Impression lookback window | How many hours (1–72) after an ad view an install can be credited to it when there was no click. |
| Re-attribution window | Days (up to 730). A reinstall inside it keeps the first install's attribution; after it, the reinstall is attributed again as a new install. |
| Re-engagement window | Days (up to 90) after a retargeting (deep-link) click during which in-app events are credited to it. |
| Fraud protection | Blocks high-risk clicks and conversions from proxy IPs and suspicious devices. |
View-Through Attribution
To pay affiliates for conversions from ads that were seen but not clicked, open the campaign's Security tab and turn on Credit Ad Views in the View-Through Attribution card. Then set Count Views For between 1 and 168 hours.
- A conversion within that time of an impression, with no click from the same person, is credited to the affiliate who showed the ad.
- 24 hours is the industry standard; 7 days is the maximum.
- A click always wins over a view.
The App Console
| Tab | What you do there |
|---|---|
| Overview | Installs, events, revenue and cost KPIs, with a daily trend. |
| Reports | Performance report grouped by date, campaign, affiliate, attribution method, platform or ad network; Cohort LTV by install date; raw data; SKAdNetwork postbacks. |
| SDK & Links | Setup checklist, credentials, SDK code, attribution links and server-to-server events. |
| Test Devices | Register your phone by its advertising ID to repeat installs and watch its events live, without affecting reports. |
| Partners & Export | Ad network connections, partner postbacks with a delivery log, raw data export and a signed pull API. |
| Audiences | Build user segments from installs and events, download them as a CSV of advertising IDs, or sync them to a Meta Custom Audience daily. |
| Costs | Combine affiliate payouts, ad-platform spend from Report Sync and costs you enter or import by CSV, for eCPI and ROAS. |
| Settings | App details, attribution windows, deep links, uninstall tracking, purchase validation, events and SKAdNetwork conversion values. |
Only users with a real advertising ID who have not refused ad-data sharing can be added to an audience. Meta sync uses the token of a Meta connection you have already set up.
Ad Networks & Partner Postbacks
- Ad network connections — send installs and in-app events to Meta (App Events API), TikTok (Events API) or Snapchat (Conversions API) so their campaigns can optimise. Add the network app ID, the events to send and an access token, which is stored encrypted.
- Partner postbacks — call any partner's URL template with macros when chosen events happen. Recent deliveries show each call and its response.
- Pull API — fetch installs, events, revenue or uninstalls with an export token. Each request is signed: sig is the hex HMAC-SHA256 of the query string (without sig) under the token, and ts must be within 5 minutes.
Deep Links, Uninstalls & Purchases
| Feature | What to add in Settings |
|---|---|
| Deep links | Android signing-certificate SHA-256 fingerprints (Play Console → Setup → App signing) and, for iOS, your Apple Team ID and bundle identifier. They are published in assetlinks.json and apple-app-site-association on your domain. |
| Uninstall tracking | Turn it on and add a Firebase service-account JSON (Android) and an APNs .p8 key with its Key ID (iOS). |
| Purchase validation | A Google Play service-account JSON and an App Store In-App Purchase .p8 key with its Key ID and issuer ID, so revenue events are checked with the store. |
| SKAdNetwork conversion values | List your events in the order users reach them, and the revenue steps since install. The iOS SDK sets conversion values automatically from this schema. |
Credentials are stored encrypted. Leave a secret field blank when editing to keep the saved value.