usually I deactivate the emails in that stream.    If you really don't want it, just slide to the RIGHT and change its name so it's not used anymore. ... View more

a single inbox or a single person?   The throttle is likely on the domain. ... View more

If you can't use Contact Roles, you need an Account or Contact level field identifying an opp.   Has Opp filter has Record Type or Opp Type filter (or you can add it in SFDC). ... View more

You may want to read SFDC docs on Formula fields to accomplish this.   If you look at Account scoring guides, most don't recommend this approach anymore. ... View more

Each tool should have its own docs.   Try zapier or tray for these scenarios. ... View more

Hi James,   Generally none of the webinar providers recommend this. You want a 1-1 relationship between Program and Webinar.   Glad it's working.   If you want to track success rate of AB tests, different channels, etc I recommend leveraging UTM parameters and then reporting in SFDC or using smart lists.   It's sleeker and easier to maintain. ... View more

Agreed.   Need a very clear process chart and an understanding of which fields map, can be overwritten, etc. There are several dozen threads on this site about this kind of situation. I believe there is even a presentation in the past couple of years on how to manage it.   CRM > Marketo > SFDC ... View more

Something doesn't sound right. The Module or Element should be editable unless the original coder of the Template made it not editable.   You may need to adjust the Template slightly. ... View more

please describe your use case more?   If Munchkin is on the page, it will fire (barring exceptions) and log the activity.   If you don't want a Trigger Campaign to fire, tell it to ignore that URL.   Otherwise I'm not sure what you are attempting to do. ... View more

Did you check developers.marketo.com?   My understanding was that on multiple sites, the Lead will be assigned multiple cookies. They won't be merged until the Lead fills out a form on two or more sites with the same email address.   (assuming dupes aren't an issue here). ... View more

Hi Malik, This is well covered in earlier discussions. But without knowing more about why Sales (??) is asking for the smart lists, it's hard to give you a good answer for your needs. Nested Smart Lists, as a rule, should be avoided or at least minimized. Yes, if you reference a lot of smart lists in a single smart list, it will slow down processing. If those smart lists ALSO have smart lists, Marketo will cascade this down, waiting for each lower smart list to complete in order to pull the right people. Cross Tab Smart Lists - you have the right idea and you will need to take say a Vertical and cross it with "Emailable" One of the key ways to reduce the overhead is Smart Lists run from top to bottom. I always run smart lists LAST so that the dataset is smaller by the time it reaches the last filter. Segmentations - if you have standard Vertical, Geo, and Emailable concepts, you can easily create a Segmentation and that will run a lot faster and allow you to build on top of those. Standing Smart Lists like you propose are a GOOD idea.  Yes, they will get referenced everywhere and you need to be prepared to carefully update any master lists because it will cascade.  Be ok with thousands of these. It will happen. It's ok. Organize your Lead Database in good foddering (lots of Naming & Org options in the Community here) Watch out for multiple Workspaces. ... View more

I agree with all of these. Check out some of what I've written about before: https://www.marketingrockstarguides.com/?s=lead+scoring https://www.marketingrockstarguides.com/webinars/ https://www.slideshare.net/jdavidhill/marketo-revenue-cycle-model-and-lead-lifecycle-how-to ... View more

What's the use case YOU are trying to solve for? What do you mean by "claim event leads"? Most firms I've worked at route event leads to the Account, Contact, or Lead Owner per whatever territory rules exist. If you are setting up something like a Round Robin that is usually better than a free for all. ... View more

That does work. Another option is to disable the Deduping flag on the backend and then you can let your normal Partitioning work. Then you take the master list, upload just the fields you want to a special WS/LP and you send the follow ups from there. The downside is you lose the reporting data on the actual lead. But it's an option for certain situations where you can't mix data across Workspaces or with SFDC. Jackie's method definitely takes a step out and you'd need to have such a WS anyway to upload the leads so they are processed centrally anyway. The concern I would have is the wrong marketer having access to ALL the data and possibly using the wrong lists to send the follow up if that person isn't used to having full access. ... View more

I like that. Here are a few ways we do this: Field Identification I do this primarily to manage 250ok seed lists, but you can flag a lead with a Boolean and say this person is a Seed. This is a good way to automatically BLOCK seeds unless you specifically bring them into a list. I then put this into a Segment so they are easily used or blocked as a group. easy to remove/delete later. Email Address IS with the OR Logic: (Whatever) or [Seedlist] where the seed list is a List or a list of email addresses and is the LAST filter on the smart list. Be sure the record exists already! Lists/Smart Lists as Abishek noted, you may need several "groups" like "Customer Marketing - Seed List" or "UK Email Seed List" Naming: prob better to say "Seedlist - NAME" to ensure they show up easily. ... View more

Generally the smart campaign, smart list, email perf report, and email insights, and RCE will all be slightly different. This is due to how Marketo records information. There is a doc on docs.marketo.com as well as a ton of threads on this topic. ... View more

Amit Jain wrote: Some of these might already be pointed out but here is my take:    SFDC Field sync: As of now, Marketo sync all the fields visible to marketo user in SFDC automatically and if we already have a similar field existed in Marketo, it creates a duplicate. We have to go to Marketo support to merge those fields. It would be ideal to let admin which SFDC field needs to be sync with Marketo and merge with existing field, if needed.    Yes, orphaned fields are a problem and they typically appear based on their object in this case. Sometimes it's helpful, sometimes not: Opt In (L) (C) or (A) if this happens. But sometimes it's just on one object, sometimes not. The best thing to do in this situation is to ask Support to help you merge the fields. The challenge is to do this as soon as you notice this, or work with them BEFORE you create the field in SFDC. They can merge the fields, but it does destroy data if you don't do it right. ... View more

good to know Pierce, thanks! ... View more

Smart Campaign 1: Select Account 1: Send Email 1 Smart Campaign 2: Select Account 2: Send Email 2 If you have a specific identifier for each account rather than just an email address you can do this. You could also run a single flow but you would need 10 Choice Steps within the Send Email Step     Select all 10 accounts Send Email: if Account 1, Send Email X, if Account 2, Send Email X You may find it works better with 10 email assets, but it should work with 1 email asset and 10 choice steps if you select the accounts correctly. ... View more

You could push the two SFDC Orgs into separate WS/LPs depending on the use cases and security. That might have been a better idea for the scenario Jay identified. I agree with Sanford that this needs to be load tested due to the use of the API instead of the std Sync. What's the record volume and update volume? Dedupe plan? A second Marketo instance may not be that expensive depending on your existing deal with them and if you plan to keep your record count total for both instances within the existing range. ... View more

Yes that would be ideal unless you are running a weekly batch update for some reason. Please note a few things: 500mb daily limit for bulk api upload. You can increase this for a fee, but the increase is temporary unless you negotiate it up. You would only see the trigger eval queue or sync get clogged if you happened to trigger or batch run something tied to a field or Custom Object that had a mass update. Remember std REST API has a 20 per second update limit. ... View more

I can't speak to the legality, but you can use RingCentral APIs, Twilio, and Informatica's tools. ... View more

You can do a lot of this already. But it's not on a single screen. ... View more