"Person is Pushed to MKTO" Trigger

[Anonymous]

Hi Sanford, I'm not seeing the Person Pushed in the Activity Log either. All I see is the person being created or updated in the DB, and any other associated activities that are happening on the back-end, as a result of the form submit. The trigger is definitely not working. If I configure the Smart List with the Person is Created and Data Vale Changes triggers, it works fine.

[Anonymous]

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

[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.

[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

[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]

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 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