Send attribution links with a custom integration
Send attribution links to Unity Ads from your server to track user interactions and support custom install attribution without an MMP.
Read time 2 minutesLast updated 4 days ago
To pass engagement and attribution data to Unity using a custom server-to-server integration, use server requests to generate attribution tracking links. Refer to this article for GET requests you can use to send attribution links to Unity.
Prerequisites
To send install data to Unity, you must add at least one app to the Unity Ads User Acquisition dashboardSend links with postback requests
Use the following HTTP GET requests to send install postbacks to Unity. Refer to the Custom integration postback request reference table to ensure you include the required parameters.iOS
Use the following postback request URL to send iOS postbacks:https://postback.unityads.unity3d.com/games/[game_id]/install?advertisingTrackingId=[YOUR_MACRO_FOR_IDFA]&gamerId=[unity_gamer_id]&attributed=[attributed]
Android
Use the following postback request URL to send Android postbacks:Review the following postback parameters to ensure your Android postback request is formatted correctly:https://postback.unityads.unity3d.com/games/[game_id]/install?advertisingTrackingId=[YOUR_MACRO_FOR_GOOGLE_AD_ID]&gamerId=[GAMER_ID]&attributed=[ATTRIBUTED]
Parameter name | Requirement | Format | Description | Notes |
|---|---|---|---|---|
| Required | String | Your Unity Ads advertiser Game ID. | Ensure that you retrieve your advertiser Game ID from the User Acquisition dashboard. Don't use the publisher Game ID used in SDK integration from the Monetization dashboard. |
| Optional | String | The unique Unity Ads identifier mandatory for attributing users that have Limited Ad Tracking (LAT) on. You can find the | The |
| Optional | Integer ( | A flag indicating whether this install is attributed to Unity Ads and can be charged. | The default value ( |
URL formatting
To ensure your attribution works correctly, ensure you format your links according to the following requirements:- Use HTTPS for the URL and any redirects.
- Include the dynamic custom token. Refer to the Dynamic custom tokens reference to review supported tokens.
{ifa} - Use HTTP 3XX redirect codes. Don't use HTML or JavaScript redirects.
- Don't redirect URLs to the Apple App Store or the Google Play Store.