AnsweredAssumed Answered

Munchkin API & Smart List Triggers

Question asked by Gary McCarthy-James on Nov 12, 2016
Latest reply on Nov 12, 2016 by Sanford Whiteman

The majority of lead data that is delivered to our client's Marketo instances is via the Munchkin API. When we first received training from the local Marketo trainer and talked about the API and the best way to go about things they suggested the best way to fire triggers for smart lists for leads delivered by the Munchkin API was the following:

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

1. Create a program

2. Create a smart campaign for a new lead with the following smart list parameters:

new-lead.png

3. Create the flow steps for that "new lead" smart campaign

4. Clone the smart campaign for "new leads" and rename it to "existing leads" and use the following smart list parameters:

existing-lead.png

We would then use the following javascript code to get the lead information into Marketo using the Munchkin API. The $.now() in the "formID" attribute is used to trigger the "data value changes" for existing leads at is sends over a unix timestamp so Marketo sees it as a change in that value.

from-id-field.png

 

This method works fine but it seems like a lot of duplicate effort. We have to make a smart campaign for new leads and a smart campaign for existing leads. And if the flow steps need to change we have to update them in both new & existing smart campaign flows.

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

So, we thought, what about the following revised method? It seems to be achieving the same trigger results for both new and existing leads but we can do it with a single smart campaign for both new and existing leads.

 

1. Create a program

2. Create a smart campaign with the following smart list parameters:

revised-method.png

We would then use the following javascript code to get the lead information into Marketo using the Munchkin API. This associates the lead for new and existing leads and we send a "virtual page view" with the "visitWebPage" method that we can then use for our trigger.

form-id-page.png

 

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

 

Are there flaws in the revised method or is there a better way to do it?

Outcomes