You can set Location targets at both the campaign and ad group levels. Note that if you don’t set a location target for the campaign or ad group, you will be targeting the global marketplace.
You can only create or delete these targets, and only change the bid modifier.
If you upload a bulk file without any location targeting attached to the campaign or ad group, then the corresponding campaign or ad group will be targeting world-wide.
The following fields are available for creating and managing a location target:
|Location ID||The Location ID of the location, which is optional when specifying the WOEID value. Gemini uses WOEID codes in order to determine locations. Location targeting is supported for country, city, state, DMA levels. Note that you cannot set a zip code as a Location ID. The Location ID is reserved ONLY for direct WOEID targeting. The Location field is reserved to supply a geo location (i.e. Sunnyvale, CA or United States or zipcode.) If you enter a zip code in the Location field, it will search WOEID matching that zipcode. If there is a match, that WOEID becomes the location targeting. This works the same for city, state, etc. To target a location (whether it’s a city, country, zipcode, etc), it becomes a WOEID that gets targeted. Note that if the Location ID is missing, the bulk row will fail with: Missing location WOEID or unable to resolve from location and location targeting will NOT get created.||long||optional||required|
|Location||The name of the geographic location associated with the Location ID.||string||read-only||read-only|
|Campaign ID||The ID of the parent campaign.||long||Required if location target is set at the campaign level.||Required if location target is set at the campaign level.|
|Ad Group ID||The ID of the parent ad group.||long||Required if location target is set at the ad group level.||Required if location target is set at the ad group level.|
|Bid Modifier||The bid modifier enables you to increase or decrease your search campaign bid for any valid location ID.The bid modifier range for location is: -90 to 900||string||optional||optional|
|Match Type||Optional for creates, read-only for updates. If the value is
Create Location Targeting¶
The following example contains the fields required to create a location targeting object that targets California at the campaign level. All other fields in this spreadsheet are blank and are not shown:
|Action||Object Type||Location ID||Location||Campaign ID|
|Add||Location Target||2347563||(not required)||123|
Create Negative Location Targeting¶
You can exclude locations from your campaigns or ad groups by setting Match Type = Negative. The following example contains the fields required for creating a location targeting object that excludes Sacramento. All other fields in this spreadsheet are blank and are not shown:
|Action||Object Type||Location ID||Location||Campaign ID||Match Type|
|Add||Location Target||2486340||(not required)||123||Negative|
Delete Location Targeting¶
When deleting a Location target, the required fields are Action, Object Type, Location Id for the Location and the Parent Campaign Id or Ad Group Id. To delete a location target, you must explicitly delete the location target. Updating status won’t have an effect (i.e. user cannot set to status for this object to paused). Other fields in the spreadsheet are blank and are not shown:
|Action||Object Type||Campaign ID||Location ID|
Advanced Location Targeting¶
Advanced Location Targeting can be set on both the Campaign and Ad Group level, but not the Location Target. It applies to all location targets you’ve set in that campaign or ad group. Ad group level setting trumps campaign level.
This field has the following values and format:
Positive [Default or Physical or Interest]:Negative [Default or Physical]
Anything outside of that format returns an error. Examples would be:
Positive[Physical]:Negative[Physical] or Positive[Interest]:Negative[Default]
If Positive or Negative are not provided, Gemini will set them to
Default, so setting
Positive[Physical] alone will mean that you’re implicitly setting negative to default.
So on download, you will get:
You always get both in bulk export.