Version | 2.171 |
|---|---|
Integration | Google Ads, Facebook, Linkedin, Pinterest, Amazon DSP |
| Warning |
|---|
If you do not follow this step, the integrations won’t work and will always show an error message. |
What will change?
Security is of the highest importance to us and this includes also third-party integrations
...
Google Ads: [Set up connection] in Google Ads
Linkedin: [Set up connection] in Linkedin
Pinterest: [Set up connection] in Pinterest
Amazon DSP: [Set up connection] in Amazon DSP Pilot
...
What If I don’t use Media Buying, but AdServer Integrations (e.g. Google AdManager, Xandr, Adswizz, Freewheel ect.)
For non Media Buying Integrations, this change should not have a negative impact. However it can be that if you already had a value in your Access Token field on the Connection Record, that his value remains not encrypted and can cause problems.
We are looking into solutions to prevent these kinds of situations, meanwhile, please check the following steps:
Check the Access Token field for your Connection Record (If this is not visible, you might need to modify your page layout to show the missing field)
If there is a text, which appears to be not encrypted, please edit the field and empty it, save the record
If needed, you can paste in again the former value and save the record again, but except the connections listed above, other systems are not using the access token field.
More information can be found here:
Third Party Integrations: Problems with Encryption Errors (AdServer, Media Buying, Programmatic)
...
Setup
There are no additional steps in setup required.