Mobile app monetization must use the GMA SDK to pass device identifiers.
Device identifiers for mobile phones, video game consoles, and over-the-top (OTT) streaming devices, can be used to enhance ad serving by allowing developers and marketers to target based on user activities. In non-browser environments where there are no cookies, they also allow buyers to apply critical features that facilitate additional demand, such as frequency capping. This type of user targeting is similar to how cookies can be used with web browsers.
Device identifiers are provided by the device operating system and can be reset by the user. The value of the identifiers are a string and contain 36 characters (32 alphanumeric characters and four hyphens). The characters are grouped in the form 8-4-4-4-12. For example,
You can use the device ID macro to propagate the identifier to a third-party ad network.
Device identifier availability per device type
See the supported device types.
Chromecast does not have its own resettable device identifier. The casting device determines the device ID, its
idtype, and sends it to the Chromecast. For example, if the casting device is an Roku, the Roku device sends its
rida to Chromecast.
To pass a resettable device identifier when you are not using a Google Ads SDK, the following parameters must be appended to the ad request URL (all 3 must be present):
Session identifier for frequency capping
Per the IAB's Guidelines for Identifier for Advertising (IFA) on OTT platforms, a session ID is a temporary, privacy-safe advertising identifier that can be used for frequency capping, competitive ad exclusions, and sequential ad rotation within a single user session. Unlike other advertising identifiers that persist across multiple sessions, such as PPID, device IDs (as described above), or web cookies, the max duration that a session identifier may persist in Ad Manager is 6 hours.
Session identifiers are supported on CTV environments and in-stream video inventory from mobile app devices. There are several instances where they may be valuable, such as:
- Instances where a user has disabled personalization on their device (where
- If you're monetizing inventory on a device that doesn't have a privacy-safe IAB-compliant IFA value
- When you need an alternative to an IFA or PPID value to limit access to your first-party audience data
This identifier may be passed alongside other identifiers that are supported in Google Ad Manager, such as cookies, though the identifier may not be used for ad targeting. The value of a session ID must not contain any personal information, third-party identifiers or device IDs. This identifier is used for enabling frequency capping on both programmatic-eligible requests and reservations.
Session IDs are automatically included on ad requests from IMA SDK and Programmatic Access Libraries, but publishers can opt out by setting
sid=0. Learn more about the
Publishers are required to proactively inform users about this use case and provide opt-out controls where required by state or local law. Refer to the Ad Manager and Ad Exchange program policies for more information.