Skip to Content
Last modified by Admin User on 2025/05/29 16:38
From version 10.1
edited by Admin User
on 2025/05/29 16:36
Change comment: There is no comment for this version
To version 11.1
edited by Admin User
on 2025/05/29 16:38
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -MAPPING ENGAGEMENT DATA
1 +DEXTR -- Converting Your Data
Content
... ... @@ -1,4 +1,4 @@
1 -dNEW DEXTR
1 += Introduction =
2 2  
3 3  DExTr is ONEcount’s data exchange and transformation engine. This tool enables data exchangs 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.
4 4  
... ... @@ -31,44 +31,44 @@
31 31  
32 32  
33 33  
34 -[[image:new-dextr-doc_387f0c278f1e2969.png||height="173" width="665"]]\\
34 +[[image:new-dextr-doc_387f0c278f1e2969.png||height="173" width="665"]]
35 35  
36 36  To get started, go to Data Management → DExTR from the menu on the left side. You’ll see a list of existing DExTR mappings, and have the opportunity to create a new mapping by clicking the button on the upper right side.
37 37  
38 -[[image:new-dextr-doc_ca0183ab0ec25820.png||height="557" width="665"]]\\
38 +[[image:new-dextr-doc_ca0183ab0ec25820.png||height="557" width="665"]]
39 39  
40 40  
41 41  
42 42  
43 -Click Create Mapper
43 +== Click Create Mapper ==
44 44  
45 45  You will be asked to give the mapper a title, and a description if needed. You should plan on creating one mapper per data source, although there may be examples where you need more than one mapper. For example, you may export data from SalesForce, but in two different ways: one for webinar registrations, one for sales data. Each format could require a separate mapper to handle the data.
46 46  
47 47  The easiest way to build a mapper is to upload your file and let DExTR pre-populate the mapping. The file must be in CSV format in order to import into ONEcount, so we recommend using that for building the mapper.
48 48  
49 -[[image:new-dextr-doc_68c2dcabfcf1448b.png||height="349" width="665"]]\\
49 +[[image:new-dextr-doc_68c2dcabfcf1448b.png||height="349" width="665"]]
50 50  
51 51  Select the file and hit upload. The system will load all of the column headings from your file into the DExTR UI.
52 52  
53 53  
54 54  
55 -[[image:new-dextr-doc_49c7e86855c5f89f.png||height="554" width="665"]]\\
55 +[[image:new-dextr-doc_49c7e86855c5f89f.png||height="554" width="665"]]
56 56  
57 57  DExTR Maps Demographic, Transaction and Engagement Data. The pull-down next to each column heading lets you choose what type of data is in that column.
58 58  
59 59  
60 -[[image:new-dextr-doc_fa3f55daf981a1e7.png||height="542" width="665"]]\\
60 +[[image:new-dextr-doc_fa3f55daf981a1e7.png||height="542" width="665"]]
61 61  
62 62  
63 63  If you select Demographic, a new column pops up with all of the Demographic Questions you have configured in the ONEcount system. The pull-down only contains the first 20 or so demographic questions. If the one you are looking for is not there, click the back-space button and start typing the demo, and the system will auto-complete as you type.
64 64  
65 -[[image:new-dextr-doc_eb4c8f499e373c8.png||height="556" width="665"]]\\
65 +[[image:new-dextr-doc_eb4c8f499e373c8.png||height="556" width="665"]]
66 66  
67 67  
68 68  
69 69  For transactions, DExTR shows the transaction fields that can be mapped into the system.
70 70  
71 -[[image:new-dextr-doc_df0894c16d4a01b0.png||height="556" width="665"]]\\
71 +[[image:new-dextr-doc_df0894c16d4a01b0.png||height="556" width="665"]]
72 72  
73 73  If you select an option in the third column, demo/trans/engagment that has fielded data, like check-box, select, multi-select, etc., a fourth column will automatically appear that says, “Map Values.” Clicking on this link will open a pop-up that allows you to map the column values from your file into the appropriate values in ONEcount. The value from the file will appear in the box on the right, the ONEcount value to map it to will appear in the pull-down on the left.
74 74  
... ... @@ -76,7 +76,7 @@
76 76  
77 77  
78 78  
79 -[[image:new-dextr-doc_e3e1a93820e15af4.png||height="313" width="491"]]\\
79 +[[image:new-dextr-doc_e3e1a93820e15af4.png||height="313" width="491"]]
80 80  
81 81  
82 82  
... ... @@ -131,7 +131,7 @@
131 131  **Product Column Field:** This identifies the column header for the product column in the import file. In the above example, you would enter "product".
132 132  
133 133  **__Product Status Mapping Area (Optional)__**
134 - **For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
134 +**For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
135 135  
136 136  * For example, a user has a product status of "Not Active(405)" in ONEcount. The third party requires that the report output show a value of Inactive, rather than Not Active. Mapping ONEcont's "Not Active(405)" status to "Inactive(203)" will display the Third Party Product Status of Inactive on the output.
137 137  
... ... @@ -144,7 +144,7 @@
144 144  **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".
145 145  
146 146  **__Subscription Mapping Area__**
147 - **For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
147 +**For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
148 148  
149 149  * For example, a user has a subscription type of "n" in ONEcount. The third party requires that the report output show a value of new, rather than "n". Mapping ONEcont's "n" status to "new(new)" will display the Third Party Product Status of new on the output.
150 150  
... ... @@ -157,7 +157,7 @@
157 157  **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".
158 158  
159 159  **__Date Mapping Area__**
160 - **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
160 +**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
161 161  
162 162  MM : months, dd: days, yyyy: years, hh: hours (12 hour format), HH: hours (24 hour format), mm: minutes, ss: seconds, a:AM/PM
163 163  
... ... @@ -180,7 +180,7 @@
180 180  
181 181  A saved mapping is ready to be used for generating automated feed reports in the Dashboard. See Dashboard Reports – Create Feed Report for more information.
182 182  
183 -=== {{id name="HMAPPINGENGAGEMENTDATA"/}}**MAPPING ENGAGEMENT DATA** ===
183 +== **MAPPING ENGAGEMENT DATA** ==
184 184  
185 185  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.
186 186  
... ... @@ -236,7 +236,7 @@
236 236  * Site name: Website URL
237 237  * Page URL: URL of the Page.
238 238  
239 -=== {{id name="HHOWDExTrMAPSDATA"/}}**HOW DExTr MAPS DATA** ===
239 +== **HOW DExTr MAPS DATA** ==
240 240  
241 241  The following information is being provided to help you understand how DExTr will map/transform your data on import.
242 242  
... ... @@ -261,8 +261,7 @@
261 261  1. If Data and campaign ID, name, List ID and name then they will be imported as well.
262 262  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.
263 263  
264 -
265 265  
266 266  
267 -~*~**Remember to SAVE the values mapping, and SAVE the DExTR mapping when you are through.
268 268  
267 +~*~**Remember to SAVE the values mapping, and SAVE the DExTR mapping when you are through.