Overview
Singular is a mobile measurement platform (MMP) that attributes installs and in-app events using sng.link tracking links and server-to-server postbacks.
Singular Links
Macro-based click attribution via sng.link.
Postbacks
Install and in-app event callbacks via S2S.
Revenue
Revenue, ROI and currency-aware reporting.
Make sure you have access to your Singular Partner Configuration and Affclix Mobile Tracking settings.
Attribution Flow
User Clicks Singular Link
Singular captures the click and device identifiers; click_id travels in cl.
App Installation
Singular 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 (Singular Link)
Singular links use the sng.link domain and carry network macros for attribution.
https://subdomain.sng.link/abc/xyz
?cl={click_id}
&psid={affiliate_id}
&pssid={sub_aff1}
&idfa={idfa}
&aifa={gaid}
&pcn={campaign_name}
&pcid={campaign_id} Pass click_id in cl — it must be returned in every postback for attribution to succeed.
Postback Configuration
Singular fires install, revenue 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={evt}
&revenue={rev}
¤cy={currency}
&gaid={aifa} Copy Postback URL
Open Mobile Tracking → Singular and copy the generated URL.
Configure Partner
Add the URL in Singular Partner Configuration and map cl → tid, evt → event, rev → revenue.
Enable Events
Enable install, revenue and in-app event postbacks.
Event & Revenue Tracking
Singular passes the event and revenue on each postback:
evt=purchase
rev=15.75
currency=USD Install Events
Automatically reported after attribution.
Custom Events
Signup, purchase and custom in-app actions.
Revenue Tracking
rev and currency for ROI reporting.
Fraud Prevention & Best Practices
- Verify HMAC signatures on every callback.
- Always pass click_id in cl and return it as tid.
- Deduplicate conversions using click_id and event name.
- Include revenue and currency for purchase events.
- Use HTTPS endpoints only.