Mautic = suitecrm - lead vs contacts?

đź’¬ General Discussion
1

I am trying to work out with mautic and suitecrm how to deal with the fact that suitecrm has leads, and mautic does not.

I’ve been using suite crm as a way to keep track of all my leads/ contact and accounts.

But when trying to use the built in integration, leads are not an option to have sync’d.

Can I have feed back on how to handle the missing leads in mautic? How dto adapt to this?>

Thanks

Joseph

2

You can check out this video:

3

There is no such concept in Mautic as Leads vs. Contacts. All are “contacts”.

Don’t worry it’s all handled pretty well.

Leads in SuiteCRM - > Contact in Mautic
Contacts in SuiteCRM → Contact in Mautic
Contact in Mautic → Lead in SuiteCRM.

It matches on email address as a unique identifier so there are not duplicates.

If you convert a lead to a contact in SuiteCRM Mautic handles that by overriding the lead with the contact.

It all works very smoothly. The only issue you run into is if you have leads or contacts with a blank email. Then you have problems because there is no unique identifier. This will create many duplicate contacts in Mautic as it treats each as unique on every sync.

What I do in order to keep it straight, because sometimes you want campaigns going to just leads or just contacts, is I sync the lead status (I also ensure all contacts have a lead status of converted). Then if I need to segregate leads vs contacts in Mautic I just filter on converted vs. not converted.

4

Thanks for these ideas. Clarifies things a lot.
One thing that I still need to clear up. I need to segment the contacts/leads into 3 categories.

The lead/contact is in either a or b or c.

But, c can also be some ties a or b.

Ia there a way to:
1 - set up the three segments in the contact or lead?
2 - have a 2nd category for a lead/contact(in suite crm, and mautic)?

Thanks

Joseph

5

Yes just set up your segments like this:

Assuming you have a field like “type” = a , b , c in SuiteCRM

In mautic:

Segment A = type =a
Segment B = type =b
Segment C= type c

Segment ABC = type=a or type=b or type=c

6

Thank you very much for your assistance.

A situation came up:

I have a lead that was converted to a contact. Now, there is a lead and a contact with the same name and email.

In a previous message, Paul stated that a contact overrides a lead.

“If you convert a lead to a contact in SuiteCRM Mautic handles that by overriding the lead with the contact.”

Does this mean that both lead and contact exist, but since the lead is marked as converted, only the contact is used?

Thanks

Joseph

7

Both the lead and contact will exist in SuiteCRM but only one contact record linked to both will exist in Mautic

8

That makes sense. But, I just want to be sure of the logic that is behind which is used in Mautic.

In your previous message, you said that s long as the lead is set to “converted”, than the contact will be the one that is used with in Mautic, right?

Thanks

Joseph

9

It doesn’t matter the email address is the key on which it matches records.

10

I understand that the email address is the key.

But, when using mautic to send things to potential clients and clients, the result that we are trying to achieve is to differentiate between lead and client.

In this case, I would think that it would matter if there is a lead and a contact with the same email. I need that lead to say converted, I would think, so that mautic would then not not to use the lead. Otherwise, mautic will send messages to leads that are destined for contacts, and vice versa.

How do we differentiate the two, if the question? You proposed making sure that the lead status is converted. Which makes sense.

Does that hold true? Will mautic ignore a lead that is converted and use the contact with the same email?

11

Mautic does not have any lead/contact logic. All your logic needs to be in SutieCRM. As mentioned above Mautic only cares about the email address as a unique ID. It does not differentiate between leads and contacts. If you want to set up a campaign specific to either, you need a key field on which to differentiate your segments. I suggested “status” = converted vs. not converted, but you may devise any mechanism you like as long as their is a field that sync’s to Mautic you can calculate your segment membership based on.