The Platform

Three jobs.
One pipeline.

Intently is server-side attribution for ad buyers who cannot afford to lose conversion signal. We capture complete first-party data, credit revenue with nine inspectable models, sync CRM and ad spend for ROAS, deliver to your ad platforms with proof — and use AI to explain the math, not invent it.

Read the docs

8

server-side destinations

9

attribution models

5

CMP integrations

0

third-party ad pixels required

What it does

Three jobs. One pipeline.

01

Capture complete signal

One first-party script on your site collects clicks, sessions, and conversions. Consent is enforced server-side before storage or destination routing.

02

Attribute revenue correctly

Nine transparent multi-touch models, lookback from 1 day to lifetime, Stripe + HubSpot/Salesforce closed-won, and ad spend for campaign ROAS — on journeys you can inspect touch by touch.

03

Deliver with proof

Conversions route server-side to GA4, Meta CAPI, TikTok, Snapchat, LinkedIn, Pinterest, X, and Segment. Delivery logs and match quality show whether each destination accepted the event — not a black-box pipe.

The Intently wedge

No single stack gives ad buyers complete first-party capture, nine inspectable attribution models, CRM + spend ROAS, delivery proof with match quality, and AI that cites the math — in one pipeline you can audit end to end.

On-site visibility

See what you capture — on your live site

The debug overlay shows events, consent blocks, and payloads as they happen. No third-party pixel scripts required.

  • Nine models including last non-direct, linear paid, and source-specific lenses — lookback from 1 day to lifetime
  • Journey inspector: per-touch credit % and credit-by-model matrix
  • Stripe + CRM closed-won and Meta/Google/Microsoft spend for campaign ROAS
  • Delivery proof and match quality on attributed conversions
All capabilities
yoursite.com — debug overlay
Debug overlay — yoursite.comlive
page_viewcaptured
scroll_depthcaptured
form_startcaptured
add_to_cartconsent

Delivery proof

See which destinations accepted each send

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.

  • Per-destination status for dispatched events
  • Failed sends surfaced with error detail
  • Audit trail you can share with media buyers
Delivery proof docs
app.intently.io/pixels#delivery-log
eventdestinationresult
page_viewGA4delivered
add_to_cartMeta CAPIdelivered
purchaseTikTokdelivered
purchaseMeta CAPItimeout
form_submitSegmentdelivered

Revenue attribution

Credit revenue to the channels that drove it

Nine transparent models and lookback windows on complete server-captured signal — with Stripe and CRM revenue, ad spend ROAS, journey inspection, and delivery proof.

  • Nine models including last non-direct, linear paid, and source-specific lenses
  • Journey inspector, HubSpot/Salesforce closed-won, and campaign ROAS
  • Delivery proof and match quality on attributed conversions
Attribution report
app.intently.io/attribution

Marketing attribution

Last-touch · 30 days

Stripe linked
ChannelConv.RevenueROAS
Google Ads142$48,2904.2x
Meta98$31,4403.1x
TikTok54$12,8802.8x
Organic76$18,220
All conversions include delivery proof per destination

How it works

Capture, attribute, and deliver — on your infrastructure

Intently moves tracking to your domain, credits revenue across sessions, and routes enriched events to every ad platform — with proof each destination accepted the conversion.

01 · Capture

Server-side event collection

A first-party SDK on your site collects interactions and stores them server-side — so attribution and delivery are not limited to what fragile client tags survive.

  • First-party script on your site
  • Bot filtering on captured sessions
  • Lightweight client collector
  • Consent-mode compatible by default

02 · Understand

Behavioral intelligence layer

Raw events are enriched, sessionized, and scored in real time so your team can see who is interested and why.

  • Intent scoring per session
  • Behavioral profiles per session and page
  • Segment by behavior, not just demographics
  • Cross-session stitching when user hashing is enabled

03 · Act

Deliver to ad platforms

Enriched conversions route server-side to GA4, Meta CAPI, TikTok, Snapchat, LinkedIn, Pinterest, X, and Segment — with a delivery log for each send.

  • Optional webhook forwarding for custom pipelines
  • Eight native server-side destinations
  • Delivery proof for dispatched sends
  • Consent checked before storage or routing

Architecture

Built for your infrastructure,
not against it

Intently runs as a first-party SDK on your site plus server-side processing — so capture, consent, attribution, and destination delivery stay in one pipeline you can audit.

  • First-party SDK on your site; events stored and routed server-side
  • Hosted on Vercel with PostgreSQL (Neon)
  • GDPR & CCPA consent-aware data handling
  • Hosted on SOC 2-certified cloud infrastructure (Vercel, Neon, Stripe for billing).

Your visitors

WebsiteWordPressShopifyNext.jsTrack API

Intently collection layer

Event collectionConsent enforcementBot filteringSession stitching

Intelligence & routing

Intent scoringContent intelligenceSession profilesEnrichment

Your destinations

GA4Meta CAPITikTokSnapchatLinkedInPinterestXSegment

Privacy first

Compliance is the foundation, not a feature

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 Neon).

Consent-mode native

Respects granted/denied signals from your CMP automatically. No code changes needed when consent changes.

First-party collection

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.

Data minimisation

Collect exactly what you need. Configure field-level redaction, IP anonymisation, and retention windows per event type.

Ready to see the full platform?

Get a personalised walkthrough with a member of the team.