Gotcha. You could always use workspaces and partitions, which would make the process a bit more bulletproof. ... View more

Hey Stephen, when we're doing this consistent level of targeting at audiences, we bake it into the processes as an extra step, using segmentations. Because this is such a driver for your marketing, that kind of targeting warrants the creation of a Marketo segmentation. New segmentation: "Targeting: Customer/Prospect" Segment one: Customers Segment two: Prospects Segment three: Default (should have 0 leads/contacts in it) Then in each of the smart campaigns and targeting lists, you'll make sure to include (1) the filter for customers when you only want it to customers, (2) the filter for prospects when you only want to send to prospects, and (3) no filter when the program is targeting both prospects and customers. As part of the process, you'll have to make sure the smart campaigns match your program tag—there isn't an automated way (out of the box) to match the filters to the tags. If you wanted to bake in the filters a bit more, you could create program templates, where you have separate program templates for Customers (using the appropriate filter) and separate program templates for Prospects (using the appropriate filter). Cheers, Edward Unthank | Founder, Etumos ... View more

I find this makes much more sense to do in SFDC. Marketo's cross-lead lookup functionality through the UI is nearly non-existent, with the exception of "duplicate field" filters. I'd have an SFDC workflow run upon the SFDC lead creation, and if there's a customer match, mark a separate SFDC field (synced with Marketo) to show that the record has a customer match based on email address. That way you can run automation based on that field becoming "Customer" or not, such as your Lifecycle Processing to move them from MQL to Customer. If you're writing to that separate field, also, you can have a more modular setup where you're improving the accuracy of writing to "Customer" field or not—you'll quickly see there are other exception situations running where you'll want to improve the logic, and it becomes easier to improve the logic when you're writing to a separate field with workflows so you don't just need one monster workflow to supply all use cases. E.g.: Workflow triggered upon SFDC lead creation looking up against existing customer email domains and marking the new lead as 'Customer' Workflow triggered upon an SFDC lead/contact being unmarked as a customer, and then unmarking all matching email domains to no longer be 'Customer' Workflow triggered upon an SFDC lead/contact being marked as a customer (new customer), then marking all matching email domains as 'Customer' I think maintaining the customer list of email addresses in Marketo becomes really unmanageable very quickly. You have to add a daily task for two individuals (one Marketo person, one customer list-holding person) to update it; it isn't real-time, just updated once a day; it's easy to overlook when someone goes on vacation or is sick or has too much work. Doing it in Marketo with a "customer" email address smart list isn't scalable or robust. Cheers, Edward Unthank | Founder, Etumos ... View more

Do all of your landing pages have GA code on them? I see that happen all the time—some templates have GA code, but not all of them. Some get missed, like the out-of-the-box template for landing pages, i.e., the unsubscribe page. Especially prevalent with enterprise companies, you get lots of rogue templates that were created by vendors a long time ago, and the final step of using the template forgot to include your GA tracking code. Then marketing managers clone old templates and landing pages that never had GA code, and the problem continues onward. Google Analytics and Marketo will basically never show the exact same traffic numbers for a large amount of reasons, but a 1/3 difference is worth looking into. Edward ... View more

Looks like you have a paragraph tag wrapping around the image, would be my guess. If that's in the rich text editor, change it to a div tag (from <p> to <div>), and see if that changes your situation at all. Edward ... View more

I've done what Justin has suggested before, and that works, especially when you have the campaign scheduled to run on the 1st of every month—then you're controlling the date filters, so you're not hitting dates that are in the middle of the months. That way you have the smart campaign scheduled to run every month, and you just have the same "in future after 5 months" AND "in future 6 months" filter on the date you're working off of. We have run into a problem before where you can't have wait steps in those scheduled campaigns, but you can be clever with using batch smart campaigns that lead to "request campaign" and convert the flow into trigger-based with wait steps. Edward ... View more

Alex is right! Rich text tokens are wrapping the values in paragraph tags, which is creating the line breaks. If you use text tokens instead, it won't automatically wrap your tokens in <p></p>, so it'll be on the same line. ... View more

