Pixel & MMP Setup
Implement app, browser, and billing signals so ad platforms can optimize toward users who create business value—not people who only install.
| Signal | Tracks | Why it is needed |
|---|---|---|
| App SDK or MMP | Installs, attribution, and in-app actions | Connects app behavior to the campaign that acquired the user |
| Browser pixel | Landing-page and web-funnel activity | Tracks actions before the user enters the app |
| Billing integration | Confirmed subscription events | Captures trials, payments, renewals, and refunds when the app is closed |
Takeaway
Choose one primary MMP
| MMP | Best suited for | Notes |
|---|---|---|
| Branch | Web-to-app, referrals, and deep-linking journeys | Strong when links must open specific in-app content |
| Adjust | Larger teams across several networks and markets | Advanced reporting, automation, and fraud prevention |
| Tenjin | Early-stage teams needing affordable core attribution | Simpler setup without a large enterprise stack |
- Supports every advertising platform you plan to use.
- Supports both iOS and Android, including AdAttributionKit.
- Integrates with your billing provider and subscription lifecycle events.
- Supports deep links when the journey requires them.
- Provides raw-data export, cost-data import, and enough reporting support.
Use one primary MMP. Installing several creates competing attribution claims and duplicate event paths.
Install the MMP SDK
Add the SDK to iOS and Android and initialize it early in the first session. Use the same internal user ID across the app, MMP, billing provider, and product analytics whenever possible.
- Record first app open and receive the acquisition source.
- Preserve campaign, ad-set, and creative information.
- Distinguish new installs from re-engagement.
- Associate in-app events with the acquired user.
- Connect the anonymous install to the known user after signup.
- Pass supported conversion events back to advertising platforms.
Takeaway
Connect advertising platforms
Connect each account through the MMP’s official partner integration. A connection is not finished until the correct events are mapped and enabled as postbacks.
- Meta, TikTok, Google Ads, and Apple Ads.
- Any additional networks currently in use.
- Required IDs, access tokens, link IDs, datasets, and developer tokens.
- Conversion mapping, postback permissions, and cost-data permissions.
Map conversion events
| Internal event | Typical platform mapping |
|---|---|
| install | Install or first open |
| signup | Complete registration or sign up |
| onboarding_complete | Custom onboarding-complete event |
| paywall_view | View content or custom paywall-view event |
| trial_start | Start trial |
| purchase | Purchase or subscribe |
| trial_conversion | Subscription payment |
| renewal | Recurring subscription payment |
| refund | Refund or revenue adjustment |
- Never map signup, onboarding, or a button tap as a purchase.
- Do not record a zero-revenue trial as a paid purchase.
- Send refunds as negative adjustments, not positive revenue.
- Keep initial purchases and renewals distinguishable.
Connect subscription events
Trials, purchases, conversions, renewals, cancellations, expirations, and refunds should come from the billing provider or store—not only from the app.
- Pass the MMP attribution identifier to RevenueCat before the first purchase.
- Use the same customer ID across systems.
- Include product ID, price, and currency.
- Keep initial purchases, renewals, refunds, sandbox, and production distinct.
- Do not let placeholder sources such as unknown overwrite final attribution.
Add the browser pixel when needed
Install it across the full web journey when ads lead to a landing page, quiz, web onboarding, lead form, web paywall, checkout, or a page that later sends users to an app store.
- Preserve UTMs and platform click IDs.
- Preserve landing-page session and anonymous user IDs.
- Preserve campaign and creative parameters.
- Complete the browser-to-app handoff through the MMP and supported deep links.
If ads go directly to the App Store, a website pixel is not required for that journey.
Prevent duplicates and respect privacy
A purchase can be sent by the app SDK, MMP, RevenueCat, network SDK, and direct platform integration. Define one primary sending path for each conversion.
- Preserve transaction ID, timestamp, product ID, price, currency, customer ID, and environment.
- Do not send the same subscription revenue through multiple paths unless the receiver can deduplicate it.
- Respect App Tracking Transparency, AdAttributionKit, Google consent, regional privacy, and platform data-sharing rules.
- Pass consent status where required; never replace denied consent with another identifier.
Test the complete signal path
New test user: Ad or attribution link → install → signup → onboarding completion → paywall → trial or purchase.
- Install appears in the MMP with the correct source and campaign.
- Signup and onboarding completion each appear once.
- Paywall view fires only after the paywall renders.
- Trial or purchase is confirmed by the billing provider.
- Revenue and currency are correct and reach the intended platform event.
- No event is duplicated and sandbox revenue is excluded.
- iOS and Android are tested separately.
- Both consented and non-consented iOS journeys behave correctly.
Takeaway