General
Campaign Placements, a step within the programmatic campaign workflow, displays all placements included for a programmatic campaign in a table. You can also create or modify a campaign placement here.
Placements represent the media buying structure. If ad tags are to be delivered to a DSP, the placement will be aligned to represent the DSP ad groups or line items. If the ad tags are to be delivered to a publisher, Flight Control placements will represent the publisher's ad placements.
Important: Before working with a new publisher or platform, check if they're listed under your account's DSPs & Publishers page in Flight Control. If the media partner isn't listed, notify your Clinch account representative as soon as possible so they can confirm whether certification is needed.
User Permissions
- You need the Campaigns user permission to create or modify placements.
Creating Placements
You can create a programmatic campaign placement through three methods:
- manually (complete a form to configure the placement).
- by connecting to a DSP campaign.
- by importing them with a CSV/Excel file.
Table Columns
| Column | Description |
| Placement ID |
Displays the unique identifier for the placement. Note: The maximum character count is 200. |
| Placement Name |
Displays the name of the placement. Note: The maximum character count is 1,000. |
| Ad Size | Displays all included ad sizes for the placement. (This doesn't apply to video campaigns). |
| Environment | Displays the ad-serving environment that the placement uses. For more information, see Ad Serving Environments. |
|
Variations Video and interactive campaigns only |
Displays the number of variations rendered for a placement, helping you identify placements that exceed DSP variation limits. |
| Status | Displays the placement's status using icons: either successful ( |
|
Target Platform Video campaigns only |
Displays the target platform selected for the video campaign placement. Target platforms determine how Flight Control renders your campaign's video assets. Hover over the selected target platform to see its specific video rendering specifications. Note: Flight Control automatically selects target platforms for placements according to the placement’s selected DSP/publisher and ad-serving environment. You should only change a DSP's target platform selection if you have a programmatic deal with a publisher that requires rendering specifications not covered by the default. Also note that single publisher instances should never be overridden, as the default will always meet the one-to-one publisher requirements. |
| Trackers |
Displays the number of trackers by type associated with the placement. For example: Impression pixel (3), click pixel (2), and click tracker (2). The Trackers filter includes a sub-filter that allows you to quickly identify placements without any trackers or with specific trackers. For example, if you want to see the placements that do not have impression pixels, you would select "Impression Pixel" in the Tracker filter and then choose "N/A". Note: Trackers not associated with any placement (e.g., linked only to an ad size or to a specific creative) won't appear in the Trackers column on the placement page. For more details on trackers, see Campaign Trackers Overview. |
| DSP | Displays the name of the selected DSP or publisher for the placement. |
| DSP Campaign | Displays the DSP campaign to which the placement is connected. |
| Ad Group/Line Item | Displays the DSP ad unit to which the placement is connected. |
| DSP Creatives |
|
| Custom Parameters |
Lists the placement's key-value parameters, which are used for multiple purposes. Note: Custom parameters don't affect campaign placement ad tags, so you don't need to republish the ad tags for custom parameters to take effect. For more information, see Placement Custom Parameters. |
Note: You can click the gear icon to reorder or hide table columns and group table rows by DSP or DSP campaign. For more information on Flight Control tables, see Flight Control Table Functionality.
DSP Creatives Column
This column's listed creatives are color-coded to reflect their general information and publication statuses in connected DSPs:
-
Blue Text, White Background (
): The creative hasn't yet been published to the DSP.
-
Blue Text & Background (
): The creative has been successfully published to the DSP.
-
Red Text, White Background (
): The creative failed to be published to the DSP.
-
Red Text & Background (
): The creative was published with warnings or issues.
- Such issues can be:
- a duplicate creative.
- having an unexpected creative name.
- an unsupported campaign ad size.
- Such issues can be:
Note: Hover over a creative label to reveal additional creative information from the DSP, such as statuses, errors/issues, and custom placement values used.
Table Actions
Select a placement and click Actions to see the following options:
| Action | Description |
| Sync Placements from DSP |
Updates information for the selected campaign placement(s) to match their DSP configurations. If no placement is selected, this action will import placements from the selected DSP campaign. Note: After syncing placements from a DSP, be sure to review the placements and delete ones not related to Clinch. |
| Publish Tags |
Initiates the publishing of selected placements' ad tags to connected DSPs. (The publishing process can't be stopped.) When tags are published, DSP creatives are created on the DSP side for each ad tag. Once Clinch ad tags are published to the DSP as creatives, the creative names are automatically generated. Note: This action is relevant only for placements derived from DSP campaigns. Tags for manually created placements are exported through the Download Tags action. We recommend activating your Flight Control campaign version before publishing tags to DSPs. If the Publish Tags action is performed again:
|
| Download Tags | Downloads the ad tags of selected placements to an XLSX file. When downloading ad tags, you can select Disable TCF macros to remove General Data Protection Regulation (GDPR) parameters from the tags. |
| Export DoubleVerify Blueprint |
Exports your campaign information to a CSV file, which you can upload to DoubleVerify as a "blueprint" if Clinch is your primary ad server. Note: This action only displays if you enable your campaign's DoubleVerify Service. |
| Read Creative(s) From DSP |
Refreshes creative and ad group/line item data according to their DSP configurations for the selected campaign placement(s). Note: DSP-sourced creative data isn't updated upon visiting Campaign Placements. To handle this, you must use the Read Creative(s) From DSP action. |
| Delete Placement(s) |
Deletes the selected placement(s) from the campaign. Note: Re-syncing DSP placements will return deleted placements as campaign placements (including their published creatives). |
|
Set Requires Ping for Attribution Display & Video 360 Placements only |
Adds and configures the Requires Ping for Attribution custom parameter for the selected Display & Video 360 placements, which automatically activates the "Ping for Attribution" feature in Display & Video 360 (DV360) when ad tags are published to DV360 using the integration. Ping for Attribution is a feature in DV360 that requires the DSP platform to only acknowledge conversions for an ad after receiving a corresponding "ping" signal from Campaign Manager 360. This ensures that conversion data is synchronized and verified between the two platforms. |
| Export to CSV |
Exports the selected placements and their information to a CSV file. Using this action without selecting placements results in all campaign placements being exported to the CSV file. |