Private beta

45-day program

Forty-five days to proof you can defend.

Structured white-glove onboarding: full product access, a dedicated contact from day one, and live sessions to wire your stack, prove delivery, and train your team on signal you can defend.

See the steps
Cycle mapDay 1 → 45
  • Full platform access from day one
  • Dedicated contact through setup and validation
  • White-glove onboarding, not self-serve
  • Hands-on training for growth and media teams

Why teams choose it

Bad setup means bad credit and wasted spend.

The program exists so you start with attribution you trust (capture, consent, and destination proof in place) and a partner who stays hands-on until you do.

The path

Six phases across 45 days, from access to attributable conversions.

  1. Step 01 · Days 1–3

    Request access

    Share what you need to measure: channels, CRM or Stripe, destinations, and approximate monthly events. We reply within one business day and book a short walkthrough.

    • Fit and volume confirmed
    • Plan sized to Platform or Enterprise
    • Kickoff on the calendar

  2. Step 02 · Days 3–7

    Map your stack

    On the call we walk your site, CMP, ad platforms, and revenue systems. The goal is a concrete install plan, not a generic pitch deck.

    • Snippet or Track API path chosen
    • Destinations and consent categories listed
    • Stripe / CRM / spend sync scoped if needed

  3. Step 03 · Days 5–10

    Your workspace is ready

    We create the account and send a welcome email. You set a password, invite teammates, and land in a workspace configured for your plan: ready to install, not an empty trial.

    • Invite link to set your password
    • Roles for Admin, Analyst, Viewer
    • Named Intently contact for the cycle

  4. Step 04 · Days 8–18

    Install first-party capture

    Add the Intently snippet (or Track API) on your domain. The debug overlay shows events, consent blocks, and payloads on your live site so install is inspectable, not guessed.

    • Events visible in the overlay
    • Consent state readable before storage
    • First sessions in the dashboard

  5. Step 05 · Days 14–28

    Connect destinations and revenue

    Turn on server-side destinations (GA4, Meta CAPI, TikTok, and the rest), wire CMP enforcement, and connect Stripe, HubSpot/Salesforce, or ad spend when those matter to your ROAS story.

    • Destinations gated by consent category
    • Revenue or closed-won linked to journeys
    • Spend sync ready for campaign ROAS

  6. Step 06 · Days 25–45

    Prove delivery, then attribute

    Run conversion paths and open the delivery log. When destinations accept the send, attribution models, journeys, and Ask sit on signal you can defend, including MCP for Cursor or Claude when you want the same tools outside the dashboard.

    • Delivery log shows accepted sends
    • Match quality visible where reported
    • Models and Ask ready on real journeys

Partnership

Clear ownership on both sides.

You bring

  • A site (or app) where conversions happen
  • Access to your CMP and destination accounts
  • Someone who owns media or growth decisions
  • Optional: Stripe, HubSpot/Salesforce, ad spend credentials

We bring

  • Account provisioning and plan sizing
  • Install plan and a named contact for the cycle
  • Hands-on help through first live proof
  • Docs, overlay, and delivery log for ongoing QA

Definition of done

You are live when proof is visible.

The 45-day program is not “pixels pasted.” It ends when capture shows on your site, consent is enforced server-side, and the delivery log shows destinations accepting conversions. Attribution and Ask start from there.

Read the docs
OverlayEvents and consent blocks on a real page
Delivery logAccepted or failed sends per destination
AttributionJourneys and models on first-party signal

FAQ

Common questions before you start.

Why a 45-day program instead of self-serve?

Attribution fails quietly when capture, consent, or destination delivery is wrong. The program puts those foundations in place before you trust credit, ROAS, or pause/scale decisions.

Do all customers use the full 45 days?

The program is 45 days by design. Simpler stacks often hit delivery proof earlier; multi-brand or complex CMP setups may use the full window. We set expectations on the mapping call.

Is there a free trial?

We start with a Request access walkthrough, then provision a workspace sized to your volume. An empty trial without connected capture and destinations does not prove attribution.

Who installs the snippet?

Your team owns the site change. We provide the snippet or Track API path, overlay checks, and a clear definition of done. Agencies and in-house engineers both work fine.

What about Enterprise?

Enterprise includes dedicated onboarding help and room for scoped connectors beyond the standard destinations and CRM integrations. The same 45-day program applies with more hands-on coverage.

Ready to start the program?

Request access and we will map your stack, provision the workspace, and stay with you through first delivery proof.

See the platform