3 of 3 people found this helpful
The link field should be a unique ID of the event table. The title may work, but in case you have in the future 2 events with the same title that would be a problem, so I would rather use a dedicated ID field.
Now, if the only thing you really need is the event title, you do not need the event title object. Just having the event title field in the "Registration" (intermediary) object should be enough. And of course, in such a case, this object would no longer be intermediary, since it would only be linked to the lead object
The model in which you have 2 objects (Event and Registration) is only necessary if:
- you want to be able to change the event name easily, after the registrations have started
- you want to log additional information in Marketo about the event such as date, location, etc... information that obviously needs to be managed independently from registrants and registrations.
Yes! As usual, thank you for your quick and thorough response Greg.
I wonder if you could help me figure out which type of the Custom Object (one to many or many to many) we should use in our situation.
We have a list of Subscribers (parents) and each Subscriber can have either one or multiple Beneficiaries (children). Also, each Beneficiary can belong to multiple Subscribers (for example, one child may be a Beneficiary of Mom, Dad and Grandma).
In addition, each Beneficiary may have multiple Plans. Also each Beneficiary belongs to one of 4 segments.
We need to send out 4 email campaigns (one for each Beneficiary segment) targeted to Subscribers. Each Subscriber should receive an email with the list of his/her Beneficiaries' names and their Plan IDs, and the Beneficiaries listed in the email should be only from a specific Segment (depending on the email).
I understand that I need to use Email Script Tokens for this but my concern is how to create the right relationships between Subscribers, Beneficiaries, Plans and Segments. Could you help figure this out?
Olga, you should open another thread (link back to this one for reference) instead of reusing this one.
It sounds like you're definitely describing a many-to-many setup. But before we continue there, be aware that capital-S Segmentation (as in Marketo's native Segmentation feature) isn't usable for this case, because Segment filters apply to the Subscriber that receives the email, not the linked objects (even if those objects link to leads in the database).
However, an equivalent lowercase-s segmentation may be doable within Velocity base on object properties -- provided there's at least one matching Beneficiary in the linked CO list. We'll discuss more on the new thread.