Yext Pixel and Cookies in Pages Product Offerings | Yext Hitchhikers Platform

Optional Technologies

At a client’s request, the following optional pixel and optional cookie may be deployed with Pages:

Analytics Pixel

An optional analytics pixel (called the Pages pixel), which consists of an <img> tag that sends data to the following endpoint: www.yext-pixel.com.

The Pages pixel processes pageview events and click events and is used to determine how many times a page has been viewed, and by how many unique visitors. The pixel is able to integrate with any CMP (consent management platform), and can be opted-out via CMP as needed. The Pages pixel lasts for a session and is considered to be first party.

An optional analytics tracking cookie (_yfdc), which can be used to associate user events with a unique cookie ID (refer to our training for more information). This sends data to the following endpoint: realtimeanalytics.yext.com/conversiontracking. When this tracking cookie is enabled, a cookie will be set in the browser called _yfdc, and it will send the cookie value to the Pages analytics system along with all tracked events. This tracking cookie is able to integrate with any CMP, and can be opted-out via CMP. This first party cookie lasts for 90 days.

Automatically Deployed Cookies

The following cookies are automatically deployed:

  1. Cloudflare session cookie (__cf_bm) from Cloudflare is deployed with all Pages products to help protect against bot traffic (refer to Cloudflare’s documentation for more details).
    1. As this cookie should be considered to be strictly necessary (it is used for security purposes, specifically detecting and protecting against malicious bots and preventing DdoS attacks), it should not require consent. The cookie notably contains information related to the calculation of a bot score, which is used to detect malicious bots.
  2. When a client wants a site to be private and gated behind security settings (refer to our Authentication documentation to learn more), Yext “Secure Sites” session cookie (securesites) is deployed to identify user sessions. This cookie is strictly necessary in order for the security settings to work properly.
    1. For sites protected by password protection, cookie expiration occurs after 7 days.
    2. For sites protected by OIDC, expiration occurs after 2 hours, but can be renewed via refresh token transparently with the relevant OIDC provider.
Feedback