Carrie_Chandle1

Hi Adrian Cardelle‌ - when you say that the email is approved and finished, you mean that it got sent out, right?If it's just two more people, I'd create a smart campaign and send the email that way. Then, you could always pull an email performance report on the email asset (instead of using the ema...

So, you could get at 3 of your 4 asks using smart lists...Contacts - Use the "was sent email" or "was delivered email" (based on what the campaign owner wants to see), and this will get you the # of peopleIT Contacts - Add a filter to smart list #1 for your IT contacts and this will get you the # of...

Glad to hear! When you get a chance, go ahead and mark your question as answered - it helps people keep up with what's still open

I prefer to batch leads into their current revenue stage. If you don't, your qualification rules will push these leads along more quickly through stages, or skip stages, which won't be representative of how a lead typically flows through the RCM. Check out the comments on this post, too: https://nat...

Make sure each program that you're pulling in has a smart campaign with a Smart List that references the person being a member of the engagement program (and any other criteria you want, such as not having downloaded that piece of content).Your Flow step is then to send the email. You won't schedule...

I've had many of those myself Glad you got it working!

Hey Robyn Hatfield‌ - just double-checking, is the engagement program set to "on" in the settings, too?https://docs.marketo.com/display/public/DOCS/Turn+an+Engagement+Program+On+and+Off

There's a good thread here about nested programs: nation.marketo.com/thread/46624-nurture-ahem-engagement-programs-best-practicesWe use nested programs to control not sending the piece of content if that person has already downloaded it. For cadence, your assumption is correct... after a person is a...

I read Amy's inquiry as what to do after a lead has been created and exists in both systems, but they no longer want the lead in Marketo. At this point, the flag (which was originally set in SFDC) needs to be set to false.

We've taken on the flagging of our custom sync rule to FALSE on the Marketo side, otherwise you won't know. So, we agreed with our SFDC admin team that if a lead/contact met certain criteria, we would mark the custom sync rule as FALSE in Marketo, and shortly after we delete the record in Marketo (a...