For certain COs it is possible to add that as the criteria for smart list qualification. Think of something like "Justin" AND "has product X". But, can you give more specifics about the custom objects you're referencing. Are they Marketo COs or CRM COs? Are you guaranteed that only one will have a CO relationship?
Thanks for the reply, Justin Cooperman. This isn't necessarily just focused on Custom Objects but how smart campaigns qualify duplicates.
Use Case: Load a roll-up table of Uber Eats transaction data for a McDonald's location (e.g. Display 10 metrics for how each of the Franchise Owner's locations performed yesterday).
Solution: An email script loads tables in an email showing Uber Eats transaction history at 1 or multiple McDonald's locations. It's a simple #foreach loop.
Smart List Criteria: Has McDonalds Order Summary and Country. This "should" only qualify Contact: email@example.com.
Issue: There is a duplicate firstname.lastname@example.org (Lead) and since it's the first created the record, the batch campaign qualifies it instead (even though the Lead doesn't have a Custom Object relationship).
So what we're seeing is even though the smart list criteria "should" only qualify the Contact, the Lead is processed because it's the first created record. Thus Velocity references the Lead which doesn't have a custom object relationship. From what we've tested, uploading custom object data through the GUI ties it to the last updated record--not the first created record. Thus creating kind of a gap between trying to append custom object data and have it referenced in a smart campaign (only in the scenario of duplicates).
We now have an automated API upsert but besides trying to trick the upsert to append only to the first created record, I'm unaware of any other tricks.
Hi Wyatt - once you get to the bottom of the this, let’s be sure to update this master table of duplicate scenarios found here: If duplicate leads are an issue, be aware of how Marketo determines which lead is active
Thank you for the added detail, I better understand the issue you're seeing. Let me take a look at that and see what's happening there. I think you're correct that, regardless of creation date, the duplicate Lead record should not even be part of the Smart List qualification since it doesn't have the CO relationship you're specifying.
Feel free to shoot me an email so we can discuss further.