Data Mapping Overview | Yext Hitchhikers Platform
What You’ll Learn
In this section, you will learn:
- How content is displayed on Pages
- An intro into the three ways to map data
- Pages behavior when content is updated
As you learned earlier in the training, each page consists of a series of modules, and modules are made up of module parameters. When you are editing these parameters, there are two ways to display content. You can enter hard coded content, or display content dynamically.
When module parameters are configured to display content dynamically, they will pull content from a field in the Knowledge Graph.
This means that any content that is added to the Knowledge Graph can be displayed on your pages. This includes both built-in fields and custom fields.
In order to update content on your pages that is configured to display dynamically, you will need to update the content in the Knowledge Graph.
This highlights one of the reasons why it is important to preview the page for each entity. You want to ensure that the page looks correct based on the information that is being pulled in from the Knowledge Graph.
If content is added or removed from a field in the Knowledge Graph which is mapped to your pages, that content will automatically be added or removed from your Page.
Ways to Update
When configuring modules on your page, there are a few different ways to choose which content they will display. You can add static content, which allows you to display the same text or image on every page. You can also choose to pull content from your entities. This means that each page will dynamically display entity-specific information like the location address, or the start time for an event. You also have the option to pull content from one specific entity and display that across all pages.
Not all modules will have every option available. To identify which options are available for a specific field, click More options.
More details for each option are listed below:
- Method: Enter text or upload a photo into the module directly.
- Use case: To display the same content across all your pages using that module (e.g. a standard header or call-to-action button).
Map to Entity Field
- Method: Select a Knowledge Graph field to pull content for the corresponding entity. The entity being referenced may change across different webpages.
- Use case: To display content corresponding to the relevant entity (e.g, a location’s address).
Map to Another Entity
- Method: Select a field on one specific entity in the Knowledge Graph to pull content from.
- Use case: To display content corresponding to a single entity across all pages (e.g., image of the flagship location, corporate-level branding).
Each module parameter has a default behavior. Some will default to a constant value, some will default to a mapping option. However, these are suggestions to help you get started. You can adjust each module parameter accordingly based on your content strategy.