Utilities - DExTr

DExTr is ONEcount’s data exchange and transformation engine. This tool enables data exchanges between any data source or third-party vendor. Establish a data map once and, going forward, easily import and export data in and out of ONEcount’s Customer Data Platform.

This tool the capabilities to map and sync first- or third-party data to ONEcount questions/data fields.

If there are multiple databases with similar fields, DExTr can consolidate the similar datapoints into a single ONEcount question or keep the fields separate. (Example: if the field for ‘Customer ID’ in a legacy database is “CUST_ID” and the field name in a CRM is “CID”, there is an option to have the data consolidated in to the single ONEcount question that may be named “CustomerID”.

If you will be using the Dashboard Feed Report function to generate an automated feed report or will be performing a data import that requires mapping external file questions/data to ONEcount questions/data, you must complete the report mapping here first.

There are three types of mapping in the Mapper: Demographic Mapping and Transaction Mapping.

• Demographic Mapping: Demographic mapping maps external demographic questions/data fields and responses to ONEcount demographic questions and responses.

• Transaction Mapping: Transaction mapping maps external transaction data, e.g. product purchase activity, status, and date formats.

• Engagement Mapping: Activity mapping maps external activity headers, e.g. time on page, URL, impressions, etc. This mapping is used primarily for feed reports for export, or importing activity from another system like an e-mail system.

One or all of these types of mapping may be required, depending on the type of automated feed report you want to generate or the data import you'll be performing.

You can either import a layout file (.csv format) with all of the necessary demographic, transacactional and engagement fields,  and map demographics and transactions directly from that file, or you can manually enter the demographics, transactions, and activities you wish to map to ONEcount questions/data fields, or do a combination of both.

Please Note:

ONEcount questions, response valuess, products and packages must be created prior to performing mapping.

Third-party activity headers currently can't be mapped via an uploaded layout file. They must be mapped manually in the Activity Mapping Area.

OPEN THE MAPPING WINDOW

Select DATA MANAGEMENT from the main menu and the DExTr from the sub-menu.

This will open the Main DExTr Listing Page, as shown below.

CREATE A NEW DExTr MAPPING

Select "Create Mapping" to create a new mapping. This will open the Mapping Builder, as shown below.

To edit an existing mapping, select the Edit icon.
To copy an existing mapping, select the Copy icon.
To delete an existing mapping, select the Delete icon.

Creating a Data Mapping

As you can see, a DExTr mapping consists of the following parts. You may use any or all of these components. The only required component to save the mapping is the mapping Title. All other components are optional.

Navigate across the six tabs at the top of the interface to configure how the customer data platform will interpret and exchange data.

1. Exchange Map - Define Exchange Map

   1. Enter a name and description for this data exchange, then proceed to the next tab (Demographic Fields). 

1. Demographic Fields -  Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.

Define field names (the column headers from the import file) on the left and match them to the ONEcount field on the right.

If the ONEcount field does not yet exist, you'll need to create it using the Question Builder (see “Getting Started” section above).Map Values & Field Response Labels (non-text fields only)

If the response is not a text field and is either a drop down, radio button or check box selection, click the [ Map Values] button in the row under the “Map Responses” column. The Map Values button will open a pop-up window. Listed on the left are ONEcount Response Labels (and values). These are the responses defined for the ONEcount Question paired to the field from the database.  On the right, enter the values that will appear in the import file.  It is very important to map all values, because if a value in the input file is not found in ONEcount, the response for that field will be dropped. ONEcount will not allow external imports to add values to its response table. Also, if the values in your import file exactly match the values that ONEcount has (ie., for the State question, both the import/export file and ONEcount use the two-letter abbreviations) then you do not need to create a mapping.

Define how ONEcount should translate each response using the fields in the right column, ‘Field Response’. DExTr can use the same responses, or you may choose to translate or ‘transform’ data to another format.

(Example: states may be abbreviated with 4 letters in a POS database [Conn., Mass.], while the ecommerce database has two letter abbreviations.)

Optional: add validations for the field to either check for duplicates, require an entry, or verify the format entered to the field.Click “Add” to enter additional demographic fields. 

1. Transactional Fields - Map external transaction data, e.g. product activity, status, and date formats.

• 1. Define transactional fields by entering the field name from the import file, the field type and then match the value of the field to the value in ONEcount by clicking the [Map] button. 

  2. i.e. if the source/import file has a product field called “PUB_TITLE” and the value for current subscribers is “YES” on the import file, but the ONEcount product is “Active Subscriber”, the Package Status Value from the import file should be matched with the Package Status in ONEcount.)

  3. Within the “Map Values” pop up window, click “Add” to define all possible transactional statuses. 

  Engagement Fields - Map external engagement (activity) headers, e.g. time on page, URL, impressions, email opens, registrations, link clicks,  etc. Engagement field mapping is used primarily for exporting feed reports.

