Build the audience before anything activates.
One graph. The same identity blocks, pulled from the partner network, composed into a set you can actually send to. Firmographics, behavior, and exclusions in one audience — not three lists reconciled later.
Every node is the same record. The audience is which nodes you keep.
Learn moreThe set is ours. The send is yours.
Most “audiences” are a filter on a rented file.
A list
Titles and industries. No idea who is in market, who bounced, or who sales already owns.
A pixel
People who visited. No company, no title, and no way to mail them without a second vendor.
An intent feed
A topic surge on an account. Still not a person you can suppress.
An audience is the join. Without it, every channel is building its own.
How a set gets built.
Four cuts. Sending is not one of them.
01 Ask
Who you sell to. Industry, size, title, geography — or the CRM you already trust. That brief is the only input. It selects from the graph. It does not scrape a rented list.
02 Match
Those filters run against the graph: person, company, and behavior from the partner network. Same blocks, many sources. The diagram is this step.
03 Cut
Bots, undeliverable emails, do-not-contact, customers, and open opportunities come out. An audience that cannot be suppressed is not finished. This is a workflow control, not a legal guarantee.
04 Hand off
The set lands in ads, email, CRM, or the partner product. Building stops here. Sending does not start here.
Four sets. One graph.
Lookalikes from a truth set
Customers or closed-won accounts in. Neighbors out. Not a platform lookalike trained on a thin pixel.
In-market, inside the ICP
The researching slice, constrained to people who fit. Behavior without a fit is traffic. The signal itself lives on intent targeting.
Intent targetingExclusions that travel
The same suppression in paid, email, and the rep’s queue. One person, removed once.
A set your platform can sell
Embed the builder. Their brand, your graph. The audience shows up as a line item. No public API promise.
Intent targeting finds who is researching. The builder decides who is allowed into the audience. Activation is where that audience goes.
Anyone reconciling three lists that should have been one.
Demand gen
One set for paid and outbound, with the people you already own taken out before the spend.
Agencies
A client audience built from fit, behavior, and exclusions — not a file cleaned by hand before every launch.
Platforms
The builder inside your product, your name on it. Customers compose the set. The graph stays here.
Build it once. Activate it everywhere.
Fit, identity, behavior, and exclusions in one set — then into the tools that already send.
Learn moreFrequently asked questions
What is an audience here?
A composed set: fit, identity, behavior, and exclusions. Not a filter on a rented file.
How is this different from intent targeting?
Intent is a signal — who is researching. An audience is the set you are allowed to activate. Behavior without a fit, or a fit you cannot suppress, is not finished.
What does the diagram mean?
Each node is the same kind of record, from the partner network. The audience is which of those records you keep.
Do you send it?
No. We build the set and hand it off. Your platform, your rep, or your tool sends.
Where does it go?
Meta, LinkedIn, your DSP, your email platform, and your CRM.
Can exclusions move with the audience?
Yes. The point of one set is that suppression is applied once, then travels to paid, email, and the rep queue.
Can we embed this?
Yes, as a partner integration under your brand. Not a self-serve public API.
Can you guarantee compliance?
No. Do-not-contact and verification are workflow controls. They are not a legal opinion.