Some technical questions we’ve received about the Answers product are answered below. For more information about Answers, refer to the Answers Overview
on the Hitchhikers site, or contact your Client Success Manager.
What is the high-level architecture of the Answers product? Where is it located?
The content in Yext’s Knowledge Graph (KG), along with the infrastructure used to update the data stores used to serve answers, is served from a private data center in New Jersey. When the knowledge graph is updated, the relevant data are pushed into S3 buckets and Elastic Search indexes in multiple redundant global regions and cached by our CDN, Cloudflare. Yext’s Machine Learning Pipelines run machine learning models on data from a variety of sources, and updates to those models are also published to multiple redundant global regions.
When a consumer starts to type a search, their browser fetches autocomplete results from the Cloudflare CDN cache. This architecture lowers latency for short phrases to ensure that consumers receive suggestions with minimal delay. When the user completes a search it is passed to the federated architecture in the Answers backend to gather and rank answers from the Knowledge Graph, Semi-Structured FAQs, and blue link search providers.
The only time that the answers-serving infrastructure is in contact with the Knowledge Graph is when data is updated. As a result, answers availability is not dependent on KG availability.
How are HTTPS certificates managed?
HTTPS certificates are generated and managed through Cloudflare. When a subdomain is registered in the Pages UI, HTTPS certificates are automatically created and deployed. Because Cloudflare detects that the subdomain has been pointed at Yext servers in DNS, HTTPS certificates can be authorized and renewed without the need for any human intervention.
What kind of monitoring does Yext have on Answers?
Yext uses third-party and proprietary software to monitor all answers traffic. We track and keep historical records for answers-availability metrics like uptime, latency, and timeouts.
If any abnormalities are detected, alerts are pushed to appropriate in-house Engineering teams for review. Critical issues are escalated to a 24/7 on-call rotation that handles emergencies immediately.
Do we provide reporting from our monitoring systems to customers?
Currently, we do not surface reporting from our internal monitoring systems to customers. However, customers can visit https://www.yexttrust.com
/ to view the operational status of the Answers Serving system. From this page, users can subscribe to receive status-update notifications, view upcoming scheduled maintenance periods, and access incident-history logs. Incident reports show the current status of any ongoing system-level events and include postmortem analyses upon incident resolution.
Can customers run regular vulnerability scans on their Answers?
Yes, customers can run their own vulnerability scans on the pages they create with Pages. However, customers should alert Yext before running any scans so that we can anticipate and handle any potential side effects.
What should customers do if they are experiencing problems while publishing pages?
Your Client Success Manager is the first line of defense for any Answers-related issues. If needed, your CSM can escalate urgent problems to Yext Support.
Will Yext drop cookies on our site?
Cloudflare will drop a cookie on your Answers, and Yext will include a tracking pixel. For more information, see Yext’s Data Processing Agreement.
Additionally, if you decide to use Conversion Tracking and enable it on Answers, you will be walked through the steps to select your desired cookie settings and both technical information and usage will be tracked. For more information on Conversion Tracking and privacy, see How to Respect Data Privacy with Conversion Tracking
or Yext’s Data Processing Agreement
Does Yext collect personally identifiable information about Answers visitors?
The Cloudflare cookie and Yext tracking pixel collect IP addresses. For more information, see Yext’s Data Processing Agreement