Skip to main content
Tierra Davis a posé une question dans #Trailhead Challenges

Is there someone that's familiar with the relationship between Salesforce and LinkedIn Lead Gen forms? I'm having trouble with the overall setup. I believe I've set up the fields correctly but I need help with testing and making sure things are tracking correctly. Could someone walk through the process with me in real time?  

 

#Trailhead Challenges

6 réponses
  1. 14 sept., 07:30

    Hi Tierra, 

     

    Per the official Salesforce documentation: "When prospective customers fill out a form on your LinkedIn ad, we convert the data directly to new leads in Salesforce." So the native LinkedIn Lead Gen Forms integration always creates a new Lead record, it doesn't check against existing Contacts first, which lines up with what Aman mentioned. 

    Reference:

    https://help.salesforce.com/s/articleView?id=sales.leads_linkedin_lead_gen.htm&type=5

     

     

    To document a form fill on an existing Contact's record instead, here are your options, in order of effort: 

     

    1. Manual match-and-convert (lowest effort, no extra tools): 

       Set up a report or list view filtered on Lead Source = LinkedIn, reviewed periodically. When a new LinkedIn Lead matches an existing Contact by email, use standard Lead Conversion and choose "Attach to existing Contact" instead of creating a new one. Not real-time, but zero extra build. 

     

    2. Automated matching via Flow (moderate effort, native only): 

       Build a Record-Triggered Flow on Lead (After Save) that searches Contact by Email. If a match is found, auto-run Lead Convert pointed at that existing Contact, and log an Activity/Task on the Contact noting the LinkedIn form submission details. This gets you close to real-time without a third-party tool. 

     

    3. Third-party connector (what Aman flagged): 

       Tools like LeadsBridge offer built-in "search Contact first, only create Lead if no match" branching out of the box, but bringing in a whole platform just for this one gap is real overhead if it's your only need. 

     

    Given you're already this deep into setup, option 2 (Flow-based auto-match-and-convert) is the best native middle ground, no new licenses, and it directly solves documenting the form fill on the existing record without manual review.

0/9000