Changes for page Utilities - DExTr

Last modified by rayaan@one-count_com on 2023/11/09 10:38
From version 12.1
edited by Admin
on 2019/12/28 18:29
Change comment: There is no comment for this version
To version 14.1
edited by Admin
on 2021/03/11 15:37
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -61,7 +61,7 @@
61 61  (% style="margin-left: 30.0px;" %)
62 62  \\
63 63  
64 -Creating a Data Mapping
64 +=== Creating a Data Mapping ===
65 65  
66 66  **[[image:attach:New-DExTr-Mapping.png||height="250"]]**
67 67  
... ... @@ -263,6 +263,90 @@
263 263  
264 264  
265 265  {{id name="End ScreenSteps Content"/}}
266 +
267 +=== MAPPING ENGAGEMENT DATA ===
268 +
269 +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 +
271 +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 +
273 +Generic Engagement Fields
274 +
275 +* Activity Date: Date of the Activity
276 +* Activity Time: Time of the Activity, Mandatory for Import.
277 +* Channel Codes: Codes for Email, Banner and Web page views, CMI needed it in export.
278 +* End Date: End date of export, mainly used in aggregate export.
279 +* Unique External ID: Unique ID for each transaction.
280 +* Month: Month of the Activity.
281 +* OCID:
282 +* OCID Hash: Unique hash of the user. This is the cookie set on user’s browser.
283 +* Platform Viewed: Platform of the user in which Impression or Page view happened.
284 +* 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.
285 +* Start Date: Start date of export, mainly used in aggregate export.
286 +
287 +Metric Engagement Fields
288 +
289 +* 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.
290 +* 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.
291 +* Activity Metric count: Mainly used for export. It has counts for each activity.
292 +* 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.
293 +* 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.
294 +* Aggregate Metric count: Mainly used for export. It has counts for each activity.
295 +
296 +Banner Engagement
297 +
298 +* Ad Server Name: Name of the Ad Server, i.e., DFP
299 +* Advertiser ID: ID of the Advertiser
300 +* Advertiser Name: Name of the Advertiser
301 +* Banner ID: ID of the Banner
302 +* Banner Name: Name of the Banner
303 +* Campaign ID: ID of the Campaign
304 +* Campaign Name: Name of the Campaign
305 +* Viewable Impression: If Impression is viewed or not, Boolean (0, 1 accepted)
306 +
307 +Newsletter Engagement Fields
308 +
309 +* Click URL: URL of the Clicked link. Mandatory for Importing Email clicks.
310 +* List ID: ID of the newsletter List of Group
311 +* List Name: Name of the newsletter list or group
312 +* Message ID: Campaign ID of the newsletter
313 +* Message Name: Campaign name of the newsletter
314 +* Recipient ID: Unique User Id in the Email service provider
315 +* Message Subject: Subject of the Campaign
316 +
317 +Web Engagement Fields
318 +
319 +* Referrer: Referrer for the page view
320 +* Site name: Website URL
321 +* Page URL: URL of the Page.
322 +
323 +=== **HOW DExTr MAPS DATA** ===
324 +
325 +The following information is being provided to help you understand how DExTr will map/transform your data on import.
326 +
327 +(% class="diff-block-target" %)
328 +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.//
329 +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
330 +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.
331 +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.
332 +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.
333 +1. For Package transactions: Term ID, Package status, source code and transaction type are mandatory.
334 +11. If Term ID is not mapped, then the transaction won’t be imported.
335 +11. IF Package status is not mapped then default Package status from term will be added.
336 +11. If source code is not mapped. Then default source code from import job will be selected.
337 +11. If transaction type is not added, then default type from Import job will be selected.
338 +1. For Product transaction: Product ID, source code and transaction type are mandatory.
339 +11. If Product ID is not mapped, then the transaction won’t be imported.
340 +11. If source code is not mapped. Then default source code from import job will be selected.
341 +11. If transaction type is not added, then default type from Import job will be selected.
342 +1. If Transaction Date is not mapped or not formatted correctly, then current date will be used as request date.
343 +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.
344 +1. For Engagement imports, Activity type is mandatory.
345 +1. If Engagement date is not formatted, then current date will be used as activity date.
346 +1. If Data and campaign ID, name, List ID and name then they will be imported as well.
347 +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.
348 +
349 +\\
266 266  {{/layout-cell}}
267 267  
268 268  {{layout-cell}}
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -23331872
1 +62521418
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/23331872/Utilities - DExTr
1 +https://info.onecount.net//wiki/spaces/OD/pages/62521418/Utilities - DExTr