the contexture sdk
jQuery for data layers.
A calculated, first-party context layer that makes the tools you already run smarter. Most of your traffic never logs in, so your CDP never sees it. Contexture builds persistent, anonymous, first-party profiles on exactly that traffic, then calculates behavioral context you can use in any tool. Built for the practitioner who owns the dataLayer and the tag manager, reads JavaScript fluently, and has felt the ceiling of a profile script. 6 KB, zero dependencies, and every line is free to read.
CX.io("behavior", "visitorType") //==> "Returning"
02 · see your context
This page is already reading you.
That bar at the very top is Contexture, live.It starts on a clearly labeled sample and tracks nothing. Tap show my real context and it switches to your own first-party profile, consent-gated, and updates as you move through the site. Expand it to query yourself with CX.io().
03 · the borrowed-context problem
Inconsistency. Redundancy. Captivity.
Every tool draws a different line
Every tool calculates "engaged visitor" differently. Target, GA4, and your CDP each draw a different line, so the same person is three different people.
The same math, rebuilt forever
The same affinity and recency math gets rebuilt in every platform, by hand, every engagement. You pay to compute the same context again and again.
Your data, rented back
The context lives inside the vendor that made it. Switch tools and it stays behind. You rent your own behavioral data back from the platform.
Contexture calculates context once, in first-party storage you own, and syndicates it to every tool. One definition, computed on your side, portable everywhere.
It makes the tools you already have smarter
Feed first-party affinities and scores into audiences Target could never compute on anonymous traffic.
Target experiments on persistent behavioral context, not just this-session signals.
Send a consistent, owned engagement definition as a custom dimension, the same one everywhere.
Expose calculated context to every tag without rebuilding the math in each one.
Contexture sits beneath the data and personalization categories. It does not compete with these tools. It enriches them, and the context travels with you when you switch.
Five layers, one instrument
embedded · abstracted · persistent · calculated · integrated
profile
- whotraits
- whatbehaviors
- howaffinities
segment
- whymotives
- wheremilestones
- whenthresholds
collect at the base · calculate in the middle · syndicate from the top
One library, one book, one toolkit.
The Contexture SDK is three parts: the library you install, the field manual that teaches it, and the toolkit that debugs it.
The 6 KB, source-available SDK. Install it, query context with io(), syndicate it anywhere.
Read the source →The field manual: the whole method, the recipes, the privacy model, and the full API reference. Free to read on-site; licensed to deploy.
Read the whole book, free →Inspect and debug the context layer in the browser, on any site, then syndicate with confidence.
Open the toolkit →Built over twenty years at Adobe, Symantec, and Ensighten, by the person who kept inventing this layer until it was small enough to give away. Read the story →
07 · start here
Read all of it. Then license it to ship.
The library, the docs, and the whole book are free to read. No gate, no card, no email. You buy the license to deploy Contexture in commercial work.