Adobe Analytics Beacon is not Firing even when the tracker is set | Community
Skip to main content
Level 2
January 3, 2022
Question

Adobe Analytics Beacon is not Firing even when the tracker is set

  • January 3, 2022
  • 2 replies
  • 5158 views

I am facing an issue where my Adobe Analytics page view beacon is not firing. I could see my rule getting fired, the tracker with all the variables is getting set and the logs also show "Firing Page View Beacon". However, there is no beacon triggered. When I call s.t() with a delay of 500ms in a custom code, the tags start firing as expected however, this is not the case with the default action of Send Beacon.

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

2 replies

Pablo_Childe
Community Advisor
Community Advisor
January 3, 2022

Is your web app a Single page App? Like Angular for example?

 

Level 2
January 4, 2022

It is a standard web application.

Pablo_Childe
Community Advisor
Community Advisor
January 5, 2022

So 2 things then.

 

If you add a delay and then see data its a race type of condition. The pagebottom adobe snippet is firing and all datalayer elements required are not ready.

 

You can try and make sure the pagebottom code is later in page load.

 

Also make sure all data layer is indeed ready or else you will see this blank data type of behaviour.

 

Kishore_Reddy
Community Advisor
Community Advisor
January 4, 2022

Did you try inspecting the beacon on a different machine? and different internet connection?

 

The reason I ask this is, generally beacon firing is a two-way procedure between Browser and Adobe server. So if there's any network related firewall which is allowing after a certain time out or may be network speed etc.

Level 2
January 5, 2022

HI @kishore_reddy ,

Yes, I tried it on different machines, connections and browsers as well.

Kishore_Reddy
Community Advisor
Community Advisor
January 5, 2022

Interesting! Last question, is there a condition that's not meeting the criteria until initial 300-400ms? As in, is there a latency factor attached to condition (of the page load Rule) validation? Like a datalayer or function or object, with 'direct call' event.