Missing Orders in Adobe - > 20% in most cases | Community
Skip to main content
February 21, 2024
Solved

Missing Orders in Adobe - > 20% in most cases

  • February 21, 2024
  • 1 reply
  • 532 views

Hi Everyone,

 

Since moving to Single page application(SPA), our company has been missing some orders in Adobe Analytics. Before the move to SPA Orders accuracy was up to 95% and it has since dropped to - 20%.

 

Has anyone experience this before?

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 Jennifer_Dungan

SPAs in general shouldn't cause this, in fact, this usually results in less lost data (as in there is much less chance of the beacon being cancelled as the user moves from page a to b, since the actual page doesn't "unload").. however, it's possible that what you are using to trigger the tracking could have intermittent issues?

 

In order to really find the issue, you are going to have to do a lot of testing.. maybe testing at load, or an automated test that can run the test many times in a row and try to determine if you can find and replicate when tracking doesn't occur...  is the trigger failing? Or is the analytics encountering an issue that causes the tracking to fail.

1 reply

Jennifer_Dungan
Community Advisor and Adobe Champion
Jennifer_DunganCommunity Advisor and Adobe ChampionAccepted solution
Community Advisor and Adobe Champion
February 21, 2024

SPAs in general shouldn't cause this, in fact, this usually results in less lost data (as in there is much less chance of the beacon being cancelled as the user moves from page a to b, since the actual page doesn't "unload").. however, it's possible that what you are using to trigger the tracking could have intermittent issues?

 

In order to really find the issue, you are going to have to do a lot of testing.. maybe testing at load, or an automated test that can run the test many times in a row and try to determine if you can find and replicate when tracking doesn't occur...  is the trigger failing? Or is the analytics encountering an issue that causes the tracking to fail.