Skip to content

What is Qinto?

Qinto is the engine that powers the Blotout platform. It runs on a hostname you own, collects what visitors do on your site, resolves which person each event belongs to, and runs the apps you install on it. An app can forward an event to a tool you already use, but it can also transform the event, keep its own data, expose an endpoint, run on a schedule, show its own UI or hand an agent a tool. The app store has apps for the tools most businesses run, and when the app you need does not exist, you build it on the same platform. The name shows up wherever you work with the engine directly: the API reference, the CLI and the app SDK.

We created EdgeTag in 2019, a server-side tag built for the marketing stack. It gave a store one first-party endpoint on its own domain and fed the ad platforms and the email tools from there. Five years of running it for e-commerce brands taught us how the industry works and where the gaps are: every tool keeps its own copy of the customer, every integration is a one-off, and the whole stack assumes a person reads a dashboard and acts by hand.

AI is changing tools faster than anything since the web, and we built Qinto for that era with one vision: you install prebuilt apps from the app store, for marketing and more, or build your own apps and workflows, and Qinto gives them the context. The context is who the visitor is, what they did and what they consented to. A tool you buy keeps it inside itself; an app on Qinto reads it from the ID graph and sends the result wherever it has to go. Qinto is AI first and agent agnostic: whichever agent you use works with the same API and tools a person uses in the Blotout platform, so it can set up a site, install an app or write the one you need. It started in marketing and e-commerce. Today it serves every business that needs to know who a visitor is and wants to build its stack on that knowledge.

Qinto comes from quinto, the Spanish and Italian word for “fifth”. A business runs a stack of four kinds of tool, and each one holds a part of the customer. Qinto is the fifth: the one that sits between the four and connects them.

Qinto in the middle of the stack, connected to the storefront, the ad platforms, CRM and messaging, and analytics and the warehouse1The storefront or siteShopify, WooCommerce, a CMSWhere the visitor lands2The ad platformsMeta, Google, TikTokWhere the money goes out3CRM and messagingLoop, HubSpot and SMSWhere the relationship lives4Analytics and the warehouseEdgeLake, GA, BigQuery, SnowflakeWhere the numbers are read5Qintoone profile per personvisitor eventsconversionsprofilesevents
Events enter from the storefront. Qinto resolves the person behind each one and forwards it to the ad platforms, the CRM and the warehouse, with the same identity in each.
  1. The storefront or site. Shopify, WooCommerce, a CMS. Where the visitor lands, and where every event starts.
  2. The ad platforms. Meta, Google, TikTok. Where the money goes out, and where a conversion has to arrive with the right person attached for the spend to be judged.
  3. CRM and messaging. Blotout Loop, HubSpot, email and SMS. Where the relationship lives, and where a profile needs the traits and the consent the visitor gave on the site.
  4. Analytics and the warehouse. EdgeLake, GA, BigQuery, Snowflake. Where the numbers are read, and where every event has to land with the same identity the other tools use.

Without a fifth element, each pair of tools is its own integration: a pixel per ad platform, a plugin per CRM, an export per warehouse. Each one runs its own tracking code and keeps its own idea of who the visitor is, so the same purchase reaches the ad platform, the CRM and the warehouse as three different people, or does not reach one of them at all.

Qinto replaces those point-to-point integrations with one place for events, identity and data. The site sends it once. Qinto resolves the person behind it with the ID graph, keeps the traits and consent that person gave, and the apps you install deliver the event, the identity and the data to each destination, the same in each. Adding a tool is a change in the platform, never a change in your tracking code. And the fifth element is not only a connector: anything you want to run on top of your visitors and their events is an app you can build here.