Private beta · Limited onboarding. Request access to join
Capabilities
Intently is server-side attribution for ad buyers who cannot afford to lose conversion signal. Nine transparent models, CRM and Stripe revenue, ad spend ROAS, pause or boost on Meta/Google/Microsoft with confirm, delivery proof with match quality, AI that cites the numbers, and a read-only MCP server for Cursor and Claude.
Proof it is installed correctly. Proof each destination accepted the send.
How it stacks
Better tracking
First-party capture + delivery proof
Better attribution
Inspectable models on complete signal
AI that cites both
Cited answers — and pause/boost on Meta, Google, Microsoft
Attribution with proof
Better tracking means better attribution. Intently credits revenue on server-captured signal with nine inspectable models, CRM and spend for ROAS, pause/boost write-back on Meta/Google/Microsoft with confirm, and logs whether each destination accepted the event.
Marketing attribution
Last-touch · 30 days
Better tracking means better attribution. Nine inspectable models, Stripe + CRM closed-won, ad spend ROAS, pause or +20% budget write-back on Meta/Google/Microsoft (confirm required), journey credit, and delivery proof with match quality, on complete server-captured signal.
Debug overlay removes install guesswork: watch events and consent on your live site. Delivery log confirms each destination accepted the send. Two proofs, not a black box.
Collect with a first-party SDK, then route conversions server-side, without loading third-party ad pixels in the browser.
Reads Consent Mode v2 and major CMPs. Consent is enforced server-side before events are stored or routed to destinations.
Automatic form field tracking and section engagement, with no manual event setup required. Optional visitor engagement scoring (scroll / active time) lives under Ask depth and is off by default.
Ask across ad spend, attribution, and first-party behavior in one place: cited answers on model, window, and ROAS, plus form and content questions GA4 never sees. Pause or boost recommendations can apply to Meta, Google, or Microsoft with confirm.
Watch events as they arrive. Filter and search the stream, with optional live updates, and inspect payloads without leaving the product.
Optional visitor attention scores from scroll depth and active time (Ask depth, off by default). Stored on converting sessions when Engagement Tracking is on — inspectable in Experience and Ask, not used for attribution credit.
Forward conversions server-side to GA4, Meta CAPI, TikTok, LinkedIn, Pinterest, X, Reddit, and Segment, with optional webhooks for custom pipelines.
Track API and product APIs for your stack. A read-only MCP server exposes attribution and Ask tools to Cursor, Claude Code, and Claude Desktop with your account API key. Forward events to a customer webhook, or pull reports from Attribution endpoints.
Dashboard, Attribution, campaigns, and conversion views with the filters you need. Export attribution reports to CSV.
On-site actions
Experience is the investigation layer on the same first-party capture: prioritized tests to try, readiness for the signal you need, optional visitor engagement scores when Ask-depth Engagement Tracking is on, converter vs non-converter cohort gaps, and Ask on that evidence. Associations to try, not guaranteed lifts.
Experience
On-site investigation for attributed traffic
Tests to try, not guaranteed lifts · Meta paid · last 30d
What to try next
2 rankedReduce abandon on “Company size”
highIn Meta paid traffic, non-converters abandon this field more often than converters — a form friction association to test, not proof of cause.
Non-converter abandon 50%·Converter abandon 12%·Gap +38pp
Get more of this cohort onto /pricing
highConverters from branded search hit /pricing more often than non-converters. Test routing or creative that lands more of this traffic there.
Converter rate 82%·Non-converter rate 41%·Gap +41pp
Engagement on conversions
Evidence · credited traffic
Low
18
Mid
41
High
52
No score
9
Investigation readiness
Core capture · Ask depth
Core
CI · Forms · Sections
Depth
Scroll · Clicks
Cohort gaps
Converters had · non-converters often didn't
| Experience | Type | Conv. | Non-conv. | Gap |
|---|---|---|---|---|
| /pricing | page | 82% | 41% | +41pp |
| Company size | form | 12% | 50% | +38pp |
| ROI calculator | section | 55% | 22% | +33pp |
“Which pages do converting Meta sessions hit that non-converters miss?”
AI influence
Because Intently captures rich behavioral signal server-side, AI can answer questions about intent, content, and conversion friction, not just pageviews. Ad spend and attribution live in the same pipeline, so Ask cites ROAS and model math.
“Which campaigns have ROAS under 0.5x on last-touch?”
“Why do linear and last-touch disagree on Meta?”
“Which channels drive closed-won pipeline this month?”
Ask Intently AI
Reading reports…
“Which campaigns have ROAS under 0.5x on last-touch?”
Go deeper
Intently captures complete first-party signal, attributes revenue with models you can audit, proves delivery to ad platforms, lets you pause or boost Meta/Google/Microsoft campaigns from Attribution, uses AI that cites the numbers, and exposes the same data through a read-only MCP server.