One additional clarification here, as you may be faced with another warning screen after initially changing the URL and logging in. Simply replace bank.demdex.com w/ audiencemanager.adobe.com once more, without altering the rest of the URL. Then, you will be able to view your token. 

Hey Rich, If you refresh your token utilizing the workaround provided in the other forum post, are you still encountering this 401 Token error?Best,Curtis Oliver  |  Technical Support Engineer

Hey Rich, Thanks for letting us know, we reached out to Google regarding this concern. In the mean-time, you can replace the URL with https://audiencemanager.adobe.com/portal/baaam/token when faced with the "deceptive site ahead" warning, and generate your token in this way. This should enable you t...

The VisitorID service is the extension which actually generates a device ID and sets that value in the demdex cookie. If you are still leveraging the VisitorID service, that would explain the presence of the demdex cookie. If you would like to remove 3rd party cookies without removing the visitor ID...

Hi Michael,   Comparing your destination setup to our documentation , I'm not seeing any configuration issues. I can see in the last screenshot there is an error code indicating that Facebook did not accept the customer ID provided in this request. Are you able to provide the segment ID & your websi...

Hey Alex,   Thanks for clarifying your account status & providing the webinar link. After reaching out to the organizer of the webinar, we believe the 'https://' portion of the URL is causing the issue here. Would you be able to remove this from the URL & attempt to sign up once more? Best, Curtis O...

Hey Alex,   So sorry for the frustration here while attempting to sign up for a free webinar. Do you happen to have a link for the specific webinar? I'd like to investigate the issue with the URL field you are describing.   In terms of the personal vs enterprise account, if you submitted a customer ...

I was specifically referring to ID sync tags, which are configured within your Audience Manager container in the Adobe back-end. Customer care can assist with the removal of these. You're correct that we would not be able to assist with any code removal within a tag manager such as Tealium.   

Hi Uma,   a 302 response indicates a re-direct, which is not necessarily a concern. In this case, the request looks to be going to Google. Our URL destinations which send requests to Google's following endpoint are typically redirected to a separate Google URL: http://googleads.g.doubleclick.net/ Do...

Hello,   If you would like to pull all ECIDs via a bulk export, feel free to submit a ticket to customer care so we can assist with the configuration of that export. Due to the nature of the relationship between ECIDs & UUIDs, our system innately activates on ECIDs. These two ID types are mathematic...