CustomTargetingKeys
Create, update, and query DoubleClick for Publishers Custom Targeting Keys.
Select
The following queries are processed server side by the Google Ad Manager APIs.
Retrieve a list of CustomFields. For example:
SELECT * FROM [CustomTargetingKeys]
Additionally, you can specify the Id or filter by any other column.
SELECT * FROM [CustomTargetingKeys] WHERE Id = '10721398'
INSERT
To create a new CustomTargetingKey, the Name and Type fields are required.
INSERT INTO [CustomTargetingKeys] (Name, Type) VALUES ('tg_key', 'PREDEFINED')
Update
You can update any field not marked as read-only (except Name column that can only be inserted), by specifying the Id column.
UPDATE [CustomTargetingKeys] SET DisplayName = 'targeting key (Deprecated)' WHERE Id = '10721398'
Delete
The DELETE operation is not supported for this table.
Columns
Name | Type | ReadOnly | Description |
Id [KEY] | Long | True |
The ID of the CustomTargetingKey. This value is readonly and is populated by Google. |
Name | String | False |
Name of the key. This can be used for encoding . If you don't want users to be able to see potentially sensitive targeting information in the ad tags of your site, you can encode your key/values. For example, you can create key/value g1=abc to represent gender=female. Keys can contain up to 10 characters each. |
DisplayName | String | False |
Descriptive name for the key. |
Type | String | False |
Indicates whether users will select from predefined values or create new targeting values, while specifying targeting criteria for a line item. The allowed values are PREDEFINED, FREEFORM. |
Status | String | True |
Status of the CustomTargetingKey. This field is read-only. A key can be activated and deactivated by calling CustomTargetingService.performCustomTargetingKeyAction. The allowed values are ACTIVE, INACTIVE, UNKNOWN. |
ReportableType | String | False |
Reportable state of a {@CustomTargetingKey} as defined in ReportableType. The allowed values are UNKNOWN, ON, OFF, CUSTOM_DIMENSION. |