Documentation

User Acquisition

Campaign goals

Attribution

Partner integration

User Acquisition

Custom integration attribution links

Review the format and parameters for custom server-to-server integration attribution links
Read time 1 minuteLast updated 11 hours 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. 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 name

Requirement

Format

Description

Notes

game_id
RequiredStringYour Unity 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.
GAMER_ID
OptionalStringThe unique Unity 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.
ATTRIBUTED
OptionalInteger (
0
or 
1
)		A flag indicating whether this install is attributed to Unity 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 format 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.
  • 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.
When you save the attribution link, the dashboard checks for errors to validate that the URL is syntactically correct.