The place to specify where you want to use a segment is the Activation Target. This setting designates the destination or channel where the segment will be applied, such as a specific activation campaign, platform, or workflow. The segment itself defines who is included, but Activation Target is about where that segment is deployed. Calculated Insights is about deriving metrics from data, not about where to apply the segment. A Segment is the audience group you’ve defined, not the deployment destination. Activation refers to the overall process of sending or applying the segment, but it doesn’t specify the exact destination. So you choose Activation Target to tell the system exactly where the segment should be activated.

In data modeling, a one-to-many relationship means one parent record can be linked to many child records, with each child tied to that single parent. Contact Point Phone fits this pattern because one Individual can have multiple phone numbers, each represented as a separate Contact Point Phone record that references that Individual. This clearly shows a single parent to many children. The other options don’t illustrate the multiplicity as directly: a Purchase Order is typically tied to a customer or account rather than the person directly, and the remaining options don’t represent the “many” side of a single parent relationship in this context.

Saving an Insight from the Visual Insights Builder does not lock it from further edits. The saved Insight remains editable, so you can reopen it in the Visual Builder and adjust its metrics, filters, visualization type, or layout, then save the updated version. This supports iterative improvement and reuse of insights. The only times you wouldn’t be able to edit are if you lack permission to modify that particular Insight or if it’s explicitly locked by an admin, but these are access controls rather than a limitation of saving itself.

Matching records across systems relies on a stable, universal identifier that maps to the same real-world party. A party ID serves as that universal reference, acting as a single key that uniquely identifies a person or organization across different data sources. Using an exact party ID to unify records ensures that all data belonging to the same party is connected, even if other attributes change or vary across sources. Emails can change, be mistyped, or be shared by multiple people, making them unreliable as a sole identifier. Loyalty IDs tie records to a specific program and may not exist in all systems or for all parties. Org IDs focus on organizations and overlook individual-level records. Because the party ID remains a constant, cross-source linkage is robust and comprehensive, which is why it’s the best match rule for unifying records.