Skip to Content

Changes for page Utilities - DExTr

Last modified by Admin User on 2025/04/30 18:37
From version 17.1
edited by Admin User
on 2025/04/30 09:34
Change comment: There is no comment for this version
To version 13.1
edited by Admin
on 2020/05/08 16:35
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 -=== Creating a Data Mapping ===
64 +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,12 +76,14 @@
76 76  )))
77 77  )))
78 78  
86 +\\
79 79  
80 80  [[image:attach:DExTr Demo Tab.png||width="800"]]
81 81  
90 +\\
82 82  
83 83  1. (((
84 -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.
85 85  )))
86 86  
87 87  Define field names (the column headers from the import file) on the left and match them to the ONEcount field on the right.
... ... @@ -90,20 +90,24 @@
90 90  
91 91  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.
92 92  
102 +\\
93 93  
94 94  [[image:attach:DExTr Value Mapping Pop-Up.png||height="250"]]
95 95  
106 +\\
96 96  
108 +\\
97 97  
98 98  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.
99 99  
100 100  //(Example: states may be abbreviated with 4 letters in a POS database [Conn., Mass.], while the ecommerce database has two letter abbreviations.)//
101 101  
114 +\\
102 102  
103 103  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.
104 104  
105 105  1. (((
106 -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.
107 107  )))
108 108  
109 109  * (((
... ... @@ -117,9 +117,9 @@
117 117  Within the “Map Values” pop up window, click “Add” to define all possible transactional statuses.
118 118  )))
119 119  
120 -1.
133 +1.
121 121  
122 -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.
123 123  )))
124 124  
125 125  * (((
... ... @@ -151,7 +151,9 @@
151 151  *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.
152 152  )))
153 153  
167 +\\
154 154  
169 +\\
155 155  
156 156  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.
157 157  
... ... @@ -176,7 +176,7 @@
176 176  
177 177  **THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).**
178 178  
179 -*(% style="text-decoration:underline" %)Product Mapping Area(%%) *
194 +*(% style="text-decoration: underline;" %)Product Mapping Area(%%) *
180 180  **For automated data feed reports**, the Third Party Product column shows what the ONEcount product name will be displayed as on output.
181 181  
182 182  * (((
... ... @@ -193,7 +193,7 @@
193 193  **Product Column Field:** This identifies the column header for the product column in the import file. In the above example, you would enter "product".
194 194  )))
195 195  
196 -(% style="text-decoration:underline" %)**Product Status Mapping Area (Optional)**(%%)
211 +(% style="text-decoration: underline;" %)**Product Status Mapping Area (Optional)**(%%)
197 197  **For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
198 198  
199 199  * (((
... ... @@ -210,7 +210,7 @@
210 210  **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".
211 211  )))
212 212  
213 -(% style="text-decoration:underline" %)**Subscription Mapping Area**(%%)
228 +(% style="text-decoration: underline;" %)**Subscription Mapping Area**(%%)
214 214  **For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
215 215  
216 216  * (((
... ... @@ -227,20 +227,14 @@
227 227  **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".
228 228  )))
229 229  
230 -(% style="text-decoration:underline" %)**Date Mapping Area**(%%)
231 -**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
232 -
233 -(% 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
234 -
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.
235 235  **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.
236 236  
237 -**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
238 -
239 -(% 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
240 -
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.
241 241  **Date Column Field:** This identifies the column header for the date column in the import file.
242 242  
243 -When done with mapping, click "Next".
252 +When done with mapping, click "Next".
244 244  You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.**SAVE MAPPING**
245 245  
246 246  When done with mapping(s), click "Next".
... ... @@ -255,64 +255,10 @@
255 255  
256 256  {{id name="End ScreenSteps Content"/}}
257 257  
258 -=== MAPPING ENGAGEMENT DATA ===
267 +\\
259 259  
260 -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.
269 +**HOW DExTr MAPS DATA**
261 261  
262 -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.
263 -
264 -Generic Engagement Fields
265 -
266 -* Activity Date: Date of the Activity
267 -* Activity Time: Time of the Activity, Mandatory for Import.
268 -* Channel Codes: Codes for Email, Banner and Web page views, CMI needed it in export.
269 -* End Date: End date of export, mainly used in aggregate export.
270 -* Unique External ID: Unique ID for each transaction.
271 -* Month: Month of the Activity.
272 -* OCID:
273 -* OCID Hash: Unique hash of the user. This is the cookie set on user’s browser.
274 -* Platform Viewed: Platform of the user in which Impression or Page view happened.
275 -* 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.
276 -* Start Date: Start date of export, mainly used in aggregate export.
277 -
278 -Metric Engagement Fields
279 -
280 -* 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.
281 -* 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.
282 -* Activity Metric count: Mainly used for export. It has counts for each activity.
283 -* 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.
284 -* 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.
285 -* Aggregate Metric count: Mainly used for export. It has counts for each activity.
286 -
287 -Banner Engagement
288 -
289 -* Ad Server Name: Name of the Ad Server, i.e., DFP
290 -* Advertiser ID: ID of the Advertiser
291 -* Advertiser Name: Name of the Advertiser
292 -* Banner ID: ID of the Banner
293 -* Banner Name: Name of the Banner
294 -* Campaign ID: ID of the Campaign
295 -* Campaign Name: Name of the Campaign
296 -* Viewable Impression: If Impression is viewed or not, Boolean (0, 1 accepted)
297 -
298 -Newsletter Engagement Fields
299 -
300 -* Click URL: URL of the Clicked link. Mandatory for Importing Email clicks.
301 -* List ID: ID of the newsletter List of Group
302 -* List Name: Name of the newsletter list or group
303 -* Message ID: Campaign ID of the newsletter
304 -* Message Name: Campaign name of the newsletter
305 -* Recipient ID: Unique User Id in the Email service provider
306 -* Message Subject: Subject of the Campaign
307 -
308 -Web Engagement Fields
309 -
310 -* Referrer: Referrer for the page view
311 -* Site name: Website URL
312 -* Page URL: URL of the Page.
313 -
314 -=== **HOW DExTr MAPS DATA** ===
315 -
316 316  The following information is being provided to help you understand how DExTr will map/transform your data on import.
317 317  
318 318  (% class="diff-block-target" %)
... ... @@ -337,14 +337,22 @@
337 337  1. If Data and campaign ID, name, List ID and name then they will be imported as well.
338 338  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.
339 339  
340 -
295 +\\
341 341  {{/layout-cell}}
342 342  
343 343  {{layout-cell}}
344 -{{panel borderStyle="solid" title=""}}{{/panel}}
299 +{{panel borderStyle="solid" title="Search all Documentation:"}}
345 345  
346 -{{panel borderStyle="solid" title=""}}{{/panel}}
347 347  
302 +{{livesearch/}}
303 +{{/panel}}
304 +
305 +{{panel borderStyle="solid" title="Search System UTILITIES:"}}
306 +
307 +
308 +{{pagetreesearch rootPage="System Utilities"/}}
309 +{{/panel}}
310 +
348 348  {{panel title="More System UTILITIES"}}
349 349  {{expand title="Expand"}}
350 350  
... ... @@ -376,6 +376,7 @@
376 376  (% style="margin-left: 30.0px;" %)
377 377  [[Widget Builder>>doc:Utilities - Widget Builder]]
378 378  
342 +(% style="margin-left: 30.0px;" %)
379 379  
380 380  
381 381  (% style="margin-left: 30.0px;" %)
... ... @@ -383,8 +383,9 @@
383 383  {{/expand}}
384 384  {{/panel}}
385 385  
350 +\\
386 386  
387 -
352 +\\
388 388  {{/layout-cell}}
389 389  {{/layout-section}}
390 390  {{/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 +45940746
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/45940746/Utilities - DExTr