Why does my app's cookie disappear during the checkout process?

Topic summary

An app-set cookie used in a shop flow works normally but disappears when entering checkout, making it inaccessible throughout checkout (not visible in the browser console). The goal is to read the cookie’s value after checkout using the Pixel API; while the API’s checkout_completed event appears designed to read cookie values, the cookie is not present during checkout.

Key details:

  • Cookie exists in the shop environment; vanishes at checkout, preventing retrieval during the process.
  • Pixel API (used for tracking and events) and its checkout_completed event seem to support reading cookie values, creating confusion about availability.
  • No documentation found indicating that checkout deletes app-set cookies.

Open questions:

  • Is the disappearance of cookies during checkout intended behavior?
  • Is there a configuration or scope issue the developer is missing?
  • Is reading cookies via Pixel API at checkout not feasible?

Status: Unresolved; seeking clarification on expected behavior and possible solutions.

Summarized with AI on January 3. AI used: gpt-5.

Hello there,

I’m developing an app that relies on a cookie previously set by the same app. In the shop everything is working fine, but as soon as I enter checkout that cookie is gone. I want to retrieve the cookies value after checkout with the Pixel API which seems like it would work, but the cookie is apparently gone/unavailable during the whole checkout process, I can’t even see it in the browser console.
I can’t find any info about cookies set by an app being deleted by the checkout process and it seems a little odd since the Pixel APIs checkout_completed event explicitly gives the functionality to read cookie values.

So is this intended behavior, am I missing something or is what I’m trying to do just not possible?
Thank you!