Welcome to the Spring ‘22 Release!
As always, the Spring Release is packed full of features across the entire Yext platform. In these release notes you will find every feature released as part of the Spring ’22 release.
We’re unveiling a modernized Posting UI in the Yext platform that will provide a more intuitive user experience. This enhanced interface offers seamless navigation between important posting actions, while maintaining modern design standards.
The new UI also presents some added functionality we could not previously support, including:
We can now support embedded fields from Knowledge Graph in the body of Facebook and Google Local Posts. This is particularly helpful if you are posting to several locations at once, because fields like phone numbers and addresses differ for each location. Embedding fields allows you to post the same message to each location, with dynamic values for those location-specific fields.
We are adding Social Posting API functionality to our Knowledge API v2. With seven new endpoints dedicated to posting, users can create and update dynamic social campaigns across multiple entities at once and monitor how their customers engage with the content through comments, click, and impression metrics. This new version will support CRUD operations on social posts. Most notably, users who integrate directly with our new Posting API will benefit from the following expanded functionality:
A Listings subscription is required to utilize the Posting endpoints.
In the Winter ‘21 Release, we added more visibility and control to your Listings publishers with the launch of Publisher Tabs and Publisher Detail Pages. Now we are extending those same offerings to all publishers in our Knowledge Network, regardless of whether they support Listings or not.
This means that publishers who only support Reviews and Posting will now have their own Publisher Detail Page and appear on the Publishers Tab. It also means that in situations where a publisher supports Listings, but you have only purchased a Reviews or Posting subscription from that publisher, they will now have their own Publisher Detail Page and appear on the Publishers Tab. With key information gathered in one place for all publisher types, it will now be even more convenient to accomplish tasks like linking accounts or choosing Listings matches during onboarding.
We are introducing a series of new filtering capabilities on the ‘All Listings’ page that will enable additional options for viewing the exact set of Listings you want to action.
We have announced to partners that the
has_hours fields will be removed from the GET: Scan Result (API v2) endpoint on May 2, 2022.
On this date, we can:
In the Winter ’21 Release, we introduced configuration tabs within select Publisher Detail pages that allow users to customize their sync settings with that publisher. You can enable or disable the sync of certain fields and change the default Knowledge Graph field mapped for certain publisher fields.
This release, we’re updating the Google Publisher configuration settings tab to include:
With the introduction of configuration within Publisher Detail pages, we wanted to make it easy for parent accounts to control the sync settings of any existing or new sub-accounts. Administrators will now have the convenient option to apply the settings of the parent account to its sub-accounts. You can even make separate choices to override the settings in existing sub-accounts versus applying these sync settings to any new sub-accounts created in the future.
This will be particularly helpful for our partners who manage sub-accounts because they can save time configuring sync settings across all accounts.
Viewing all of your reviews, as quickly as possible, within a single platform, helps you to track trends and efficiently engage with your customers. Now, in addition to receiving real-time notifications for new reviews on Google, Yext will now perform daily backup scans to ensure all new Reviews are identified within a 24-hour window.
We’ve made it easier to manage and monitor Saved Filters used throughout the Yext platform. UX enhancements give users a simplified button interface to update, save, and toggle between Saved Filters. Users can also now see a table overview of existing Saved Filters, including how many entities are in each filter and which systems each filter is in use by.
The process for updating saved filters which are currently in use by downstream systems (Pages, Answers, etc) also now includes a final confirmation modal that describes the impact of proposed changes before they are made. Now whenever administrators are making edits to Saved Filters, they are better able to prevent unintended changes to important Yext systems.
With this release, it’s now easier for administrators to manage relationships in the Knowledge Graph. Previously, Knowledge Graph supported relating entities using the Entity Relationship field type, which defined a relationship in a single direction. We’ve upgraded entity relationship with the introduction of a dedicated Relationship Field Type that supports both one-way and net-new two-way relationships. Now users can create dedicated two-way relationship fields; relating one entity to another in a two-way relationship will also result in a relationship being created in the opposite direction, so that the relationship is stored on and accessible from both related entities.
For example, two-way relationships are necessary to accurately represent healthcare systems in the Knowledge Graph. Healthcare users want the ability to relate healthcare professionals to the different specialties they treat — but, they also know it’s important for their patients to be able to find doctors by referencing a specific specialty to see its related doctors. It’s important to have this relationship be registered properly on either side for a flexible user experience downstream.
In this release we’re giving developers more tools to handle data management flows with the ability to Create Suggestions via API. Now users can programmatically create suggestions, making it easier to manage data wherever it is centrally controlled. This provides added flexibility for users working with multiple sources of data and necessary layers of control for teams focused on data compliance.
With the Spring ’22 release we have defaulted “Show Changes” in Suggestion Settings to be enabled for all accounts. As the new default, users will be able to view all versions of fields with suggested edits. For some applicable fields, the changes will be shown with highlights, underlines, and strikethroughs, making it easier for users to identify what changes have been made. Although we will be defaulting this setting on, users will retain the option to opt out in Suggestion Settings.
Knowledge Graph has supported a single built-in price field for quite some time. We have just created a built-in field type for price, allowing users to create new custom fields of type Price. This field type is a struct type made up of two sub-fields: a Value field for the numerical price, and a Currency field, which is a single-select from a list of known currencies.
Now users will have more freedom to create custom price fields which conform to a standard price type.
Historically, the Custom Fields API has been permissioned by a combination of Entities API Permissions and an app-level setting called Custom Fields Behavior. In order to support more granular permissions, we have added a new dedicated Custom Fields Permission Group. The combination of Entities Permissions and Custom Fields Behavior will continue to grant the same access to the Custom Fields API.
|Custom Fields Get/List (Read Operations)||
|App can read all custom fields|
|Custom Fields Create/Update/Delete (Write Operations)||
|App can write to any custom field|
The Custom Fields Behavior Setting is no longer settable with the new Developer Console UI, and always defaults to None. As such, any new Apps should use this new Custom Fields Permission Group in order to obtain access to edit custom fields via API.
The display name for Google Account ID has been updated to Google Location Group ID. This name more accurately reflects the purpose of the field, which is populated by Yext with the Google-assigned Location Group ID once a connection is made between a Yext entity and a Google listing.
The ID of the field will not be changed, so this will not impact any API integrations or Configuration as Code resources. This change will also not impact any saved upload configurations, export configurations or saved filters.
Our new Search Merchandiser is an easy way for administrators to modify their search results in Answers experiences using a drag-and-drop, point-and-click interface. This tool allows you to: reorder entities, reorder verticals, and change featured snippets directly within the search results.
This will be particularly useful for Administrators who aren’t familiar with Yext’s Query Rules and Experience Training, or those who simply prefer to modify results through a quick and easy visual interface.
Example use cases:
Developers can now execute arbitrary TypeScript functions within Query Rules in order to power brand new use cases in Answers. By integrating external APIs, we can return real time data in search. Ever-changing data like stock prices, product inventory, package tracking updates, or service outages are not static data points that you would typically store in your Knowledge Graph, so it’s crucial that we can fetch them from these external data sources.
Now, with Serverless Functions in Query Rules, a developer could configure an experience where users can ask questions like: “what’s your company’s stock price?” or “Is the blue soccer ball in stock in Soho?” or “where is my package?” or “Is there an outage in my neighborhood?” and expect realtime, accurate answers.
We are introducing a new vertical ranking model based on the same powerful embedding technology we use in . Verticals are now assigned a “Semantic Vertical Score” from 0 to 1 based on how relevant that vertical is to the user’s query. This score allows us to present verticals in the most relevant order for a user’s query on a more consistent basis.
Additionally, we are introducing 3 (optional) configurable inputs for Administrators looking to train the Vertical Ranking model within their search experience, including:
In the Winter ’21 Release, we introduced Answers Headless React as a new option for developers looking to build a bespoke Answers frontend quickly. You can find examples of how to use Answers Headless React in our Site Search Starter sample app.
Building on and the Site Search Starter, we’re now launching the Answers React Components. This offers React developers an even easier way to get started with Answers React because you can incorporate our search components into an existing project, without needing to copy the components from our Site Search Starter. The library can be accessed via npm or Github in beta. Version 1.0.0 will be cut with General Access in May.
We have made a number of updates to our faceting framework to better support numerical facets and hierarchical facets.
Now, Administrators using our Hitchhikers Theme can set facets that contain numbers, which is particularly useful for price ranges, multipack options, and more.
Additionally, Answers Headless React and the new Answers React Components now support a range filter for numbers and hierarchical facets, commonly found in e-commerce experiences. If a user selects a value that falls under another category, the parent categories will automatically be applied as filters. For example, when “Hats & Caps” are selected as a filter, “Accessories” as the parent category will also be applied.
As of the Spring ‘22 Release, our Extractive QA model is compatible with English, Japanese, French, German, and Spanish Languages.
is now able to support French, German, and Spanish languages. Search experiences in these languages will benefit from more accurate results, because the Answers Algorithm can detect the true meaning behind each query and determine the most relevant entity to return.
With the new Answers Hitchhikers Theme 1.29 and Answers Search UI SDK 1.14, we’ve added support for RTF truncation, custom autocomplete prompts, number facets, and more.
You can find the full list of features and bug fixes below, with additional details available in their linked Community posts.
universalLimitfor Vertical Grid Templates to three.
In case you missed it, we have also released Hitchhikers Theme since the Summer Release. The good news is that each theme builds on top of the previous theme, so you’ll be able to access all of these helpful features when you upgrade to Theme v1.29.
We’ve recently introduced a lot more layers to our frontend stack (including Answers Core, Answers Headless, and Answers Headless React). With this release, we’re now tracking the version of those libraries being used in your experience. This opens up more helpful debugging resources and the option to support additional version-dependent analytics features in the future.
It is now even easier to duplicate the backend configuration of your Answers experience.
Just select the existing Answers experience in your account that you want to duplicate, and then check off which entity types you want to include in the duplicate.
If you’ve built a custom Answers frontend, such as via Answers Core or Answers Headless React, you can now take advantage of the Analytics Library for Answers to easily enable click analytics. This networking layer makes it easy to hit Yext’s analytics endpoints. Check out the repo .
With this update, you can now restrict the results of a Store Locator to a particular country.
For example, if you have stores in Naples, Florida and your customers search for Naples, the locator may interpret this as a search in Italy!
Now, you can set the Country Restriction parameter to a particular locale code (e.g., “US” for United States, “IT” for Italy).
This enhancement will not impact any currently live locators. If you’d like to use it, simply open your Store Locator Module and set the Country Restriction parameter.
Users now have the option to display the full address for each location that appears in their “Nearby Locations” module.
Previously, the Nearby Locations module would only show Address Line 1 by default, but now users can toggle whether or not the full address profile shows up.
We’re continually making improvements to Answers search term clustering to make it even easier to identify what your customers are searching for on your experience.
In this release we made updates to our cluster generation process to take advantage of our new embedding model as well as introducing a new input (the number of search terms your experience receives) to help better identify clusters.
For example, these improvements made to clustering will ensure that search terms like “auto loans,” “car loans,” and “vehicle loans” — while different terms — are clustered together as they all contain the same underlying user intent.
The release of Logs API will enable users to get event level data out of the platform in raw form in near real time.
With Logs API, customers will be able to fetch, filter, and sort a log of the events conducted on their Yext experience(s) which can be used to extract data from Yext for offline analysis or to embed analytics in the places you need them most.
For example, if a user were to begin their journey on a Yext experience and ultimately creates a support ticket, you can embed that user’s activity (Searches, Clicks, and Viewed Content) into your ticketing platform to better understand the actions that led up to a customer submitting a ticket.
Logs API currently returns Analytics events for Answers and Pages, but will expand to support even more parts of the platform in the future.
When creating custom dashboards or reports in the Analytics platform, users can now add search term word count as a filter or dimension. This provides a helpful tool for users looking to understand how queries may vary between longer and shorter searches.
Previously, users could only dimension Analytics metrics by only one of the All Entities, Folders, or Labels dimensions at a time. With this update, we now allow users to combine the All Entities, Folders and Labels dimensions with any applicable Analytics metrics interchangeably.
Count of Searches and Search Terms by Search Term Label
Count of Searches by Search Term where Has Direct Answer = True
Count of Clicks by Vertical Position
We’ve updated our Connectors framework to support access to APIs that require OAuth 2.0 authentication. Previously, these connections required users to build and host an integration with these sources outside of Yext. Now our Pull from API Connector source supports these integrations through a simple, no-code interface. This makes new Connectors for sources with OAuth, like Google Drive and Salesforce, available for users to integrate with on the Yext platform.
Updates to the Crawler now enable administrators to crawl PDF files from websites so that their contents can be stored and made searchable with Yext algorithms. This allows users to more completely store the contents of a website to a Knowledge Graph for a comprehensive site search experience.
When preparing data for ingestion into the Knowledge Graph, users may need to exclude data that is outdated or not relevant. For added flexibility, we have added a new transform tool that lets users specify columns they would like to ignore when loading data into the Knowledge Graph.
Now you can use Connectors to easily ingest Multi-Language data and store it in corresponding Language Profiles. The updated Connectors workflow now allows users to specify the primary Language Profile and create and edit alternate Language Profiles using any source, including the Crawler and API integrations.
Today, users can configure “Pull from API” Connectors to make HTTP GET requests. While this covers most standard “Pull from API” cases, we have also seen a need to support POST requests with a request body.
Yext can now support POST requests such as: Support for GraphQL - if a user wants to fetch data from a GraphQL endpoint, they’d need to make a POST request and supply a body.
This new feature will allow users to fetch data from any endpoint.
Yext now supports listings for locations and professionals on we shop local. This API-based integration supports photos, hours, holiday hours, duplicate suppression, real-time updates, and more.
Yext now supports listings for locations and professionals on Seznam. This submission-based integration supports NAP, lat/long, business description, hours, and more.
Yext now supports listings for healthcare professionals on Healthline. This API-based integration supports NAP, real-time updates, professional description, hours, holiday hours, specialties, and more.
Yext now supports listings for locations and professionals on goudengids.be. This API-based integration supports NAP, special offer, hours, review monitoring, and more.
Yext now supports Apple Service Hours on Apple Maps. Apple Service Hours are used to describe hours of operation associated with a specific service or line of business.
Apple accepts the following hours types (which already exist as built-in fields in Knowledge Graph):
Goldenpages.ie now supports review monitoring.
eirphonebook.ie is rebranding to become phonebook.ie.
TelephoneCity is expanding its country support to French Guiana, Guadalupe, Martinque, Mayotte, and Réunion. It is also expanding support for Review Response.
Yext’s integration with TripAdvisor now supports listings for hospitality brands. When using the Hotel entity type in Yext, businesses now can sync hospitality-specific fields on TripAdvisor, like if breakfast is included, or if you have a pool on property.
The following publishers now support listings in Cook Islands, Democratic Republic of Congo, and Liberia:
We have expanded the number of publishers that support search impressions, profile views, and featured message clicks.
As of May 11, 2022, Superbranchen will be removed from the Knowledge Network.
Customers can now use the new SkillJar Course Connector to add their courses in SkillJar as structured data in the Knowledge Graph. This makes it easy to surface content from SkillJar courses across experiences powered by the Knowledge Graph, such as Answers search.
With the new NHS Common Health Questions Connector, you can pull in nearly 150 frequently asked questions related to topics such as infections, medicines, pregnancy, and more. Use this connector to bring in these questions and answers as FAQ entities into your Knowledge Graph.
With the Slack Private Content Connector, users can now pull in private Slack channels, messages and threads from a Slack workspace, as well as users in a workspace. On install, users can choose which data from Slack they want to pull into the Knowledge Graph.
The new Allpoint data connector allows users to ingest ATM location information with just a few clicks! After downloading the app, users will simply need to provide their Allpoint API username and password – the connector will automatically ingest ATM information, including but not limited to address, phone number, cash withdrawal limit, and surcharge fee.
This new analytics app includes three preconfigured dashboards purpose built for our Support Search solution set. Specifically, you’ll see distinct dashboards for Help Site, Case Deflection, and Agent Desktop search. Now you can see how each of your search bars is performing in isolation, even if they are all based on the same search experience.
The new WordPress Connectors use the new WordPress Connector Sources to pull in Pages, Posts, and Media from your WordPress site. The connector includes pre-built WordPress entity types so you can pull in your WordPress data with a few clicks. Each connector will pull in a different entity type, so you will have to install each one if you would like to pull in different types.
With the new Yext AI Search for Wordpress plugin, you can now easily add Yext Search to your WordPress site. Installation is quick and simple — download the , then add the search bar and search results page to your WordPress site by dragging and dropping Gutenberg Blocks! No code or custom integration work required.
what3words is a global addressing system that provides the simplest way to communicate location. It has divided the world into 3 meter squares and assigned each one a unique address made of just 3 words. It is more accurate than traditional street addressing, and even allows location information to be captured for places without addresses, such as parks or beaches. The seamless integration between Yext and what3words allows businesses to populate in real-time what3words addresses to their database and use them on listings. With what3words, users can save time in finding their corresponding what3words address for each of their location entities like retail stores, offices, etc. This app will be available by General Access.
Multiple Configurations for Redox Review Generation Now Supported
Users who have downloaded the Redox app are now able to apply multiple Review Invitation configurations on their healthcare professional and facility entities. Whereas before, users could only set one contact method (text/email) and delay option for all of their healthcare entities, now users can set as many configurations as they’d like. Users simply create labels to categorize their entities in the Knowledge Graph and then apply different Redox configurations to these labels during the app installation flow. Note that the different labels should not contain any of the same entities. This will be available by General Access.
Each of the updates for Salesforce will be available by General Access.
Support for Authorized Search
Yext AI Search in Salesforce now supports authorized search, meaning that search results can now respect user-level Salesforce permissions. For more information on Consumer Authorization, you can review our guide .
Improved Admin UI
We’ve added a custom admin UI to make it easier than ever to configure your Yext search experiences within Salesforce.
Expansion to Salesforce Platform
Add Yext AI Search to any one of your products built on the salesforce platform. This notably excludes Digital Marketing Platform and B2C Commerce.
Custom Visualforce Tab
We’ve included a custom visualforce tab to the package so users can view a full-page search experience, wherever they are in Salesforce.
Search Triggers for Agent Desktop
You can now select one or multiple case fields to trigger a search within the agent desktop component.
Result actions now allow agents to seamlessly interact with their page or chat with a single click. Options include: Copy Result Link, Copy Result Text, Attach to Case, Send to Chat, Send to Chatter, Attach as Note. These options display dynamically based on which page the agent is on (case vs. chat) and which features they have enabled (chatter, notes).
Yext Objects in Analytics
You can now also report on result actions, directly within Salesforce. See how agents are leveraging Yext results to solve customer questions.
Agents can now view related Salesforce cases within a separate tab, powered by Yext Search.
Agents can now view related Salesforce knowledge articles within a separate tab, powered by Yext Search.
Query Source Analytics Dimension
We updated the configuration to include an integration source for all of the Analytics events occurring in the app for more accurate reporting into the Yext platform. If you are using the Zendesk app, you can now filter to the “AGENT_DESKTOP” integration source and see the Analytics specific to the app.
By following the updated , you can now add interactivity between the subject line of your ticket submission form and the search experience on your page. Previously, the option for interactivity was only available between a category field and your search experience.
We also updated the configuration to include an integration source for all of the Analytics events occurring in the app for more accurate reporting into the Yext platform. Updated instructions are included in our .
Easily fetch your Wordpress Posts, Pages, and Media with the new Wordpress Connector source. Yext can fetch both public or private content. If private, we require that the user supplies a username and password.
We’ve added a new Google Drive Connector Source that allows you to pull in content from your Google Drive account. In order to use this source, you must first link your Google Drive account to Yext via OAuth. With the source, you can pull in the metadata for all of the different file types you have in Google Drive. For Google Documents, you can additionally pull in the document content.
We’ve added a new Salesforce Connector Source that allows you to pull in content from your Salesforce account. In order to use this source, you must first link your Salesforce account to Yext via OAuth. With the source, you can pull in all records of a given object type by simply providing your Salesforce Instance URL and the ID of the object.
We’ve added a new Contentful Connector source that allows you to pull in content from your Contentful Space. With the source, you can pull in all of the different content types you have in Contentful.
With the new Bizzabo Connector Source you can now pull in events from your Bizzabo account, and speakers, partners, and sessions from a Bizzabo event.
The Zendesk Source now supports pulling authenticated help articles and community posts. Additionally, we’ve added support for authenticated and unauthenticated categories and sections from your Zendesk Help Center.
There is now a new look and feel to the Yext platform, including a redesigned navigation and a modernized Built-In Home Screen. With this release, the platform interface has been upgraded with a new left navigation that can be collapsed/expanded for added flexibility. Here, each platform feature can be accessed in a collapsible section, making it even easier to switch between feature groups while working in the platform. The left navigation also includes two updated productivity features — Favorites and Quick Find — that help users find what they need to carry out their day-to-day actions in Yext.
We added a Favorites feature at the top of the new left navigation. Here, users can pin their most visited pages by simply clicking the star icon at the right of the page name in the navigation. By grouping a list of most frequently visited pages for easy access, users are enabled to stay more organized and work more efficiently on the Yext platform.
We’ve also upgraded Quick Find search in the platform to make it more useful and intuitive. Quick Find is now at the top of the new navigation and it includes new shortcut functionality. Users can press Command+K (Ctrl+K for PC) to both open and close the Quick Find modal. Also, pressing Command (or Ctrl) with a click will now allow users to open Quick Find results in a new tab. This will make it easier for users to find what they need quickly and build with Yext’s interconnected systems.
The Yext platform Built-In Home Screen has also been redesigned to better serve the day-to-day needs of its users. In addition to cosmetic enhancements, the new Home Screen offers users quick access to account metrics, suggested actions, Hitchhiker’s content, and more.
While the default, Built-In Home Screen was built to be digestible regardless of the product combination on the account, users also still have the option to configure their own Home Screen customized to their specific needs and preferences.
Altogether, these enhancements make it easier than ever for users to find what they are looking for and build powerful experiences on the Yext platform with as few clicks as possible.
We’ve added support for Live API in the Developer Console Logs UI. Now, when looking at the app logs page, developers will see a Live API tab which displays the logs for Live API calls made.
Yext now requires the user to input their current password when updating their password in Personal Settings. Previously, users saw 2 fields for “Password” and “Confirm Password.” Users will now see “Current Password,” “New Password,” and “Confirm New Password.” When a user is resetting their password, Yext will validate that the current password they entered matches the password recorded for them before allowing them to reset their password.
In order to simplify our taxonomy, better align it with our publisher network, and support more streamlined Answers experiences, we will be consolidating several duplicate categories within the healthcare vertical. Any listings that are currently using the categories set to be deprecated will be switched over to the remaining category; this process should be seamless and will have no impact on your listings.
ACTION REQUIRED: Clients who use the Yext Knowledge API to update their healthcare location and/or providers’ data will need to update their ETL to stop referencing any of the merged categories and use only the remaining categories instead. Failure to do so will result in API errors.
The specific changes can be seen below. This change is set for May 11th, any necessary Yext Knowledge API updates should be completed prior to this date. Please reach out to your Yext point of contact with any questions.
|Merged Category ID||Merged Category Name||Remaining Category ID||Remaining Category Name|
|1505902||Medical Bariatrician||2167||Bariatric Medicine|
|1505880||Breast Medical Oncology||20000002||Breast Medical Oncologist|
|1505912||Pediatric Psychology||1512875||Child Psychologist|
|1135566||Pediatric Internal Medicine||1257||Pediatrician|
|1505891||Family Medicine||1135560||Family Practice Physician|
|20000006||Hematology-Oncology||1505899||Hematology & Oncology|
|1135568||Pediatric Allergist||20000018||Pediatric Allergy and Immunology|
We have updated our Streams localization logic to better align with the localization logic of the Knowledge Graph, such that:
We are vastly improving our support in the CLI for investigating Streams. Specifically, we are introducing some new commands, and updating some existing commands.
|Command||New or Existing?||Details|
||New||Displays the logs for a given Stream. These logs include all records which have been produced by a Stream in the past year.|
||Existing||New name for
Looking to offer customized experiences for your end-users? Would it be helpful to see some ideas of use cases that advanced administrators have built on top of Yext? Check out our to find all kinds of unique projects built on the Yext platform and implemented by talented Hitchhikers.
This release we have made a number of enhancements to Hitchhikers Ideas to make it even easier to share your product feature ideas with Yext’s product team. Enhancements include:
These materials contain non-public, confidential information including information regarding Yext’s upcoming product and feature releases. This confidential information is being shared with you solely in your role as a Yext Hitchhiker. By viewing any part of these materials you represent and agree that you are a Yext Hitchhiker, you will only use this confidential information to enhance your organization’s use of Yext. You further represent and agree that you will abide by applicable securities laws with respect to this confidential information and will not purchase or sell, directly or indirectly, any Yext securities or share this confidential information with anyone when it is reasonably foreseeable that such person is likely to purchase or sell Yext securities. These materials may not be shared or published, in whole or in part, except as agreed in writing by Yext.