"Person is Pushed to MKTO" Trigger

[Nicol_Maurer]

We are relatively new to Salesforce, and up until now had never had a sync with our CRM. In re-setting up some of my nurture campaigns, I'm wondering if I should include the "Person is Pushed to MKTO" as a trigger. May I assume that these are leads/contacts created in Salesforce that are NOT already in MKTO?

[Anonymous]

Hey Nicol,

Once you sync your Marketo and Salesforce instances for the first time and connect the two, you don't need to add a trigger in your campaigns to sync the leads from Salesforce to Marketo moving forward because this will happen automatically. It is a bi-directional sync. So once the initial sync is set up, if a lead or contact is added to your Salesforce instance, it will automatically sync to Marketo. Here is a good graph that shows the bi-directional Marketo and Salesforce sync and what fields are included in that:

Hope this helps!

-Courtney

[Nicol_Maurer]

Thank you! I just wanted to make sure I wasn't missing those folks that may have been created in SF, rather than those that came in directly to MKTO via a form fill.

[Anonymous]

No problem! Yeah, as long as you have the Marketo and Salesforce sync live and set up, you won't miss anyone. You will also be able to see where the lead was created (whether it came from a Marketo form fill or from your CRM database) in the Person Source field.

[SanfordWhiteman]

No, this trigger is not relevant to SFDC sync. It logs the use of a separate Marketo-specific API.

[Anonymous]

Hi Sanford,

I just posted a question relating to this on another post (What exactly is the "Lead Pushed to Marketo" trigger on a Smart List?), but since this post is much more recent, I'm posting the same question here...

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]

Is it also possible to use the "Lead is Pushed to Marketo" trigger for updates to existing Marketo Leads/Contacts,

Yes.

[Anonymous]

So I tested this today with a Rest API update from a web form, and unfortunately the "Person Pushed to Marketo" trigger doesn't seem to work. I tested the same campaign with two different Smart List filters. For the first version, I used the "Person is Created" and "Data Value Changes" triggers, and I selected "Web service API" as the source. For the second version I used only the "Person Pushed to Marketo" trigger, and the person was not added to the campaign.

I'm wondering if there is anything else that I need to include in the REST API call to make this work? 

Thanks!

[SanfordWhiteman]

Are you seeing the Person Pushed... in the Activity Log? Can you show the ActLog detail?

The Push Lead endpoint is designed to trigger every time -- wouldn't be useful otherwise.

[Anonymous]

Hi Sanford,

Just following up to see if you might know why the "Person Is Pushed to MKTO" trigger isn't working for me? Would be great if I could get this working, since the "Update Data Value" triggers aren't really ideal for my situation (although they do work).

Thanks

Timo

[Steven_Vanderb3]

If you can provide the JSON of your request and response and a screenshot of how the Smart List in your campaign is set up, it will be easier to troubleshoot what's going wrong.

[SanfordWhiteman]

Ah, that's the Java code (which you should delete from your post immediately as it may contain privileged information).

I just want to see the endpoint the dev is using and the JSON that's being sent. The programming language doesn't matter (and just confuses things).

In a search of the source I don't see the Push endpoint. I have a feeling they're not using the Push Lead method. This has to be a deliberate choice. It's not the same as the older upsert (leads.json) endpoint.

[Anonymous]

Hi Sanford,

So you're feeling was correct. It's doesn't look like dev is using the Push Lead method...

EndPoint:  /rest/v1/leads.json

At this point we would be a bit pressed for time to make any back-end changes for this project, so we are going to continue with the current method and use the Data Value Change trigger (which I mentioned is working). This information was very helpful though, and we will consider it for any upcoming projects.

Thanks Again

[SanfordWhiteman]

Definitely think about it for the future! I didn't see the need for Push when it first came out, but now I use it exclusively instead of the leads.json upsert.

[Anonymous]

Thanks, I will certainly consider this.

As I'm not a developer myself, would this be a relatively easy switch for the dev team? When I approached them with the suggestion to use Push, they didn't seem to know much about it. Is there some specific documentation I can send them for reference?

Timo

[SanfordWhiteman]

It's in the developer docs -- pretty easy to work out but I wouldn't want to push someone unless you could show value. To me the value is immediately apparent since you can see API-only activity explicitly in the UI (without having to drill down into details).

[Anonymous]

Thanks Sanford,

Going to relay this feedback to our developers to see what we can do. I did have a feeling that it may have been a result of not using the Push Lead method (or similar), which is why I had originally asked if we may be missing something to make this work. 

[Anonymous]

Hi Steven,

I'm not sure what you mean by the JSON of the request and response? Are you looking for the code for the REST API call that is writing our external form values to Marketo? I have attached a screenshot of one of the Campaign Smart Lists.

Thanks

Timo

[SanfordWhiteman]

Yes, the actual JSON going on the wire.

[Anonymous]

Thanks! I've asked our developer for the code, and will post it here shortly.

Timo

[Anonymous]

Here is a person sample from the test I ran on Friday...