Skip to main content

Summary

Contacts, segments, and tags are related, but they do different jobs in TruAgents.
  • Contacts are the individual records your team communicates with.
  • Segments are reusable audience groupings used for targeting and organization.
  • Tags are reusable labels that help classify contacts or communications.
This distinction matters because teams often blur these together and then struggle to understand why campaigns, filtering, and reporting behave differently than expected.

Who this is for

  • Anyone learning the TruAgents audience model
  • Campaign managers
  • Operators maintaining contact quality and audience organization

Where to find it in the app

  • Contacts
  • Contacts → Segments
  • Settings → Tags
  • related campaign and communications flows

The three layers of audience organization

Contacts

Contacts are the base records. They carry the individual-level data that determines whether outreach can happen and how personalized it can be. That means contact quality still matters even when segmentation and tagging look organized. If contact data is incomplete, stale, or inconsistent, campaigns and communications review will usually become harder to trust.

Segments

Segments are groups of contacts. They help teams target and reason about subsets of the audience without manually rebuilding the same selection logic each time. In the current product flow, segments are connected to more than just list organization. They influence campaign targeting and can later be traced through campaign history and operational review.

Tags

Tags are lighter-weight labels. They do not replace segments. Instead, they help teams apply shared classification to contacts or communications. That last part matters: tags are not only for contacts. In the app model, they can also be applied to communications, which makes them useful for operational labeling as well as record classification.

Practical rule of thumb

  • Use a contact when you are thinking about one person or record.
  • Use a segment when you are thinking about a group for targeting.
  • Use a tag when you are trying to classify or label for shared operational meaning.

How they work together

If your team is trying to…Best fit
store or clean one person’s dataContact
define who a campaign should targetSegment
apply a reusable label like “VIP” or “Needs follow-up”Tag
classify a communication for later reviewTag
explain why a campaign reached a specific audienceSegment plus underlying contacts

Segment stability matters

The app already hints that segments can depend on linked data-source behavior. That means a segment may look healthy today but drift later if the upstream source changes. Simple version: if a segment depends on moving external data, do not treat it like a permanently stable manual list.

Good audience hygiene

  • contacts contain enough usable data for targeting and personalization
  • segments are named clearly enough that another teammate understands who is inside
  • tags are used consistently instead of becoming private shorthand
  • campaigns rely on segments for targeting instead of memory or guesswork
  • communications labels support operations without pretending to be audience logic

Common misunderstandings to avoid

  • Tags are not the same thing as targeting logic.
  • A segment being present does not automatically mean it is ready or healthy.
  • Clean contact data is still required even when segmentation or tagging looks correct.
  • A tag-heavy workflow does not remove the need for a well-defined segment.
  • A segment tells you who should be targeted, not whether the underlying contact data is trustworthy.

Operational examples

Example: campaign targeting

If you want to launch a campaign to a specific audience, build or review the segment first. Do not try to approximate targeting with a loose set of tags.

Example: communications review

If a communications team wants to mark certain messages or threads for follow-up, a tag may be the right tool because the goal is classification, not audience targeting.

Example: data cleanup

If campaign performance looks strange, go back to the contacts and segment inputs before assuming the campaign logic is wrong.