Your operations you can use in that case are the same as you would see on a trigger or filter regarding a field: Data value is changed, and new value: Or, as a filter, that specific field: So there are some options as long as you concatenate those fields with prefixed unique identifiers. The problem is you won't be able to do ranges effectively, but instead you'll have to watch for all options via the green plus sign there. Your values now: 000125 000024 000009 000000 000000 000000 An example of what those values could be: OTP000125 TDP000024 NDP000009 X000000 Y000000 Z000000 If the above were the values, with each one being prefixed with a unique identifier ("OTP" = "On Time Payment", "TDP" = "Thirty-Day Payment", "NDP" = "Ninety-Day Payment"), you could have a smart list targeting all values of five or more by explicitly calling out each value (can't do ranges when you don't have a number field). Smart List "Late Payers (90+ day payments of $5 or more)" "Payment Field" CONTAINS: NDP000005 NDP000006 NDP000007 NDP000008 NDP000009 NDP000010 (etc.) And you could reference membership of that smart list in your email campaigns (so you're not replicating that logic more than once). What you're getting into sounds like a good use of custom objects, which might be worth getting into. Best, Edward Unthank | Founder, Etumos ... View more

EDIT: Woops, looks like I misunderstood your question. The below is more of an answer for displaying "your top 5 upcoming webinars" on a confirmation page. You could sure (technically) do it via a lead field that concatenates the values together, then display the token onto the confirmation page. ---- Approach One, which doesn't work for very long. Smart Campaign: Trigger: Fills out registration form for webinar (this specific one) Flow: Change data value of "Z - Webinar Registrations" with two choices: IF "Z - Webinar Registrations" is empty, then new value is: <div class="webinar-item"><span class="webinar-name">{{my.Webinar Name}}: </span><span class="webinar-date">{{my.Webinar Date}}</span></div> IF "Z - Webinar Registrations" is not empty, then new value is: {{lead.Z - Webinar Registrations}}<br><div class="webinar-item"><span class="webinar-name">{{my.Webinar Name}}: </span><span class="webinar-date">{{my.Webinar Date}}</span></div> Then on the page, you could just throw out some CSS onto the page to format that however you want. Just define the program tokens for Webinar Date and Webinar Name on each program and make sure this a smart campaign that's turned on. The annoyance is going to be that it'll grow infinitely and be impossible to prune based on dates. But something like this might directionally work. I think a safer route would be to combine this field concatenation on the Marketo back-end to output the names and dates of webinars that the lead is registered for, output it into a custom JavaScript snippet on the confirmation page, and use some logic and formatting through JavaScript to show those registrations on the page. ---- Approach Two, giving adequate information to be used in JavaScript on the page. You could use Marketo smart campaigns to create a JSON object to be used in JavaScript on the page itself, which would look like a smart campaign like below. Smart Campaign: Trigger: Fills out registration form for webinar (this specific one) Flow: Change data value of "Z - Webinar Registrations" with two choices: IF "Z - Webinar Registrations" is empty, then new value is: {"webinar-name": "{{my.Webinar Name}}","webinar-date": "{{my.Webinar Date}}"} IF "Z - Webinar Registrations" is not empty, then new value is: {{lead.Z - Webinar Registrations}},{"webinar-name": "{{my.Webinar Name}}","webinar-date": "{{my.Webinar Date}}"} Then output that into JavaScript, with something like this: <script> var webinars = 'webinars: [{{lead.Z - Webinar Registrations}}]'; //Do other logic with that new JSON object, like make sure that you're taking the top 5 webinars that occur in the future and display them in a table via a loop </script> Note: I just hand-typed out all that code, so I'm reasonably confident that I screwed up somewhere by missing commas or otherwise. Sanford Whiteman​ Cheers, Edward Unthank | Founder, Etumos ... View more

Hey Dexter, is it when newly editing queue assignment, or is affecting all previously-functioning smart campaigns that haven't been edited? I.e., is the problem with the Marketo UI submitting to the back-end, or is it a problem with back-end processing? I just checked in our instance and this isn't a problem affecting us, so it's probably pod-specific. Interested to see if any other users on app-sjqe.marketo.com have errors. If it's a front-end problem, I might have a (complex and technical) solution for you that I can walk you through off-line. Edward ... View more

Interesting! Must be a new improvement in Marketo, change of phrasing. It's the same thing, but "person" seems less misleading than "lead." ... View more

The "Delete Lead" flow step in the smart campaign Justin describes will do the actual work of deleting the leads, after you've exported the leads. Edward ... View more

Exactly right. Because the Pre-Promotion smart campaigns are run first (before smart campaigns run upon promotion), the additional filters will keep any action from happening on the desired smart campaigns. ... View more

Also, I always export those leads first with all of their fields and save them on a work computer somewhere. No reason in having all that data go away irreparably. Export all lead data first, then do what Justin recommends. Edward ... View more

You can do this without a special feature request, if you're clever with order of operations. Lifecycle Processing, which starts out with a "lead is created" trigger and then runs through smart campaigns that are linked, can go through and change lead values. These happen upon the "lead is created" trigger, going through data management, lead assignment, and a medley of other operational processing. The first step of Lifecycle Processing is to change "Lifecycle Status" from "[null]" to the appropriate Lifecycle Status value. In the new world of no anonymous leads, all smart campaigns that will be triggered before a lead has been promoted (Marketo's lingo for going from Anonymous to Known) won't have run through these smart campaigns in Lifecycle Processing yet. Let's take a look at the order of operations in the Activity Log of when a lead is created: Using the above, we can add a filter to all smart campaigns that we want to keep from going through said smart campaign, explicitly. Which filters to add to triggered smart campaigns EXPLICIT EXCLUSION OF 'ANONYMOUS' LEADS: This filter would equal "Don't apply this smart campaign retrospectively to leads upon their promotion to known:" EXPLICIT EXCLUSION OF 'KNOWN' LEADS: This filter would equal "Only apply this smart campaign retrospectively to leads upon their promotion to known, but exclude any leads who are already known:" Don't have Lifecycle Processing and aren't ready for that project yet? Create a new Marketo-only boolean field called "Is Promoted" and change the data value to "true" with a smart campaign triggered by "Lead is created." By default, the field will be unchecked (false) for new leads. Only your smart campaign, upon triggering, will check that box (become true). Use that as a filter in the smart campaigns you explicitly want to exclude from "upon promotion" smart campaigns. Then your filter in your smart campaigns becomes "Is Promoted" with values of true or false, and you get (operationally) the same functionality (although inverse) of "Is Anonymous" was providing. Best, Edward Unthank | Founder, Etumos ... View more

