Country Enricher
When the input file does not contain anyCountry column, you can choose a Country from the catalogue fields without a corresponding input column. You can then select this enricher to hardcode a Country value for all user data in the source. You can choose this option when all data belongs to the same Country.
However, if you do not wish to hardcode a Country column, then this enricher also allows you to map the Country column in the input file to the following formats:
-
2 Letter ISO Country Code – If the input file contains a
Countrycolumn with values in the standard alpha ISO 2 letter Country code format, then you can set the mapping and add this enricher. Some sample Country values under the Alpha ISO 2 Country codes are as follows:- Spain - ES
- France - FR
- United Kingdom - GB
- Italy - IT
- Germany - DE
- India - IN
- United States - US
- Canada - CA
-
3 Letter ISO Country Code – If the input file contains a
Countrycolumn with values in the standard alpha ISO 3 letter Country code format, then you can set the mapping and add this enricher. Some sample Country values under the Alpha ISO 3 Country codes are as follows:- Spain - ESP
- France - FRA
- United Kingdom - GBR
- Italy - ITA
- Germany - DEU
- India - IND
- United States - USA
- Canada - CAN
-
Name of the Country – If the input file contains a
Countrycolumn with the name of the Country, then you can set the mapping and add this enricher. The incoming value must be the exact name of a Country to find its corresponding 3 letter ISO country code.
Note:
- For more information about the 2 and 3 Letter ISO Country Code, refer to List of ISO 3166 country codes.
- To know more about how to configure this enricher, refer to Configuring Country Enricher.
Timestamp Enricher
Collect supports epoch timestamp format for all date and timestamp fields. Therefore, if your input data contains any other timestamp or date formats, the same can be translated by simply adding the Format Selector and choosing the exact date or timestamp format of the values in the input column. It is automatically converted to epoch timestamp while ingesting. This provides more flexibility when it comes to audience creation down the line. The table below lists all the formats that can be selected for input values.| Value | Format |
|---|---|
| 31/12/2020 | dd/MM/yyyy |
| 12/31/2020 | MM/dd/yyyy |
| 31-12-2020 | dd-MM-yyyy |
| 12-31-2020 | MM-dd-yyyy |
| 2020.12.31 | yyyy.MM.dd |
| 20201231 | yyyyMMdd |
| 1623090782 | epoch timestamp |
| 2006-02-15T05:03:42Z[UTC] | yyyy-MM-dd’T’HH:mm:ssX’[‘z’]‘ |
| Wed, 4 Jul 2001 12:08:56 -0700 | EEE, d MMM yyyy HH:mm:ss Z |
| 010704120856-0700 | yyMMddHHmmssZ |
| 2001-07-04T12:08:56.235-0700 | yyyy-MM-dd’T’HH:mm:ss.SSSZ |
| 07/04/2001 12:09 | MM/dd/yyyy HH:mm |
| 10/08/2021 00:00 | dd/MM/yyyy HH:mm |
| 2021-06-16 06:32:00 | yyyy-MM-dd HH:mm:ss |
| 1/2/09 6:17 | M/D/yy H:mm |
| 2011-12-03T10:15:30+01:00 | yyyy-MM-dd’T’HH:mm:ss[xxx] |
| 2011-12-03T10:15:30+01:00[Europe/Paris] | yyyy-MM-dd’T’HH:mm:ss[xxx]’[‘VV’]‘ |
| Wed, Jul 4, ‘01 | EEE, MMM d, ”yy |
| 2001.July.04 AD 12:08 PM | yyyy.MMMM.dd GGG hh:mm a |
| 2001-07-04T12:08:56.235-07:00 | yyyy-MM-dd’T’HH:mm:ss.SSSXXX |
| 2021-08-23 09:34:25.566946 UTC | yyyy-MM-dd HH:mm:ss.SSSSSS z |
| 2021-02-20 10:27:12 UTC | yyyy-MM-dd HH:mm:ss z |
| 2022-03-18T16:45:45Z | yyyy-MM-dd’T’HH:mm:ssX |
| 1975-06-07 02:00:00.000 +0200 | yyyy-MM-dd HH:mm:ss[.n] [Z] |
Note:To know more about how to configure this enricher, refer to Configuring Timestamp Enricher.
Value Mapper Enricher
Some of the data captured in the sources are in the rawest form. This includes data in a binary form or representing some code that cannot be easily referred to. Therefore, these codes must be transformed into values that can be easily consumed. The Value Mapper enricher solves the above-mentioned problem. It allows you to map the raw data value of a source to a different value as per your requirement. This implies that you can map an incoming value to a value that the end-user can view and consume. For example, as part of the source data, if user consent is captured as1 or 0 (where 1 means yes and 0 means no) then using the Value Mapper enricher, the data can be stored as yes and no in Zeotap.
Note:You cannot add the Value Mapper enricher for the Country and ID fields. To know more about how to configure this enricher, refer to Configuring Value Mapper Enricher.
Custom Field
At the time of ingesting data, if you want to add a flag to the data that is not available as part of your source data, then you can define a custom field by applying one of the following two enrichers:- Hardcode enricher
- Derived enricher
Hardcode Enricher
This enricher allows you to define a fixed value for all the records ingested as part of a source. If a source field is not available, then you can add a custom field and hardcode a value. Following are the scenarios for which you can add a custom field:- To identify the audience
- To filter the data while creating the segment
Note:To know more about how to configure this enricher, refer to Configuring Hardcode Enricher.
Derived Enricher
At the time of ingesting a record, you may want to derive a field based on the input fields of the same source. This can be achieved by using the Derived Field enricher.Note:To know more about how to configure this enricher, refer to Configuring Derived Field Enricher.