Conversion Tracking
Who is this for: Advertisers who need to choose the right method for implementing MomentScience conversion tracking.
Outcome: Compare the tracking methods, pick the one that fits your setup, and open the matching integration guide.
Overview
MomentScience tracks conversions from offers by matching each conversion to the click that started it. Every method below works the same way at its core. MomentScience sends traffic to your landing page with a click ID. You capture that ID, and you report back when the user converts.
The methods differ in where the tracking runs: in the browser, in Google Tag Manager, or on your server.
Choose your integration method
Method | Best for | What you do | You need |
|---|---|---|---|
๏ปฟOmniSDK๏ปฟ | Teams that can edit their site code | Add the OmniSDK script to your landing and conversion pages, capture click IDs, and fire conversion events with JavaScript | Your account ID (from your account manager), landing page URLs, and conversion page URLs |
Teams that manage tracking in Google Tag Manager | Create the account ID variable and OmniSDK tags in GTM, then set up data layer variables for click and conversion events | Your account ID, landing page URLs, and conversion page URLs | |
Teams that need tracking without client-side code, for example when browser tracking is restricted | Store the adpx_click_id from incoming traffic with the user session, then send a postback from your server when a conversion happens | The ability to capture URL parameters and store click IDs on your server |
How to choose
- You manage tags in Google Tag Manager: use OmniSDK + Google Tag Manager.
- You can add a script to your pages: use OmniSDK.
- You track conversions on a backend, or browser tracking is unreliable: use S2S Postback.
If you run into issues during integration, contact us at [email protected].