Skip to main content
pramseycom
pramseycom
Level 2
August 5, 2020
Solved

Beacon Blocking

We're seeing some of our users blocking our beacon at the network level.  I'm guessing they're seeing the IP for our beacon on some sort of deny list since that IP is the same as Adobe.  Anyone have a good way around this?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Jacob-DDdev
Jacob-DDdevAccepted solution
Level 6
August 5, 2020

If the issue is an Adobe-blacklist you should look into first-party tracking--unless your IP is also on a blacklist.

Also, if it is blocking Launch/DTM code, you can host your own versions instead of using Akamai.

View in thread

8 replies

Jacob-DDdev
Jacob-DDdevAccepted solution
Level 6
August 5, 2020

If the issue is an Adobe-blacklist you should look into first-party tracking--unless your IP is also on a blacklist.

Also, if it is blocking Launch/DTM code, you can host your own versions instead of using Akamai.

Translate
pramseycom
pramseycomAuthor
Level 2
August 6, 2020
So we use first-party cookies, but even though the beacon call is with our local domain, the IP it resolves to is still an Adobe one. My guess is that it's the IP that's in a deny-list vs the the subdomain we're using. Ideally what we'd be able to do is proxy, but I'm not sure what all is involved with that and the issues we may have.
Translate
Terms & ConditionsAccessibility statement

Loading footer...