Data Mapping Overview| 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.

Content mapping from Knowledge Graph displaying on pages

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.

light bulb
Pages are a great use case for custom fields! If you want to add content to your pages that is not natively built-in to the Knowledge Graph, you can add it as a custom field.

For more details on Custom Fields, visit the Custom Fields module in the Knowledge Graph training.

Updating Content

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.

Content missing on page because of missing Knowledge Graph data

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.

More details for each option are listed below:

Option Functionality Use Case
Constant Value Hardcode a value (Enter in specific text or upload a photo) into the module directly. If you want the value to be the same across all of your webpages. E.g., headers or call-to-action buttons.
Map to Entity Field Select the field in the Knowledge Graph you would like to pull content for the corresponding entity. If you want content to vary by entity. Commonly used for entity-specific information like address, phone number, etc.
Map to Another Entity Select the entity and the field in the Knowledge Graph you would like to pull content from. To display information from one entity across all pages. Examples include an image of the flagship location, corporate-level branding, etc.

Note: Not all modules will have every option available. To identify which options are available for a specific field, click More options.

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.

unit Quiz
+20 points
Daily Quiz Streak Daily Quiz Streak: 0
Quiz Accuracy Streak Quiz Accuracy Streak: 0
    Error Success Question 1 of 2

    True or false, both custom fields and built-in fields can be displayed on Pages

    Error Success Question 2 of 2

    When a field is mapped to an entity, how do you edit the content in that field?

    Way to go, you passed! 🏁

    You've already completed this quiz, so you can't earn more points.You completed this quiz in 1 attempt and earned 0 points! Feel free to review your answers and move on when you're ready.
1st attempt
0 incorrect
Splash Loading