• 1. To map engagement values of fields, define the engagement field name (the column header from the import file) and match it to the engagement type in ONEcount. 

  2. If the Engagement Field Value is a metric that is not a count, click the [] icon to map the metric field value to the ONEcount metric

     (i.e. if the source/import file has an ‘Engagement Field Name’ that is “NEWSLETTER_ACTIVITY_TYPE” the ‘ONEcount Engagement’ would be “Metric >> Activity Metric Name” and then map the values of metric type [“OPEN”, “CLICK”] to the ONEcount metric [“Email opens”/”Email clicks”]). 

5.    Static Fields

1. *Optional Step: If a column and values needs to be added for identification, record keeping, sourcing, etc. purposes, DExTr can append data to each row.

2. Define the “Static Field Name” which will be the column heading on the export file (i.e. “DATA_SYNC_NAME”), and then the value of the static field (i.e. “CRM_SYNC”). 

3. Click “Add” to create additional static field appends. 

6.    Re-order Fields

1. *Optional Step: If the order of the columns needs to be re-arranged for the order in which they appear on the export from a data feed: simply drag and drop the order of fields by clicking and holding the field labels.

Transaction Mapping is done the same way as Demographic Mapping by using the drag and drop functionality to match Third-Party transaction values with ONEcount transaction values.

There are four Mapping Areas for Transaction Mapping:

• Product Mapping Area

• Product Status Mapping Area (optional)

• Subscription Mapping Area

• Date Mapping Area

NOTE THAT MAPPING IS ID TO ID IN TRANSACTION MAPPING. THE ID IS FOUND IN PARENTHESIS AFTER THE TEXT IN THE "THIRDPARTY..." COLUMN OF MAPPING AREAS.

AS WITH DEMOGRPHIC MAPPING, ONECOUNT PRODUCTS, PRODUCT STATUSES, AND SUBSCRIPTION TYPES MUST BE CREATED PRIOR TO PERFORMING TRANSACTION MAPPING.

THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).

*Product Mapping Area *
For automated data feed reports, the Third Party Product column shows what the ONEcount product name will be displayed as on output.

• For example, a user is subscribed to/registered for ABCXY Pharma Aug. Webinar(207) in ONEcount. The third party requires that on the report output show a value of August Webinar rather than ABCXY Pharma Aug. Webinar. Mapping ONEcount's ABCXY Pharma Aug. Webinar(207) product to August Webinar(400) will display the Third Party Product value of August Webinar on the output.

  Product Column Field: This identifies what to output as the header for the product field. Enter the heading that's required for the report output.

For imports, the Third Party Product column identifies the names/values from the import file that will be mapped to the ONEcount product.

• For example, there's "product" column in the import file that identifies what product a particular record is subscribed to or registered for. In the import file, August Webinar in that colum indicates the record is subscribed to/registered for the August Webinar. In ONEcount, the product name is ABCXY Pharma Aug. Webinar. Any record in the import file that has August Webinar in the product column will be subscribed to the ABCYXY Pharma Aug. Webinar product in ONEcount.

  Product Column Field: This identifies the column header for the product column in the import file. In the above example, you would enter "product".

Product Status Mapping Area (Optional)
For automated data feed reports, the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.

• For example, a user has a product status of "Not Active(405)" in ONEcount. The third party requires that the report output show a value of Inactive, rather than Not Active. Mapping ONEcont's "Not Active(405)" status to "Inactive(203)" will display the Third Party Product Status of Inactive on the output.

  Product Status Column Field: This identifies what to output as the header for the product status field. Enter the heading that's required for the report output.

