Building and sharing audiences
Cohorts under segments: how audiences are built, shared, and made activation-ready.
Audiences are organized simply: two segments, B2B and D2C, and under each, cohorts, named groups defined by shared traits, scores, or behavior. A cohort is the working unit: what you watch, share, and activate.
Ways to build
Ask iHarness. The fastest path: "accounts that visited pricing in the last 30 days and score Hot." The cohort arrives with its logic attached and stays live as members qualify in and out.
Hot lists. Auto-maintained cohorts the system keeps for you, your hottest accounts, your resolved recent visitors, so the obvious lists never need building.
Import. Bring a list from CSV, Sheets, or your CRM. Imported records join identity resolution like everything else, so duplicates collapse instead of multiplying.
From the loop. Plays produce cohorts too: everyone a play touched, everyone who converted, everyone suppressed.
Sharing
Cohorts are workspace objects: your team sees the same audiences, with the same membership and scores, governed by roles. One shared definition beats five private spreadsheets that almost agree.
Activation-ready means something
A cohort can be activated when its members carry what the destination needs: the right identifier (email for outbound; hashed identifiers for ad platforms) and the right consent. The platform checks this per destination and reports matched counts honestly, what the channel accepted, not what you uploaded. Suppressed records are excluded before anything leaves.
What you get back
A built cohort returns four things:
a live membership, resolved through identity so one person is one record,
a FIRE score on every member, with the reason attached,
an activation-readiness read per destination: matched counts, missing identifiers, consent gaps,
and a shared workspace object your whole team sees identically.
Audiences do not sit still after building; the system keeps watching them. See Always-on monitoring.
Last updated