Why at_geo Cookie is generated?

[PrabhatSharma]

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.

[pradnya_balvir]

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 · Accepted solution]

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.