Use these fields to create and manage ad groups.
The following fields are available for creating and managing ad groups:
|Campaign ID||The ID of the campaign associated with the ad group.||long||required||optional (read-only)|
|Ad Group ID||The ID of the ad group.||long||N/A||optional|
|Ad Group||The namer of the ad group.||string||required||optional|
|Start Date||The start date string value of the ad group (in MM/DD/YYYY format) in the time zone of the account. The time will automatically get set to 00:00:00:000.||string||required||optional|
|End Date||The end date string value of the ad group (in MM/DD/YYYY format) in the time zone of the account. The time will automatically get set to 23:59:59:000. If blank, this will get set to .||string||Required only if the ad group is under a campaign with a lifetime budget type.||optional|
|Ad Group Status||
The status of the ad group. Valid values are:
Ad groups are defaulted to Active if no status is provided upon creation.
|Search CPC||The bid amount in the currency of your account. The minimum accepted CPC bid is $0.05.||decimal||Required if the campaign runs on mobile search.||optional|
|Stream CPC||The bid amount in the currency of your account. The minimum accepted CPC bid is $0.05.||decimal||Required if the campaign runs on native.||optional|
|CPM||The bid amount in the currency of your account. The minimum accepted CPM bid is $0.25.||decimal||Required if the campaign runs on native and uses the PromoteBrand objective||optional|
|CPV||The Cost per Video View (CPV) Bid.||decimal||Required for Video campaigns with the campaign objective of PromoteBrand or InstallApp.||optional|
Note that this field is deprecated in favor Campaign bidding strategy. Refer to Campaign fields for more information. Applies only to native campaigns with either VISIT_WEB or INSTALL_APP objectives. Available values:
|ECPA Goal||The value you place on the conversion. Required when the Bidding Strategy is OPT_CONVERSION. The minimum is $1. Note that decreasing your ecpaGoal will typically lower the delivery of your campaign.||numeric||optional||optional|
|DPA Audience Strategy||The audience strategy for DPA.||enum||optional||optional, defaulted to RETARGETING.|
Create an Ad Group¶
The following example contains the fields required for creating an ad group that will run on both the mobile search and native channels. All other fields in this spreadsheet are blank and are not shown:
|Action||Object Type||Campaign ID||Ad Group||Search CPC||Stream CPC||Start Date||End Date||Ad Group Status|
|Add||Ad Group||75614||Your Ad Group Name||2.1||1.5||5/29/2014||Required only if the ad group is under a campaign with a LIFETIME budget type||(Will default to Active if not provided)|
Update an Ad Group¶
When updating an ad group, the only required fields are Action, Object Type, Ad Group ID and the fields you would like to update. The following example shows updating the start date for an ad group with an ID of 1475. All other fields in this spreadsheet are blank and are not shown:
|Action||Object Type||Ad Group ID||Start Date|
Create Advanced Location Targeting¶
Gemini Search provides support for advanced location targeting. By default all your campaigns target users by their physical location as well as location of intent (in the search query).
You can now explicitly target either users physically located in your geo-targeted location or users searching for your geo-targeted location, or both (default).
If you upload a bulk file without any location targeting attached to the ad group, then the corresponding ad group will be targeting world-wide.
Three advanced location options are available:
- (Default) Show ads to people in, searching for, or viewing pages about your targeted location.
- Show ads to people in your targeted location only.
- Show ads to people searching for your targeted location only.‚Ä® All three options are supported by Gemini. You can access this feature using a Bulk file or the Gemini API.
Positive and Negative advanced location options are also supported.
The Negative advanced location option only supports the physical location and default (both physical & location of interest) options. All three options are supported by positive advanced location.
If your Bing accounts are synced with Gemini, the advanced location options will not be carried over. You can leverage this feature by breaking the sync and setting the advanced geo targeting option using Bulk or the Gemini API.
This change will not impact your location bid modifiers. Bid modifiers will be applied, and will work in accordance with existing behavior.
Note that support for reporting in the UI will not be available immediately. You should be able to run ad-hoc reports if required, however.
The output looks like this:
This field will have the following values/format:
Positive [Default or Physical or Interest]:Negative [Default or Physical]
Examples would be:
If Positive or Negative are not provided, we would set them to Default, so setting
Positive[Physical] alone would mean that you’re implicitly setting negative to default so on download you will get:
Note the following:
- Value is set on Campaign and Ad Group object types.
- Value is optional.
- Value is editable on existing object.
Create an Ad Group with Bidding Strategy of OPT_POST_INSTALL¶
The following example contains the fields required for creating an ad group with a bidding strategy of OPT_POST_INSTALL. All other fields in this spreadsheet are blank and are not shown:
|Action||Object Type||Campaign ID||Ad Group||Stream CPC||ECPA Goal||Bidding Strategy||Start Date||End Date||Ad Group Status||Custom Parameters||Tracking Template|
|Add||Ad Group||123456||adgroup post install||2||10||OPT_POST_INSTALL||1/26/2015||2/26/2015||ACTIVE||