Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
@Deeps, Marketo automatically de-duplicates people in the Email Send program and batch campaigns and only sends one email to that email address. The count for the smart campaign will always include all qualified leads because duplicate leads will still run through the same smart campaign and qualify...
You’re welcome, @arvindaiah! Glad to be of help.
Thanks for posting all the detailed findings @michellechopin ! I totally agree with you regarding the limitation, where the user whose account is integrated needs to create a webinar in Webex for Marketo to see it. Also, yes, let me reach out to relevant people at Adobe and request them to add these...
Yes, running a batch campaign to process the existing people created from CRM should do the trick. I usually create a trigger campaign first, clone it and remove the triggers from it and set it up as a batch campaign for such things. You can also create a monitoring smart list to see whether anyone ...
You’re welcome, @Guitarrista82! I am glad to be of help. 🙂
@Ghizlane1, This is more of a strategy-related thing (i.e., which channel and medium to choose)! If I were you, I'd have taken a call based on the past engagement data to see which of the two, i.e., LinkedIn Lead Gen Forms or the Marketo Registration page, has performed better for similar things. Ad...
I agree with Katja here! You should consider creating a dedicated operational program to process people coming from your CRM and updating the acquisition program and other updates that you'd normally want to do for people getting created from Marketo. This would allow you to keep things organized an...
@Guitarrista82, batch and trigger campaigns are processed in separate queues (the article you have linked also states the same). Additionally, the campaign priority override feature that you mentioned is applicable to the trigger campaign only. You cannot override the batch campaign's priority. When...
I just checked this, and it turns out that for your particular use case where you want to integrate MSI for non-native integration, you'd need to use the unique Salesforce-provided Account/Opportunity/SalespersonId unique IDs; you can't use your own custom IDs as those aren't configurable in the MSI...
You're welcome, @rgallegos! Glad to be of help.