Hey Rashida, I have a feeling that Brite Verify is the closest to what you're looking for. Depending on what you're wanting to do with "validation," you can accomplish some things by an operational program with smart campaigns that can clean data. I've heard some people coin this a "data washing machine." That could do things like: do basic filtering and marketing suspending of leads based on the rules you come up with (e.g., blacklisting competitors or marketing suspending people who have email addresses or sites that you frequently determine as fake). You could upload leads into this Here are some other data management smart campaigns I've seen people do well: Standardize country from "US" and "USA" (etc.) to "United States" Standardize Job Role from job titles, e.g., if someone comes in with a job title of "c.e.o.", the smart campaign can watch for this and assign a job role of "Executive" Marketing suspend leads who have phone numbers with inappropriate amounts of digits Verify that an email address is both valid and email-able, contains "@", and isn't a generic email address Marketing suspend leads who have invalid names (e.g., Micky Mouse and Bill Gates) For pre-Marketo upload email verification via CSVs, I think Brite Verify is your best option. They'll spit you back if an email address is valid and email-able or not. For Marketo email verification through webhooks (i.e., checking to see if email addresses are valid and email-able after they've been imported into Marketo but before being emailed), StrikeIron and Etumos Verify are options. Cheers, Edward Unthank | Founder, Etumos ... View more

Agreed. I suspect that a long time ago Marketo baked in the actual field names into the code of smart lists and flow steps, instead of the field unique IDs, and that's an enormous amount of reprogramming to change all of those references in all client instances to be the unique IDs of the fields instead of the actual field names. They've learned since then, though, hence the ability to rename landing pages and emails—in those cases, we're looking at the secondary description, not the actual unique ID for the assets. Edward ... View more