Skip to Content

Changes for page Utilities - DExTr

Last modified by Admin User on 2025/04/30 18:37
From version 18.1
edited by Admin User
on 2025/04/30 09:35
Change comment: There is no comment for this version
To version 11.1
edited by Admin
on 2019/12/23 14:26
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,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,9 +150,12 @@
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 +\\
153 153  
154 -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.
169 +\\
155 155  
171 +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.
172 +
156 156  There are four Mapping Areas for Transaction Mapping:
157 157  
158 158  * (((
... ... @@ -174,7 +174,7 @@
174 174  
175 175  **THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).**
176 176  
177 -*(% style="text-decoration:underline" %)Product Mapping Area(%%) *
194 +*(% style="text-decoration: underline;" %)Product Mapping Area(%%) *
178 178  **For automated data feed reports**, the Third Party Product column shows what the ONEcount product name will be displayed as on output.
179 179  
180 180  * (((
... ... @@ -191,7 +191,7 @@
191 191  **Product Column Field:** This identifies the column header for the product column in the import file. In the above example, you would enter "product".
192 192  )))
193 193  
194 -(% style="text-decoration:underline" %)**Product Status Mapping Area (Optional)**(%%)
211 +(% style="text-decoration: underline;" %)**Product Status Mapping Area (Optional)**(%%)
195 195  **For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
196 196  
197 197  * (((
... ... @@ -208,7 +208,7 @@
208 208  **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".
209 209  )))
210 210  
211 -(% style="text-decoration:underline" %)**Subscription Mapping Area**(%%)
228 +(% style="text-decoration: underline;" %)**Subscription Mapping Area**(%%)
212 212  **For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
213 213  
214 214  * (((
... ... @@ -225,20 +225,14 @@
225 225  **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".
226 226  )))
227 227  
228 -(% style="text-decoration:underline" %)**Date Mapping Area**(%%)
229 -**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
230 -
231 -(% 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
232 -
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.
233 233  **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.
234 234  
235 -**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
236 -
237 -(% 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
238 -
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.
239 239  **Date Column Field:** This identifies the column header for the date column in the import file.
240 240  
241 -When done with mapping, click "Next".
252 +When done with mapping, click "Next".
242 242  You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.**SAVE MAPPING**
243 243  
244 244  When done with mapping(s), click "Next".
... ... @@ -252,93 +252,21 @@
252 252  
253 253  
254 254  {{id name="End ScreenSteps Content"/}}
266 +{{/layout-cell}}
255 255  
256 -=== MAPPING ENGAGEMENT DATA ===
268 +{{layout-cell}}
269 +{{panel borderStyle="solid" title="Search all Documentation:"}}
257 257  
258 -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.
259 259  
260 -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.
272 +{{livesearch/}}
273 +{{/panel}}
261 261  
262 -Generic Engagement Fields
275 +{{panel borderStyle="solid" title="Search System UTILITIES:"}}
263 263  
264 -* Activity Date: Date of the Activity
265 -* Activity Time: Time of the Activity, Mandatory for Import.
266 -* Channel Codes: Codes for Email, Banner and Web page views, CMI needed it in export.
267 -* End Date: End date of export, mainly used in aggregate export.
268 -* Unique External ID: Unique ID for each transaction.
269 -* Month: Month of the Activity.
270 -* OCID:
271 -* OCID Hash: Unique hash of the user. This is the cookie set on user’s browser.
272 -* Platform Viewed: Platform of the user in which Impression or Page view happened.
273 -* 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.
274 -* Start Date: Start date of export, mainly used in aggregate export.
275 275  
276 -Metric Engagement Fields
278 +{{pagetreesearch rootPage="System Utilities"/}}
279 +{{/panel}}
277 277  
278 -* 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.
279 -* 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.
280 -* Activity Metric count: Mainly used for export. It has counts for each activity.
281 -* 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.
282 -* 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.
283 -* Aggregate Metric count: Mainly used for export. It has counts for each activity.
284 -
285 -Banner Engagement
286 -
287 -* Ad Server Name: Name of the Ad Server, i.e., DFP
288 -* Advertiser ID: ID of the Advertiser
289 -* Advertiser Name: Name of the Advertiser
290 -* Banner ID: ID of the Banner
291 -* Banner Name: Name of the Banner
292 -* Campaign ID: ID of the Campaign
293 -* Campaign Name: Name of the Campaign
294 -* Viewable Impression: If Impression is viewed or not, Boolean (0, 1 accepted)
295 -
296 -Newsletter Engagement Fields
297 -
298 -* Click URL: URL of the Clicked link. Mandatory for Importing Email clicks.
299 -* List ID: ID of the newsletter List of Group
300 -* List Name: Name of the newsletter list or group
301 -* Message ID: Campaign ID of the newsletter
302 -* Message Name: Campaign name of the newsletter
303 -* Recipient ID: Unique User Id in the Email service provider
304 -* Message Subject: Subject of the Campaign
305 -
306 -Web Engagement Fields
307 -
308 -* Referrer: Referrer for the page view
309 -* Site name: Website URL
310 -* Page URL: URL of the Page.
311 -
312 -=== **HOW DExTr MAPS DATA** ===
313 -
314 -The following information is being provided to help you understand how DExTr will map/transform your data on import.
315 -
316 -(% class="diff-block-target" %)
317 -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.//
318 -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
319 -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.
320 -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.
321 -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.
322 -1. For Package transactions: Term ID, Package status, source code and transaction type are mandatory.
323 -11. If Term ID is not mapped, then the transaction won’t be imported.
324 -11. IF Package status is not mapped then default Package status from term will be added.
325 -11. If source code is not mapped. Then default source code from import job will be selected.
326 -11. If transaction type is not added, then default type from Import job will be selected.
327 -1. For Product transaction: Product ID, source code and transaction type are mandatory.
328 -11. If Product ID is not mapped, then the transaction won’t be imported.
329 -11. If source code is not mapped. Then default source code from import job will be selected.
330 -11. If transaction type is not added, then default type from Import job will be selected.
331 -1. If Transaction Date is not mapped or not formatted correctly, then current date will be used as request date.
332 -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.
333 -1. For Engagement imports, Activity type is mandatory.
334 -1. If Engagement date is not formatted, then current date will be used as activity date.
335 -1. If Data and campaign ID, name, List ID and name then they will be imported as well.
336 -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.
337 -
338 -
339 -{{/layout-cell}}
340 -
341 -{{layout-cell}}
342 342  {{panel title="More System UTILITIES"}}
343 343  {{expand title="Expand"}}
344 344  
... ... @@ -350,10 +350,10 @@
350 350  [[Backend User Permissions>>doc:Utilities - Backend Users and Permissions]]
351 351  
352 352  (% style="margin-left: 30.0px;" %)
353 -[[Email Engine Sender Score>>doc:ONEmail and Sender Score]]
292 +[[Email Engine Sender Score>>doc:Email Engine and Sender Score]]
354 354  
355 355  (% style="margin-left: 30.0px;" %)
356 -[[doc:ONEmail]]
295 +[[doc:Email Engine]]
357 357  
358 358  (% style="margin-left: 30.0px;" %)
359 359  Action Manager
... ... @@ -370,6 +370,7 @@
370 370  (% style="margin-left: 30.0px;" %)
371 371  [[Widget Builder>>doc:Utilities - Widget Builder]]
372 372  
312 +(% style="margin-left: 30.0px;" %)
373 373  
374 374  
375 375  (% style="margin-left: 30.0px;" %)
... ... @@ -377,8 +377,35 @@
377 377  {{/expand}}
378 378  {{/panel}}
379 379  
320 +\\
380 380  
381 -
322 +\\
382 382  {{/layout-cell}}
383 383  {{/layout-section}}
384 384  {{/layout}}
326 +
327 +\\
328 +
329 +\\
330 +
331 +\\
332 +
333 +\\
334 +
335 +\\
336 +
337 +\\
338 +
339 +\\
340 +
341 +\\
342 +
343 +\\
344 +
345 +\\
346 +
347 +\\
348 +
349 +\\
350 +
351 +\\
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 +23331608
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/23331608/Utilities - DExTr