Changes for page Utilities - DExTr

Last modified by Admin User on 2025/04/30 18:37

From 15.1 to 16.1

From version 16.1

edited by rayaan@one-count_com
on 2023/11/09 11:38

Change comment: There is no comment for this version

To version 19.1

edited by Admin User
on 2025/04/30 18:37

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.rayaan@one-count_com
++XWiki.admin

Content

@@ -1,8 +1,6 @@
  {{layout}}
  {{layout-section ac:type="two_right_sidebar"}}
  {{layout-cell}}
--
--
  {{id name="Start ScreenSteps Content"/}}
  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.
@@ -47,7 +47,6 @@
  [[image:attach:DExTr Listing Page.png||height="250"]]
--\\
  Select "Create Mapping" to create a new mapping. This will open the Mapping Builder, as shown below.
@@ -54,18 +54,14 @@
  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.
--\\
++
--\\
--(% style="margin-left: 30.0px;" %)
--\\
  === Creating a Data Mapping ===
  **[[image:attach:New-DExTr-Mapping.png||height="250"]]**
--\\
  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.
@@ -73,7 +73,7 @@
 . (((
  (((
--Exchange Map** - **Define Exchange Map
++Exchange Map** - **Define Exchange Map
  )))
  (((
@@ -83,14 +83,11 @@
  )))
  )))
--\\
--
  [[image:attach:DExTr Demo Tab.png||width="800"]]
--\\
 . (((
--Demographic Fields** - ** Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.
++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.
@@ -99,24 +99,20 @@
  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:DExTr Value Mapping Pop-Up.png||height="250"]]
--\\
--\\
  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.
 . (((
--Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
++Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
  )))
  * (((
@@ -130,9 +130,9 @@
  Within the “Map Values” pop up window, click “Add” to define all possible transactional statuses.
  )))
--1.
++1.
--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.
++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.
  )))
  * (((
@@ -164,10 +164,6 @@
  *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:
@@ -191,7 +191,7 @@
  **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(%%) *
++*(% 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.
  * (((
@@ -208,7 +208,7 @@
  **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)**(%%)
++(% 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.
  * (((
@@ -225,7 +225,7 @@
  **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**(%%)
++(% 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.
  * (((
@@ -242,20 +242,20 @@
  **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**(%%)
++(% 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/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
--(% style="color: rgb(51,51,51);" %)MM : months, dd: days, yyyy: years, hh: hours (12 hour format), HH: hours (24 hour format), mm: minutes, ss: seconds, a:AM/PM(%%)\\
++(% style="color:#333333" %)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
--(% style="color: rgb(51,51,51);" %)MM : months, dd: days, yyyy: years, hh: hours (12 hour format), HH: hours (24 hour format), mm: minutes, ss: seconds, a:AM/PM
++(% style="color:#333333" %)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".
++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".
@@ -345,7 +345,7 @@
 . If Product ID is not mapped, then the transaction won’t be imported.
 . If source code is not mapped. Then default source code from import job will be selected.
 . 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 Request Date is not mapped or not formatted correctly, then current date will be used as request date.
 . 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.
 . For Engagement imports, Activity type is mandatory.
 . If Engagement date is not formatted, then current date will be used as activity date.
@@ -352,22 +352,10 @@
 . If Data and campaign ID, name, List ID and name then they will be imported as well.
 . 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}}
  {{layout-cell}}
--{{panel borderStyle="solid" title="Search all Documentation:"}}
--
--
--{{livesearch/}}
--{{/panel}}
--
--{{panel borderStyle="solid" title="Search System UTILITIES:"}}
--
--
--{{pagetreesearch rootPage="System Utilities"/}}
--{{/panel}}
--
  {{panel title="More System UTILITIES"}}
  {{expand title="Expand"}}
@@ -399,7 +399,6 @@
  (% style="margin-left: 30.0px;" %)
  [[Widget Builder>>doc:Utilities - Widget Builder]]
--(% style="margin-left: 30.0px;" %)
  (% style="margin-left: 30.0px;" %)
@@ -407,9 +407,8 @@
  {{/expand}}
  {{/panel}}
--\\
--\\
++
  {{/layout-cell}}
  {{/layout-section}}
  {{/layout}}