Hi,
so we want to get started with the LinkedIn Lead Gen forms and going through the the field mapping!
But we have our own lookup field for country and region, and I found that we are not able to map a field to a lookup field it seems!
So how is this being solved to ensure we get the right country and regions in LinkedIn Lead Gen forms?
regerds
Martin
Hi Susanne, if you read the comments above you can see there are lots of issues with this integration. I also wanted to use hidden LinkedIn fields and map them to a custom field in 365. This is not possible and it means we cannot process the lead correctly without quite a lot of manual work. We do not want a semi-automation solution.
It also seems that Microsoft are not interested in fixing this integration.
We will look to make our own API integration with LinkedIn. I have seen however that Zapier have their own API connector which might be of interest to you? www.youtube.com/watch
Hi everyone,
I do not have an answer to this question, I've rather come here to see if there is any news on this topic with recent releases.
We're having the same issues of LeadGen forms not mapping all fields (no hidden fields with lookups in Dynamics) which means a lot of manual work for our team.
If there is no native seamless way to map this, my question would be whether this can be achieved through a flow in the background to bridge the gap of direct field mapping.
Has anyone any experience with this?
With all the automation in 365M I don't want to believe I have to go back to importing leads from excel spreadsheets....
Any idea is much appreciated. Thanks!
Susanne
Hi Niels,
I think this is great information and very thankful for you posting this here, and I have had my suspicion regarding this as well so we are probably going to wait with this in our org if I can convince higher management..
very useful input, thanks.
regards
Martin
The whole Linkedin lead gen connection is a mess and from my support tickets with Microsoft it seemed that not many people were using it. I hope that after the big real time customer journey updates Microsoft has more time to fix the integrations.
1. It creates new leads / contacts for all active campaigns without matching with your current database (so be aware that it might create a bunch of duplicates / create hundreds of contacts when you activate the sync for every user. Test this in dev first).
2. Everything gets assigned to 'system'. There is no way to assign it to teams/users like with normal landing page forms (have to create workflows/flows for this). This might be an issue depending on your environment/security roles.
3. It wouldn't work with custom business process flows (supposedly fixed, but haven't been able to test that yet).
4. Fields don't sync correctly (email was for example not transferred to dynamics unless they had their email public. This means you could see the email in the submission/export, but it wouldn't transfer to dynamics making it pretty useless for marketing campaigns. Don't know if this is fixed yet).
5. field mapping limitations like you mentioned.
Anyways, this is just a small portion of the issues I've had with this functionality and my contact with Microsoft. Due to all these limitations we are currently not using it. I understand that this is not a very useful reaction, but it's just a caution.
André Arnaud de Cal...
292,111
Super User 2025 Season 1
Martin Dráb
230,934
Most Valuable Professional
nmaenpaa
101,156