Bulk Imports
Bulk imports allow you to:
- Control location targeting of individual or group advertisements at Country, State, City, Postal Code, and DMA level using an Excel upload.
- Add, modify, and/or delete location targeting in a single campaign or a set of campaigns.
- Map external IDs and names at Campaign, Adgroup, and Ad level using the bulk actions. The external entities mapped can be used for reporting or as a reference to campaigns created on external platforms.
List of Columns
Below is the overall list of columns that can be used in the bulk actions file for location targeting and external ID/Name:
| Column Name | Description |
|---|---|
| Action | Allows you to specify the action that you want to take on the current row. The available options are: - Add: Specify this option if you want the system to add the details in the current row. - Modify: Specify this option if you want to modify the details of an existing campaign, ad group, ad, or keyword. - Delete: Specify this option if you want to delete the details of the current row from the system. When you are adding an entity, ensure that you specify the relevant entity name and the parent entity name. For example, while adding a new ad group, ensure that you specify the CampaignName and the AdGroupName. Note: The Action column is a mandatory column for all the rows. If no value is specified in the Action column, then the specific row will not be considered for processing. |
| Entity Type | Allows you to specify the entity type that you want to add, modify or delete. The following are the possible values in Entity Type for location targeting & externalID/Name mapping. - Location Target - Campaign - Adgroup - Ad Note: The CampaignID and CampaignName are mandatory values for geo-location Targeting. |
| TargetType | Specify one of the following options if you want to include or exclude the location or the domain. - Include: To include the location. - Exclude: To exclude the location. |
| LocationName (old, to be deprecated) | Indicates the location; this column is used for targeting the campaign to a particular geo-location. You can whitelist or blacklist a location based on the value that you specify in the TargetType column. |
| Location Type | Specify one of the following values for the system to determine the type of location to be targeted. - Country - State - City - PostalCode - DMA |
| CountryCode (new) | Enter the Country ISO Code for the Country-level location targeting. |
| StateCode (new) | Specify the ISO state code for the State level location targeting. |
| City (new) | Specify the City Name for city-level location targeting. |
| PostalCode (new) | Specify the Postal code for zip code level location targeting. |
| DMACode (new) | Specify the DMA code for DMA level targeting. |
| Location ID (old, to be deprecated ) | Contains the location ID from the database. This column is to be used for targeting locations using the old method. If location targeting is done using the old as well as the new method, the old method is given the preference. |
| AliasID | The user can specify the IDs for corresponding entities on external platforms. |
| AliasName | The user can specify the name of the corresponding external entity in this column. Note: The AliasID is mandatory for the Alias name to be mapped to a Campaign, Adgroup or an Ad. |
Location Targeting: How it Works
Country Level Targeting
Entity type: Location Target
Below is the list of mandatory columns which are required for targeting a country using the bulk actions feature:
- Action
- CampaignID, CampaignName
- Location Type: Country
- Target Type: Include/ Exclude
- CountryCode: Specify the ISO code of the country that needs to be mapped to the campaign.
State Level Targeting
Entity type: Location Target
Below is the list of mandatory columns which are required for targeting a state using the bulk actions feature:
- Action
- CampaignID, CampaignName
- Location Type: State
- Target Type: Include/ Exclude
- CountryCode
- State code: Specify the state ISO that needs to be mapped to the campaign
- Example: For New York, StateCode – NY
City Level Targeting
Entity type: Location Target
Below is the list of mandatory columns which are required for targeting a city using the bulk actions feature:
- Action
- CampaignID, CampaignName
- Location Type: City
- Target Type: Include/ Exclude
- CountryCode
- StateCode
- City
Postal Code Targeting
Entity type: Location Target
Below is the list of mandatory columns which are required for adding zip code level targeting using the bulk actions feature:
- Action
- CampaignID, CampaignName
- Location Type: PostalCode
- Target Type: Include/ Exclude
- CountryCode: Specify the ISO code of the country that needs to be mapped to the campaign.
- Postal Code: Specify the Postal Code that needs to be mapped to the campaign.
DMA Level Targeting
Entity type: Location Target
Below is the list of mandatory columns which are required for adding DMA level targeting using the bulk actions feature.
- Action
- CampaignID, CampaignName
- Location Type: DMA
- Target Type: Include/ Exclude
- DMACode: Specify the DMA Code that needs to be mapped to the campaign.
note
- Details regarding the Country, State, Postal, DMA Code, and City name can be found here.
- The StateCode is not mandatory but recommended during PostalCode and DMA level location targeting.
Alias ID/Name: How it Works
AliasID and name are unique identifiers that help the user to identify & map the external entity to the corresponding entity in the Perform Media Console (PMC).
The platform currently supports external ID/Name at a Campaign, Adgroup, and at an Ad level.
Adding an AliasID
- ActionType: ADD
- EntityType: Campaign/Adgroup/Add
- Along with the mandatory columns at the respective level, AliasID and AliasName columns can be used to map the ID and Name to the corresponding entities.
Deleting an AliasID
- ActionType: Modify
- EntityType: Campaign/Adgroup/Add
- To remove the ID/name mapped, leave the respective columns empty, save the file and re-upload it by following the Importing A File steps described below.
note
To map an AliasName, the AliasID is mandatory.
Importing a File
After you have created a Microsoft Excel file following the instructions above, you may initiate the import process in the PMC dashboard to complete your account additions/modifications/deletions.
Perform the following steps to import the Microsoft Excel file:
- Log into the dashboard
- In the left pane, click Bulk Actions and then select Import.
- In the Select File to Upload section, either drag and drop the Microsoft Excel file or click choose file and select the appropriate file.
- Click the Upload button. The system starts gathering the data from the file and displays a preview of all the changes that will be made once the file is uploaded.
- Go through the preview and verify whether all the changes are displayed correctly.
- To start uploading the data, click Apply Changes. The importing process starts. After the importing process is completed, the dashboard displays an Import Summary that provides a list of all the successful and failed changes
Grace Period
Location targeting is currently supported using both the old method (Location ID, LocationName, LocationType columns) and the newer method set of columns introduced.
However, when both the methods are used at the same time (for mapping a single entity), the old method will be prioritized.