SnipForm Documentation

Cookieless by design

The SnipForm universe, mapped for developers

One script collects the visits. Forms, conversions, contacts and money hang off the same session. Everything the dashboard shows, you can read back from the API, an SDK, or an AI assistant.

Install the tracker See the map

index.html

<!-- one tag, every page -->
<script src="https://cdn.snipform.io/api/analytics/signals.js?site=YOUR_KEY" defer></script>

// console, one second later
Initialized
View loaded: <view id>, Session: <session id>

The map

One session, three lanes

A visit becomes a session. Everything else either writes to that session or reads from it, which is how a form submit, an ad click and a paid Shopify order end up on the same row.

Collect

In the browser, or from your own server.

Signals tracker One script tag. Page views, events, revenue and identity. Forms HTML, React or dashboard-built. All validated server-side. Session handoff Pass the session id to your backend and keep writing to it. Shopify The session id rides the cart through to the paid order. Ad platforms Google and Meta spend, normalised to USD cents.

Model

What SnipForm builds out of it.

Sessions One visit, one document. Every field is filterable. Channels Classified once on arrival, in a fixed order you can override. Conversions Funnels that trip on views, events, links and form submits. Contacts The person behind the session, once they tell you who they are. Short links Campaign links with UTM presets and per-click geography. Money Revenue and ad cost, on the session, in integer cents.

Use

Get it back out, on your terms.

Dashboards Widget canvases, shareable on a public token. Weekly reports A stored snapshot per completed week, with checks. Automations When a signal fires, do something. Once per session, exactly. REST API Token-scoped and property-scoped, with a predictable envelope. MCP Twelve read-only tools, so an assistant can answer from real data. SDKs PHP and React packages, plus the tracker itself.

First five minutes

Pick a client and paste

Every snippet below works against a live property as soon as you have a key. Money is always integer cents.

Track an event

Events →

// anywhere after the script tag
signals('newsletter_signup');
signals('purchase', 9900, { order: 'X-1042' });

// or declare it in the markup
<button data-signal="cta_click">Buy</button>

Capture a form

HTML library →

<snip-form key="YOUR_FORM_KEY">
  <form>
    <input name="email"
      sf-validate:required
      sf-validate:email />
    <button>Subscribe</button>
  </form>
</snip-form>

A form in React

React package →

const form = useSnipForm({
  key: 'YOUR_FORM_KEY',
  fields: {
    email: { type: 'email', rules: { required: null } },
  },
});

<SnipForm form={form}>
  <input {...form.register('email')} />
</SnipForm>

Write from your server

PHP SDK →

// the browser knows the visitor,
// your backend confirms the money
Snipform::revenue(9900, 'USD');
Snipform::event('order_shipped');

// from a job, pass the id you stored
Snipform::eventFor($id, 'refunded');

Straight there

I want to...

Send an event from the browser signals/events Send an event from Laravel sdks/php/laravel Get the session id to my backend signals/session-handoff Validate a React form as the user types forms/react/validation Filter sessions by channel and country api/query-language Look up the name of a field api/fields Let Claude read my analytics mcp/connect Post form submits into Slack automations/slack Verify a webhook signature automations/webhook Attribute Shopify orders to a visit integrations/shopify Answer a GDPR or POPIA question privacy Migrate a form from V1 forms/upgrade-guide

Build on it

Three ways in, same data

REST API

Read analytics, sessions, contacts, conversions and short links. Write events and revenue. Tokens are scoped to one property and the scopes you pick.

Bearer token · JSON envelope

MCP

Point Claude, Cursor or any MCP client at a property and ask in English. Read-only is enforced in code and covered by a test, not by instructions.

12 tools · OAuth or token

SDKs

A PHP package with a fluent query builder and a Laravel facade, a React package for forms, and the browser tracker they all feed.

composer · npm · CDN

Before you ship it

What we guarantee

Cookieless, not cookie-light: No cookies and nothing in localStorage beyond a single opt-out flag. The session id is derived server-side from a salt that is unique per property and rotates daily.
No CAPTCHA in front of your users: Forms score a human gate, a honeypot and behavioural signals. Spam is stored and labelled rather than argued with, and the bot is never told.
Form sessions are single use: Every submission runs against a server-issued token: ten minutes, one use, pinned to the requesting IP hash, with the field set frozen at init.
The AI bridge cannot write: MCP tools are read-only and pinned to one property. A test walks the bridged tools to keep it that way.
Pin a version or ride the rolling one: Both browser libraries publish an immutable versioned URL next to the rolling one, so you choose between automatic fixes and reproducible builds.
Your data leaves the way it came: Anything the dashboard renders is available on the API under a token you scope yourself, and contacts can be redacted on request.