Skip to content

How related data works

After reading, you know which related values a result can show and why a result is in an audience.

A result is one record of the audience object, such as a Contact. The results table can show more than that record’s own fields: fields of its parent records, one value from its related records, and the value of an aggregate the audience calculates.

A Contact has one Account, and that Account has one owner. Values along such lookups are unambiguous, so a column can show them directly, up to five relationship levels deep.

A Contact can have many Opportunities. To show one value per result without repeating the Contact, CAB uses a Data Inclusion. It follows a path of the audience, for example from Contact to the node Gift in last 24 months. At each step that leads to many records, it keeps one.

The sort decides which record that is. Sorting by Amount, descending, keeps the largest gift; sorting by Created Date, descending, keeps the newest. The field of the last step is the value in the column.

The related records come from the audience’s own nodes, with their conditions. A Data Inclusion is saved with the audience, so it can be added again later. Which columns you show is stored in your browser for each audience object, not with the audience.

An aggregate condition on the canvas, such as the sum of won Opportunity amounts, also exists as a value. As a column, it shows the aggregate for each result, calculated from the current records each time the results are shown or acted on. See Filter on related record totals.

The Record Match Breakdown of one result shows the records that made it qualify. At the top is the result with the fields its conditions use. Below it are the related and parent records that matched, each with its own condition fields. A node with Without has no records here, because it matched by having none.

  • Data Inclusion. A saved rule that turns related records into one value per result.
  • Audience Data Graph. The paths of an audience, from its object through its related nodes, from which Data Inclusions are built.
  • Record Match Breakdown. The view that explains why one result is in the audience.