"Person is Pushed to MKTO" Trigger | Community
Skip to main content
N
Nicol_Maurer
Level 3
March 28, 2018
Question

"Person is Pushed to MKTO" Trigger

  • March 28, 2018
  • 2 replies
  • 6240 views

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?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

SanfordWhiteman
SanfordWhiteman
Level 10
March 28, 2018

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

    N
    Nicol_MaurerAuthor
    Level 3
    March 28, 2018

    Thank you!!!

    A
    Anonymous
    March 28, 2018

    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

      N
      Nicol_MaurerAuthor
      Level 3
      March 28, 2018

      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.

      A
      Anonymous
      March 28, 2018

      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.

      Terms & ConditionsAccessibility statement

      Loading footer...