Once a supported contract (Commission, CPM, Co-Op) is replicated to Portal 3.0, the corresponding account is automatically created. To ensure successful integrations, search for the account name and verify that the account settings have been entered correctly, especially:
- On the Main subtab:
- Advertiser Homepage URL is correct
- If running FB, the Facebook Page ID. However, this is not a blocker and can be entered later.
- Container Pixel Configuration: The container pixel needs to be configured in order for the integrations to start. If you have any doubts about the integration, please hold off on configuring the container pixel. To configure it, either select a Container Pixel and the Property ID, or select None Selected for standard pixels.
Integrations are then triggered for the account, meaning that:
- A Navi advertiser and pixels are created and linked to the account
- Advertisers are created in the required DSPs, based on the channels selected on the contract, and linked to the Portal account:
- CM360: advertiser created in all cases
- Display: Xandr, TTD, DV360
- SEM: Google Ads and Bing
- Facebook/Instagram: Facebook
- Pixels are created in the DSPs and piggybacked to Navi
- Pixel integration guide is generated and available to download
(If you prefer, check out this quick demo)
Things to Note:
- The automation for DSP advertiser & pixel creation only supports net new accounts running Co-Op and CPM contracts. Meaning that:
- CSMs will no longer need to submit tasks to the AdOps team for creating new advertisers and pixels in the DSPs. Consequently, the AdOps team will no longer need to create advertisers and pixels for net new accounts.
- Accounts that previously ran with Sojern - winbacks - a non-Commission contract, will need to continue to be managed by the AdOps team. Advertiser & pixel creation is only supported for completely new accounts.