Send attribution links with a custom integration

To pass install 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 dashboard

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:

https://postback.unityads.unity3d.com/games/[GAME_ID]/install?advertisingTrackingId=[YOUR_MACRO_FOR_GOOGLE_AD_ID]&gamerId=[GAMER_ID]&attributed=[ATTRIBUTED]

Review the following postback parameters to ensure your Android postback request is formatted correctly:

Parameter nameRequirementFormatDescriptionNotes
GAME_IDRequiredStringYour Unity Ads Game ID.You can locate your Game ID at the top of the Campaigns page for your selected app in the User Acquisition dashboard.
GAMER_IDOptionalStringThe unique Unity Ads identifier mandatory for attributing users that have Limited Ad Tracking (LAT) on.

You can find the gamer_id parameter value from starts, views, or clicks sent for attribution.
The GAMER_ID parameter is required to successfully attribute installs.

For unattributed installs, the parameter is optional.
ATTRIBUTEDOptionalInteger (0 or 1)A flag indicating whether this install is attributed to Unity Ads and can be charged.The default value (attributed=1) indicates that the condition is true. If the condition is false (attributed=0), the install is unattributed and won't be charged.

URL formatting

To ensure your attribution works correctly, ensure you’ve formatted your links according to the following requirements:

  • Use HTTPS for the URL and any redirects.
  • Include the {ifa} dynamic custom token. Refer to the Dynamic custom tokens reference to review supported tokens.
  • UseHTTP 3XX redirect codes. Don't use HTML or JavaScript redirects.
  • Don't redirect URLs to the Apple App Store or the Google Play Store.

When you save the attribution link, the dashboard checks for errors to validate that the URL is syntactically correct.