Integrations
Your tools see people. Punchline adds the agents.
Every integration carries the same thing your other tools are missing: which visits were agents, what they did, and the person or company they led to. Set up in minutes, alongside what you already run.
Connect agents to people
The part nobody else does
Handoff links
When an agent builds a quote, a cart or a booking, your site hands it a link for its person. When they open it, the agent's work, the person's visit and what they do next become one journey. Exact, not modelled.
Server events
Send signups and purchases from your backend with the visitor's address, and each joins the visit it came from. Orders placed by agents never inflate orders placed by people.
Stripe Checkout
Purchases paid through Checkout land on the visit they came from, sealed into the session as an encrypted token Stripe can't read. A purchase an agent made counts as the agent's.
MCP analytics
If you run an MCP server, see which agents call which tools, and hand back a handoff link from the tool that builds something.
Install
Pick the install that fits your site
Each one labels every visit with its evidence. The ones at the edge also see agents that never run JavaScript.
- Next.jsA three-line proxy fileEvery request, at the edge
- Shopify HydrogenOne wrapper in server.tsEvery request, at the edge
- Static, Vite or Astro on VercelVercel middlewareEvery request, at the edge
- Anything on Vercel, no codeVercel log drainEvery page request, from Vercel's logs
- Webflow, Framer, Shopify, anything behind CloudflareCloudflare WorkerEvery request, plus whether each agent got the page
- ShopifyWorker, theme snippet and order webhookEvery request, people, and paid orders by people and by agents
- WordPress and WooCommerceWordPress pluginEvery request that reaches WordPress, the snippet for cached pages, and WooCommerce orders
- Squarespace, Wix, Tag ManagerBrowser snippet or Google Tag ManagerVisitors that run JavaScript, labelled as a browser-only view
- Not ready to installLog analyzerA one-off report from a log export, on your machine
Marketing
Your marketing stack, without agents in the numbers
Google Analytics 4
GA4's numbers next to Punchline's, day by day, with the gap explained: agents GA4 never sees, and agents in a browser it counted as people. It imports 14 months of GA4 history.
Google Ads and Meta
Conversions uploaded against the ad click that brought them, from people only. Agents that follow your ads never teach your bidding the wrong lesson.
Google Tag Manager
Install the snippet from your container, and send your GA4 events to Punchline under the same names.
Sales
Signals where your reps already work
HubSpot and Salesforce
What agents researched for a company, written onto it as a note or task, and a note when someone there opens a handoff link. Deals come back so you see the revenue behind the research. Companies, never named people.
Slack and webhooks
"A company is researching you", "agents spiked", "people from AI assistants dropped": a daily digest in Slack, or signed JSON for Zapier, Make or your own code.
Data
Your numbers in your own tools
BigQuery and Snowflake
Four tables a day: traffic split by visitor type, and agent sessions with the rules and evidence behind each label. You grant access on your side; no passwords handed over.
REST API and SDK
Every dashboard number, with real example responses in the reference and a typed TypeScript client.
AI
For your assistants, and for theirs
Punchline's MCP server
Ask Claude, ChatGPT or Cursor about your traffic, and let it set up alerts and goals if you allow it.
Edge markdown
Hand AI assistants a markdown version of the page they asked for, made from your own HTML. Same facts, easier to read.
Claude Code skill
The log analyzer as a skill: ask Claude Code who visited, from a log export, offline.
Every integration
The same rules wherever the data goes
- Privacy travels with the data. Anything that leaves your dashboard withholds groups of fewer than 5 people and never includes a person's session.
- Credentials are stored encrypted and never shown again. Where a service allows it, you grant access on your side instead.
- Failures show where you set things up, and the next daily run picks up where it left off.