Changes for page Utilities - DExTr

Last modified by rayaan@one-count_com on 2023/11/09 10:38
From version 15.1
edited by rayaan@one-count_com
on 2023/11/09 10:38
Change comment: There is no comment for this version
To version 3.1
edited by melanie@one-count_com
on 2016/12/13 12:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Utilities - DExTr
1 +Utilities - Mapper (v12.x)
Parent
... ... @@ -1,1 +1,0 @@
1 -System Utilities
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.rayaan@one-count_com
1 +XWiki.melanie@one-count_com
Content
... ... @@ -1,415 +4,250 @@
1 -{{layout}}
2 -{{layout-section ac:type="two_right_sidebar"}}
3 -{{layout-cell}}
4 4  
5 5  
6 6  {{id name="Start ScreenSteps Content"/}}
4 + The Mapper is used to create mappings for generating automated feed reports for export and for data import. This tool allows you to map your, or third party, data to ONEcount questions/data fields.
7 7  
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.
9 -
10 -This tool the capabilities to map and sync first- or third-party data to ONEcount questions/data fields.
11 -
12 -If there are multiple databases with similar fields, DExTr can consolidate the similar datapoints into a single ONEcount question or keep the fields separate. //(Example: if the field for ‘Customer ID’ in a legacy database is “CUST_ID” and the field name in a CRM is “CID”, there is an option to have the data consolidated in to the single ONEcount question that may be named “CustomerID”.//
13 -
14 14  **If you will be using the Dashboard Feed Report function to generate an automated feed report or will be performing a data import that requires mapping external file questions/data to ONEcount questions/data, you must complete the report mapping here first.**
15 15  
16 16  There are three types of mapping in the Mapper: Demographic Mapping and Transaction Mapping.
17 17  
18 -* (((
19 -**Demographic Mapping:** Demographic mapping maps external demographic questions/data fields and responses to ONEcount demographic questions and responses.
20 -)))
21 -* (((
22 -**Transaction Mapping:** Transaction mapping maps external transaction data, e.g. product purchase activity, status, and date formats.
23 -)))
24 -* (((
25 -**Engagement Mapping:** Activity mapping maps external activity headers, e.g. time on page, URL, impressions, etc. This mapping is used primarily for feed reports for export, or importing activity from another system like an e-mail system.
26 -)))
10 +* **Demographic Mapping:** Demographic mapping maps external demographic questions/data fields and responses to ONEcount demographic questions and responses.
11 +* **Transaction Mapping:** Transaction mapping maps external transaction data, e.g. product activity, status, and date formats.
12 +* **Activity Mapping:** Activity mapping maps external activity headers, e.g. time on page, URL, impressions, etc. This mapping is used primarily for feed reports for export.
27 27  
28 28  One or all of these types of mapping may be required, depending on the type of automated feed report you want to generate or the data import you'll be performing.
29 29  
30 -You can either import a layout file (.csv format) with all of the necessary demographic, transacactional and engagement fields,  and map demographics and transactions directly from that file, or you can manually enter the demographics, transactions, and activities you wish to map to ONEcount questions/data fields, or do a combination of both.
16 +You can either import a layout file (.csv format) and map demographics and transactions directly from that file or manually enter the demographics, transactions, and activities you wish to map to ONEcount questions/data fields, or do a combination of both.
31 31  
32 32  **Please Note:**
33 33  
34 -**ONEcount questions, response valuess, products and packages must be created prior to performing mapping.**
20 +**ONEcount questions and response values must be created prior to performing mapping.**
35 35  
36 36  **Third-party activity headers currently can't be mapped via an uploaded layout file. They must be mapped manually in the Activity Mapping Area.**
37 37  
38 -**OPEN THE MAPPING WINDOW**
24 +=== OPENING THE MAPPING WINDOW ===
39 39  
40 -Select DATA MANAGEMENT from the main menu and the DExTr from the sub-menu.
26 +=== Select UTILTIES from the main menu. ===
41 41  
42 -[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 8.png||thumbnail="true" height="250"]]
28 +[[image:attach:media_1468251499518.png||align="center"]]
43 43  
44 -This will open the Main DExTr Listing Page, as shown below.
30 +=== Select Mapper from the sub-menu. ===
45 45  
46 -**CREATE A NEW DExTr MAPPING**
32 +[[image:attach:media_1468251557794.png||align="center"]]
47 47  
48 -[[image:attach:DExTr Listing Page.png||height="250"]]
34 +This will open the Manage Mapping Listing Page, as shown below.
49 49  
50 -\\
36 +=== CREATE A NEW DATA MAPPING ===
51 51  
38 +[[image:attach:media_1467388147151.png||align="center"]]
39 +
52 52  Select "Create Mapping" to create a new mapping. This will open the Mapping Builder, as shown below.
53 53  
54 54  To edit an existing mapping, select the Edit icon.
55 -To copy an existing mapping, select the Copy icon.
56 -To delete an existing mapping, select the Delete icon.
57 -\\
43 + To delete an existing mapping, select the Delete icon.
58 58  
59 -\\
45 +=== 1 – INFORMATION AND DEMOGRAPHIC MAPPING ===
60 60  
61 -(% style="margin-left: 30.0px;" %)
62 -\\
47 +[[image:attach:media_1468252151743.png||align="center"]]
63 63  
64 -=== Creating a Data Mapping ===
49 +Information and Demo Mapping consists of three main parts:
65 65  
66 -**[[image:attach:New-DExTr-Mapping.png||height="250"]]**
51 +**1 – Information**
52 + **2 – Mapping Area**
53 + **3 – ONEcount Questions**
67 67  
68 -\\
55 +See below for detail on each part.
69 69  
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.
57 +=== INFORMATION ===
71 71  
72 -Navigate across the six tabs at the top of the interface to configure how the customer data platform will interpret and exchange data.
59 +**Name:** Give the mapping a name (required)
73 73  
74 -1. (((
75 -(((
76 -Exchange Map** - **Define Exchange Map
77 -)))
61 +**Description:** Provide a description of the mapping (optional)
78 78  
79 -(((
80 -1. (((
81 -Enter a name and description for this data exchange, then proceed to the next tab (Demographic Fields).
82 -)))
83 -)))
84 -)))
63 +**Select whether you want to map transactions and/or activity:** You can create a mapping for demographic questions only, or map any combination of demographics, transactions, and actions.
85 85  
86 -\\
65 +**Upload Layout:** Uploading a layout document is optional. You may opt to manually enter demographic and transactional questions and values to be mapped to ONEcount questions and values. Or, you may use a combination of both uploading a layout and manual entry.
87 87  
88 -[[image:attach:DExTr Demo Tab.png||width="800"]]
67 +(% style="text-decoration: underline;" %)//**To Upload a Layout File**//(%%)
68 + Click on the "Browse" button, locate the file on your computer, then click on "Upload File".
89 89  
90 -\\
70 +When you upload an external layout, the Demographic and Transacton Mapping Areas will be automatically pre-populated with each question/data field and values for that field. (See screenshotbelow)
91 91  
92 -1. (((
93 -Demographic Fields** - ** Map external demographic questions/data fields and responses to ONEcount demographic questions and responses.
94 -)))
72 +See screenshots of pre-population and layout formatting rules below.
95 95  
96 -Define field names (the column headers from the import file) on the left and match them to the ONEcount field on the right.
74 +=== Layout File Format ===
97 97  
98 -If the ONEcount field does not yet exist, you'll need to create it using the Question Builder (see “Getting Started” section above).Map Values & Field Response Labels (non-text fields only)
76 +[[image:attach:media_1468252886176.png||align="center"]]
99 99  
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.
78 +_(% style="text-decoration: underline;" %)**Layout File Format**(%%) _
79 + The layout file must be in .csv format and include markers for demographic questions (~#~##demographics), products (~#~##products~#~##), subscription type(~#~##subscriptionType~#~##), and product status (optional) (~#~##productStatus~#~##).
101 101  
102 -\\
81 +(% style="text-decoration: underline;" %)//Demographic Mapping//
103 103  
104 -[[image:attach:DExTr Value Mapping Pop-Up.png||height="250"]]
83 +* For Demographic Questions: Question text must be in Column A, response values for multiple response-type questions* in Column B, and response text values in Column C.
84 + *Note that text-response type questions, e.g. last name, don't require values in Column B or C.
105 105  
106 -\\
86 +(% style="text-decoration: underline;" %)//Transaction Mapping//
107 107  
108 -\\
88 +* For Products: Product ID must be in Column A and Product name in Column B.
89 +* For Subscription Type: Sub Type ID/value is in Column A and subscription type name in Column B.
90 +* For Product Status: Status ID must be in Column A and Status name in Column B.
109 109  
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.
92 +=== Screenshot: Pre-Populated Demographic Questions/Data Fields - Uploaded Layout ===
111 111  
112 -//(Example: states may be abbreviated with 4 letters in a POS database [Conn., Mass.], while the ecommerce database has two letter abbreviations.)//
94 +[[image:attach:media_1467396172019.png||align="center"]]
113 113  
114 -\\
96 +=== Screenshot: Pre-populated Question Responses - Uploaded Layout ===
115 115  
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.
98 +[[image:attach:media_1467391080266.png||align="center"]]
117 117  
118 -1. (((
119 -Transactional Fields** - **Map external transaction data, e.g. product activity, status, and date formats.
120 -)))
100 +=== Screenshot: Pre-Populated Transaction Mapping - Uploaded Layout ===
121 121  
122 -* (((
123 -1. (((
124 -Define transactional fields by entering the field name from the import file, the field type and then match the value of the field to the value in ONEcount by clicking the [Map] button.
125 -)))
126 -1. (((
127 -i.e. if the source/import file has a product field called “PUB_TITLE” and the value for current subscribers is “YES” on the import file, but the ONEcount product is “Active Subscriber”, the Package Status Value from the import file should be matched with the Package Status in ONEcount.)
128 -)))
129 -1. (((
130 -Within the “Map Values” pop up window, click “Add” to define all possible transactional statuses.
131 -)))
102 +[[image:attach:media_1467391409099.png||align="center"]]
132 132  
133 -1.
104 +=== MAPPING AREA ===
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.
136 -)))
106 +[[image:attach:media_1467397686498.png||align="center"]]
137 137  
138 -* (((
139 -1. (((
140 -To map engagement values of fields, define the engagement field name (the column header from the import file) and match it to the engagement type in ONEcount.
141 -)))
142 -1. (((
143 -If the Engagement Field Value is a metric that is not a count, click the [] icon to map the metric field value to the ONEcount metric
108 +Prior to uploading a layout file, or if you opt to create the mapping on the fly (without uploading a layout file), the Mapping Area will be empty.
144 144  
145 -//(i.e. if the source/import file has an ‘Engagement Field Name’ that is “NEWSLETTER_ACTIVITY_TYPE” the ‘ONEcount Engagement’ would be “Metric >> Activity Metric Name” and then map the values of metric type [“OPEN”, “CLICK”] to the ONEcount metric [“Email opens”/”Email clicks”]). //
146 -)))
147 -)))
110 +The mapping area consists of three columns: **Third Party Questions, ONEcount Questions, and Validations.**
148 148  
149 -5.    Static Fields
112 +* **Third Party Questions** shows questions/data fields your, or a third party's, data file.
113 +* **ONEcount Questions** shows the corresponding ONEcount question to be mapped to the Third Party Question.
114 +* **Validations** allows you to select validations for the mapped question, i.e., Required, Email, Number and Text, Text Only.
150 150  
151 -1. (((
152 -*Optional Step: If a column and values needs to be added for identification, record keeping, sourcing, etc. purposes, DExTr can append data to each row.
153 -)))
154 -1. (((
155 -Define the “Static Field Name” which will be the column heading on the export file (i.e. “DATA_SYNC_NAME”), and then the value of the static field (i.e. “CRM_SYNC”).
156 -)))
157 -1. (((
158 -Click “Add” to create additional static field appends.
159 -)))
116 +=== Manually Add Third-Party Questions ===
160 160  
161 -6.    Re-order Fields
118 +[[image:attach:media_1467398286154.png||align="center"]]
162 162  
163 -1. (((
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 -)))
120 +When you click on the "Add Questions" button, you'll be presented with a pop-up to create a new question/data field to be mapped to an existing ONEcount question.
166 166  
167 -\\
122 +Be sure to select "Yes" if it is a question with selectable responses, i.e. radio button/select/checkbox-type. Click Save.
168 168  
169 -\\
124 +=== Map Questions and Responses ===
170 170  
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.
126 +[[image:attach:media_1467398257338.png||align="center"]]
172 172  
173 -There are four Mapping Areas for Transaction Mapping:
128 +If the question is a radio button/select/checkbox-type question, a button will be presented which will allow you to map responses and values. (See "Upgrade Checkbox" question above.)
129 + If it's a text-type response, you won't need to map responses and values.
174 174  
175 -* (((
176 -Product Mapping Area
177 -)))
178 -* (((
179 -Product Status Mapping Area (optional)
180 -)))
181 -* (((
182 -Subscription Mapping Area
183 -)))
184 -* (((
185 -Date Mapping Area
186 -)))
131 +**YOU MUST FIRST MAP THE QUESTION TO THE CORRESPONDING ONECOUNT QUESTION BY DRAGGING AND DROPPING THE CORRESPONDING ONECOUNT QUESTION FROM THE ONEcount Questions SECTION INTO THE ONEcount Questions Column BEFORE YOU CAN MAP RESPONSES. THIS APPLIES TO BOTH MANUALLY ADDED QUESTIONS AND QUESTIONS PRE-POPULATED BY UPLOAD OF AN IMPORT.**
187 187  
188 -**NOTE THAT MAPPING IS ID TO ID IN TRANSACTION MAPPING. THE ID IS FOUND IN PARENTHESIS AFTER THE TEXT IN THE "THIRDPARTY..." COLUMN OF MAPPING AREAS.**
133 +**ONEcount QUESTIONS AND RESPONSE VALUES MUST BE CREATED PRIOR TO PERFORMING MAPPING.**
189 189  
190 -**AS WITH DEMOGRPHIC MAPPING, ONECOUNT PRODUCTS, PRODUCT STATUSES, AND SUBSCRIPTION TYPES MUST BE CREATED PRIOR TO PERFORMING TRANSACTION MAPPING.**
135 +[[image:attach:media_1467398730892.png||align="center"]]
191 191  
192 -**THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).**
137 +Simply drag and drop ONEcount questions from the question pool into the appropriate cell in the mapping table.
193 193  
194 -*(% style="text-decoration: underline;" %)Product Mapping Area(%%) *
195 -**For automated data feed reports**, the Third Party Product column shows what the ONEcount product name will be displayed as on output.
139 +Note the Search function at the top of the list of ONEcount questions. Just begin typing in the question name, and the list will be filtered for you. (See screenshot below.)
196 196  
197 -* (((
198 -For example, a user is subscribed to/registered for ABCXY Pharma Aug. Webinar(207) in ONEcount. The third party requires that on the report output show a value of August Webinar rather than ABCXY Pharma Aug. Webinar. Mapping ONEcount's ABCXY Pharma Aug. Webinar(207) product to August Webinar(400) will display the Third Party Product value of August Webinar on the output.
141 +[[image:attach:media_1467398948360.png||align="center"]]
199 199  
200 -**Product Column Field:** This identifies what to output as the header for the product field. Enter the heading that's required for the report output.
201 -)))
143 +Once Questions are mapped, you can add validations and/or map responses for radio/select/checkbox-type questions.
202 202  
203 -**For imports,** the Third Party Product column identifies the names/values from the import file that will be mapped to the ONEcount product.
145 +To add validations, click in the empty "Validations" box for the corresponding question and select from the drop-down list the validation(s) you want to apply to the question, i.e. Required, Email, Number and Text, Text Only. (See screenshot below.
204 204  
205 -* (((
206 -For example, there's "product" column in the import file that identifies what product a particular record is subscribed to or registered for. In the import file, August Webinar in that colum indicates the record is subscribed to/registered for the August Webinar. In ONEcount, the product name is ABCXY Pharma Aug. Webinar. Any record in the import file that has August Webinar in the product column will be subscribed to the ABCYXY Pharma Aug. Webinar product in ONEcount.
147 +=== Screenshot – Mapped Questions with Validations ===
207 207  
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 -)))
149 +[[image:attach:media_1467399198566.png||align="center"]]
210 210  
211 -(% style="text-decoration: underline;" %)**Product Status Mapping Area (Optional)**(%%)
212 -**For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
151 +=== Map Question Responses ===
213 213  
214 -* (((
215 -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.
153 +[[image:attach:media_1467391237758.png||align="center"]]
216 216  
217 -**Product Status Column Field:** This identifies what to output as the header for the product status field. Enter the heading that's required for the report output.
218 -)))
155 +To map question responses, click on the "Response Map" button. Doing so will present a pop-up window where you can map third-party to ONEcount responses. Just drag and drop ONEcount responses from the list of ONEcount Responses into the appropriate cell.
219 219  
220 -**For Imports**, the Third Party Product Status column identifies what name/value from the import file will be mapped to the ONEcount product.
157 +When done mapping responses, click the "Save" button.
221 221  
222 -* (((
223 -For example, there's a "product status" column in the import file that identifies the product status a particular record has for a particular product. In the import file, "Inactive(203)"in that column indicates the record has a product status of inactive. In ONEcount, the product status is "Not Active(405)". Any record in the import file that has a product status of "Inactive" in the product status column will have the product status of "Not Active" applied to the record in ONEcount.
159 +You'll be returned to Information and Demo Mapping where you can then continue mapping remaining questions or click "Next" to continue.
224 224  
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 -)))
161 +Depending on the mapping selections you made under "Information", clicking "Next" will direct you either to save the Demographic Mapping or to the Transaction Mapping and/or Activity Mapping sections.
227 227  
228 -(% style="text-decoration: underline;" %)**Subscription Mapping Area**(%%)
229 -**For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
163 +=== 2 – TRANSACTION MAPPING ===
230 230  
231 -* (((
232 -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.
165 +[[image:attach:media_1467651841763.png||align="center"]]
233 233  
234 -**Subscription Column Field:** This identifies what to output as the header for the subscription type field. Enter the heading that's required for the report output.
235 -)))
167 +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.
236 236  
237 -**For Imports**, the Third Party Subscription column identifies what name/value from the import file will be mapped to the ONEcount product.
169 +There are four Mapping Areas for Transaction Mapping:
238 238  
239 -* (((
240 -For example, there's a "Subcription Type" column in the import file that identifies the subscription type a particular record has for a particular product. In the import file, "New" in that column indicates the record has a subscription type of new. In ONEcount, the subscription type is "n". Any record in the import file that has a product status of "New" in the subscription type column will have the product status of "n" applied to the record in ONEcount.
171 +* Product Mapping Area
172 +* Product Status Mapping Area (optional)
173 +* Subscription Mapping Area
174 +* Date Mapping Area
241 241  
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 -)))
176 +**NOTE THAT MAPPING IS ID TO ID IN TRANSACTION MAPPING. THE ID IS FOUND IN PARENTHESIS AFTER THE TEXT IN THE "THIRDPARTY..." COLUMN OF MAPPING AREAS.**
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/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
178 +**AS WITH DEMOGRPHIC MAPPING, ONECOUNT PRODUCTS, PRODUCT STATUSES, AND SUBSCRIPTION TYPES MUST BE CREATED PRIOR TO PERFORMING TRANSACTION MAPPING.**
247 247  
248 -(% style="color: rgb(51,51,51);" %)MM : months, dd: days, yyyy: years, hh: hours (12 hour format), HH: hours (24 hour format), mm: minutes, ss: seconds, a:AM/PM(%%)\\
180 +**THIRD-PARTY TRANSACTION VALUES CAN BE PRE-POPULATED BY UPLOADING A LAYOUT FILE OR MANUALLY ENTERED (AS DESCRIBED IN "INFORMATION" SECTION ABOVE).**
249 249  
250 -**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.
182 +*(% style="text-decoration: underline;" %)Product Mapping Area(%%) *
183 + **For automated data feed reports**, the Third Party Product column shows what the ONEcount product name will be displayed as on output.
251 251  
252 -**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
185 +* For example, a user is subscribed to/registered for ABCXY Pharma Aug. Webinar(207) in ONEcount. The third party requires that on the report output show a value of August Webinar rather than ABCXY Pharma Aug. Webinar. Mapping ONEcount's ABCXY Pharma Aug. Webinar(207) product to August Webinar(400) will display the Third Party Product value of August Webinar on the output.
186 + **Product Column Field:** This identifies what to output as the header for the product field. Enter the heading that's required for the report output.
253 253  
254 -(% style="color: rgb(51,51,51);" %)MM : months, dd: days, yyyy: years, hh: hours (12 hour format), HH: hours (24 hour format), mm: minutes, ss: seconds, a:AM/PM
188 +**For imports,** the Third Party Product column identifies the names/values from the import file that will be mapped to the ONEcount product.
255 255  
256 -**Date Column Field:** This identifies the column header for the date column in the import file.
190 +* For example, there's "product" column in the import file that identifies what product a particular record is subscribed to or registered for. In the import file, August Webinar in that colum indicates the record is subscribed to/registered for the August Webinar. In ONEcount, the product name is ABCXY Pharma Aug. Webinar. Any record in the import file that has August Webinar in the product column will be subscribed to the ABCYXY Pharma Aug. Webinar product in ONEcount.
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".
257 257  
258 -When done with mapping, click "Next".
259 -You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.**SAVE MAPPING**
193 +(% style="text-decoration: underline;" %)**Product Status Mapping Area (Optional)**(%%)
194 + **For automated data feed reports,** the Third Party Product Status column shows what the ONEcount product status will be displayed as on output.
260 260  
261 -When done with mapping(s), click "Next".
196 +* 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.
197 + **Product Status Column Field:** This identifies what to output as the header for the product status field. Enter the heading that's required for the report output.
262 262  
263 -You then have the option to save the mapping (Save) or return to mapping (Previous).
199 +**For Imports**, the Third Party Product Status column identifies what name/value from the import file will be mapped to the ONEcount product.
264 264  
265 -Once mapping is saved, you can find it on the Manage Mapping listing page.
201 +* For example, there's a "product status" column in the import file that identifies the product status a particular record has for a particular product. In the import file, "Inactive(203)"in that column indicates the record has a product status of inactive. In ONEcount, the product status is "Not Active(405)". Any record in the import file that has a product status of "Inactive" in the product status column will have the product status of "Not Active" applied to the record in ONEcount.
202 + **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".
266 266  
267 -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.
204 +(% style="text-decoration: underline;" %)**Subscription Mapping Area**(%%)
205 + **For automated data feed reports,** the Third Party Subscription column shows what the ONEcount subscription type will be displayed as on output.
268 268  
207 +* 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.
208 + **Subscription Column Field:** This identifies what to output as the header for the subscription type field. Enter the heading that's required for the report output.
269 269  
210 +**For Imports**, the Third Party Subscription column identifies what name/value from the import file will be mapped to the ONEcount product.
270 270  
271 -{{id name="End ScreenSteps Content"/}}
212 +* For example, there's a "Subcription Type" column in the import file that identifies the subscription type a particular record has for a particular product. In the import file, "New" in that column indicates the record has a subscription type of new. In ONEcount, the subscription type is "n". Any record in the import file that has a product status of "New" in the subscription type column will have the product status of "n" applied to the record in ONEcount.
213 + **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".
272 272  
273 -=== MAPPING ENGAGEMENT DATA ===
215 +(% style="text-decoration: underline;" %)**Date Mapping Area**(%%)
216 + **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.
217 + **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.
274 274  
275 -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.
219 +**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.
220 + **Date Column Field:** This identifies the column header for the date column in the import file.
276 276  
277 -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.
222 +When done with mapping, click "Next".
223 +You will then be brought either to Activity Mapping or Save, depending on selection made in 1 – Information.
278 278  
279 -Generic Engagement Fields
225 +=== 3 – ACTIVITY MAPPING ===
280 280  
281 -* Activity Date: Date of the Activity
282 -* Activity Time: Time of the Activity, Mandatory for Import.
283 -* Channel Codes: Codes for Email, Banner and Web page views, CMI needed it in export.
284 -* End Date: End date of export, mainly used in aggregate export.
285 -* Unique External ID: Unique ID for each transaction.
286 -* Month: Month of the Activity.
287 -* OCID:
288 -* OCID Hash: Unique hash of the user. This is the cookie set on user’s browser.
289 -* Platform Viewed: Platform of the user in which Impression or Page view happened.
290 -* 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.
291 -* Start Date: Start date of export, mainly used in aggregate export.
227 +[[image:attach:media_1468256607407.png||align="center"]]
292 292  
293 -Metric Engagement Fields
229 +Activity Maping is done the same way as Demographic and Transaction Mapping by using the drag and drop functionality to match Third Party Activity Header with ONEcount Activity Header. The Third Party Activity Headers will display as column headings for Web, Ad, and Newlsetter data in the export file.
294 294  
295 -* 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.
296 -* 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.
297 -* Activity Metric count: Mainly used for export. It has counts for each activity.
298 -* 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.
299 -* 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.
300 -* Aggregate Metric count: Mainly used for export. It has counts for each activity.
231 +**Third-party activity headers currently can't be mapped via an uploaded layout file. They must be mapped manually in the Activity Mapping Area by clicking on the "Add Activity Header" button.**
232 + When you click on the "Add Activity Header" button, you'll be presented with a pop-up where you can add the Activity Header Name.
301 301  
302 -Banner Engagement
234 +The ONEcount Activity Header section is divided into the following categories: Web, Ad, Newsletter, Generic (includes general headers, such as ONEcount unique identifier, Channel Code, etc.) Note the scroll bar to move through the categories.
303 303  
304 -* Ad Server Name: Name of the Ad Server, i.e., DFP
305 -* Advertiser ID: ID of the Advertiser
306 -* Advertiser Name: Name of the Advertiser
307 -* Banner ID: ID of the Banner
308 -* Banner Name: Name of the Banner
309 -* Campaign ID: ID of the Campaign
310 -* Campaign Name: Name of the Campaign
311 -* Viewable Impression: If Impression is viewed or not, Boolean (0, 1 accepted)
236 +When finished mapping, click the "Next" button.
312 312  
313 -Newsletter Engagement Fields
238 +=== Save Mapping ===
314 314  
315 -* Click URL: URL of the Clicked link. Mandatory for Importing Email clicks.
316 -* List ID: ID of the newsletter List of Group
317 -* List Name: Name of the newsletter list or group
318 -* Message ID: Campaign ID of the newsletter
319 -* Message Name: Campaign name of the newsletter
320 -* Recipient ID: Unique User Id in the Email service provider
321 -* Message Subject: Subject of the Campaign
240 +When done with mapping(s), click "Next".
322 322  
323 -Web Engagement Fields
242 +You then have the option to save the mapping (Save) or return to mapping (Previous).
324 324  
325 -* Referrer: Referrer for the page view
326 -* Site name: Website URL
327 -* Page URL: URL of the Page.
244 +Once mapping is saved, you can find it on the Manage Mapping listing page.
328 328  
329 -=== **HOW DExTr MAPS DATA** ===
246 +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.
330 330  
331 -The following information is being provided to help you understand how DExTr will map/transform your data on import.
332 332  
333 -(% class="diff-block-target" %)
334 -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.//
335 -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
336 -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.
337 -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.
338 -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.
339 -1. For Package transactions: Term ID, Package status, source code and transaction type are mandatory.
340 -11. If Term ID is not mapped, then the transaction won’t be imported.
341 -11. IF Package status is not mapped then default Package status from term will be added.
342 -11. If source code is not mapped. Then default source code from import job will be selected.
343 -11. If transaction type is not added, then default type from Import job will be selected.
344 -1. For Product transaction: Product ID, source code and transaction type are mandatory.
345 -11. If Product ID is not mapped, then the transaction won’t be imported.
346 -11. If source code is not mapped. Then default source code from import job will be selected.
347 -11. If transaction type is not added, then default type from Import job will be selected.
348 -1. If Transaction Date is not mapped or not formatted correctly, then current date will be used as request date.
349 -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.
350 -1. For Engagement imports, Activity type is mandatory.
351 -1. If Engagement date is not formatted, then current date will be used as activity date.
352 -1. If Data and campaign ID, name, List ID and name then they will be imported as well.
353 -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.
354 354  
355 -\\
356 -{{/layout-cell}}
357 -
358 -{{layout-cell}}
359 -{{panel borderStyle="solid" title="Search all Documentation:"}}
360 -
361 -
362 -{{livesearch/}}
363 -{{/panel}}
364 -
365 -{{panel borderStyle="solid" title="Search System UTILITIES:"}}
366 -
367 -
368 -{{pagetreesearch rootPage="System Utilities"/}}
369 -{{/panel}}
370 -
371 -{{panel title="More System UTILITIES"}}
372 -{{expand title="Expand"}}
373 -
374 -
375 -(% style="margin-left: 30.0px;" %)
376 -[[Job List>>doc:Utilities - Job List]]
377 -
378 -(% style="margin-left: 30.0px;" %)
379 -[[Backend User Permissions>>doc:Utilities - Backend Users and Permissions]]
380 -
381 -(% style="margin-left: 30.0px;" %)
382 -[[Email Engine Sender Score>>doc:ONEmail and Sender Score]]
383 -
384 -(% style="margin-left: 30.0px;" %)
385 -[[doc:ONEmail]]
386 -
387 -(% style="margin-left: 30.0px;" %)
388 -Action Manager
389 -
390 -(% style="margin-left: 30.0px;" %)
391 -[[Configuration Manager>>doc:Utilities - Configuration Manager]]
392 -
393 -(% style="margin-left: 30.0px;" %)
394 -Backend Activity Log
395 -
396 -(% style="margin-left: 30.0px;" %)
397 -IVT Mitigator
398 -
399 -(% style="margin-left: 30.0px;" %)
400 -[[Widget Builder>>doc:Utilities - Widget Builder]]
401 -
402 -(% style="margin-left: 30.0px;" %)
403 -
404 -
405 -(% style="margin-left: 30.0px;" %)
406 -Import/Export Tool
407 -{{/expand}}
408 -{{/panel}}
409 -
410 -\\
411 -
412 -\\
413 -{{/layout-cell}}
414 -{{/layout-section}}
415 -{{/layout}}
250 +{{id name="End ScreenSteps Content"/}}
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 +67341
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/67341/Utilities - Mapper (v12.x)