Apptrove is the youngest MMP in this series — built by the team behind Trackier and adopted mainly by performance-focused app advertisers in fast-growing mobile markets. The integration model is conventional and flat: query-parameter click and impression URLs, GET postbacks, HMAC verification. What is different is variability — Apptrove integrations are more often custom-configured per advertiser than the older MMPs, which makes explicit mapping confirmation the most important step in this guide. For the general tracker–MMP architecture, start with the mobile attribution guide.
Where Apptrove Fits
You will meet Apptrove on offers from advertisers who chose an MMP optimised for performance-marketing workflows over enterprise analytics — commonly gaming, utilities, and fintech apps in India, MENA, Southeast Asia, and LATAM. It supports the full standard surface: SDK attribution, click and impression endpoints, in-app event forwarding with revenue, and per-postback fraud flags. Nothing in the flow will surprise you if you have integrated AppsFlyer or Kochava; the discipline is in verifying the specifics rather than assuming them.
Step 1 — Build the Click and Impression URLs
Apptrove's endpoints take your affiliate context as plain query parameters:
// Click
https://track.apptrove.com/click
?cid={campaign_id}
&campaign_name={campaign_name}
&click_id={click_id} // your click ID — the round-trip key
&affiliate_id={affiliate_id}
&sub_aff_id={sub_aff1}
&sub_aff_id2={sub_aff2}
&source={source}
&country={country}
// Impression (view-through)
https://track.apptrove.com/impression
?cid={campaign_id}&click_id={click_id}One naming quirk to note immediately: on the click URL, cid is the campaign ID, while on the postbacks below, cid carries the click ID. Same three letters, different meaning per direction — the kind of detail that makes the confirmation step in this guide non-optional. As with Kochava, price impression-attributed conversions separately; view-through payouts without their own rules are a fraud magnet.
Step 2 — Configure the Postbacks
Register your tracker's endpoints for install and each payable event:
// Install
https://track.yourdomain.com/postback
?cid={click_id}&aff_id={affiliate_id}&sub1={sub_aff1}
&country={country}&device={device_type}
// In-app event
https://track.yourdomain.com/postback
?cid={click_id}&event={event}
&payout={revenue}¤cy={currency}Standard series rules apply: agree event identifiers in writing before launch, and enable event postbacks even on CPI-only deals so post-install activity can expose install farms.
Step 3 — The Payload Fields That Matter
Apptrove postbacks are flat, and the analytically useful fields mirror the mature MMPs: a full timestamp trail (click_time, install_time, event_time), the applied lookback window (click_lookback), device identity (gaid / idfa under their standard names — no renaming traps here), revenue with currency, and two governance fields. attribution_type distinguishes click, impression, and organic attributions — filter organic hard, and route impression attributions to their own payout class. is_fraud with fraud_reason is Apptrove's own verdict; enforce it as a hard block ahead of your tracker-side screening.
Step 4 — Verify, Filter, Deduplicate
Apptrove signs postbacks with HMAC-SHA256 over the raw body when a postback secret is configured — verify with a constant-time comparison and reject mismatches before parsing, exactly as with Singular and Branch. Affclix flags unsigned integrations in logs so they surface at audit time. Behind the signature: deduplicate on click ID + event against retries, quarantine unknown click IDs as diagnostics rather than discarding them, and run everything through your standard fraud layers.
Step 5 — The Mapping Confirmation Ritual
Because Apptrove setups vary more between advertisers than the older MMPs, run an explicit end-to-end confirmation before real traffic flows — fifteen minutes that prevents the classic week-one dispute:
- Fire a test click; confirm the click ID appears in Apptrove's click log unmodified
- Trigger a test install; confirm the postback returns your click ID in
cid - Fire each payable event once; confirm event names and revenue fields match your CPA rules
- Confirm the postback secret is set on both sides and a tampered body is rejected
- Confirm
attribution_typevalues for click, impression, and organic test cases
Troubleshooting
- Click IDs not returning — the
cidclick/campaign ambiguity struck; one side mapped campaign ID where the other expected click ID. Re-run the confirmation checklist. - Organic conversions converting —
attribution_typeunfiltered. Gate on it explicitly; do not assume only attributed traffic is forwarded. - Impression attributions paid at click rates — same fix as every MMP with view-through: separate conversion classes and payouts.
- Numbers diverge — reconcile against Apptrove's install reports API (Bearer-token authenticated, daily pulls) rather than dashboard aggregates.
Affclix's Apptrove integration generates the click, impression, and postback URLs with the mapping already consistent — including the cid disambiguation — verifies signatures, filters on attribution_type, honours fraud flags, and reconciles via the reports API. With this guide, the series covers all six MMPs Affclix integrates: AppsFlyer, Adjust, Branch, Kochava, Singular, and Apptrove.