For Imports, the Third Party Product Status column identifies what name/value from the import file will be mapped to the ONEcount product.

• For example, there's a "product status" column in the import file that identifies the product status a particular record has for a particular product. In the import file, "Inactive(203)"in that column indicates the record has a product status of inactive. In ONEcount, the product status is "Not Active(405)". Any record in the import file that has a product status of "Inactive" in the product status column will have the product status of "Not Active" applied to the record in ONEcount.

  Product Status Column Field: This identifies the column header for the product status column in the import file. In the above example, you would enter "product status".

Subscription Mapping Area
For automated data feed reports, the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.

• For example, a user has a subscription type of "n" in ONEcount. The third party requires that the report output show a value of new, rather than "n". Mapping ONEcont's "n" status to "new(new)" will display the Third Party Product Status of new on the output.

  Subscription Column Field: This identifies what to output as the header for the subscription type field. Enter the heading that's required for the report output.

For Imports, the Third Party Subscription column identifies what name/value from the import file will be mapped to the ONEcount product.

• For example, there's a "Subcription Type" column in the import file that identifies the subscription type a particular record has for a particular product. In the import file, "New" in that column indicates the record has a subscription type of new. In ONEcount, the subscription type is "n". Any record in the import file that has a product status of "New" in the subscription type column will have the product status of "n" applied to the record in ONEcount.

  Subscription Column Field: This identifies the column header for the subscription type column in the import file. In the above example, you would enter "Subscription Type".

Date Mapping Area
For automated data feed reports, enter the format you would like dates to be exported as. For example MM/dd/yyyy will export as 07/05/2023 and yy/MM/dd will export as 23/07/05. If you want to import time along with date add hh:mm:ss:a along with date. For example MM/dd/yyyy hh:mm:ss:a will be exported as 07/23/2023 11:45:32:AM

MM : months, dd: days, yyyy: years, hh: hours (12 hour format), HH: hours (24 hour format), mm: minutes, ss: seconds, a:AM/PM

Date Column Field: This identifies what to output as the header for the date field. Enter the heading that's required for the report output.

For Imports, enter the format of dates in the import file. For example, if a date is 07/05/2016, enter the format MM/dd/yyyy. If you want to import time along with date add hh:mm:ss along with date. For example MM/dd/yyyy hh:mm:ss:a will be exported as 07/23/2023 11:45:32:AM

MM : months, dd: days, yyyy: years, hh: hours (12 hour format), HH: hours (24 hour format), mm: minutes, ss: seconds, a:AM/PM

Date Column Field: This identifies the column header for the date column in the import file.

When done with mapping, click "Next".
You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.SAVE MAPPING

When done with mapping(s), click "Next".

You then have the option to save the mapping (Save) or return to mapping (Previous).

Once mapping is saved, you can find it on the Manage Mapping listing page.

A saved mapping is ready to be used for generating automated feed reports in the Dashboard. See Dashboard Reports – Create Feed Report for more information.

MAPPING ENGAGEMENT DATA

This section outlines the types of engagement data that DExTr can import/export. Please note that Generic and Engagement data fields can be used for both web, banner and newsletter engagement data.

If you need data points imported or exported that are not on this list, check with the ONEcount team to see if those fields can be accommodated.

Generic Engagement Fields

• Activity Date: Date of the Activity
• Activity Time: Time of the Activity, Mandatory for Import.
• Channel Codes: Codes for Email, Banner and Web page views, CMI needed it in export.
• End Date: End date of export, mainly used in aggregate export.
• Unique External ID: Unique ID for each transaction.
• Month: Month of the Activity.
• OCID:
• OCID Hash: Unique hash of the user. This is the cookie set on user’s browser.
• Platform Viewed: Platform of the user in which Impression or Page view happened.
• Resource Details: This is used for export. It has Page title for Web activity, Banner name for Banner Activity and Message title for Email data.
• Start Date: Start date of export, mainly used in aggregate export.

Metric Engagement Fields

