Badges
Accepted Solutions
Likes Received
Posts
Discussions
Ideas
Blog Posts
I would go with a rolling list not based on type, so LIM1, LIM2, LIM3, etc.For how you accomplish this, you could set up a smart campaign triggered by "Has interesting moment" and then in the flow, you have change value steps for all your LIM fields. Each change value step would reference the previo...
When you cloned the campaign, all the smart campaigns and other objects were reset to use the newly-cloned lists. Meaning, you need to go into the smart campaigns and everything else and remove references to the lists you want to get rid of before you'll be able to delete them.
Apologies if there's already a few threads on this, but I just wanted to see what other folks have found works best when configuring your forms to re-subscribe/opt people back in that have previously unsubscribed. I know some documentation says just add the Unsubscribed field to each form, hide it a...
Hey Robb Barrett did you ever find a solution? I've had some of these errors as well and all support tells me is that it has to do with "My REST Service" in LaunchPoint and I have to track it down myself from there.
Wanted to add a use case to this idea: I like to keep all my email blasts/programs centralized together, which means they live outside of programs they are promoting (e.g. a webinar). But if I want activities related to an email program promoting the webinar to affect smart lists/flow steps inside t...
Allow for SFDC Campaign tokens to be used in the "Added to SFDC Campaign" trigger within a smart list. Currently it doesn't accept the token, even though most all other flow step actions having to do with SFDC campaigns do accept the token type.
I'm curious how people have dealt with organizations in which purchased leads are a big element to their demand generation programs. I'm staunchly opposed to purchasing leads, but despite my arguments against them and how they can damage a company's reputation, are bad for compliance, etc. -- I get ...
You're absolutely correct that this would be ideal, but I neglected to mention we're also battling database limits with Marketo at the moment. Keeping all the purchased leads in Marketo would put us way over our limit. It might be worth upgrading to the next tier rather than mess with the alternativ...
I'm working through a scenario dealing with preventing purchased leads from flowing down into Marketo UNTIL they opt-in naturally. Our sales team acquires leads and imports them directly into Salesforce, I believe as contacts, and in order to maintain compliance, we mark them in a way that prevents ...
Is the program in Marketo synced with the Salesforce campaign? Or are you adding them to the campaign via a flow step elsewhere?