Tag Archives: CampaignCriterion

Connected TV Device Targeting, Reporting, & Management

Starting on Jan 8, 2019 you will be able to target and generate reports for a new device category via the AdWords API - connected TV. The connected TV platform, (or “TV screens,” as it’s referred to in the new Google Ads experience), is a new Platform type similar to desktop, tablet, and mobile. It targets devices such as smart TVs, gaming consoles and standalone connected devices including Chromecast, Roku, and AppleTV.

Since connected TV shares the same functionality as the three existing platforms, you can target or exclude it using bid modifiers for Display/Video ad campaigns; the new criterion will have a platformName of “ConnectedTv” and an ID of 30004. You can also isolate it in reports using a Device segment named CONNECTED_TV. Note that even though bidding will only be supported for Display and Video ads, some residual traffic may appear in other kinds of reports so you should still pull the new segment for non Display/Video ad reports.

The new connected TV device segment will be available anywhere Device-level or Device-segmented reporting is available. Currently any reporting data related to this platform is consolidated under the Desktop platform.

For more background on device targeting see the Help Center.

If you have questions, please reach out to us on the AdWords API forum.
Ben Karl, AdWords API Team

Check the Forward Compatibility Map before modifying LocationGroups in CampaignCriterion (v201409, v201502)

Do you use LocationGroups in CampaignCriterion? If so, read on to learn about a new key in the Forward Compatibility Map to identify whether a Location Group is compatible with the AdWords user interface or the API.

Through the Campaign Settings tab of the user interface and the AdWords API CampaignCriterionService, you can create a LocationGroups campaign criteria to target locations within a specific radius around all of your campaign's location extensions.


The user interface also allows you to further restrict the LocationGroups criterion to location extensions within geographical targets or Cities-DMA regions. However, the AdWords API does not currently support modifying these additional settings.

To indicate in the AdWords API that someone created a configuration of the latter form through the user interface, the CampaignCriterion.forwardCompatibilityMap has a new key called LocationGroups.locationId.

Key
Read-Only
Value Description
IMPORTANT
Service
CampaignCriterionService
Entity
CampaignCriterion
Key Name
LocationGroups.locationId
Yes
The Location criterion ID chosen for the LocationGroups criterion from Geographical Targeting or Cities-DMA Regions. For example, an ID of 2752 indicates targeting around location extensions within Sweden.
If this key appears in CampaignCriterion .forwardCompatibilityMap, then re-adding the LocationGroups after removal or using a copy of the LocationGroups may result in a loss of configuration information.

We’re working to support the geographical targets and Cities-DMA regions option in future API versions.

Be on the lookout for an upcoming addition to the Forward Compatibility Map regarding which feed ID will be used for proximity targeting.

Questions? Visit us on the AdWords API Forum or our Google+ page.

Nadine Sundquist, AdWords API Team