Multiple image request calls: Inflated metrics for unique visitors/ visits | Community
Skip to main content
Level 3
October 11, 2020
Solved

Multiple image request calls: Inflated metrics for unique visitors/ visits

  • October 11, 2020
  • 3 replies
  • 2548 views

Hello Team, 

 

I am new to AA's world. Trying to figure out some of the basic reasons for traffic spikes for one of our Single page applications. When debugged using adobe experience cloud debugger, we noticed on our home page, that there were two image requests that are being fired (two hits). Here are the details of those two image requests.

 

Image request 1: Yes, obviously, the page load rule that sends a beacon (s.t() call) ---> we are setting few variables like page name, referrer, load time.. etc.

Image request 2:  A direct call rule that gets called while listening to dispatched custom event ( addEventListener)  that sends a beacon (s.tl() call)  ---> we are setting few new variables which are not set in the first image request. 

 

So, now, when we take a look at the reports for unique visitors, visits and page views, the metrics got a spike(almost doubled) for  unique visitors and visits. the report for page views is not impacted with the spike. 

 

Would like to know why an extra s.tl() call causes inflated metrics and how should we go about addressing it? 

 

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 arjun0718

Just to keep everyone else updated, Andrey helped taking a look at the URLs (which I could not share in this public forum) and the server calls looked okay. He noticed ECID extension does not have tracking server configured. Checking on possibilities of upgrading these extensions to see if it gets resolved.

3 replies

Andrey_Osadchuk
Level 10
October 13, 2020

It is unlikely the UV and Visits doubled because of the multiple server calls. I presume you first and second calls have different Visitor ID values. Double check that the Experience Cloud ID (mid parameter) exists in both and it's the same.

I would doubt that the Page Views could be doubled (even if the Visitor IDs were not passed correctly) because you mentioned that only the first call is s.t().

Level 2
October 13, 2020

thanks for your response. we did double check the Experience Cloud Visitor ID parameter in both the image requests using adobe experience cloud debugger extension and yes both the image requests have same IDs. please find the same in the screenshot

One more thing i noticed is, these two image request calls are resultant of two Direct Call Rules (as opposed to page load rule and direct call rule like I mentioned earlier). Does firing back to back DCRs causes issues of this kind?

arjun0718Accepted solution
Level 2
October 13, 2020

Just to keep everyone else updated, Andrey helped taking a look at the URLs (which I could not share in this public forum) and the server calls looked okay. He noticed ECID extension does not have tracking server configured. Checking on possibilities of upgrading these extensions to see if it gets resolved.

April 21, 2023

I am facing the same issue & I just see the org id configured in ECID extension, can you please help me with server configuration in extension?