Private beta · Limited onboarding. Request access to join
The Platform
Nine inspectable models, CRM and spend ROAS, pause/boost write-back, and delivery proof — on complete first-party signal. AI cites the math; MCP puts the same tools in Cursor and Claude.
Journey inspector
Purchase · $2,490 · Linear paid
sess_8f2a…c91 · lookback 30d
Delivery proof
9
server-side destinations
9
attribution models
5
CMP integrations
0
third-party ad pixels required
The pipeline
Capture, consent, attribution, delivery, and explanation run as one system on one data model. Every credited conversion traces back to the event that produced it and forward to the destination that accepted it.
Stage 01
One script on your own domain collects clicks, sessions, forms, and conversions — with a server Track API for the rest.
What Intently gives you
“Intently gives ad buyers complete first-party capture, nine inspectable attribution models, CRM and spend ROAS, pause/boost write-back on Meta/Google/Microsoft with confirm, delivery proof with match quality, AI that cites the math, and a read-only MCP server, in one pipeline you can audit end to end.”
Nine models
Switch lookback windows and compare first-touch, last-touch, linear paid, U-shaped, and source-specific models on the same underlying journeys.
Model comparison
Same conversions · four lenses
$48.2K
Credited revenue · verified delivery on paid
$41.6K
Credited revenue · verified delivery on paid
$52.1K
Credited revenue · verified delivery on paid
$49.8K
Credited revenue · verified delivery on paid
Revenue attribution
Channel and campaign tables with ROAS when spend is synced, built on complete server-captured signal, Stripe and CRM revenue, and delivery proof.
Marketing attribution
Last-touch · 30 days
Consent
Reads OneTrust, Cookiebot, CookieYes, Consent Mode, and TCF v2, then enforces policy before storage or routing.
Routes to:GA4Segment
Routes to:MetaTikTok
Routes to:Personalization
Delivery proof
After server-side routing, the delivery log records success or failure for each destination that was dispatched, so you can audit what reached Meta, GA4, TikTok, and the rest of your stack.
Destinations
Delivery log
Intelligence
Ask for cited model, window, and ROAS answers — grounded in the same reports you can open yourself.
Ask Intently AI
Reading reports…
“Which campaigns have ROAS under 0.5x on last-touch?”
On-site debug overlay
Most tracking breaks silently. A tag misfires, consent blocks a conversion, an event never fires, and nobody notices until the numbers look wrong weeks later. The overlay sits on your live site so whoever installs and maintains Intently can see capture, consent blocks, payloads, and destination routing in seconds.
Intently
Live capture · yoursite.com
Payload · page_view
{
"event": "page_view",
"page": "/pricing",
"session": "sess_8f2a…c91"
}Architecture
Intently runs as a first-party SDK on your site plus server-side processing, so capture, consent, attribution, delivery, and Ask stay in one pipeline you can audit.
Your visitors
Intently collection layer
Attribution & intelligence
Your destinations
Install
Start with a script tag on any site, or use a stack-specific guide for WordPress, Shopify, and Next.js. Install guides and downloads live in the product after you sign in.
Any website
Script tag
Paste the Intently snippet into your site's <head> — works on static HTML, Webflow, custom stacks, and more.
WordPress
Plugin
Lightweight WordPress plugin — also covers WooCommerce stores on WordPress.
Shopify
Theme snippet
Liquid theme snippet with ecommerce event hooks for Shopify storefronts.
Next.js
App Router guide
Add Intently to Next.js (App Router or Pages Router) with a client component and env-based API key.
Privacy first
Intently was designed for a world where consent is required. Every event is consent-aware before storage or routing, and destination sends are auditable in the delivery log, without loading third-party ad pixels in the browser.
SOC 2 Type II certification is on our security roadmap. Today we host on infrastructure from providers that publish SOC 2 reports (including Vercel and Supabase).
Respects granted/denied signals from your CMP automatically. No code changes needed when consent changes.
A script on your site collects events server-side. No third-party ad pixels, no cross-site tracking graphs, no client-side destination tags required.
Collect exactly what you need. Configure field-level redaction, IP anonymisation, and retention windows per event type.
Get a personalised walkthrough with a member of the team.