I am slightly confused by Trailblazers Help's definition for Attribute Groups. What I do not understand is what is the equivalent of an attribute group in a typical database management system.
Attribute groups collect several data extensions into a single entity for use in organizing and interacting with contact information.
Do they correspond to Views? Or datasets resulted from joining two or more tables?
So, I am reaching out for help here to have a suggestion for my attribute groups setup before it is too late on the Marketing Cloud instance I am responsible for.
Our data model is quite simple.
In the diagram above,
Idwill be mapped to
ContactId. In other words, Passenger has a one-to-one relationship with the contact.
- Each Passenger can take part in zero or more number of flights. In other words, Passenger has a one-to-many relationship with Flight ("many" being on the flight side).
- Each Booking can contain one or more flights. In other words, Booking has a one-to-many relationship with Flight ("many" being on the flight side).
So the questions are:
- How many Attribute Groups would you create for the above scenario? My guess is 3: One from Passenger to Contacts and the two for linking the data extensions between Passenger-Flight and Booking-Flight.
- Do we need a population of this all to work out?
Thanks for your time in advance!