Private beta · Limited onboarding. Request access to join
First-party capture
Incomplete signal breaks credit you can defend. One script on your domain captures first-party events with consent enforced before storage, then Attribution, Experience, Ask, and destinations run on the same pipeline.
Intently
Live capture · yoursite.com
Payload · page_view
{
"event": "page_view",
"page": "/pricing",
"session": "sess_8f2a…c91"
}Why capture depth matters
Models, lookback, and delivery proof cannot invent journeys that never reached Intently. First-party capture on your domain is the foundation: UTMs and click IDs, page context, forms, and the optional depth you turn on when you need it.
Paid and organic channels resolve from UTMs and click IDs on first-party events, not from Ads Manager alone.
Form friction, section attention, and converter gaps come from the same capture that powers journeys.
Attribution Ask and behavioral Ask read what you already captured. Thin capture means thin answers.
Why both layers
Media buyers live in attribution and ROAS. Growth and CRO live in forms, funnels, and page friction. Separate tools mean separate exports, and nobody can answer both halves of the same visit without stitching vendor CSVs.
The hard part is not adding another dashboard. It is serving two job titles from one install without forcing either person to become an analyst in the other tool.
Channel credit and on-site evidence resolve from the same first-party session. When Meta looks weak, you can inspect whether those converting sessions hit form friction or thin engagement, without leaving Intently.
Attribution stays inspectable models and delivery proof. Experience stays associations to try on the site. Neither layer invents the other. They simply stop arguing past each other.
Visitor attention scores help the on-site job when Ask depth is on. They do not rewrite multi-touch credit for the media buyer. That boundary is what keeps both stories honest.
Starter insights
Low-volume signals that power Attribution Experience and many Ask answers without flooding your monthly event allowance.
Intently
Live capture · yoursite.com
Payload · page_view
{
"event": "page_view",
"page": "/pricing",
"session": "sess_8f2a…c91"
}Ask depth
Scroll, active time, clicks, video, and ecommerce browse events are optional and off by default. They count toward monthly events; enable only what you will use.
When Engagement Tracking is on, scroll and active time feed a 0-100 attention score on converting sessions, for Experience and Ask, not multi-touch credit weights.
Schedule a named Ask-depth burst under Tracking when you need citeable engagement evidence. Toggles restore when the window ends; Experience and Ask show overlapping windows for the range you investigate.
Scroll milestones and click streams are the usual volume drivers. Watch Event log and plan usage after enabling.
Ask-depth events still respect analytics consent before storage and routing.
One pipeline
Nine inspectable models on complete first-party journeys, with Stripe and CRM closed-won when linked.
Attribution capabilitiesOn-site tests to try, readiness, engagement evidence when Ask depth is on, and converter vs non-converter gaps.
On-site actionsCited Ask on spend and behavior; server-side delivery to Meta, GA4, TikTok, and more with a delivery log.
DestinationsInstall & proof
WordPress, Shopify, Next.js, or a script tag: same first-party `adt.js`. The debug overlay shows captured events, consent blocks, and payloads without leaving the page.
Verified origins
Overlay proof lives in the hero: install once, then confirm events on your live site.
We walk install, Starter vs Ask depth, and how signal quality shows up in Attribution and Experience, without a settings scavenger hunt.