Your file, decided before the program runs.
A customer file is usually treated as one list: everyone gets the same program. Intelligent Audience resolves the records you already hold against the portfolio customer graph and returns a state for every one, so the email, the mail drop, the ad audience, and the call list that follow start from value, not from recency.
- SignalA customer file: the records and identity signals you already hold.
- IdentityEach record is resolved, across brands and channels.
- GraphRecords are matched against the portfolio customer graph.
- DecisionEvery record gets a state and the program path that fits it.
- ActivationSegments by state are delivered to the channel that runs them.
- AttributionWhat each segment did is written back, and the next file scores better.
What each state does in the file.
- HHighFirst in every program. The best offer.
- MMediumStandard programs with a reason to decide now.
- LLowEntry offer, lowest cost channel.
- NNon-buyerSuppressed from paid programs.
- RRiskVerified before any value is extended.
- UUnidentifiedHeld until a signal arrives.
The flagship model. The IH Score is the standard model in the model library. Other models, and custom models built on a brand's own outcomes, decide alongside it.
What it takes to run it.
- MomentA customer file, before the program that uses it.
- SignalThe records and identity signals you already hold.
- ActivationSegments by state, delivered to email, mail, ad, or call.
- IntegrationSource records, identity signals, permitted uses, outputs, and delivery are agreed first; the file moves second.
- RecordHistorical outcomes feed the loop as Session Disposition events when they fit the event contract. A list on its own is not an outcome.
- Access modesAssisted, Programmatic, or Partner. Access modes
Build it.
Everything an engineering team needs to run Intelligent Audience is in the developer center, documented and self serve.
Intelligent Audience integration
What to agree before a file moves: records, signals, permitted uses, outputs, delivery.
User Action API
Score one record or a file; the same call behind every product.
Action types
The published actions a scored file can feed.
API · SDKs · References · API keys
Who runs it.
Lifecycle and CRM
Segments
Six segments by value, ready for the programs you already run.
Finance
Where value sits
How much of the file carries value, and how much is cost.
Data
One graph
The file resolved once, reused by every channel.
See your customer file as six states.
Bring a file you were about to mail, email, or upload. We return it with a state on every record and show where the value sits.
Prefer to talk now? 800-610-4460