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.
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?
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).
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!
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.
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.