Wiki source code of Bulk Operation - How to Perform a Bulk Merge of Duplicate Users

Version 11.11 by Admin User on 2026/05/23 16:59

version	line-number	content
4.1	1	{{layout}}
	2	{{layout-section ac:type="two_right_sidebar"}}
	3	{{layout-cell}}
3.1	4
	5
	6	{{id name="Start ScreenSteps Content"/}}
10.1	7	This lesson describes how to use the Bulk Operation tool in the USER OPERATIONS module to merge duplicate user records. Performing a batch merge will merge duplicate records into one selected record.
3.1	8
	9	Please refer to the Quick Start Guide - User Operations for important information about basic concepts and rules relating to imports and bulk operations.
	10
	11	=== IMPORTANT NOTE – FIRST GENERATE A FILE OF DUPLICATES TO BE MERGED ===
	12
	13	(% style="color: rgb(164,10,10);" %)*Note that prior to performing a merge, you must generate a csv file of duplicate ocids. ~~***(%%)
10.1	14	(% style="color: rgb(164,10,10);" %)The first column of the file should have the ocid of the user you wish to keep (i.e. the ocid of the user you wish to merge duplicate users into). (%%)
3.1	15	(% style="color: rgb(164,10,10);" %)The second column should have a list of duplicate ocids (i.e. ocids of duplicate users that you wish to merge into the one user in the first column). (%%)
	16	(% style="color: rgb(164,10,10);" %)Be sure that the file doesn't have any duplicates within itself.
	17
	18	[[image:attach:media_1438020148654.png\|\|align="center"]]
	19
	20	In the screenshot above, ocids in Column B (and all transaction activity) will be merged into the ocid in Column A, e.g. ocids 40754 and 45770 will be merged into ocid 30290, ocids 39314 and 46162 will be merged into ocid 20834, ocid 38146 will be merged into ocid 38138, etc.
	21
	22	Alternatively, you can separate duplicate ocids to merge with a comma as delimiter. (See Screenshot below)
	23
	24	(% style="color: rgb(164,10,10);" %)*~~***(%%) Use the List Wizard to generate a list of users. Once the list is generated, you can open the file and modify to fit the criteria described above. Or, if you know the ocids of duplicate users, simply enter them into a spreadsheet as shown above. BE SURE TO SAVE THE FILE AS A CSV FILE – fields separated by a comma ( , ) and enclosed by quotes ( " ).
	25
	26	[[image:attach:media_1438020317487.png\|\|align="center"]]
	27
	28	ocids 40754 and 45770 will be merged into ocid 30290, ocids 39314 and 46162 will be merged into ocid 20834, ocid 38146 will be merged into ocid 28138, ocid 41994 will be merged into ocid 19385.
	29
7.1	30	=== IMPORTANT NOTES – STATISTICS, NEWSLETTER LISTS, AND MERGED RECORDS ===
3.1	31
7.1	32	1. All transaction data and product subscriptions from a removed/merged user will be moved to the kept user's record.
	33	1. Each piece of demographic data has a timestamp attached to it. When users are merged, whichever has the latest timestamp on a per question basis becomes the latest info for that user. Each demographic field with the latest timestamp will be included in the "kept" users record. NOTE: Usernames and passwords qualify as demographic information that will be updated to the latest timestamp as well.
3.1	34
	35	When merging records/users, email stats stay the same. For example,
	36
	37	* four records are merged into one, and
	38	* all are subscribed to the same newsletter, and
	39	* there are four unique opens for those users (one unique open per user) for that newsletter, and
	40	* the unique opens count will stay at four.
10.1	41	If you drill into the List Wizard to generate a list of the users, only the record that was kept (the ones other ocids were merged into) will be included on the list.
3.1	42
	43	Users will be processed differently depending on the email engine.
5.1	44	\\If using the ONEcount email engine, those users who have been removed (merged into another ocid) and who were subscribed to the same newsletter list(s) as the kept user will be deleted in the ONEcount email engine. If a removed user is subscribed to an email list that the kept user is not subscribed to, the kept user will be added to the newsletter list.
3.1	45
	46	MagnetMail doesn't allow for deleting/ merging users, so all users that were merged into another ocid will remain in MagnetMail but will be unsubscribed from respective email list(s) in MagnetMail. If a removed user is subscribed to an email list that the kept user is not subscribed to, the kept user will be added to the newsletter list.
	47
	48	=== OPEN THE BULK OPERATION WINDOW ===
	49
10.1	50	=== Select DATA MANAGEMENT from the Main Menu. ===
3.1	51
10.1	52	\\
3.1	53
10.1	54	[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 3.png\|\|thumbnail="true" height="250"]]
3.1	55
10.1	56	=== Select "BULK OPERATIONS" from the DATA MANAGEMENT sub-menu. ===
3.1	57
10.1	58	[[image:attach:Screen Shot 2021-10-09 at 4.33.36 PM (2) copy 7.png\|\|thumbnail="true" height="250"]]
	59
	60	\\
	61
