Dan_Stevens_

I’m not Josh, so take this for what it’s worth. Field A is essentially a “history” field. So all you need is a conditional CDV flow step that says:if Field A not contains {{Field B}}Field A value = {{Field A}}, {{Field B}}elsedo nothing.

You need to define/approve your trigger campaigns first and THEN define your A/B testing. Just be aware of this flaw if you need to make any changes to your trigger campaigns or A/B criteria, which require unapproving the email program: Re: Unable to unapprove email program

Elliott, see Mike's response to my question in this thread: Any update on when customers will be migrated to Munchkin v2? We still have not been migrated to Munchkin v2

Hey Adam— this idea already exists here and here: This was supposed to finally be addressed in Sky, but still isn’t within the beta environment.

Hi Colin - check out my reply over in this thread (and download my Summit presentation from last year): Re: Custom Report - All Interesting Moments

What’s the benefit of including a PURL in an email when the link is already trackable (and you can mask the url with whatever text you want). PURLs are mainly useful for direct mail campaigns to provide a simple URL to enter.

If duplicate leads are an issue, be aware of how Marketo determines which lead is active

Hmm, did you enable the limits within the qualification rules? Are you sure your test group received production emails (and not just tests/samples)?

That's not true. Communication limits apply to default programs as well, if a smart campaign is included that sends an email:What I would do Megan is setup a separate smart campaign to send the same email to your seed list - but for this campaign, disable the blocking of the email, regardless of co...

There was an active discussion last February regarding Courtney Grimes’s blog post: Re: [Shared Blog]: I Want to Believe, But: Your Email Link Clicks Aren’t Real