Add Facebook Leads With Consent To Customer Insights Journeys

While scrolling through Instagram recently, I saw an ad for a newsletter for cat knowledge and tips. As the owner of two kittens, I thought why not! It was good ad placement and I also wanted to see how their ‘subscribe’ option worked. I clicked the button and it pulled in my name and email from my Instagram account and said I was subscribed. I didn’t get any kind of confirmation email, and it was well over a week before I got anything from them. So I wondered how that process could be improved and how it all might work in conjunction with Customer Insights – Journeys. This post comes from my own curiosity, so much that I even set up a new Facebook Page and Instagram account just for the D365 Marketing Weekly newsletter (with 1 subscriber each ). Read on to find out how you can get your meta (FB and IG) leads in to Dynamics 365 along with a Contact Point Consent record for each one.

First things first, this is not a post on how to set up Meta Business Suite. That was a PROCESS and their documentation is a bit sparse and at times inaccurate. Hopefully if you’ve come to this post it’s because you’ve got all of that already set up and already doing ads. I felt like I was going back and forth clicking between different screens trying to figure it all out. In the end I was able to create an account that is linked to a Facebook page and Instagram business profile.

Then I created a new campaign with the objective of gathering leads.

I then used Instant forms for the conversion location which determines WHERE leads should be generated. An instant form gives the option for the person on Facebook (or Instagram) to fill out a form automatically on Facebook without needing to add any data. It will pull from their profile instead. Makes it faster and easier for someone to share their details.

You’ll have the option to create a new form or use one of your existing instant forms. One important thing to do is change the questions. By default it will have Full Name. However, D365 uses two fields, first name and last name to make up the full name, and we need to capture the persons data in the same way. Delete the full name then add in the first name and last name fields from the user category option at the bottom of the form.

Set up everything else about your add so that it looks nice and explains what someone is going to be subscribing to. You can make it all live or schedule for when you want it to be published and accessible.

Now, the part to get things in to Dynamics 365, go to the Instant Forms overview.

From here you can click on CRM Setup.

Dynamics 365 is NOT an option, and neither is Power Automate. However, there is a great tool out there called Zapier. I already had this and have used it for other processes in the past where there was no connector for a flow. Hopefully your IT or Procurement team are OK with you having this as although there are free options, you will need to use some of their premium steps and connections.

You will then be taken through a series of steps of a wizard where you will be prompted to select which Meta account to use, which Facebook page and which of your instant forms (any or a specific one). You can then test the trigger which will generate a test lead for you.

Your next step will be to connect to your Zapier account then select Microsoft Dynamics 365 CRM as the CRM of choice. You will be prompted to authenticate and connect to Dynamics 365. Then pick the action you want to use. At this point, we are just going to pick Create Contact or Create Lead and fill in a few bits of information to store on the new Contact (or Lead, but I am doing Contacts) record. We are going to end up going in to Zapier to finish everything off so don’t worry too much about this step. You WILL need a field to store the Lead ID generated from Facebook so if you don’t have a field to store it on, make sure you get that added first.

Once you’ve confirmed everything is connected and your test Contact ended up in D365 you can finish with the wizard in the Meta Business Suite and then go find the Zap you created in Zapier. This will be the start of your Zap which shouldn’t need any changes to it at all.

Next we are going to delete the Create Contact step and instead add a Find Contact action event instead. We certainly don’t want to create new records if they already exist and mess up our nice clean database right? So the Find Contact step will let us search using the email value to see if they are in D365 already.

Start filling out the values on the fields you have in D365 and either populate them with data from the first step (pretty much the same way you would with a flow in Power Automate) or by setting defaults. We can see I am adding the email, first and last name values, and using the Created Time in a field named Subscription Date. Midway down the list of fields, you will see an option that says Match if any of the fields match and then Search by email only. I have the first option set as No and then the second as True (yes). I don’t want to try and match on multiple fields, email only.

Then you will see a tick box that says, create the Contact if it doesn’t already exist. So, if there is no Contact found, let’s go ahead and create a new one.

You can then fill out all of the other fields you want to populate (things like email, first name and last name are above this create tick box). you can see below, I have actually set a specific URL link for one field, and updating some other values that I want to have as defaults for Facebook Leads.

Our next step is Update Contact as the action event.

In the configure part of this, get the ID from step 2 above so that we know the record found is the one we will update. You can now choose to update whichever fields you want on this existing record.

Now we will do another find step and update step but this time for a custom entity.

Select the Contact Point Consent custom entity and use the Email field from the first step from Facebook as the searching criteria. Again, we want No for matching if any fields match but search by email only to be False. Then tick the box for creating a new record if one doesn’t exist. Then fill out all of the fields to link to the correct Channel, Purpose etc.

Step 5 will be the Update for the custom entity of Contact Point Consent and you will use the id found in step 4. You just need to update the Consent status field to Opted In, Reason can be Opt in – Advertisement and Reason can be Internal. You can also use the Who requested the change field to type in Facebook Lead Gen or something that makes sense to you. I’ve got a send email step at the end to notify me, but that’s just so I knew it was working!

Now when we get someone filling out the instant form on Facebook, we can see everything came through in to D365.

Their Contact Point Consent record is either created or updated, brilliant!

Now what about sending the welcome journey? That’s up to you how you do it, but because this person isn’t filling out a Customer Insights marketing form, I needed a different way from the regular subscription journey. For this I added a new dataverse trigger that fires when the Lead ID field on the Contact is updated (either existing Contact or New).

Then on a journey you can use the trigger and set a condition to make sure the Lead ID is not empty, and any other additional logic that makes sense. For me, I have a Subscription Date field that gets set when the new Contact is added from Facebook so I set it to make sure that date was today so I am not sending someone old through it.

The most amount of work was figuring out the whole Meta Business account side of things to be honest! Although I did this for a test, I have had 7 new people subscribe via this method so not a bad result for a blog post. Is this something you think you might use? Let me know in the comments!

Original Post http://meganvwalker.com/add-facebook-leads-customer-insights-journeys/