Skip to Content

Changes for page Utilities - DExTr

Last modified by Admin User on 2025/04/30 18:37
From version 13.1
edited by Admin
on 2020/05/08 16:35
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

Summary

Details

Page properties
Parent
... ... @@ -1,0 +1,1 @@
1 +System Utilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Admin
1 +XWiki.admin
Content
... ... @@ -1,8 +1,6 @@
1 1  {{layout}}
2 2  {{layout-section ac:type="two_right_sidebar"}}
3 3  {{layout-cell}}
4 -
5 -
6 6  {{id name="Start ScreenSteps Content"/}}
7 7  
8 8  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.
... ... @@ -37,9 +37,9 @@
37 37  
38 38  **OPEN THE MAPPING WINDOW**
39 39  
40 -Select UTILITIES from the main menu and the DExTr from the sub-menu.
38 +Select DATA MANAGEMENT from the main menu and the DExTr from the sub-menu.
41 41  
42 -[[image:attach:DExTr Nav.png||width="707"]]
40 +[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 8.png||thumbnail="true" height="250"]]
43 43  
44 44  This will open the Main DExTr Listing Page, as shown below.
45 45  
... ... @@ -47,7 +47,6 @@
47 47  
48 48  [[image:attach:DExTr Listing Page.png||height="250"]]
49 49  
50 -\\
51 51  
52 52  Select "Create Mapping" to create a new mapping. This will open the Mapping Builder, as shown below.
53 53  
... ... @@ -54,18 +54,14 @@
54 54  To edit an existing mapping, select the Edit icon.
55 55  To copy an existing mapping, select the Copy icon.
56 56  To delete an existing mapping, select the Delete icon.
57 -\\
54 +
58 58  
59 -\\
60 60  
61 -(% style="margin-left: 30.0px;" %)
62 -\\
63 63  
64 -Creating a Data Mapping
58 +=== Creating a Data Mapping ===
65 65  
66 66  **[[image:attach:New-DExTr-Mapping.png||height="250"]]**
67 67  
68 -\\
69 69  
70 70  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.
71 71  
... ... @@ -73,7 +73,7 @@
73 73  
74 74  1. (((
75 75  (((
76 -Exchange Map** - **Define Exchange Map
69 +Exchange Map** - **Define Exchange Map
77 77  )))
78 78  
79 79  (((
... ... @@ -83,14 +83,11 @@
83 83  )))
84 84  )))
85 85  
86 -\\
87 -
88 88  [[image:attach:DExTr Demo Tab.png||width="800"]]
89 89  
90 -\\
91 91  
92 92  1. (((
93 -Demographic Fields** - ** Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.
83 +Demographic Fields** - ** Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.
94 94  )))
95 95  
96 96  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 @@
99 99  
100 100  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.
101 101  
102 -\\
103 103  
104 104  [[image:attach:DExTr Value Mapping Pop-Up.png||height="250"]]
105 105  
106 -\\
107 107  
108 -\\
109 109  
110 110  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.
111 111  
112 112  //(Example: states may be abbreviated with 4 letters in a POS database [Conn., Mass.], while the ecommerce database has two letter abbreviations.)//
113 113  
114 -\\
115 115  
116 116  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.
117 117  
118 118  1. (((
119 -Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
105 +Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
120 120  )))
121 121  
122 122  * (((
... ... @@ -130,9 +130,9 @@
130 130  Within the “Map Values” pop up window, click “Add” to define all possible transactional statuses.
131 131  )))
132 132  
133 -1.
119 +1.
134 134  
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.
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.
136 136  )))
137 137  
138 138  * (((
... ... @@ -164,10 +164,6 @@
164 164  *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.
165 165  )))
166 166  
167 -\\
168 -
169 -\\
170 -
171 171  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.
172 172  
173 173  There are four Mapping Areas for Transaction Mapping:
... ... @@ -191,7 +191,7 @@
191 191  
192 192  **THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).**
193 193  
194 -*(% style="text-decoration: underline;" %)Product Mapping Area(%%) *
176 +*(% style="text-decoration:underline" %)Product Mapping Area(%%) *
195 195  **For automated data feed reports**, the Third Party Product column shows what the ONEcount product name will be displayed as on output.
196 196  
197 197  * (((
... ... @@ -208,7 +208,7 @@
208 208  **Product Column Field:** This identifies the column header for the product column in the import file. In the above example, you would enter "product".
209 209  )))
210 210  
211 -(% style="text-decoration: underline;" %)**Product Status Mapping Area (Optional)**(%%)
193 +(% style="text-decoration:underline" %)**Product Status Mapping Area (Optional)**(%%)
212 212  **For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
213 213  
214 214  * (((
... ... @@ -225,7 +225,7 @@
225 225  **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".
226 226  )))
227 227  
228 -(% style="text-decoration: underline;" %)**Subscription Mapping Area**(%%)
210 +(% style="text-decoration:underline" %)**Subscription Mapping Area**(%%)
229 229  **For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
230 230  
231 231  * (((
... ... @@ -242,14 +242,20 @@
242 242  **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".
243 243  )))
244 244  
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.
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 +
247 247  **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.
248 248  
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.
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 +
250 250  **Date Column Field:** This identifies the column header for the date column in the import file.
251 251  
252 -When done with mapping, click "Next".
240 +When done with mapping, click "Next".
253 253  You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.**SAVE MAPPING**
254 254  
255 255  When done with mapping(s), click "Next".
... ... @@ -264,10 +264,64 @@
264 264  
265 265  {{id name="End ScreenSteps Content"/}}
266 266  
267 -\\
255 +=== MAPPING ENGAGEMENT DATA ===
268 268  
269 -**HOW DExTr MAPS DATA**
257 +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.
270 270  
259 +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.
260 +
261 +Generic Engagement Fields
262 +
263 +* Activity Date: Date of the Activity
264 +* Activity Time: Time of the Activity, Mandatory for Import.
265 +* Channel Codes: Codes for Email, Banner and Web page views, CMI needed it in export.
266 +* End Date: End date of export, mainly used in aggregate export.
267 +* Unique External ID: Unique ID for each transaction.
268 +* Month: Month of the Activity.
269 +* OCID:
270 +* OCID Hash: Unique hash of the user. This is the cookie set on user’s browser.
271 +* Platform Viewed: Platform of the user in which Impression or Page view happened.
272 +* 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.
273 +* Start Date: Start date of export, mainly used in aggregate export.
274 +
275 +Metric Engagement Fields
276 +
277 +* 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.
278 +* 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.
279 +* Activity Metric count: Mainly used for export. It has counts for each activity.
280 +* 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.
281 +* 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.
282 +* Aggregate Metric count: Mainly used for export. It has counts for each activity.
283 +
284 +Banner Engagement
285 +
286 +* Ad Server Name: Name of the Ad Server, i.e., DFP
287 +* Advertiser ID: ID of the Advertiser
288 +* Advertiser Name: Name of the Advertiser
289 +* Banner ID: ID of the Banner
290 +* Banner Name: Name of the Banner
291 +* Campaign ID: ID of the Campaign
292 +* Campaign Name: Name of the Campaign
293 +* Viewable Impression: If Impression is viewed or not, Boolean (0, 1 accepted)
294 +
295 +Newsletter Engagement Fields
296 +
297 +* Click URL: URL of the Clicked link. Mandatory for Importing Email clicks.
298 +* List ID: ID of the newsletter List of Group
299 +* List Name: Name of the newsletter list or group
300 +* Message ID: Campaign ID of the newsletter
301 +* Message Name: Campaign name of the newsletter
302 +* Recipient ID: Unique User Id in the Email service provider
303 +* Message Subject: Subject of the Campaign
304 +
305 +Web Engagement Fields
306 +
307 +* Referrer: Referrer for the page view
308 +* Site name: Website URL
309 +* Page URL: URL of the Page.
310 +
311 +=== **HOW DExTr MAPS DATA** ===
312 +
271 271  The following information is being provided to help you understand how DExTr will map/transform your data on import.
272 272  
273 273  (% class="diff-block-target" %)
... ... @@ -285,7 +285,7 @@
285 285  11. If Product ID is not mapped, then the transaction won’t be imported.
286 286  11. If source code is not mapped. Then default source code from import job will be selected.
287 287  11. If transaction type is not added, then default type from Import job will be selected.
288 -1. If Transaction Date is not mapped or not formatted correctly, then current date will be used as request date.
330 +1. If Request Date is not mapped or not formatted correctly, then current date will be used as request date.
289 289  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.
290 290  1. For Engagement imports, Activity type is mandatory.
291 291  1. If Engagement date is not formatted, then current date will be used as activity date.
... ... @@ -292,22 +292,10 @@
292 292  1. If Data and campaign ID, name, List ID and name then they will be imported as well.
293 293  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.
294 294  
295 -\\
337 +
296 296  {{/layout-cell}}
297 297  
298 298  {{layout-cell}}
299 -{{panel borderStyle="solid" title="Search all Documentation:"}}
300 -
301 -
302 -{{livesearch/}}
303 -{{/panel}}
304 -
305 -{{panel borderStyle="solid" title="Search System UTILITIES:"}}
306 -
307 -
308 -{{pagetreesearch rootPage="System Utilities"/}}
309 -{{/panel}}
310 -
311 311  {{panel title="More System UTILITIES"}}
312 312  {{expand title="Expand"}}
313 313  
... ... @@ -339,7 +339,6 @@
339 339  (% style="margin-left: 30.0px;" %)
340 340  [[Widget Builder>>doc:Utilities - Widget Builder]]
341 341  
342 -(% style="margin-left: 30.0px;" %)
343 343  
344 344  
345 345  (% style="margin-left: 30.0px;" %)
... ... @@ -347,9 +347,8 @@
347 347  {{/expand}}
348 348  {{/panel}}
349 349  
350 -\\
351 351  
352 -\\
380 +
353 353  {{/layout-cell}}
354 354  {{/layout-section}}
355 355  {{/layout}}
DExTr Demo Tab.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +196.0 KB
Content
DExTr Listing Page.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +144.2 KB
Content
DExTr Nav.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +51.4 KB
Content
DExTr Value Mapping Pop-Up.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +119.3 KB
Content
New-DExTr-Mapping.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +89.9 KB
Content
Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +17.7 KB
Content
media_1467388147151.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +30.4 KB
Content
media_1467391080266.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +56.2 KB
Content
media_1467391237758.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +63.3 KB
Content
media_1467391409099.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +160.0 KB
Content
media_1467396172019.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +80.4 KB
Content
media_1467397686498.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +29.5 KB
Content
media_1467398257338.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +37.2 KB
Content
media_1467398286154.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +18.0 KB
Content
media_1467398730892.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +112.7 KB
Content
media_1467398948360.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +8.8 KB
Content
media_1467399198566.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +51.5 KB
Content
media_1467651841763.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +170.2 KB
Content
media_1468251499518.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +28.5 KB
Content
media_1468251557794.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +26.0 KB
Content
media_1468252151743.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +122.0 KB
Content
media_1468252886176.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +92.5 KB
Content
media_1468256607407.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.XWikiGuest
Size
... ... @@ -1,0 +1,1 @@
1 +90.4 KB
Content
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -45940746
1 +67230
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/45940746/Utilities - DExTr
1 +https://info.onecount.net//wiki/spaces/OD/pages/67230/Utilities - DExTr