Why at_geo Cookie is generated? | Community
Skip to main content
October 14, 2024
Solved

Why at_geo Cookie is generated?

  • October 14, 2024
  • 2 replies
  • 660 views

I have implemented an activity with at.js version 2.11.6. And I noticed that, in addition to the at_check and mbox cookies, the at_geo cookie is also generated and stores information about the user's location, including longitude, latitude, country, region, and city.

 

I could not find any mention of this cookie in the official documentation. Therefore, I would like to inquire about the reason for its generation and whether there is a specific setting that allows for its activation.

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 kandersen-1

Hi @prabhatsharma ,

 

prads is spot on.

 

The at_geo cookie is set when on-device decisioning is enabled. 

During on-device decisioning, when Target initially retrieve the artifact from the Akamai CDN, it also retrieve the user's geo location in the headers. Adobe then create a dedicated cookie called at_geo which contains this information. When a getOffers() call is made with the ipAddress, Target check the at_geo cookie to make the decision on-device.

 

i hope this clarifies. 

2 replies

pradnya_balvir
Community Advisor
Community Advisor
October 14, 2024

Hi @prabhatsharma , It stored the information for geographical locations so that you can create the target audiences.

  1. In the Target interface, click Audiences > Create Audience
  2. Name the audience and add a description
  3. Drag and drop Geo into the audience builder pane
  4. Click Select and choose a geo option, such as Country/Region, State, City, or Zip Code
  5. Specify an operator and the appropriate value
  6. Optionally, set up additional rules for the audience
  7. Click Done

 

kandersen-1
Community Advisor
kandersen-1Community AdvisorAccepted solution
Community Advisor
October 14, 2024

Hi @prabhatsharma ,

 

prads is spot on.

 

The at_geo cookie is set when on-device decisioning is enabled. 

During on-device decisioning, when Target initially retrieve the artifact from the Akamai CDN, it also retrieve the user's geo location in the headers. Adobe then create a dedicated cookie called at_geo which contains this information. When a getOffers() call is made with the ipAddress, Target check the at_geo cookie to make the decision on-device.

 

i hope this clarifies. 

Test forum signature