Every Bituser Solution is a named set of products from one catalog. Tell us what your data cannot do, and it is assembled from parts that already exist — not bought from another vendor.
One platform. One contract. One graph you own.
Nothing is bundled and nothing is a tier. Everyone gets the same platform, and what differs is which products you subscribe to.
The products come from one catalog, and they compose. That is why a Solution can be assembled rather than built, and why the second one costs less than the first.
A point solution sells you one output, rented. One vendor, one graph, one channel — and every new requirement means another vendor, another tag, another contract, and a second charge for the same person. Bituser sells the capability underneath.
The Type describes the shape of a Solution — what it is made of and how it runs. Two Solutions of the same Type are assembled the same way and read the same way.
Most of the people who reach you never say who they are, and the few who do can usually only be reached one way. A Pipeline collects the event at the edge, resolves the person once, and delivers them to a destination you already own — an email platform, an ad platform, a mail house, your own analysis.
Its Core is two legs: where the person comes from, and where they go.
Adding a destination roughly halves your cost per reachable person, because the resolution is already yours.
Choose the entry point you already have and the destination you already own.
Every Solution, and what each one is made of.
A Solution’s Core products are the ones that make it work. Everything else in the catalog is optional, and any of it can be added.
Add a destination to a Pipeline and the resolution does not run again. It already ran, at the entry leg, and a query that has been answered is not asked twice.
Add an entry point and it feeds the same destinations and the same graph. A Pipeline that starts with website visits can take inbound calls as well.
You cannot pick the wrong one. Any Solution can grow into any other.
We publish the method rather than a match rate. A rate measured on somebody else’s traffic tells you nothing about yours, so what we show is the structure — which product runs, which feature it performs, what each usage costs you and what it does not. We measure the rate on your traffic during onboarding.
Solution contains Products. A Product contains Features. A Feature emits one Usage per disposition. Identifiers publish, exactly as they do on the platform taxonomy.
A No Match emits a usage and generates no charge. Nothing here is billed on an attempt that found nothing.
Add the Ad destination and only the second product changes. The entry leg has already run, and its resolution is reused.
Value is charged on egress and on data. Everything that makes egress possible is included, because charging for the machinery as well as the output is how a utility turns into a tax.
Filter by Type, entry point and destination, and see what each one is made of.
If the Solution you need is not in the catalog, it is usually a new arrangement of parts that are. Ask.
We measure on your actual visits and calls, and show you what a Solution produces before you commit to anything. No rate quoted in advance, because the only one that matters is yours.