Below you will find an overview of where the Adserver Placement ID (also known as Mercury UUID) must be stored so that Mercury can recognize the data from the various technical systems and correctly assign it to your campaigns.
Note: The automated daily import of data into Mercury requires that the technical systems listed below are set up as data pipelines.
When storing the ID, it does not matter in principle where this is placed in the name or field. It also does not matter whether you insert it with or without a separator. This way, existing naming taxonomies can largely be retained, and the ID can be placed flexibly.
Example
- GCM as Placement External ID
= mrc-PpNbqxt2vHH - LinkedIn in the Creative Name
= "Motif1_mrc-PpNbqxt2vHH" or "Motif1mrc-PpNbqxt2vHH" or "mrc-PpNbqxt2vHH-Motif1" etc. - Facebook in the Ad Name
= "Text_mrc-PpNbqxt2vHH" or "Text_mrc-PpNbqxt2vHH-Text" etc.
Please store the Adserver Placement ID in the following way within the different systems:
AdServers
| System | Option 1 | Option 2 |
| Adform Adserver | in the field AdGapId | - |
| Google CM360 | in the field Placement External ID | - |
| Flashtalking | in the field ThirdParty Placement ID | - |
DSPs
| System | Option 1 | Option 2 |
| Active Agent (Addition) | in the Order Name | - |
| Adform DSP | in the field AdGap ID | - |
| Amazon DSP | in the LineItem Name | - |
| Google DV360 | in the LineItem Integration Code | in the Insertion Order Integration Code |
| Hawk DSP* | planned | - |
| The Trade Desk | in the campaign description | - |
| Verve DSP | in the Media Plan External ID | - |
Paid Social Platforms
| System | Option 1 | Option 2 |
| in the Creative Name | - | |
| Meta | in the Ad Name | in the Campaign Ad Labels |
| in the Ad Name | - | |
| in the Ad Name | - | |
| Snapchat | in the Ad Name | - |
| TikTok | in the Ad Name | - |
| X (formerly Twitter) | in the Card Name | - |
| in the Ad Name | - |
Organic Social (on request):
| System | Option 1 | Option 2 |
| Facebook Pages | no direct matching possible | - |
| LinkedIn Organic | no direct matching possible | - |
| Pinterest Pages | no direct matching possible | - |
| TikTok Organic | no direct matching possible | - |
| YouTube Organic | no direct matching possible | - |
Native DSPs/Platforms
| System | Option 1 | Option 2 |
| Factor Eleven | contact us (custom) | - |
| Outbrain | in the Campaign Name | - |
| Readpeak* | coming soon | |
| Taboola | in the Campaign Name | - |
| Teads* | coming soon | - |
Other Platforms
| Adnami* | coming soon | - |
| Apple Search Ads | in the Ad Group Name | - |
| Bing Ads | in the Campaign Labels | - |
| Google Ads | in the Campaign Labels** | - |
| Spotify Ads* | coming soon | - |
**Labels must be stored at account level, not at MCC level.
Validation Systems
(currently only via Bridge, not available in Mercury)
| Audience Project | no storage required | - |
| Adobe Analytics | no storage required | - |
| Google Analytics | depending on the target, consult with MMT Support | - |
| Nielsen ONE | no storage required | - |
| Integral Ad Science | no storage required | - |
| DoubleVerify | no storage required | - |
| Mapp (Webtrekk) | as URL parameter | - |
*Integrations under development, coming soon