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 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
Content
... ... @@ -150,7 +150,6 @@
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  
153 -
154 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.
155 155  
156 156  There are four Mapping Areas for Transaction Mapping:
... ... @@ -328,7 +328,7 @@
328 328  11. If Product ID is not mapped, then the transaction won’t be imported.
329 329  11. If source code is not mapped. Then default source code from import job will be selected.
330 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.
330 +1. If Request Date is not mapped or not formatted correctly, then current date will be used as request date.
332 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 333  1. For Engagement imports, Activity type is mandatory.
334 334  1. If Engagement date is not formatted, then current date will be used as activity date.