Your stack. Our loop.
One headless campaign definition, rendered wherever your customers are — and every consented data point delivered wherever your systems live. Integration is a first-class pillar of Trueloops, not an afterthought.
Four ways to put a campaign in front of people.
Hosted microsite + QR
Every published campaign gets a hosted page and a QR code — ready for packaging, point-of-sale displays and print. Live the moment you hit publish.
Web component
One async script and one tag. The experience renders in an isolated shadow root — your CSS can't break it, it can't break your page, and your Core Web Vitals stay green.
<script src="https://cdn.trueloops.ai/embed.js" async></script> <trueloop-experience campaign-id="…"></trueloop-experience>
Drupal module
A native module for Drupal 10.3+ and Drupal 11: editors place a campaign as a block or as an Experience Builder component, pick it from a live dropdown, done. Ships with a Drupal CMS recipe for one-click setup. More CMS plugins follow on the roadmap.
Your design tokens
Campaigns theme themselves from your workspace's brand kit — colors, type, radius — so the experience looks like your brand on every surface, without designers redoing every campaign.
An API for your systems. MCP for your AI.
REST API + workspace keys
Everything Studio can read, your systems can read: campaigns, results, review queues. Machine callers authenticate with revocable workspace-scoped API keys (tl_live_…) that are read-only by design — publishing and payouts stay human decisions.
MCP for AI agents
Trueloops speaks the Model Context Protocol. Your AI assistants and agents drive the same governed capability layer as the UI — list campaigns, read analytics, draft new campaigns — with risk-tiered permissions and an audit receipt for every call. Built AI-native, not retrofitted.
Your data lands in your systems.
Route — the data spine — delivers consented profiles and verified purchase events where you want them, honoring the consent purposes attached to every datum.
CDP / CRM delivery
Consent-aware delivery of profiles and events to your systems of record, with first-class connectors rolling out with our design partners.
Webhooks & export
Generic webhook delivery plus complete CSV export — every integration path works from day one, whatever your stack.
The fallback store
No CDP yet? Trueloops stores your data — fully visible in Studio and fully exportable, so you can migrate to your own stack whenever you're ready. That's the anti-lock-in promise.
What builders and editors ask.
Do I need developers to run a campaign?
No. Marketers build and publish campaigns in Trueloops Studio without code, and the hosted microsite with a QR code needs zero integration. Embedding into your own site is one copy-paste snippet a web editor can place.
Will the embed slow down or break our website?
The experience renders inside an isolated web component (shadow DOM), so your site's styles and the campaign's styles can never collide, and the bundle loads asynchronously so it doesn't block your page.
What about CMSs other than Drupal?
The universal script embed and web component work in every CMS today — WordPress, Webflow, Shopify, AEM, Sitecore and anything that renders HTML. Native plugins beyond Drupal are on the roadmap, prioritized with our clients.
Can AI agents and assistants use Trueloops?
Yes — Trueloops ships a Model Context Protocol (MCP) endpoint, so AI agents can list campaigns, read results and draft new campaigns using the same governed capability layer as the human interface. Agents authenticate with revocable workspace API keys and can never execute privileged actions like publishing or paying out — those always require an explicit human confirmation.
See it inside your stack.
Bring a page from your website to the demo — we’ll embed a live campaign into a copy of it while you watch.
Book a demo