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: (or if you are on Classic Pages ).

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.

Yext Analytics Pixel to Integrate with Your CMP

You can integrate the Yext Analytics pixel with your CMP by calling the function to enable the Yext Analytics pixel. As a summary, this process would go as follows:

  • The site implementer must ensure their website is explicitly opted out of Analytics; for website implemented using Pages, this can be done by setting requireOptIn to true on the AnalyticsProvider component (refer to the component props ).
  • After user’s relevant consent, enable the Yext analytics pixel by calling the function window.enableYextAnalytics();.
  • In other words, a tag to call the function is triggered within your tag manager based on conditional logic on whether the user has consented via your CMP or not.

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: 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.

The __cf_bm cookie from Cloudflare is present in all domains as you go through our Cloudflare setup. For EU-hosted clients, below is a list of possible hostnames. Note wildcards are used so as not to enumerate every subdomain. The most relevant domains for a Pages or Search setup are bolded. The descriptions may help you filter down to a list which is relevant for the client.

  • * (Photo/Assets Serving)
  • * (Yext Analytics)
  • * (Yext APIs)
  • * (Yext platform, legacy API endpoints)
  • * (Yext platform static assets)
  • * (Yext platform static assets)
  • * (Yext white labelled platform)
  • * (Yext white labelled platform static assets)
  • * (Sites placeholder domains)
  • * (Yext Reviews endpoints)
  • * (Sites preview links, bridge domains)
  • * (Classic Pages, legacy bridge domains)
  • * (Classic Pages preview links)
  • * (Classic Pages/Page Builder previews)
  • Any client provided domains/subdomains that are powering a Pages or Search experience
    • For example, branches.[clientDomain].ie

Treatment of IP Addresses for Yext Pages

The Yext Pages Pixel collects IP address information in order to determine the user’s approximate city and country as well as to calculate user sessions. We employ the use of a hashing algorithm to ensure that these IP addresses are obscured after receipt of the analytics event.

Yext also collects IP address information from Cloudflare, Yext’s content distribution network provider, in order to enforce bot-blocking against known malicious bots. To obscure the IP addresses, Cloudflare drops the last octet before Yext ingests the logs into its internal database.

With this treatment of IP addresses, Yext wants to ensure that IP addresses cannot be traced back to individual users. Similarly, Yext does not match IP addresses to other personal data of users, nor does Yext use IP addresses to construct user profiles. Furthermore, this data is only available in Yext’s backend databases to a limited number of employees who have a need to have access to it.