Manually Mapping Event Types

Last updated on May 30, 2023
On This Page

Hevo provides you an option to manually map Event Types and fields from your Source to the corresponding tables and columns in the Destination. You can map these Event Types by disabling Auto Mapping for the Pipeline during its creation. For such Pipelines, Hevo displays Auto Mapping Disabled in the Pipeline Overview page and sidelines the ingested Events. You can either enable Auto Mapping to automatically map the Source Event Types to the Destination table or map the Events manually. Read Auto Mapping Event Types to know how Hevo handles different data scenarios when you enable or disable Auto Mapping for your Pipeline.

AM disabled

The Event Types displayed in the Schema Mapper page of your Pipeline remain in UNMAPPED state until you enable Auto Mapping or map them manually.

Schema Mapper

Read Auto Mapping Event Types to know how Hevo handles different data scenarios when you enable or disable Auto Mapping for your Pipeline.

The following diagram illustrates the manual mapping process. The steps are also described in detail below.

Manual Schema Mapping

Perform the following steps to manually map an Event Type to a Destination table:

  1. In the Schema Mapper page, select the Event Type you want to map.

    Unmapped ET

  2. In the Mapping Summary section, click CREATE TABLE & MAP.

    Create Table and Map

  3. In the mapping page that appears, Hevo suggests the Destination table name and the fields that can be mapped to the Source Event Type field. In this page, you can do the following:

    Mapping manually

    • Map to a different table: Specify the Destination Table Name to which you want to map the Source Event Type.

    • Modify the order of fields in the Destination: Click the upward (Upward arrow) or downward (Downward arrow) arrow to define how you want to organize the fields in the Destination.

    • Skip a field: Select the check box corresponding to the fields to skip them for ingestion and loading.

    • Map to a different field: Specify the Destination Field Name to which you want to map the Source Events.

    • Map to a different data type: Select the Data Type that you want to use for the Destination field above. Read Schema Mapper Compatibility Table to know about the data type that may be compatible with your Source field.

    • Select the primary and other keys for your table according to your requirements. Refer to your respective Destination documents to know about the keys available for it.


      • It is not mandatory to select these keys. However, their absence may cause issues with data replication and querying in your Destination.

      • Except for the primary key, all keys displayed on the UI are subject to change based on the Destination for which you created the Pipeline.

  4. Click CREATE TABLE & MAP.

    Repeat the above steps for all Event Types that you want to map manually.

When you disable Auto Mapping post-Pipeline creation, you can modify the existing mapping for Event Types. Read Modifying Schema Mapping for Event Types for the steps to do this.

See Also

Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
May-03-2023 NA Added the manual mapping process flow diagram.
Mar-09-2023 NA New document.

Tell us what went wrong