Skip to Content

Changes for page Utilities - DExTr

Last modified by Admin User on 2025/04/30 18:37
From version 19.1
edited by Admin User
on 2025/04/30 18:37
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

Summary

Details

Page properties
Parent
... ... @@ -1,1 +1,0 @@
1 -System Utilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.admin
1 +XWiki.Admin
Content
... ... @@ -1,6 +1,8 @@
1 1  {{layout}}
2 2  {{layout-section ac:type="two_right_sidebar"}}
3 3  {{layout-cell}}
4 +
5 +
4 4  {{id name="Start ScreenSteps Content"/}}
5 5  
6 6  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.
... ... @@ -35,9 +35,9 @@
35 35  
36 36  **OPEN THE MAPPING WINDOW**
37 37  
38 -Select DATA MANAGEMENT from the main menu and the DExTr from the sub-menu.
40 +Select UTILITIES from the main menu and the DExTr from the sub-menu.
39 39  
40 -[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 8.png||thumbnail="true" height="250"]]
42 +[[image:attach:DExTr Nav.png||width="707"]]
41 41  
42 42  This will open the Main DExTr Listing Page, as shown below.
43 43  
... ... @@ -45,6 +45,7 @@
45 45  
46 46  [[image:attach:DExTr Listing Page.png||height="250"]]
47 47  
50 +\\
48 48  
49 49  Select "Create Mapping" to create a new mapping. This will open the Mapping Builder, as shown below.
50 50  
... ... @@ -51,14 +51,18 @@
51 51  To edit an existing mapping, select the Edit icon.
52 52  To copy an existing mapping, select the Copy icon.
53 53  To delete an existing mapping, select the Delete icon.
54 -
57 +\\
55 55  
59 +\\
56 56  
61 +(% style="margin-left: 30.0px;" %)
62 +\\
57 57  
58 58  === Creating a Data Mapping ===
59 59  
60 60  **[[image:attach:New-DExTr-Mapping.png||height="250"]]**
61 61  
68 +\\
62 62  
63 63  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.
64 64  
... ... @@ -66,7 +66,7 @@
66 66  
67 67  1. (((
68 68  (((
69 -Exchange Map** - **Define Exchange Map
76 +Exchange Map** - **Define Exchange Map
70 70  )))
71 71  
72 72  (((
... ... @@ -76,11 +76,14 @@
76 76  )))
77 77  )))
78 78  
86 +\\
87 +
79 79  [[image:attach:DExTr Demo Tab.png||width="800"]]
80 80  
90 +\\
81 81  
82 82  1. (((
83 -Demographic Fields** - ** Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.
93 +Demographic Fields** - ** Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.
84 84  )))
85 85  
86 86  Define field names (the column headers from the import file) on the left and match them to the ONEcount field on the right.
... ... @@ -89,20 +89,24 @@
89 89  
90 90  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.
91 91  
102 +\\
92 92  
93 93  [[image:attach:DExTr Value Mapping Pop-Up.png||height="250"]]
94 94  
106 +\\
95 95  
108 +\\
96 96  
97 97  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.
98 98  
99 99  //(Example: states may be abbreviated with 4 letters in a POS database [Conn., Mass.], while the ecommerce database has two letter abbreviations.)//
100 100  
114 +\\
101 101  
102 102  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.
103 103  
104 104  1. (((
105 -Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
119 +Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
106 106  )))
107 107  
108 108  * (((
... ... @@ -116,9 +116,9 @@
116 116  Within the “Map Values” pop up window, click “Add” to define all possible transactional statuses.
117 117  )))
118 118  
119 -1.
133 +1.
120 120  
121 -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.
135 +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.
122 122  )))
123 123  
124 124  * (((
... ... @@ -150,6 +150,10 @@
150 150  *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.
151 151  )))
152 152  
167 +\\
168 +
169 +\\
170 +
153 153  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.
154 154  
155 155  There are four Mapping Areas for Transaction Mapping:
... ... @@ -173,7 +173,7 @@
173 173  
174 174  **THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).**
175 175  
176 -*(% style="text-decoration:underline" %)Product Mapping Area(%%) *
194 +*(% style="text-decoration: underline;" %)Product Mapping Area(%%) *
177 177  **For automated data feed reports**, the Third Party Product column shows what the ONEcount product name will be displayed as on output.
178 178  
179 179  * (((
... ... @@ -190,7 +190,7 @@
190 190  **Product Column Field:** This identifies the column header for the product column in the import file. In the above example, you would enter "product".
191 191  )))
192 192  
193 -(% style="text-decoration:underline" %)**Product Status Mapping Area (Optional)**(%%)
211 +(% style="text-decoration: underline;" %)**Product Status Mapping Area (Optional)**(%%)
194 194  **For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
195 195  
196 196  * (((
... ... @@ -207,7 +207,7 @@
207 207  **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".
208 208  )))
209 209  
210 -(% style="text-decoration:underline" %)**Subscription Mapping Area**(%%)
228 +(% style="text-decoration: underline;" %)**Subscription Mapping Area**(%%)
211 211  **For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
212 212  
213 213  * (((
... ... @@ -224,20 +224,14 @@
224 224  **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".
225 225  )))
226 226  
227 -(% style="text-decoration:underline" %)**Date Mapping Area**(%%)
228 -**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
229 -
230 -(% 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
231 -
245 +(% style="text-decoration: underline;" %)**Date Mapping Area**(%%)
246 +**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.
232 232  **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.
233 233  
234 -**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
235 -
236 -(% 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
237 -
249 +**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.
238 238  **Date Column Field:** This identifies the column header for the date column in the import file.
239 239  
240 -When done with mapping, click "Next".
252 +When done with mapping, click "Next".
241 241  You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.**SAVE MAPPING**
242 242  
243 243  When done with mapping(s), click "Next".
... ... @@ -327,7 +327,7 @@
327 327  11. If Product ID is not mapped, then the transaction won’t be imported.
328 328  11. If source code is not mapped. Then default source code from import job will be selected.
329 329  11. If transaction type is not added, then default type from Import job will be selected.
330 -1. If Request Date is not mapped or not formatted correctly, then current date will be used as request date.
342 +1. If Transaction Date is not mapped or not formatted correctly, then current date will be used as request date.
331 331  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.
332 332  1. For Engagement imports, Activity type is mandatory.
333 333  1. If Engagement date is not formatted, then current date will be used as activity date.
... ... @@ -334,10 +334,22 @@
334 334  1. If Data and campaign ID, name, List ID and name then they will be imported as well.
335 335  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.
336 336  
337 -
349 +\\
338 338  {{/layout-cell}}
339 339  
340 340  {{layout-cell}}
353 +{{panel borderStyle="solid" title="Search all Documentation:"}}
354 +
355 +
356 +{{livesearch/}}
357 +{{/panel}}
358 +
359 +{{panel borderStyle="solid" title="Search System UTILITIES:"}}
360 +
361 +
362 +{{pagetreesearch rootPage="System Utilities"/}}
363 +{{/panel}}
364 +
341 341  {{panel title="More System UTILITIES"}}
342 342  {{expand title="Expand"}}
343 343  
... ... @@ -369,6 +369,7 @@
369 369  (% style="margin-left: 30.0px;" %)
370 370  [[Widget Builder>>doc:Utilities - Widget Builder]]
371 371  
396 +(% style="margin-left: 30.0px;" %)
372 372  
373 373  
374 374  (% style="margin-left: 30.0px;" %)
... ... @@ -376,8 +376,9 @@
376 376  {{/expand}}
377 377  {{/panel}}
378 378  
404 +\\
379 379  
380 -
406 +\\
381 381  {{/layout-cell}}
382 382  {{/layout-section}}
383 383  {{/layout}}
DExTr Demo Tab.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -196.0 KB
Content
DExTr Listing Page.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -144.2 KB
Content
DExTr Nav.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -51.4 KB
Content
DExTr Value Mapping Pop-Up.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -119.3 KB
Content
New-DExTr-Mapping.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -89.9 KB
Content
Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -17.7 KB
Content
media_1467388147151.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -30.4 KB
Content
media_1467391080266.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -56.2 KB
Content
media_1467391237758.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -63.3 KB
Content
media_1467391409099.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -160.0 KB
Content
media_1467396172019.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -80.4 KB
Content
media_1467397686498.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -29.5 KB
Content
media_1467398257338.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -37.2 KB
Content
media_1467398286154.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -18.0 KB
Content
media_1467398730892.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -112.7 KB
Content
media_1467398948360.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
media_1467399198566.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -51.5 KB
Content
media_1467651841763.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -170.2 KB
Content
media_1468251499518.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -28.5 KB
Content
media_1468251557794.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -26.0 KB
Content
media_1468252151743.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -122.0 KB
Content
media_1468252886176.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -92.5 KB
Content
media_1468256607407.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -90.4 KB
Content
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -67230
1 +62521418
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/67230/Utilities - DExTr
1 +https://info.onecount.net//wiki/spaces/OD/pages/62521418/Utilities - DExTr