• Activity Metric code: Metric codes for Activity data. It has codes for Email sent, delivered, opened, clicked, banner impression, banner clicked and page view. It is mandatory for Import and export.
• Activity Metric Name: Metric Names for Activity data (CMI report needs Metric code and Name). It has codes for Email sent, delivered, opened, clicked, banner impression, banner clicked and page view.
• Activity Metric count: Mainly used for export. It has counts for each activity.
• Aggregate Metric code: Metric codes for Aggregate data. It has codes for Email sent, delivered, opened, clicked, banner impression, banner clicked and page view. Mandatory for aggregate export.
• Aggregate Metric Name: Metric Names for Aggregate data (CMI report needs Metric code and Name). It has codes for Email sent, delivered, opened, clicked, banner impression, banner clicked and page view.
• Aggregate Metric count: Mainly used for export. It has counts for each activity.

Banner Engagement

• Ad Server Name: Name of the Ad Server, i.e., DFP
• Advertiser ID: ID of the Advertiser
• Advertiser Name: Name of the Advertiser
• Banner ID: ID of the Banner
• Banner Name: Name of the Banner
• Campaign ID: ID of the Campaign
• Campaign Name: Name of the Campaign
• Viewable Impression: If Impression is viewed or not, Boolean (0, 1 accepted)

Newsletter Engagement Fields

• Click URL: URL of the Clicked link. Mandatory for Importing Email clicks.
• List ID: ID of the newsletter List of Group
• List Name: Name of the newsletter list or group
• Message ID: Campaign ID of the newsletter
• Message Name: Campaign name of the newsletter
• Recipient ID: Unique User Id in the Email service provider
• Message Subject: Subject of the Campaign

Web Engagement Fields

• Referrer: Referrer for the page view
• Site name: Website URL
• Page URL: URL of the Page.

HOW DExTr MAPS DATA

The following information is being provided to help you understand how DExTr will map/transform your data on import.

1. On import, ONEcount will always check if fields in the DExTr mapping are present in the file or not; if any field is not present in the file, then we fail the job. This is to ensure that we won’t miss mandatory data or dedupe fields and possibly corrupt the data. If you are importing data and the file does not have all of the fields in the DExTr mapping you are using, you can create a blank column with that field name in it–as long as that field is not a de-dupe field for the import.
2. If there are multiple dedupe fields in mapping then we dedupe the data based on order that the fields appear in the mapping. For Example if mapping has dedupe fields as “Email” (1^st field in order) and “AccountID” (2^nd field in order) then DExTr will first query the datase for a match on “Email,” if match is not found then it will query on “AccountID”. It always an OR match. You can not match on Email AND AccountID
3. If OCID is present as a dedupe field, then it always takes precedence irrespective of order. If you import a file with OCID as a dedupe field, and a record does not have an OCID, then a new user will be created in ONEcount and a unique OCID will be generated.
4. There are a variety of validations which can be added to DExTr mapping like, “Numeric”, “Required” etc.. If any record/row doesn’t satisfy these validations, then that record won’t be imported into ONEcount. It will be saved into a failed record file and mailed to the email address supplied with the import job.
5. If there are any passwords that are being imported, they should be imported as plain text. ONEcount will encrypt the field based on encrypt function for your installation.
6. For Package transactions: Term ID, Package status, source code and transaction type are mandatory.
   1. If Term ID is not mapped, then the transaction won’t be imported.
   2. IF Package status is not mapped then default Package status from term will be added.
   3. If source code is not mapped. Then default source code from import job will be selected.
   4. If transaction type is not added, then default type from Import job will be selected.
7. For Product transaction: Product ID, source code and transaction type are mandatory.
   1. If Product ID is not mapped, then the transaction won’t be imported.
   2. If source code is not mapped. Then default source code from import job will be selected.
   3. If transaction type is not added, then default type from Import job will be selected.
8. If Transaction Date is not mapped or not formatted correctly, then current date will be used as request date.
9. If Expiration date is not mapped or not formatted correctly, then expiration date will be calculated based on the duration of the term and the request date.
10. For Engagement imports, Activity type is mandatory.
11. If Engagement date is not formatted, then current date will be used as activity date.
12. If Data and campaign ID, name, List ID and name then they will be imported as well.
13. If dedupe is not added/matched for an engagement import then new users will be created in the system just like Users and transaction import.