Coming Soon - Updates to Native Marketo CRM Connector

Ather01
Marketo Employee
Marketo Employee

I’m happy to announce a that the current Native Marketo CRM connector has a new update to the CRM background synch which is now built on a modernized tech stack and will be available soon.

 

What’s Changing

Although the core functionality remains basically the same, this new version offers greater efficiencies in terms of speed and increased reliability. This version applies to the incremental ongoing background synch and not the initial bootstrap synch which is performed when customers initially setup and run the integration for the first time.

 

All standard entities like Lead, Contact, Account, Campaign Opportunity will be supported with this version. Other Salesforce entities like Custom Objects, Tasks, PMCF, Events and Activities are soon to follow in another up-and-coming release.

 

Benefit

As we know, bulk updates using Trigger Campaign Flow Steps have been a constant challenge triggering Salesforce platform errors like Lock Rows and CPU Timeout errors. With this new update, these errors should be greatly reduced and offer higher synch success rates overall. This particular functionality is part of the new version and will be made GA once its fully functional.

 

Some customers will experience immediate performance improvements upon transitioning over to the new version, possibly as much as 2-3x faster depending on their configuration and objects being synched.

 

Transition to the new version should be seamless to customers and do not require any migration or re-configuration of the current native connector or to field mappings.

 

Scope

This version only applies to Salesforce Integrations and does not include MS Dynamics at this time, but rest assured it is on the Roadmap and will be communicated to customers as soon as we have a firm timeframe. Documentation revisions are in progress to provide more details on the new version and will be published at the time of the rollout.

 

Timeframe

I’m sure you’re all wondering when, so I’m happy to share that availability of the new version will be available to customers sometime in Q1 of 2025 and will be rolled out to customers incrementally.

Update: The availability timeframe for this feature has now been changed to Q2 2025. 

 

Multi-CRM Integration

There are some customers who require a Multi-CRM integration with Marketo Engage as part of their overall marketing strategy. Adding an additional CRM source can be achieved using a 3rd party solution offered by Vertify. More information on this solution can be found here https://vertify.com/integrations/marketo/

 

2850
4
4 Comments
Jo_Pitts1
Level 10 - Community Advisor

@Ather01 ,

does this mean that when someone is transitioned to the new version, the events not supported in this release (Custom Objects, Tasks, PMCF, Events and Activities) will no longer be synced, or will they continue to be synced using the current methodology/version?

Cheers

Jo

Ather01
Marketo Employee

Hi @Jo_Pitts1 , 

Thanks for your reply and great question.

For customers who have been transitioned to the new version, the events that are not covered in the new version will be synch via the existing version. This should happen in the background seamlessly. The remaining objects will be included in an up and coming release and I will post here when they are ready. 

 

Regards,

Ather

AAlvarez_ZI
Level 1

Great to see that this.  Way overdue.  My question is what enhancements will customers on Performance Tiers get with this?

Ather01
Marketo Employee

Hi There,

Thanks for posting. This is primarily an infrastructure improvement that is part of core connector that is used by all customers that integrate with Salesforce and not limited to Performance Tiers. Performance Tier customers will ideally notice some higher synch rates based on the newer technology its built on. Also, if they use Trigger Campaigns with Flow Actions that synch to SFDC using large lists, this will reduce synch failures due to Salesforce Platform limitations like Lock Rows, CPU Time outs.

 

Regards,

Ather