Changes for page Utilities - DExTr

Last modified by rayaan@one-count_com on 2023/11/09 10:38

From 5.1 to 6.1 From 14.1 to 15.1

From version 6.1

edited by melanie@one-count_com
on 2016/12/13 13:45

Change comment: There is no comment for this version

To version 14.1

edited by Admin
on 2021/03/11 16:37

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)
Objects (1 modified, 0 added, 0 removed)
- Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--Utilities - Mapper (v12.x)
++Utilities - DExTr

Author

@@ -1,1 +1,1 @@
--XWiki.melanie@one-count_com
++XWiki.Admin

Content

@@ -4,238 +4,186 @@
  {{id name="Start ScreenSteps Content"/}}
-- The Mapper is used to create mappings for generating automated feed reports for export and for data import. This tool allows you to map your, or third party, data to ONEcount questions/data fields.
++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 activity, status, and date formats.
--* **Activity 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.
++* (((
++**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) and map demographics and transactions directly from that file or manually enter the demographics, transactions, and activities you wish to map to ONEcount questions/data fields, or do a combination of both.
++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 and response values must be created prior to performing mapping.**
++**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** ==
++**OPEN THE MAPPING WINDOW**
--=== Select UTILTIES from the main menu. ===
++Select UTILITIES from the main menu and the DExTr from the sub-menu.
--[[image:attach:media_1468251499518.png||align="center"]]
++[[image:attach:DExTr Nav.png||width="707"]]
--=== Select Mapper from the sub-menu. ===
++This will open the Main DExTr Listing Page, as shown below.
--[[image:attach:media_1468251557794.png||align="center"]]
++**CREATE A NEW DExTr MAPPING**
--This will open the Manage Mapping Listing Page, as shown below.
++[[image:attach:DExTr Listing Page.png||height="250"]]
--== **CREATE A NEW DATA MAPPING** ==
++\\
--[[image:attach:media_1467388147151.png||align="center"]]
--
  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 delete an existing mapping, select the Delete icon.
++To copy an existing mapping, select the Copy icon.
++To delete an existing mapping, select the Delete icon.
++\\
--=== **1 – INFORMATION AND DEMOGRAPHIC MAPPING** ===
++\\
--[[image:attach:media_1468252151743.png||align="center"]]
--
--Information and Demo Mapping consists of three main parts:
--
--**1 – Information**
-- **2 – Mapping Area**
-- **3 – ONEcount Questions**
--
--See below for detail on each part.
--
--==== (% style="color: rgb(128,0,0);" %)__Information__(%%) ====
--
  (% style="margin-left: 30.0px;" %)
--**Name:** Give the mapping a name (required)
++\\
--(% style="margin-left: 30.0px;" %)
--**Description:** Provide a description of the mapping (optional)
++=== Creating a Data Mapping ===
--(% style="margin-left: 30.0px;" %)
--**Select whether you want to map transactions and/or activity:** You can create a mapping for demographic questions only, or map any combination of demographics, transactions, and actions.
++**[[image:attach:New-DExTr-Mapping.png||height="250"]]**
--(% style="margin-left: 30.0px;" %)
--**Upload Layout:** Uploading a layout document is optional. You may opt to manually enter demographic and transactional questions and values to be mapped to ONEcount questions and values. Or, you may use a combination of both uploading a layout and manual entry.
++\\
--(% style="margin-left: 30.0px;" %)
--(% style="text-decoration: underline;" %)//**To Upload a Layout File**//(%%)
-- Click on the "Browse" button, locate the file on your computer, then click on "Upload File".
++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.
--(% style="margin-left: 30.0px;" %)
--When you upload an external layout, the Demographic and Transacton Mapping Areas will be automatically pre-populated with each question/data field and values for that field. (See screenshotbelow)
++Navigate across the six tabs at the top of the interface to configure how the customer data platform will interpret and exchange data.
--(% style="margin-left: 30.0px;" %)
--See screenshots of pre-population and layout formatting rules below.
++1. (((
++(((
++Exchange Map** - **Define Exchange Map
++)))
--(% style="margin-left: 60.0px;text-align: center;" %)
--**
--**
++(((
++1. (((
++Enter a name and description for this data exchange, then proceed to the next tab (Demographic Fields).
++)))
++)))
++)))
--[[image:attach:media_1468252886176.png||align="center"]]
++\\
--(% style="margin-left: 60.0px;" %)
--_(% style="text-decoration: underline;" %)**Layout File Format**(%%) _
-- The layout file must be in .csv format and include markers for demographic questions (~#~##demographics), products (~#~##products~#~##), subscription type(~#~##subscriptionType~#~##), and product status (optional) (~#~##productStatus~#~##).
++[[image:attach:DExTr Demo Tab.png||width="800"]]
--(% style="margin-left: 60.0px;" %)
--(% style="text-decoration: underline;" %)//Demographic Mapping//
--
--*
--**
--*** For Demographic Questions: Question text must be in Column A, response values for multiple response-type questions* in Column B, and response text values in Column C.
-- *Note that text-response type questions, e.g. last name, don't require values in Column B or C.
--
--(% style="margin-left: 60.0px;" %)
--(% style="text-decoration: underline;" %)//Transaction Mapping//
--
--*
--**
--*** For Products: Product ID must be in Column A and Product name in Column B.
--*** For Subscription Type: Sub Type ID/value is in Column A and subscription type name in Column B.
--*** For Product Status: Status ID must be in Column A and Status name in Column B.
  \\
--(% style="text-align: center;" %)
--//**Screenshot: Pre-Populated Demographic Questions/Data Fields - Uploaded Layout**//
++1. (((
++Demographic Fields** - ** Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.
++)))
--[[image:attach:media_1467396172019.png||align="center"]]
++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)
--(% style="text-align: center;" %)
--**//Screenshot: Pre-populated Question Responses - Uploaded Layout//**
++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.
--[[image:attach:media_1467391080266.png||align="center"]]
++\\
--
++[[image:attach:DExTr Value Mapping Pop-Up.png||height="250"]]
--(% style="text-align: center;" %)
--**//Screenshot: Pre-Populated Transaction Mapping - Uploaded Layout//**
++\\
--[[image:attach:media_1467391409099.png||align="center"]]
++\\
--==== (% style="color: rgb(128,0,0);" %)__Map Third-Party Questions__(%%) ====
++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.
--[[image:attach:media_1467397686498.png||align="center"]]
++//(Example: states may be abbreviated with 4 letters in a POS database [Conn., Mass.], while the ecommerce database has two letter abbreviations.)//
--(% style="margin-left: 30.0px;" %)
--Prior to uploading a layout file, or if you opt to create the mapping on the fly (without uploading a layout file), the Mapping Area will be empty.
++\\
--(% style="margin-left: 30.0px;" %)
--The mapping area consists of three columns: **Third Party Questions, ONEcount Questions, and Validations.**
++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.
--*
--** **Third Party Questions** shows questions/data fields your, or a third party's, data file.
--** **ONEcount Questions** shows the corresponding ONEcount question to be mapped to the Third Party Question.
--** **Validations** allows you to select validations for the mapped question, i.e., Required, Email, Number and Text, Text Only.
++1. (((
++Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
++)))
--(% style="margin-left: 30.0px;" %)
--===== Manually Add Third-Party Questions =====
++* (((
++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.
++)))
++1. (((
++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.)
++)))
++1. (((
++Within the “Map Values” pop up window, click “Add” to define all possible transactional statuses.
++)))
--(% style="margin-left: 30.0px;" %)
--[[image:attach:media_1467398286154.png||align="center"]]
++1.
--(% style="margin-left: 30.0px;" %)
--When you click on the "Add Questions" button, you'll be presented with a pop-up to create a new question/data field to be mapped to an existing ONEcount question.
++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.
++)))
--(% style="margin-left: 30.0px;" %)
--Be sure to select "Yes" if it is a question with selectable responses, i.e. radio button/select/checkbox-type. Click Save.
++* (((
++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.
++)))
++1. (((
++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
--==== (% style="color: rgb(128,0,0);" %)__Map Third-Party to ONEcount Questions and Responses
--__(%%) ====
++//(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”]). //
++)))
++)))
--(% style="color: rgb(128,0,0);" %)__ __
++5.    Static Fields
--(% style="margin-left: 60.0px;" %)
--//YOU MUST FIRST MAP THE THIRD-PARTY QUESTION TO THE CORRESPONDING ONEcount QUESTION BY DRAGGING AND DROPPING THE CORRESPONDING ONEcount QUESTION FROM THE ONEcount Questions SECTION INTO THE ONEcount Questions Column BEFORE YOU CAN MAP RESPONSES.//
++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.
++)))
++1. (((
++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”).
++)))
++1. (((
++Click “Add” to create additional static field appends.
++)))
--(% style="color: rgb(128,0,0);" %)__ __
++6.    Re-order Fields
--(% style="margin-left: 60.0px;" %)
--//THIS APPLIES TO BOTH MANUALLY ADDED QUESTIONS AND QUESTIONS PRE-POPULATED BY UPLOAD OF AN IMPORT.//
++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.
++)))
--(% style="color: rgb(128,0,0);" %)__ __
++\\
--(% style="margin-left: 60.0px;" %)
--//ONEcount QUESTIONS AND RESPONSE VALUES MUST BE CREATED PRIOR TO PERFORMING MAPPING.//
++\\
--(% style="color: rgb(128,0,0);" %)__
--__
++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.
--(% style="margin-left: 30.0px;" %)
--[[image:attach:media_1467398257338.png||align="center"]]
--
--(% style="margin-left: 30.0px;" %)
--If the question is a radio button/select/checkbox-type question, a button will be presented which will allow you to map responses and values. (See "Upgrade Checkbox" question above.)
--
--(% style="margin-left: 30.0px;" %)
--
--If it's a text-type response, you won't need to map responses and values.
--
--
--
--(% style="margin-left: 30.0px;" %)
--[[image:attach:media_1467398730892.png||align="center"]]
--
--(% style="margin-left: 30.0px;" %)
--Simply drag and drop ONEcount questions from the question pool into the appropriate cell in the mapping table.
--
--(% style="margin-left: 30.0px;" %)
--Note the Search function at the top of the list of ONEcount questions. Just begin typing in the question name, and the list will be filtered for you. (See screenshot below.)
--
--(% style="margin-left: 30.0px;" %)
--[[image:attach:media_1467398948360.png||align="center"]]
--
--(% style="margin-left: 30.0px;" %)
--Once Questions are mapped, you can add validations and/or map responses for radio/select/checkbox-type questions.
--
--(% style="margin-left: 30.0px;" %)
--To add validations, click in the empty "Validations" box for the corresponding question and select from the drop-down list the validation(s) you want to apply to the question, i.e. Required, Email, Number and Text, Text Only. (See screenshot below.
--
--(% style="text-align: center;" %)
--//**Screenshot – Mapped Questions with Validations**//
--
--[[image:attach:media_1467399198566.png||align="center"]]
--
--(% style="margin-left: 30.0px;" %)
--===== Map Question Responses =====
--
--[[image:attach:media_1467391237758.png||align="center"]]
--
--To map question responses, click on the "Response Map" button. Doing so will present a pop-up window where you can map third-party to ONEcount responses. Just drag and drop ONEcount responses from the list of ONEcount Responses into the appropriate cell.
--
--When done mapping responses, click the "Save" button.
--
--You'll be returned to Information and Demo Mapping where you can then continue mapping remaining questions or click "Next" to continue.
--
--Depending on the mapping selections you made under "Information", clicking "Next" will direct you either to save the Demographic Mapping or to the Transaction Mapping and/or Activity Mapping sections.
--
--=== 2 – TRANSACTION MAPPING ===
--
--[[image:attach:media_1467651841763.png||align="center"]]
--
--Transaction Maping 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
++* (((
++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.**
@@ -244,121 +244,197 @@
  **THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).**
  *(% style="text-decoration: underline;" %)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 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 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".
++* (((
++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".
++)))
++
  (% style="text-decoration: underline;" %)**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 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 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".
++* (((
++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".
++)))
++
  (% style="text-decoration: underline;" %)**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 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 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".
++* (((
++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".
++)))
++
  (% style="text-decoration: underline;" %)**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/2016 and yy/mm/dd will export as 16/07/05.
-- **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 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/2016 and yy/mm/dd will export as 16/07/05.
++**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.
-- **Date Column Field:** This identifies the column header for the date column in the import file.
++**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.
++You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.**SAVE MAPPING**
--=== 3 – ACTIVITY MAPPING ===
++When done with mapping(s), click "Next".
--[[image:attach:media_1468256607407.png||align="center"]]
++You then have the option to save the mapping (Save) or return to mapping (Previous).
--Activity Maping is done the same way as Demographic and Transaction Mapping by using the drag and drop functionality to match Third Party Activity Header with ONEcount Activity Header. The Third Party Activity Headers will display as column headings for Web, Ad, and Newlsetter data in the export file.
++Once mapping is saved, you can find it on the Manage Mapping listing page.
--**Third-party activity headers currently can't be mapped via an uploaded layout file. They must be mapped manually in the Activity Mapping Area by clicking on the "Add Activity Header" button.**
-- When you click on the "Add Activity Header" button, you'll be presented with a pop-up where you can add the Activity Header Name.
++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.
--The ONEcount Activity Header section is divided into the following categories: Web, Ad, Newsletter, Generic (includes general headers, such as ONEcount unique identifier, Channel Code, etc.) Note the scroll bar to move through the categories.
--When finished mapping, click the "Next" button.
--== **SAVE MAPPING** ==
++{{id name="End ScreenSteps Content"/}}
--When done with mapping(s), click "Next".
++=== MAPPING ENGAGEMENT DATA ===
--You then have the option to save the mapping (Save) or return to mapping (Previous).
++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.
--Once mapping is saved, you can find it on the Manage Mapping listing page.
++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.
--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.
++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
--{{id name="End ScreenSteps Content"/}}
--{{/layout-cell}}
++* 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.
--{{layout-cell}}
--**Search all Documentation:**
++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
--{{livesearch/}}
++* 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
--**Search System UTILITIES:**
++* 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.
--{{pagetreesearch rootPage="System Utilities"/}}
++(% class="diff-block-target" %)
++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.//
++1. 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
++1. 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.
++1. 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.
++1. 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.
++1. For Package transactions: Term ID, Package status, source code and transaction type are mandatory.
++11. If Term ID is not mapped, then the transaction won’t be imported.
++11. IF Package status is not mapped then default Package status from term will be added.
++11. If source code is not mapped. Then default source code from import job will be selected.
++11. If transaction type is not added, then default type from Import job will be selected.
++1. For Product transaction: Product ID, source code and transaction type are mandatory.
++11. If Product ID is not mapped, then the transaction won’t be imported.
++11. If source code is not mapped. Then default source code from import job will be selected.
++11. If transaction type is not added, then default type from Import job will be selected.
++1. If Transaction Date is not mapped or not formatted correctly, then current date will be used as request date.
++1. 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.
++1. For Engagement imports, Activity type is mandatory.
++1. If Engagement date is not formatted, then current date will be used as activity date.
++1. If Data and campaign ID, name, List ID and name then they will be imported as well.
++1. 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.
--
++\\
++{{/layout-cell}}
--**On this page:**
++{{layout-cell}}
++{{panel borderStyle="solid" title="Search all Documentation:"}}
++{{livesearch/}}
++{{/panel}}
--{{toc maxLevel="4"/}}
++{{panel borderStyle="solid" title="Search System UTILITIES:"}}
--
--{{expand title="More System UTILITIES"}}
-- [[QR Codes>>doc:Utilities - QR Codes (v12\.x)]]
++{{pagetreesearch rootPage="System Utilities"/}}
++{{/panel}}
++{{panel title="More System UTILITIES"}}
++{{expand title="Expand"}}
++
++
  (% style="margin-left: 30.0px;" %)
--[[Job List>>doc:Utilities - Job List (v12\.x)]]
++[[Job List>>doc:Utilities - Job List]]
  (% style="margin-left: 30.0px;" %)
++[[Backend User Permissions>>doc:Utilities - Backend Users and Permissions]]
--
  (% style="margin-left: 30.0px;" %)
--[[Email Engine Sender Score>>doc:Utilities - Email Engine (v12\.x)]]
++[[Email Engine Sender Score>>doc:ONEmail and Sender Score]]
  (% style="margin-left: 30.0px;" %)
--[[Email Engine>>doc:Utilities - Email Engine (v12\.x)]]
++[[doc:ONEmail]]
  (% style="margin-left: 30.0px;" %)
  Action Manager
  (% style="margin-left: 30.0px;" %)
--[[Configuration Manager>>doc:Utilities - Configuration Manager (v12\.x)]]
++[[Configuration Manager>>doc:Utilities - Configuration Manager]]
  (% style="margin-left: 30.0px;" %)
  Backend Activity Log
@@ -367,8 +367,8 @@
  IVT Mitigator
  (% style="margin-left: 30.0px;" %)
++[[Widget Builder>>doc:Utilities - Widget Builder]]
--
  (% style="margin-left: 30.0px;" %)
@@ -375,6 +375,11 @@
  (% style="margin-left: 30.0px;" %)
  Import/Export Tool
  {{/expand}}
++{{/panel}}
++
++\\
++
++\\
  {{/layout-cell}}
  {{/layout-section}}
  {{/layout}}

Confluence.Code.ConfluencePageClass[0]

id

@@ -1,1 +1,1 @@
--67382
++62521418

url

@@ -1,1 +1,1 @@
--https://info.onecount.net//wiki/spaces/OD/pages/67382/Utilities - Mapper (v12.x)
++https://info.onecount.net//wiki/spaces/OD/pages/62521418/Utilities - DExTr