We constantly publish updates to our documentation, which may not yet be available in your language. For the most current information, use the English version.

for Partners

Dynamic network integration•3. Append advertising IDs

3. Append advertising identifiers

When your client generates a link for your network, your unique advertising identifier is already appended in the generated link URL. Adjust uses this ID for deterministic attribution, which increases accuracy and is the easiest and most secure way for us to attribute users.

Note:

Adjust can use probabilistic modeling to measure conversions, which uses certain variables that can change and expire. This may cause conversions to be under-reported. If your client would like to use probabilistic modeling for attribution, they must enable it in the attribution settings. Probabilistic modeling is turned OFF by default.

Examples

We accept most advertising IDs and hashes. Advertising IDs are passed using Adjust parameters.

Here's an example of a link URL with an advertising identifier added, with a link token and campaign structure parameters already attached:

https://app.adjust.com/abc123?campaign={publisher_id}&adgroup={sub_publisher_id}&creative={creative_id}&gps_adid=(your_identifier_macro)

Here's an example of a link URL for an iOS app with the advertising parameter for IDFA, a link token and campaign structure parameters appended:

https://app.adjust.com/abc123?campaign={publisher_id}&adgroup={sub_publisher_id}&creative={creative_id}&idfa=(your_identifier_macro)

Accepted identifiers

Advertising IDs

Parameter	ID Type	Format
`fire_adid`	Raw Amazon Fire advertising ID	Lowercase, with hyphens
`gps_adid`	Raw Google advertising ID	Lowercase, with hyphens
`gps_adid_upper_md5`	Hashed Google advertising ID	Uppercase, with hyphens, MD5
`gps_adid_lower_md5`	Hashed Google advertising ID	Lowercase, with hyphens, MD5
`gps_adid_upper_sha1`	Hashed Google advertising ID	Uppercase, with hyphens, SHA1
`gps_adid_lower_sha1`	Hashed Google advertising ID	Lowercase, with hyphens, SHA1
`idfa`	Raw IDFA	Uppercase, with hyphens
`idfa_lower_md5`	Hashed IDFA	Lowercase, with hyphens, MD5 hash
`idfa_lower_sha1`	Hashed IDFA	Lowercase, with hyphens, SHA1 hash
`idfa_upper_md5`	Hashed IDFA	Uppercase, with hyphens, MD5 hash
`idfa_upper_sha1`	Hashed IDFA	Uppercase, with hyphens, SHA1 hash
`idfa_short`	Raw IDFA	Without hyphens
`oaid`*	Raw OAID	Lowercase, with hyphens
`oaid_lower_md5`*	Hashed OAID	Lowercase, with hyphens, MD5 hash
`win_adid`	Raw Windows advertising ID	Without hyphens

Device IDs

Important:

Adjust only uses the Android ID for attribution when the gps_adid is unavailable.
The IDFV can be used when running cross-promotional campaigns among your own apps, for example via email, push notification, or deep links. The IDFV provides more accurate attribution than only relying on probabilistic modeling.

Parameter	ID Type	Format
`android_id`*	Raw Android ID	Lowercase, without hyphens
`android_id_lower_md5`*	Hashed Android ID	Lowercase, MD5
`android_id_lower_sha1`*	Hashed Android ID	Lowercase, SHA1
`android_id_upper_md5`*	Hashed Android ID	Uppercase, MD5
`android_id_upper_sha1`*	Hashed Android ID	Uppercase, SHA1
`idfv`**	Raw IDFV	Uppercase, with hyphens
`imei`	Raw IMEI	Without hyphens
`imei_lower_md5`	Hashed IMEI	Lowercase, without hyphens
`meid`	Raw MEID	Uppercase, without hyphens
`win_naid`	Raw Windows network adapter ID	Lowercase, with hyphens
`win_hwid`	Raw Windows Store hardware ID	Without hyphens