Use case
Mobile network traffic, app install campaigns, app-to-web traffic, or MMP handoff checks.
Mobile network examples
Use these starter examples when you need a readable AppLovin or mobile network landing URL before the account-specific tracker or MMP link is finalized.
Mobile network traffic, app install campaigns, app-to-web traffic, or MMP handoff checks.
Keep UTMs readable first, then preserve the approved tracker exactly when the MMP or network provides one.
Click the final link yourself and confirm the destination page, tracker, and reporting labels survive the click path.
Use this when the campaign is still being QA checked and the team needs a link that is easy to inspect.
Use this only when the downstream report is already built around IDs. Treat the token names as placeholders until the live account or MMP confirms the final format.
| Field | Starter value | Why it exists |
|---|---|---|
utm_source |
applovin |
Keeps the traffic source easy to group in GA4. |
utm_medium |
mobile_network |
Separates mobile network traffic from paid social or search. |
utm_campaign |
summer_app_push |
Human-readable campaign name for first-pass reporting. |
creative_id |
{{creative_id}} |
Optional advanced placeholder for creative-level analysis. |
placement_id |
{{placement_id}} |
Optional advanced placeholder for placement comparison. |
Readable first, tracker-safe second, verified before launch. That sequence prevents most expensive URL mistakes.