Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
Hey @SanfordWhiteman ,Just wanting to clarify. So if I only wanted to trigger if both first and last names were changed recently (for some reason). Are you saying that there is risk of using a setup like this: Triggers:Data Value Changes - First NameData Value Changes - Last NameFilters (Use all fil...
If either of those conditions are met then it will trigger the campaign. So in this case if either first or last name is changed. If you are looking to have it so that both have to have changed you'll want to add some Data Value Changed filters with some recent time constraints (maybe 1 minute or 1...
I really would like to have the details of what is open in a particular tab listed. When working in the updated interface I've noticed all tabs are titled "Marketo Engage". Makes for a lot of clicking around in tabs if you like working with multiple open. Here is open tabs on the old UX for comparis...
You can find the Munchkin Account Id under:Admin Panel>Integration>MunchkinIt should be listed at the top of the panel that opens up
I'm not sure of this, but I think that the suggestions don't show up unless at least one lead actually has that value in the field. Even then however I have found it to be inconsistent of what values show up.
If you have the list of email addresses you could just copy them and paste them into an email address filter in a smart list, each on its own line. Then use this smart list in your report filters.
Yah, think of them like normal smart campaigns. You can add multiple triggers to accomplish this. First TriggerScore is changed (new value is 26-59)Second TriggerClicks Link in Email and pick the email/link
You could do it would 2 smart campaigns:Smart campaign that adds people to a list using random sample.Create number of lists for number of weeks you want to sendIn flow of campaign use an add to list flow step and add choices, use the random sample option and correspond that to the number of lists y...
I think the only way someone could be a part of no model is if there were none approved. Or maybe if you're using different workspaces/partitions. I think this because the first transition is a system set one when a lead becomes known.
You could create a "MQL Reason" field and then upon MQL populate that field with one of a few different things depending on your instance setup. If you make good use of interesting moments you could fill it with "{{lead.Last Interesting Moment Type}} - {{lead.Last Interesting Moment Desc}} - {{lead....