Campaign Age Criterion Record - Bulk
Defines a campaign age criterion that can be uploaded and downloaded in a bulk file.
You can target customers by age so that your ads are displayed more frequently to people who will be interested in them.
Each age criterion defines an age range for the accompanying criterion bid adjustment.
The maximum number of age criterions that you can specify per campaign or ad group is five, i.e. one for each of the supported age ranges EighteenToTwentyFour, TwentyFiveToThirtyFour, ThirtyFiveToFourtyNine, FiftyToSixtyFour, and SixtyFiveAndAbove.
If ad group level age criterions are specified, the campaign level age criterions are ignored for that ad group. In other words the ad group age criterions override the campaign age criterions, and are not applied as a union.
Tip
For an overview of how to use target criterions, see Show Ads to Your Target Audience.
You can download all Campaign Age Criterion records in the account by including the DownloadEntity value of CampaignTargetCriterions in the DownloadCampaignsByAccountIds or DownloadCampaignsByCampaignIds service request. Additionally the download request must include the EntityData scope. For more details about the Bulk service including best practices, see Bulk Download and Upload.
The following Bulk CSV example would add a new campaign age criterion if a valid Parent Id value is provided.
Type,Status,Id,Parent Id,Sub Type,Campaign,Client Id,Modified Time,Target,Bid Adjustment,Name,Radius,Unit,From Hour,From Minute,To Hour,To Minute,Latitude,Longitude
Format Version,,,,,,,,,,6.0,,,,,,,,
Campaign Age Criterion,Active,,-111,,,ClientIdGoesHere,,EighteenToTwentyFour,20,,,,,,,,,
If you are using the Bing Ads SDKs for .NET, Java, or Python, you can save time using the BulkServiceManager to upload and download the BulkAdCampaignAgeCriterion object, instead of calling the service operations directly and writing custom code to parse each field in the bulk file.
var uploadEntities = new List<BulkEntity>();
// Map properties in the Bulk file to the BulkCampaignAgeCriterion
var bulkCampaignAgeCriterion = new BulkCampaignAgeCriterion
{
// 'Campaign' column header in the Bulk file is read-only
CampaignName = null,
// 'Client Id' column header in the Bulk file
ClientId = "ClientIdGoesHere",
// Map properties in the Bulk file to the
// BiddableCampaignCriterion object of the Campaign Management service.
CampaignCriterion = new BiddableCampaignCriterion
{
// 'Parent Id' column header in the Bulk file
CampaignId = campaignIdKey,
Criterion = new AgeCriterion
{
// 'Target' column header in the Bulk file
AgeRange = AgeRange.EighteenToTwentyFour,
},
CriterionBid = new BidMultiplier
{
// 'Bid Adjustment' column header in the Bulk file
Multiplier = 20,
},
// 'Id' column header in the Bulk file
Id = null,
// 'Status' column header in the Bulk file
Status = CampaignCriterionStatus.Active,
}
};
uploadEntities.Add(bulkCampaignAgeCriterion);
var entityUploadParameters = new EntityUploadParameters
{
Entities = uploadEntities,
ResponseMode = ResponseMode.ErrorsAndResults,
ResultFileDirectory = FileDirectory,
ResultFileName = DownloadFileName,
OverwriteResultFile = true,
};
var uploadResultEntities = (await BulkServiceManager.UploadEntitiesAsync(entityUploadParameters)).ToList();
For a Campaign Age Criterion record, the following attribute fields are available in the Bulk File Schema.
Bid Adjustment
The percentage amount that you want to adjust the bid for the corresponding Target.
Supported values are negative ninety (-90) through positive nine hundred (900).
Add: Optional. The bid adjustment will be set to the default of 0 if not included.
Update: Required
Delete: Read-only
Campaign
The name of the campaign where this criterion is applied or removed.
Add: Read-only
Update: Read-only
Delete: Read-only
Client Id
Used to associate records in the bulk upload file with records in the results file. The value of this field is not used or stored by the server; it is simply copied from the uploaded record to the corresponding result record. It may be any valid string to up 100 in length.
Add: Optional
Update: Optional
Delete: Optional
Id
The Microsoft Advertising unique identifier of the criterion.
Add: Read-only
Update: Read-only and Required
Delete: Read-only and Required
Modified Time
The date and time that the entity was last updated. The value is in Coordinated Universal Time (UTC).
Note
The date and time value reflects the date and time at the server, not the client. For information about the format of the date and time, see the dateTime entry in Primitive XML Data Types.
Add: Read-only
Update: Read-only
Delete: Read-only
Parent Id
The identifier of the campaign where this criterion is applied or removed.
This bulk field maps to the Id field of the Campaign record.
Add: Read-only and Required. You must either specify an existing campaign identifier, or specify a negative identifier that is equal to the Id field of the parent Campaign record. This is recommended if you are adding new criterions to a new campaign in the same Bulk file. For more information, see Bulk File Schema Reference Keys.
Update: Read-only and Required
Delete: Read-only and Required
Status
Represents the association status between the campaign and the criterion. If the criterion is applied to the campaign, this field's value is Active. To delete the criterion, set the status to Deleted.
Add: Read-only. The status will always be set to Active when you add criterions. If you upload another value e.g., Foo the result file will contain the same value although the criterion is active.
Update: Optional
Delete: Required. The Status must be set to Deleted.To delete a specific age criterion bid, you must upload the Status, Id, and Parent Id.
Target
The age range that you want to target with the corresponding Bid Adjustment.
Supported values are EighteenToTwentyFour, TwentyFiveToThirtyFour, ThirtyFiveToFourtyNine, FiftyToSixtyFour, and SixtyFiveAndAbove.
Note
In many countries or regions, online advertisers are not supposed to target any users less than 18 years old. Microsoft Advertising does not deliver interest-based advertising to children whose birthdate in their Microsoft account identifies them as under 13 years of age. For more information see the Microsoft Privacy Statement.
Currently people ages 13 to 17 can see your ads, although you cannot adjust the bid for that age range. Soon in Microsoft Advertising you will be enabled to specifically exclude ages 13 to 17. The target value of ThirteenToSeventeen will be supported with negative bid adjustments between -100 and 0. We will announce more specific dates within the next few months.
Add: Required
Update: Required
Delete: Read-only