What exactly is the "Lead Pushed to Marketo" trigger on a Smart List?

[Anonymous]

What exactly is the "Lead Pushed to Marketo" trigger on a Smart List?

Exactly what would cause this trigger to fire? I can't find any documentation on this trigger to know the various circumstances that could fire off this trigger.

Thank You.

[Devraj_Grewal]

Robert,

I believe the "Lead is Pushed to Marketo" trigger and "Lead was Pushed to Marketo" filter are when a lead is synced into Marketo as a new lead. For example, if you created the lead in your CRM and on the next sync cycle, that lead would be "pushed" into Marketo. I also believe it would trigger if the lead is deleted in Marketo and the CRM syncs it back, in which case, it would be considered a new lead to Marketo.

You're right though, there is no documentation on it.

[SanfordWhiteman · Accepted solution]

Devraj Grewal​ Robert Conner​ guys, this is incorrect.

Lead is Pushed to Marketo means the REST API call Push Lead was used. It's not about syncing from CRM.

[Grégoire_Miche2]

+1 on Sanford

[Devraj_Grewal]

Appreciate the clarification, Sanford. I had a hunch it was regarding the sync.

[Anonymous]

Do you have any cases for when this would be used - could it replace "Campaign is Requested > Web Service API" for say a form integration from a non-Marketo form. Thanks very much

[SanfordWhiteman]

It's designed for single-call lead insertion, yes. I would never, ever invoke it via a public form because it is a guaranteed DoS attack vector. IMO (as you can see from many of my other posts) none of these methods should exist as they encourage people to build non-professional solutions.

[Anonymous]

Hi Sanford,

I have another question regarding your initial response. Is it also possible to use the "Lead is Pushed to Marketo" trigger for updates to existing Marketo Leads/Contacts, or does it only trigger based on net new Lead creation?

Thanks!

[SanfordWhiteman]

See my answer on the other thread.