Will this placement be seen and acted on?
Predicted viewability and interaction likelihood from placement type, session stage, format mix and historical outcomes for that app and position.
Home/Data platform
Most data platforms were designed to follow a person across the web. Ours was designed to understand an impression inside an app: where it is, what surrounds it, how likely it is to be seen and acted on. The output rides with the deal, not with an identifier.
01Architecture
Every bid request that reaches Inception passes through the same pipeline before a deal is offered. Nothing is applied after the fact.
Bid-stream attributes, consented first-party context, content classification
Normalize, classify against standard taxonomies, join publisher metadata
Engagement, completion and quality scores per placement
Seller-defined audiences and contextual cohorts
Deal IDs and supply-side targeting on the request
02Ingest
We collect what the supply side legitimately knows about an impression, and nothing that requires following a person from one app to another.
Publishers we represent can share consented first-party context: content category, session stage, in-app events they choose to expose. Everything else comes from the request itself and from our own classification of the app and placement.
03Model
The models are trained on outcomes from inventory we sell, so they describe what actually happens in these apps rather than a general assumption about mobile.
Predicted viewability and interaction likelihood from placement type, session stage, format mix and historical outcomes for that app and position.
Completion probability for opt-in and interstitial video, used to gate which placements qualify for outcome deals.
Invalid-traffic and authorization status, device and connection anomalies, placement consistency. Low-quality requests are dropped before any buyer sees them.
04Segment
We package context and predictions into seller-defined audiences: cohorts described in standard taxonomies that any DSP can read, without a device identifier.
Because the segments are built from what the supply side knows, they remain available when identifiers are absent. An agency can plan against a cohort today and still be buying the same cohort next year.
05Activate
The primary path. Signals and constraints are applied when the deal is assembled, so the buyer activates a pre-qualified package in its DSP.
For buyers who want signals on the open request as well. Cohorts and scores are attached to the bid request in standard fields for the DSP to act on.
06Measure
Deals report at the level agencies need: app, placement, format, cohort and outcome. For app-install and re-engagement campaigns, delivery is attributable through the mobile measurement partners buyers already run.
07Privacy
The platform's value does not depend on identifiers, which is why it did not lose value when they went away.
Cohorts are computed per request from context and consented publisher data. We do not build or sell user-level profiles.
TCF 2.2 and GPP strings, ATT status and regional requirements are read on every request and respected in what we process.
We do not derive identifiers from device characteristics, and we do not accept them from partners.
We keep what the models need, for as long as they need it, and nothing that would let a person be re-identified.
Send a vertical and a KPI, and we'll show which cohorts and scores apply.