3.1	62	This will open the Bulk Operation main window, as shown below.
	63
	64	=== BULK OPERATION Main Window ===
	65
	66	[[image:attach:media_1430151456843.png\|\|align="center"]]
	67
	68	(% style="color: rgb(0,0,0);" %)1 - (%%)Copy and paste a delimiter separated list of ONEcount IDs.
	69
	70	(% style="color: rgb(0,0,0);" %)2 -(%%) Select the bulk operation: Status Change will change the status of ocids entered in Box 1, Product Change will change the product all ocids entered in Box 1 are assigned to, Unsubscribe/Kills will unsubscribe all ocids entered in Box 1 from a designated product, Subscribe will subscribe all ocids entered in Box 1 to a designated product, Delete will delete all ocids entered in Box 1, and Merge will merge ocids enterd in Box 1.
	71
	72	(% style="color: rgb(0,0,0);" %)3 - (%%)Select the delimiter used in the list of ONEcount IDs (Box 1).
	73
	74	(% style="color: rgb(0,0,0);" %)4 - (%%)Select the status to apply to the Status Change, Product Change, Unsubscribe/Kill, or Subscribe.
	75
4.1	76	(% style="color: rgb(0,0,0);" %)5 -(%%) Select the Product(Term) that the Status Change, Product Change, Unsubscribe/kill, or Subscribe applies to. If Product Change is selected, "Select the product(Term)" will change to "Select the Product(Term)[FROM} and another box "Select the Product (Term)[[TO>>doc:TO]] will be added. See details on Product Change below.
3.1	77
	78	=== MERGE RECORDS ===
	79
	80	(% style="color: rgb(255,0,0);" %)*Note that prior to performing a merge, you must generate a csv file of duplicate ocids. ~~* (See above.)**
	81
	82	* (% style="color: rgb(255,0,0);" %)The first column of the file should have the ocid of the user you wish to keep (i.e. the ocid of the user you wish to merge duplicate users into).
	83	* (% style="color: rgb(255,0,0);" %)The second column should have a list of duplicate ocids (i.e. ocids of duplicate users that you wish to merge into the one user in the first column).
	84	* (% style="color: rgb(255,0,0);" %)Be sure that the file doesn't have any duplicates within itself.
	85
	86	=== Select "Merge" under "Please select the Bulk Operation" ===
	87
	88	[[image:attach:media_1430151885313.png\|\|align="center"]]
	89
	90	Notice how selecting "Merge" changes the content of Box 1 to a request to upload a selected list of duplicates.
	91
	92	Rather than pasting/entering ocids, you MUST select a list of duplicates to upload.
	93
	94	=== Click on the "Browse" button to locate the CSV file of duplicates to merge. ===
	95
	96	[[image:attach:media_1430163531217.png\|\|align="center"]]
	97
	98	When you click on "Browse" and locate and select your csv file of duplicates, the name of the file will appear beside the "Browse" button. (See above.)
	99
	100	=== Enter email for confirmation of process completion, batch job name, and batch description. ===
	101
	102	[[image:attach:media_1430163612501.png\|\|align="center"]]
	103
	104	"Batch job name" and "Batch description" are used to identify the Job Status in the Job List (in Utilities module).
	105
	106	=== Select "Merge Confirm" to begin the merge process or "Cancel" if you wish to cancel. ===
	107
	108	[[image:attach:media_1430163644824.png\|\|align="center"]]
	109
	110	=== To check the status of the job, go to UTILITIES > JOB LIST. ===
	111
	112	[[image:attach:media_1430163695483.png\|\|align="center"]]
	113
	114	You will receive email notification at the email address you provided when the merge is completed.
	115
