Is the Channel99 Tag on page?

The Channel99 Platform will show the overall Tag status in the Health Center within the Settings tab but this will indicate if the Tag is placed and firing on any page of your website. To assess if a specific page has the Channel99 Tag placed, follow these steps. 

Steps for confirming the Channel99 Tag has been successfully placed

1. Go to the Page URL you would like to check
2. Right click and choose "Inspect"
3. Click the "Network" tab in the Inspect window
4. In the search field enter "c99"
5. Reload the page.
6. If you are able to see the following "api.c99" request URL, the Channel99 Tag is onsite.  

Questions about the C99 Tag

What data does a Channel99 cookie store?
The Channel99 cookie stores an alphanumeric identifier in UUID format (c99_user_id). Based on the tag code, the cookie value is a pseudonymous identifier and does not itself store directly readable personal data.
Example: c99_user_id=2b91d4c7-1f88-4a63-a2d9-91c5e73b4f20

How long does the cookie persist?
400 days from creation or refresh. The tag refreshes the expiration on page load.

Is the Channel99 cookie a first- or third-party cookie?
First-party in storage. The cookie is set on the customer website’s top level domain (for example, .customerdomain.com) not on a Channel99 domain.

Is the cookie part of a cookie packet? If so, are the cookies separable by classification (such as functional, advertising, and required)?
The tag creates one explicit cookie: c99_user_id. This cookie is separable and identifiable as a single cookie. It is generally best described as a measurement or attribution cookie.

What parties will access Channel99 cookie data?
The customer website environment and Channel99, acting as the service provider/processor for measurement and attribution.

What is the root domain of the Channel99 cookie?
The root domain is the customer site’s extracted top-level/root domain. The cookie is set on that domain in the format .<customer root domain>.

Security details: Detail the path for the cookie and justify where / is used.
The cookie is set with Path=/, making it available across the entire website rather than restricting it to a subpath. This is used so the identifier remains consistent across all pages where the tag fires and attribution can persist site-wide.

Detail whether the cookie flags HttpOnly or Secure are set and, if not, provide justification.
Secure is set. HttpOnly is not set. HttpOnly cannot be used here because the cookie is intentionally created, refreshed, and read by client-side JavaScript. Secure ensures the cookie is transmitted only over HTTPS.