View transcript
Hi, guys. In this Marketo Tip we will talk about field creation in Marketo and how to keep your Marketo clean while creating those fields, whether in Marketo or in your CRM. This can be tricky and generate duplicates. I'm Sylvain Davril, founder of Merlin/Leonard and certainly the Leonard's team, and this is a new Marketo. So when creating fields in Marketo or in your CRM, that can end up with a lot of duplicate fields in Marketo. So let's see how you can create that without any duplicates in various cases. First case you want to create a field in only Marketo, that's the easiest way. So here basically you will create the field in Marketo, I mean my Marketo, I mean in field management, here, new custom field, create your field on the right object, type name and IP name and you're done. And this field will exist only in Marketo, not in the CRM, that's OK. Now if you want to create a field only in your CRM — and here I will take my Salesforce as an example. I want this field only in Salesforce and I don't want this field in Marketo. I will create the field in my Salesforce and make sure that this field is not visible by the Marketo user. How do I do that? I go to my Salesforce here in the setup, I'm on the lead object, just an example, I will create a new field, let's imagine it's a text field, that I will name test, length 255, so I don't have to enter all that, just for the test I will not go through because I don't want to create a fake field in my Salesforce. And here on the field level security screen, I will uncheck the Marketo Sync profile because that's the dedicated profile I created for my Marketo user in my Salesforce. So if this profile has not the visibility on this field, it will not create automatically this field in my Marketo, that's what I want. So if you want the field only in Salesforce, create this field in Salesforce and uncheck the Marketo profile. Then the most common case, I want to create a field in Marketo and Salesforce or Dynamics and I want those fields to map automatically. So that's exactly what we've done just before, you create your field in the CRM and you make it visible by the Marketo user, so you let the checkbox ticked, just like I did before. In Salesforce — with Salesforce, sorry — it will create automatically five minutes later in Marketo the field and the field will be visible and usable in Marketo. For Dynamics you will have to create a field in Marketo first and map it with the field coming from Dynamics. You have this mapping tool available in Marketo whereas it's more automatic with Salesforce. Please note that if the field, the technical name of the field that arrives in Marketo matches with another technical name of a field already in Marketo, Marketo will try to merge or associate those fields together. So that's the simple part, what if you've created a lot of duplicates already in your Marketo and want to purge to clean all that. So there are two ways to do that, you can either merge the fields under certain conditions or remap and hide the fields. You can merge custom fields together, so if no standard field is involved you can ask the Marketo support to merge custom fields if they are of the same type. So let's take an example, here I've got some field for the boat, yeah let's imagine those two fields have been created in error and they contain exactly the same business value, here it's the name of the boat. Let's imagine I want to merge those two fields, so here it's easy because they are not linked with the CRM, but so here I can ask my Marketo support to merge those two fields by saying that this, for instance, this field will be the master, this field will be the slave. There's an uncertainty here because I think that the master must not be associated with any segmentation, smart campaign, forms or whatever, so I may have to purge all those assets and campaigns from the field first for the support to merge. It's been a long time I've not done this with the support so there's a bit uncertainty here but the support will tell you. On the contrary, if one of those fields is a standard field — so let's imagine salutation and the business case here would be in our CRM — we don't want to use the standard field the standard Salesforce field for salutation we have created a salutation2 field and we want this salutation2 field or the unsubscribe field that's very often with the unsubscribe field. We don't want to use the email opt-out field in Salesforce — we have created dedicated field in Salesforce, but we want to map with the unsubscribe standard field. Let's take and subscribe. We want to map with the standard unsubscribe field in Salesforce — in a Marketo, sorry. So here it's used a lot in a lot of campaigns so it takes some time. So here's the technical name of the email opt-out field in Salesforce but let's imagine we have created an unsubscribe Salesforce field it would it would appear here with his own mapping. So what I could ask to the support is to remap the mapping for the standard field and subscribe in Marketo so that it maps not on the standard field in Salesforce but on the custom field I've just created in Salesforce. In this case I would be able to hide this unsubscribed standard field coming from Salesforce because I don't want to confuse my marketing team and I don't want errors to be made when the fields are used. So I could hide this field if it's not used in any campaigns forms or smart list or whatever, meaning it's here, it will be empty. I could hide this field and I would have only my custom unsubscribe2 field available. That's something we do usually, so don't hesitate to ask for help; that's something we do a lot especially with Marketo, that have lived for time, we usually find a lot of duplicate fields and sometimes it's very confusing for the marketing teams to use the right fields. So what we do is we audit all that, we select all the masters and we work with the teams and the Marketo support to make sure we have only one field in the end correctly mapped with the CRM. Talk to you soon. Bye, guys.
