Overview
Apptrove is a mobile measurement platform (MMP) that attributes installs and in-app events using tracking links and server-to-server postbacks.
Tracking Links
Macro-based click attribution and install tracking.
Postbacks
Install and in-app event callbacks via S2S.
Revenue
Revenue, ROI and currency-aware reporting.
Make sure you have access to your Apptrove dashboard and Affclix Mobile Tracking settings.
Attribution Flow
User Clicks Tracking Link
Apptrove captures the click and device identifiers; click_id travels in the link.
App Installation
Apptrove attributes the install to the original click.
Postback Triggered
Install or in-app event is sent to Affclix via S2S callback.
Conversion Logged
Affclix verifies the signature, normalizes, deduplicates and records the conversion.
Tracking Link
Apptrove tracking links carry attribution macros that are returned later through postbacks.
https://track.apptrove.com/{app}/{campaign}
?click_id={click_id}
&p={affiliate_id}
&sub_id={sub_aff1}
&gaid={gaid}
&idfa={idfa}
&campaign_name={campaign_name}
&campaign_id={campaign_id}Pass click_id on the link — it must be returned in every postback for attribution to succeed.
Postback Configuration
Apptrove fires install and event postbacks to the Affclix receiver. The integration is identified by its unique slug; authenticity is verified by the per-platform HMAC signature header.
POST https://track.your-domain.com/postback/mmp/{slug}
?tid={click_id}
&event={event_name}
&revenue={amount}
¤cy={currency}
&txid={transaction_id}Copy Postback URL
Open Mobile Tracking → Apptrove and copy the generated URL.
Configure Partner
Add the URL in Apptrove Partner Configuration and map macros (click_id → tid).
Enable Events
Enable install and in-app event postbacks.
Event & Revenue Tracking
Apptrove passes the event and revenue on each postback:
event=purchase
revenue=15.75
currency=USDInstall Events
Automatically reported after attribution.
Custom Events
Signup, purchase and custom in-app actions.
Revenue Tracking
revenue and currency for ROI reporting.
Fraud Prevention & Best Practices
- Verify HMAC signatures on every callback.
- Always pass click_id and return it as tid.
- Deduplicate conversions using click_id and event name.
- Include revenue and currency for purchase events.
- Use HTTPS endpoints only.