AA Beacon has two network requests- 302 followed by 200

Avatar

Avatar

StewSchilling

MVP

Avatar

StewSchilling

MVP

StewSchilling
MVP

13-02-2019

Can anyone explain what is happening here?  I see this occasionally.  It tends to be at the beginning of a session.

I originally thought that I had some issue in my code that was causing two beacons to be sent.  I finally caught it in the network tab this AM.

I now think that this is normal behavior, but I don't fully understand the "Why" of it.

Any help?

Screen Shot 2019-02-13 at 8.31.56 AM.png

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

ishans52004352

Employee

Avatar

ishans52004352

Employee

ishans52004352
Employee

13-02-2019

Hi stewarts16448458​,

The first 302 beacon is a redirect beacon that is used to set the s_vi cookie. Once the s_vi cookie is set, you won't see such 302 beacons (unless the cookies are cleared). The second 200 beacon is the actual beacon sent to Analytics servers.

This is an expected behavior and shouldn't be considered as duplicate beacons.

Hope this clarifies!

Answers (1)

Answers (1)

Avatar

Avatar

StewSchilling

MVP

Avatar

StewSchilling

MVP

StewSchilling
MVP

13-02-2019

Thank you!  I would assume that this does not happen when using ECID service. Right?