Email Address Vs. Marketo ID? which does marketo use to "Each lead can run through the flow once"

Anonymous
Not applicable
Hi Everyone,

So I was wondering if anyone knew what Marketo uses to consider someone unique for... "Each lead can run through the flow once" in a campaign? We connected our API but instead of immediately overwritting all our users we created a duplicate user...(our developers did not quite trust the marketo API.) Anyway I have 1 automated campaign that allows users to run through it once (sends 6 emails). I was under the impression that would be based on the email, using that as the "unique identifier". Seems, judging by the reports on the campaign, that is is actually the marketo id which determines if the user went through once. Anyone know if that is correct?

My main issue is that the campaign is triggered on the create date in marketo...now all "new users" have same created date of 3/6. which has restarted them in the 30 drip/free trial campaign, even though many are done with their older ID.

I am trying to get a hold of someone at marketo about there Merge Tool now, but enable to keep everyone on the correct sechedule I can't wait another day or so for them to get back. Looking at only about 2400 names to merge, just need to make sure they have correct (older marketo id) and the correct created date (older as well) so they do not get put into this campaign...as always any advice/ help greatly appreciated.

CB
Tags (1)
4 REPLIES 4
Anonymous
Not applicable
never mind. thanks anyway
Josh_Hill13
Level 10 - Champion Alumni
Joanna has that right. It's possible for duplicates to not qualify for the same campaign if their attributes (other than email) are different.

Email is only used to dedupe, otherwise the ID is the database key.
Anonymous
Not applicable
I believe it would be based on the Marketo ID in this case.  if for whatever reason you have duplicate email addresses in the system and each hass its own record with its own Marketo ID, then that would be treated as two leads.
Anonymous
Not applicable

Good to know, thanks!