Buttons stop working if the analytics servers cannot be reached | Community
Skip to main content
August 4, 2017
Solved

Buttons stop working if the analytics servers cannot be reached

  • August 4, 2017
  • 3 replies
  • 928 views

I noticed that the sattelite lib script stops the propagation of click events on a button if the network request to the analytics server is not successful. Unfortunately some ad or tracking blockers block the analytics domain so this happens quite often.

In that case things like the hamburger menu stop working. When I remove the analytics script from the page everything works fine.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by sbaechler

The solution was to remove the Adobe analytics script until our operation guys could add the necessary CSP headers in production.

The call that stopped the events from propagating was the first call to the analytics subdomain of the main site. The script made another call to secure-ds.serving-sys.com which failed as well (it was blocked by the CSP headers). But that didn't break the site.

3 replies

jantzen_b
Adobe Employee
Adobe Employee
August 8, 2017

Do you have a URL where we can test this? I've never heard of the Analytics beacon being blocked causing an impact to page functionality.

jantzen_b
Adobe Employee
Adobe Employee
August 14, 2017

Hi Simon,

Did you still need assistance with this issue? If not, would you mind posting the solution you found in case others run into the same issue?

Thanks,
Jantzen

sbaechlerAuthorAccepted solution
August 14, 2017

The solution was to remove the Adobe analytics script until our operation guys could add the necessary CSP headers in production.

The call that stopped the events from propagating was the first call to the analytics subdomain of the main site. The script made another call to secure-ds.serving-sys.com which failed as well (it was blocked by the CSP headers). But that didn't break the site.