Hello Team,
Thank you for your detailed explanation regarding the discrepancy between
the API response and the UI for device models in Google Ads.
I appreciate this clarification, as it helps me to better understand the
behavior of the API and UI.
To ensure we align our implementation with best practices and user
expectations, I would like to confirm/ask the following:
*1. Relevance of Device Lists: *Can you confirm if there is a reliable way
to filter or query the mobile_device_constant resource to obtain only the
currently relevant devices (e.g., those with recent traffic or actively
targeted in campaigns)?
*2. Mapping User-Friendly Names: *Is there a programmatic method or
resource available to map the API's technical identifiers to the
user-friendly names displayed in the UI? This would help improve the
usability of our reporting and targeting features.
*3. Campaign Context*: If the filtering in the UI is influenced by specific
campaign settings (e.g., geographic or demographic targeting), is there a
way to replicate similar filtering logic via the API to retrieve a
contextually relevant subset of devices?
We appreciate your continued support in addressing this query and look
forward to your guidance on the points above.
On Saturday, December 21, 2024 at 12:42:49 AM UTC+5:30 Google Ads API Forum
Advisor wrote:
> Amit:
>
> *Understanding the Discrepancy*
>
> 1.
>
> *Device Count:*
> -
>
> API shows 86 Alcatel devices with Android OS.
> -
>
> UI shows only 2 Alcatel devices.
> 2.
>
> *Device Names:*
> -
>
> API shows names like "4034e" and "5010G".
> -
>
> UI shows names like "PIXI 4 (4034E)" and "Pixi 4 5.0 (5010G)".
>
> *The Core Issue:*
>
> The fundamental issue is that the mobile_device_constant resource in the
> API provides a *comprehensive list of all known mobile devices* that
> Google Ads could potentially target. The Google Ads UI, on the other hand,
> likely filters this list down to devices that are *currently relevant and
> actively receiving traffic* for ad targeting in the specific account or
> campaign context the user is viewing.
>
> *Why the Discrepancy Exists:*
>
> -
>
> *API is a Master List:* The mobile_device_constant resource is
> essentially a database of all device models. It doesn't reflect live
> campaign performance or current targeting trends.
> -
>
> *UI is Contextual:* The UI likely uses dynamic filtering based on
> factors like:
> -
>
> *Recent Traffic:* Only showing devices that have generated
> impressions or clicks recently.
> -
>
> *Market Relevance:* Some devices might be outdated or not commonly
> used in the target location.
> -
>
> *Campaign Settings:* Specific campaign settings (e.g., geographic
> targeting) could further filter the list.
> -
>
> *UI is Simplified:* Google ads UI presents a simplified version of the
> master list to not overwhelm the user with irrelevant devices.
>
> *Device Name Differences:*
>
> The name differences are also likely due to the UI adding
> marketing/user-friendly names ("PIXI 4") for better readability, while the
> API might use the device's model identifiers ("4034e").
>
> mobile_device_constant resource is a *catalog of all possible mobile
> devices*, not a list of devices currently being targeted or receiving
> traffic in their account.
>
> The Google Ads UI dynamically filters the master device list based on
> several factors to show only the most relevant devices for a particular
> account/campaign.
>
> The API uses technical model identifiers, while the UI may use more
> user-friendly names for clarity. The name retrieved from the API should be
> treated as an identifier for targeting purposes.
> This message is in relation to case
> "ref:!00D1U01174p.!5004Q02vGp5n:ref" (ADR-00278830)
>
> Thanks,
>
> [image: Google Logo]
> Bob Hancock
> Google Ads API Team
>
>
> Feedback
> How was our support today?
> [image: rating1]
> <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=1&entry.295079254=5004Q00002vGp5n>
>
> [image: rating2]
> <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=2&entry.295079254=5004Q00002vGp5n>
>
> [image: rating3]
> <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/viewform?usp=pp_url&entry.141427034=3&entry.295079254=5004Q00002vGp5n>
>
> [image: rating4]
> <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/formResponse?usp=pp_url&entry.141427034=4&entry.295079254=5004Q00002vGp5n>
>
> [image: rating5]
> <https://docs.google.com/forms/d/e/1FAIpQLSeRhIg5VeThVmbcD0c5DTWTDjmpJuSktN8vFelEL7_KV_Orbg/formResponse?usp=pp_url&entry.141427034=5&entry.295079254=5004Q00002vGp5n>
>
>
>
>
>
>
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog:
https://googleadsdeveloper.blogspot.com/
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
You received this message because you are subscribed to the Google
Groups "AdWords API and Google Ads API Forum" group.
To post to this group, send email to adwords-api@googlegroups.com
To unsubscribe from this group, send email to
adwords-api+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
---
You received this message because you are subscribed to the Google Groups
"Google Ads API and AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to adwords-api+unsubscr...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/adwords-api/e3a8e0cf-7b46-4c6b-a94a-2cdb5057d4c8n%40googlegroups.com.