10.1	116	\\
3.1	117
8.1	118	IMPORTANT NOTE:
3.1	119
8.1	120	Performing merge operations on user accounts will not be reflected in the clients external ESP analytics, however those merged accounts will be reflected in ONEcount's analytics. This may lead to a small difference in metrics between each database, however the results in ONEcount would be reflective of the more accurate real-time information.
	121
10.1	122	\\
8.1	123
	124
	125
3.1	126	{{id name="End ScreenSteps Content"/}}
4.1	127	{{/layout-cell}}
	128
	129	{{layout-cell}}
5.1	130	{{panel title="Search All Documentation:"}}
4.1	131
	132
	133	{{livesearch/}}
5.1	134	{{/panel}}
4.1	135
5.1	136	{{panel title="Search USER OPERATIONS Documentation:"}}
4.1	137
	138
	139	{{pagetreesearch rootPage="User Operations - Managing Your Data"/}}
5.1	140	{{/panel}}
4.1	141
5.1	142	{{panel title="More USER OPERATIONS Documentation"}}
	143	{{expand}}
	144	**Add Users
4.1	145	**
	146
	147	(% style="margin-left: 60.0px;" %)
	148
	149
11.2	150
11.3	151
11.4	152
11.5	153
11.6	154
11.7	155
11.8	156
11.10	157
11.11	158
4.1	159	(% style="margin-left: 60.0px;" %)
11.11	160	[[Preparing for Data Import>>doc:OD.How-To and Cookbooks.Getting Started - Preparing for Data Import]]
4.1	161
	162	(% style="margin-left: 60.0px;" %)
11.8	163	[[doc:OD.Pre-Import Checklist]]
4.1	164
	165	(% style="margin-left: 60.0px;" %)
	166
5.1	167
11.2	168
11.3	169
11.4	170
11.5	171
11.6	172
11.7	173
11.8	174
11.10	175
11.11	176
4.1	177	(% style="margin-left: 60.0px;" %)
11.10	178	[[How to Create an Import Mapping Template>>doc:_Archive.Import - How to Create an Import Mapping Template]]
4.1	179
	180	(% style="margin-left: 60.0px;" %)
11.2	181	[[How to Use an Import Mapping Template>>doc:_Archive.Import - How to Use an Import Mapping Template]]
4.1	182
	183	(% style="margin-left: 60.0px;" %)
11.8	184	[[doc:OD.Add Audience]]
4.1	185
	186	(% style="margin-left: 30.0px;" %)
	187	Batch Operations
	188
	189	(% style="margin-left: 60.0px;" %)
11.4	190	[[doc:OD.Bulk Operations.Bulk Operation - How to Perform a Batch Delete]]
4.1	191
	192	(% style="margin-left: 60.0px;" %)
11.5	193	[[doc:OD.Bulk Operations.Bulk Operation - How to Perform a Batch Product Change]]
4.1	194
	195	(% style="margin-left: 60.0px;" %)
11.6	196	[[doc:OD.Bulk Operations.Bulk Operation - How to Perform a Batch Status Change]]
4.1	197
	198	(% style="margin-left: 60.0px;" %)
11.7	199	[[Bulk Operation - How to Perform a Batch Suscribe>>doc:OD.Bulk Operations.Bulk Operation - How to Perform a Batch Subscribe]]
4.1	200
	201	(% style="margin-left: 60.0px;" %)
11.3	202	[[Bulk Operation - How to Perform a Batch Unsubscribe>>doc:OD.Bulk Operations.Bulk Operation - How to Perform a Batch UnsubscribeKill]]
4.1	203
	204	(% style="margin-left: 60.0px;" %)
	205
	206
11.2	207
11.3	208
11.4	209
11.5	210
11.6	211
11.7	212
11.8	213
11.10	214
11.11	215
4.1	216	(% style="margin-left: 30.0px;" %)
	217	Target Audience Segments
	218
	219	(% style="margin-left: 60.0px;" %)
11.8	220	(% style="color: rgb(0,51,102);" %) [[ Target Engine >>doc:OD.Segment Manager]]__
4.1	221	__
	222
10.1	223	\\
4.1	224
10.1	225	\\
4.1	226	{{/expand}}
5.1	227	{{/panel}}
	228
10.1	229	\\
5.1	230
10.1	231	\\
5.1	232
10.1	233	\\
5.1	234
10.1	235	\\
5.1	236
10.1	237	\\
5.1	238
10.1	239	\\
4.1	240	{{/layout-cell}}
	241	{{/layout-section}}
	242	{{/layout}}