Build first-party segments based on mobile advertising IDs

Only available in Google Ad Manager 360

Audience Solutions is a Google Ad Manager 360 feature which might not be turned on for your network.

This article has been updated in alignment with upcoming changes to Audience Solutions.

To adhere to the EU user consent policy and continue creating audience segments for users in the European Economic Area (EEA), and in some cases users globally, publishers and partners must make updates to pass the required consent signals to Ad Manager by March 2024.

You can use audience pixels in apps to build first-party segments. However, you need to pass additional parameters to pull in the mobile advertising IDs (AdID or IDFA):

• dc_rdid to pass raw IDFA or AdID.

• dc_lat to pass Limit Ad Tracking signal from a device.

  • 1: Platform indicates that Limit Ad Tracking is enabled
  • 0: Platform indicates that Limit Ad Tracking is disabled

• Make sure to use HTTPS to send the request, to avoid exposing the mobile advertising IDs.
• The ad unit DFPAudiencePixel must be active for audience membership to be recorded.
• To update a segment with a PPID and another ID for the same user, invoke the Pixel tag with PPID and invoke it a second time with the alternate ID.
• When generating an ad tag in Ad Manager (under Inventory, then Audience, then open the audience segment, then click Generate tag), select Insert Mobile ID.

  You can also add a Mobile ID tag for a new creative on the creative's settings page (under Delivery, then Creatives, then Settings, then Insert audience segment).

  Note: The "Insert Mobile ID" checkbox is currently in beta and may not be enabled for your network. Watch the release notes for when this feature becomes generally available.

Here's an example tag to use for a mobile advertising ID:

Example

https://pubads.g.doubleclick.net/activity;dc_iu=/{ad-manager-network_code}/DFPAudiencePixel;ord=%%CACHEBUSTER%%;dc_seg={segment_ID};dc_rdid={your_resettable_advertising_ID};dc_lat={0,1}?gdpr=0,1&gdpr_consent=TC_string&tfua=0,1&tfcd=0,1