To provide a comprehensive and consolidated view of your Audiences and make audience management and optimization simpler, you’ll find the following improvements in Google Ads:
- New audience reporting: Go to Audiences within the Campaigns menu
for detailed reporting about audience demographics, segments, and exclusions. You can also easily manage your audiences from this report page. Learn more About Audience reporting.
- New terms: We’re using new terms on your audience report and throughout Google Ads. For example, “audience types” (these include custom, in-market, and affinity) are now referred to as audience segments and “remarketing” is now referred to as “your data”. Learn more about the Updates to Audience terms and phrases.
Data segments that are built using Mobile Device IDs (MDIDs) help you re-engage with customers who are active within your app. You can re-engage with them across Search, Shopping, and YouTube and can create these data segments using one of the following methods:
- Upload the MDID information that you collected from your customers with their consent and using the uploaded list to reach and re-engage with them.
- Collect the MDID by using Google’s app software development kit (SDK) and analytics tool Firebase or a third-party app analytics tool that fires events based on the customer’s actions within your app. You can then set up rules to create data segments based on the specific events of interest to you.
Note: By targeting or excluding a segment of Mobile Device IDs, you can choose how you re-engage with customers previously active within your app on Search, Shopping, and YouTube.
On this page
- Benefits
- Use data segments that contain Mobile Device IDs
- Cross-surface campaigns best practices
- How it works
Benefits
Here are some of the benefits of using data segments that contain Mobile Device IDs:
- Advantage of using data segments that contain MDIDs over Customer Match:
- Increase Google Ads campaigns’ coverage to users who engage directly with your app.
- Advantages over data segments for Search ads:
- You can create data segments based on specific actions carried out by the users within your app when you use either Firebase or a third-party app analytics tool.
- You can reach users who don't visit your website, but only engage with your mobile app.
- Upload the MDID list of your customers to reach them in Google Ads.
Use data segments that contain Mobile Device IDs
If you want to target data segments that contain Mobile Device IDs, follow these 2 steps:
- Collect the MDIDs for the list that you can upload to Google Ads.
- Create the User List for list collection to be used for Google Ads campaigns based on the collected MDIDs.
Privacy limitations
Privacy and policy restrictions, turned-off ads personalization, or under-18 policies, prohibit personalized ads for certain user groups. This can lead to Google not being able to personalize ads served to certain users even if they belong to the targeted or excluded audience segment. Learn more About privacy and personalized ads.
In accordance with Google EU User Consent Policy, You must obtain end users’ legally valid consent where legally required. Refer to Help with the EU user consent policy and the following articles to learn about the ways to to pass user consent to Google:
Cross-surface campaigns best practices
For multi-channel, cross-surface campaigns like Performance Max, Demand Gen, or App Campaigns, user recognition depends on the surface context, such as whether a user is currently signed in, if the ad is rendering in browser or mobile app and other factors.
To maximize your inventory coverage and targeting effectiveness, it’s best practice to apply as many audience list types as possible simultaneously such as:
- Customer match with complete customer data (such as hashed emails and phone numbers) alongside mobile device IDs.
- Dynamic audience segments based on web and app events.
Using multiple list types with different user identifiers together will help ensure a more comprehensive audience coverage across all networks and surfaces.
How it works
Collecting the Mobile Device IDs list
Let’s say that you're the advertiser and the app owner for the website https://www.example.com/someresource.
- URL Scheme =
https - Path =
www.example.com/someresource
You can use the Demo project as an example.
- Android -
https://www.example.com/someresource?gmpaid=1:300830567303:android:9b9ba2ce17104d0c&adid={IDFA}&anid=applovin&aclid={DID}&cs=AppLovin&cm={AD_TYPE}&cn={CAMPAIGN_NAME} - iOS -
https://www.example.com/someresource?gmpaid=1:300830567303:ios:09b1ab1d3ca29bda&idfa={IDFA}&anid=applovin&aclid={DID}&cs=AppLovin&cm={AD_TYPE}&cn={CAMPAIGN_NAME}
When a user clicks the link https://www.example.com/someresource from within the app, the analytics partner populates values for {IDFA}, {DID}, {AD_TYPE}, and {CAMPAIGN_NAME}.
Here's the deep link format:
https://www.example.com/someresource?gmpaid=1:300830567303:android:9b9ba2ce17104d0c&adid=testAAID&anid=applovin&aclid=testClickID&cs=AppLovin&cm=testAdType&cn=testCampaign
You, the app owner can now examine your web logs and check that device ID “testAAID” completed a specific action in your app. You can add this device ID to a “Device ID upload list” so that you can reach and re-engage this user.
You can export the Device ID using Big Query to escalate the process. Learn more about big query export schema.
Upload Device ID lists via Google Ads
- Go to Audience manager within the Tools icon
.
- Select the Audiences tab at the top of the page.
- Select the plus button
to create a new audience list.
- Give your audience list a name.
- Under “List members,” select the drop-down arrow and select Upload Mobile Device IDs.
- Select the mobile app platform and browse for your specific app name. You can select only one app per list upload that matches with the type of IDs being uploaded.
- Note: A single list upload can’t include both advertising IDs (Apple IDFA/Android AdID).
- Create your Mobile Device ID file using a typical advertising ID, either an Apple ADFA or Android AdID, but not both within a single file. You can use this template or upload a plain text (unhashed)
.CSVfile with a single column labeled "Mobile Device ID". Mobile Device IDs can't be combined with any other type of customer data (email addresses, phone numbers, zip codes, and more). - Select Choose File and upload your list of User IDs according to the formatting guidelines. After you’ve selected your data file, select the checkbox to indicate you agree with Google's Customer Match policies.
- Select the circle to customize the "Membership duration" and "Description".
- Select Upload and Save List. You’ll find this message after you save it: “Your customer list has been successfully saved.” If there are any formatting errors in your file, you'll receive a notification.
- After a list is saved, it'll show an “In progress” status until it has finished uploading, which can take up to 24 hours. You’ll find a list status change in the Google Ads UI when the file has been uploaded, matched successfully, and is eligible to serve (has met the minimum size). If you encounter “In progress” for more than 24 hours or if you encounter “error with the last upload,” it means that the system has timed out. You need to ask your client to re-upload the list to fix the issue.
For technical questions regarding the Google Ads API, Data Manager API, or SDK including specific usage queries or error codes, follow the troubleshooting steps on the technical support page of Data Manager API or Google Ads API. For issues with conversion tracking, offline uploads, or data discrepancies, refer to the Conversion management guide and Debug common errors in the developer documentation. Before contacting support, verify your conversion_action_ids, check statuses in the User interface, and ensure you've accepted all data terms.
If you need further help, provide complete API logs (including request, response headers, and IDs) along with uncropped screenshots of the Google Ads interface.
If you have questions concerning Data Manager API or Google Ads API that relate to the Google Ads UI specifically, select “Contact us” at the bottom of the page.
Upload Device ID lists via the Google Ads API
- The mobile ID field is part of UserIdentifier type in
OfflineUserDataJobServiceto allow listed users to upload user data based on AAIDs (Android Advertising IDs) and IDFAs (Identifier For Advertisers). - The
UserListmust have the upload_key_type set toMOBILE_ADVERTISING_IDwhen uploading mobile IDs.
Learn more about audience targeting using the API.
Both the Google Ads UI and the Google Ads API also support adding customers to a current segment, removing specific customers, and replacing a segment of customers with a new segment.
Collect and create user lists
List collection can be done in multiple ways, depending on your interactions with your users.
- By scanning customer devices during store visits or collecting information offline in some other way, while ensuring you adhere to Google’s first party data policy. To create a segment based off of this collection, you could upload the collected MDIDs through the Google Ads interface or the API.
- By using Firebase or another third-party analytics tool to collect App Events based on a user’s actions within the app. To create a segment based off of this collection, you can create rules on App Events to create audience segments based on rules about events of interest.
When list collection and segment creation are complete, an audience segment of users becomes available to be utilized in Google Ads.