LinkedIn Lead Gen Form (Organic Content) Automation does not work

Hi ​@RuP 

For us to have more info about what you are mentioning, post these screenshots:

• how your Zap steps are outlined
• how your Zap steps are configured in EDIT mode with the field mappings visible

Hi there, ​@RuP 👋

Just came across this and wanted to check how you’re getting on. Were you since able to get a real test record loaded in the Zap? 

If not, try creating one through the Campaign Manager UI to see if it’s able to pick that up so that you can finish setting up the Zap. 

One thing to bear in mind is that LinkedIn requires certain permissions to be in place for the connected LinkedIn account. So if the permissions aren’t quite right, then that might be why you’re not able to access any test records for the form. You can learn more about the required permissions here: What permissions do I need to access data via the New Form Response trigger? 

Looking forward to hearing from you! 🙂

Ok. I’m calling this a BUG.

I’ve run Linkedin Event + Lead Gen Forms to Zoom on Zapier for the last 4 years.

And this bug since surfaced with the release of the latest Linkedin Ads Zapier App.

To re-create:

• Create a Linkedin Event with Lead Gen Form enabled.
• Create a Zap trigger
• Use Trigger Event: New Linkedin Lead Gen Form (Organic Content)
• Select Event type: Events
• Select the test event
• publish
• create second sub so to publish the zap.

• The trigger the zap by registering via the lead form on the event (you will need to get a different acocunt to do so because you are already registered by virtue of creating the event)
  
  Go back to the zap and you will see the lead did not trigger the zap and no test records will be retrieved*
  
  *note if you had previous events from the older version of Zapiers Linkedin Ads. The test records will be retrieved from the event no matter what event you select.
  
  I hate sound melodramatic but this is about to have a huge impact of on business because we run events with 200-300 linkedin event registrations and right now this BUG is stopping us conducting the events that directly grow our business.

Thanks for reaching out here to share your findings on this, ​@Cameron31232! 🤗  

I’m so sorry to hear you’re running into issues with the New Lead Gen Form Response (Organic Content) trigger as well—really appreciate you taking the time to dig in and let us know what you’ve discovered.

Since it was working for you previously and stopped after a recent upgrade to the LinkedIn Ads app on Zapier, it could indeed be a new bug that’s surfaced. If you haven’t already, I’d recommend reaching out to our Support team directly to have it investigated further. They’ll be able to open up a bug report so our engineers can get it sorted.

Please keep us posted on how you get on with them, want to make sure this gets sorted! 

Update - to let you’ll know that after resetting and testing with a different linkedin account I was able to retrieve an event form registration. 

It is NOT a BUG.

However, the test data is misleading because of an issue with the ordering of test form submissions.

See support message below:


“So I checked on our end, and internally, we do have a feature request open for form submissions to be fetched from newest to oldest. Currently, the Zap pulls outdated sample data as we can see is the case in your example.
 
I have added you to the particular feature request and this would do a few things:
 
• Bring this to the attention of the dev folk - I have included logs and responses from the application so they can take it from there
• Help track interest - other users asking for this would be added as a vote for this request - the more the users, the better the chances of this being implemented
• Remind us to notify you when there's any progress on this - if there's an update, you'll be the first to know
 
While I don't have an ETA on when this feature might be implemented, we will definitely let you know once there's more info!”

If you want to fix this issue, get in touch with support.

Hi ​@Cameron31232,

Thank you for providing an update regarding this issue!

If there’s any members who run into this issue, please let us know and we’d be happy to add you to the feature request!