I look at both contact history. This contact is one of our staff member. He receives a newsletter that we sent out weekly so when we switched from Sendy (former mailer) to Mautic, we imported all contact over to Mautic via CVS file.
I can see both contact have same history and both was created same day 2 month ago until recently I imported a new CVS for a “Staff only” segment and that when it seem to duplicate the contact into two contact but still same name and email address.
Funny thing is history show “Contact updated” instead it duplicate the two. The only difference between two contact is one have a “staff” tag on it.
I did some testing beforehand to make sure that importing would merge the contact instead of creating a new secondary same contact and it did pass the test that it merged which I wanted in the first place.
Here a screenshot of both contact history … in history comm.cvs is the list I imported to add those who are communication staff
There are only 12 staff on communication team and I checked all contacts history. There was only one that was duplicated. The rest of the contacts in staff CVS was merged successfully.
Hi, sorry I need to catch up with things, don’t have time now, but let’s see if someone has a tip.
If it won’t get solved by the end of the week, I’ll look into it on friday.
For this user I am seeing a full history of all pages being tracked as well as emails being send.
The emails being sent are from within a campaign and they are market type “marketing”.
The field for email is publicly updatable and is also a unique identifier.
The user is being created via the Mautic tracking script and/or via forms in both cases.
@joeyk or anyone else looking for some interesting insights here.
My initial hunch was that a field was being overwritten on a specific user, but I would expect to see the values of email change in the audit log if this was the case, and then the fact that the lead_ids are consecutive also raises a small alarm.
You can of course create duplicate emails via API without problems.
When you EDIT the contact, then the API won’t check if the email already exists, since the ID will be used as UNIQUE FIELD.
You should CREATE the contact every time you want to make change using email as a key.
Thanks Joey. No it is not being done via API, a contact is created via a form submission in one scenario, at the same time the tracking script will pass through the email as well.
The other scenario is that a user registers has registered through the site mechanism (in this case Auth0) and then the tracking script passes through user details.
Ok.
Is the form a standard mautic embed? Or a post action from a wp plugin?
Also:
Do you have a synch with a crm or other system?
One more:
Do you have multiple keys besides email?
Standard Mautic form.
No other synch with any CRM
No other unique keys
I did see that they could have implemented the tracking script incorrectly as I am seeing 4 hits per anonymous user, also the dup records are created within seconds of each other
Yeah there must be a tracking issue. Can you plz check if there are ja errors while tracking? Does the page have proper access to Mautic cookie? Maybe cors error?