Appcues stores some data in localStorage and sessionStorage within the browser:

Local Storage

• apc_ann_errors: This stores any errors Appcues encounters trying to show a flow. Once the errors are reported, they are removed from storage.
• apc_local_id: This stores a UUID that is independent of the user's ID, but can help identify when an anonymous user logs into a product and becomes a known user.
• apc_user_id: This stores the user's ID, so Appcues can retain the ID without requiring an Appcues.identify() call on every page load.

Session Storage

• apc_user: This stores the user properties that you send to Appcues in an identify call, in addition to the "auto-properties" and "device properties" documented here: https://docs.appcues.com/article/67-target-property. This is used to store the user's info across pages so that Appcues can use this information to qualify the user for new content and attach user data to the events we track about the user's interaction with the Appcues content. For info on the events we track, see here: https://docs.appcues.com/article/301-client-side-events-reference
• apc_debug_enabled: This is used to ensure the Appcues debugger remains open across page loads.
• apc_debug_url: This is used by the Appcues debugger to remember the most recently tracked URL in order to help detect installation issues.
• apc_curr_flow: This stores some information about the flow that the user is currently viewing. This is used by Appcues to continue flows across page loads.
• apc_curr_checklist: This stores some information about the checklist that the user is currently viewing. This is used by Appcues to ensure a smooth experience across page loads.
• apc_cl:{checklist ID}: This stores whether a user has seen a given checklist. This is used to automatically open the checklist upon first view or to keep the checklist collapsed upon subsequent views.
• apc_followed_test_link: This stores whether the user followed a Test Mode link to the page. This is used by Appcues to show a flow to the user through Test Mode.

We store one cookie temporarily, depending on usage:

• apc_next_content_id: When a new flow is configured to be triggered after a page redirect after another flow, then Appcues stores the ID of the flow in this cookie so we can know the ID of the flow to show when the redirect is complete. We then remove this cookie, so it is very short-lived. This cookie has an expiration time of 60 seconds. It is set on the domain matching the customer's site, so it is considered a first-party cookie and cannot be used for cross-site tracking.