AA Beacon has two network requests- 302 followed by 200 | Community
Skip to main content
Stewart_Schilling
Community Advisor
Community Advisor
February 13, 2019
Solved

AA Beacon has two network requests- 302 followed by 200

  • February 13, 2019
  • 2 replies
  • 6498 views

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?

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 isinha

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!

2 replies

isinhaAdobe EmployeeAccepted solution
Adobe Employee
February 13, 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!

Stewart_Schilling
Community Advisor
Community Advisor
February 13, 2019

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

randy_floyd
April 3, 2020
A little late to the party here... 🙂 But It DOES happen with ECID.