# Marcus Reilly, Founder at Patchwork (B2B project ops SaaS, 11 people) — read of Claude Traffic, June 6 2026

> 9 years building and growing SaaS, currently obsessed with our PostHog dashboards at the expense of my marriage and my 7-year-old's Saturday soccer games, which I also coach.

## How I got here

Noticed claude.ai showing up in our Segment referrer data two weeks ago, went to GA to dig in, got nothing. Typed "how to track claude chatgpt referral traffic" into Google, this page was result number four or five. Not an ad. Organic. Clicking that link felt like exactly the right thing to do.

## What I clicked first

The hero copy landed. "Google Analytics is blind to conversations in Claude, ChatGPT, and Perplexity. We fill that gap." That's a real sentence describing a real thing I experienced 14 days ago. I kept reading.

## Where I paused

This line stopped me cold: "For each visit from Claude, ChatGPT, or Perplexity, see the conversation summary, what your page was referenced as, which CTA was clicked, and whether they converted."

Conversation summary. I read that three times. AI conversations are between a user and an LLM, client-side, behind a login. How are you reading those? I scrolled to the FAQ expecting an explanation. Instead the FAQ says: "We only see that a visitor came from Claude or ChatGPT. We never access the conversation itself. Attribution happens on your page load, client-side, using only metadata the user chose to share."

Those two things do not describe the same product. The features section promises conversation summaries. The FAQ walks it back to metadata. That gap is either a lie or a misunderstanding of what was written, and either one is a problem.

## What I distrusted

Three things.

First, the technical contradiction above. I am not a security researcher but I spent eight years at SaaS companies that had to explain to enterprise customers how data flows. "Metadata the user chose to share" and "conversation summary" are not synonyms. If the product only catches a referrer string and some URL parameters, just say that. It would still be useful.

Second, the page breaks into a business-idea scoring widget halfway down. "69/100 Adoptability. $-11,684 Year-1 take-home. Honest disclosure: we don't have live customers on this idea yet." That text is disorienting on a page that has a "Start Free Trial" button at the top. Am I buying software or buying a business concept? The page does not know which one it is, and that confusion transfers to me.

Third, "Zero Setup Required. Paste one script. Done." is doing a lot of work for a product claiming real-time conversation insight. Script tags tell you a visitor arrived. They do not tell you what the conversation was about. One of these claims has to yield.

## What would convince me

A screen recording of the actual dashboard showing a real (anonymized) visit from claude.ai with whatever data actually populates those fields. Not a mockup. Not a Figma prototype. A Loom where someone clicks around and I can see what "conversation insight" actually means in practice. Five minutes of that would answer the contradiction I found in two minutes of reading.

Also: one specific, named example. "We tracked a visit from a Claude conversation where someone asked about project management tools for small teams, clicked our pricing CTA, and converted within 48 hours." That kind of sentence, if verifiable, would have me opening a reply tab.

## What I'd ask in an email reply

1. The features section says I can see "conversation summary" but the FAQ says you never access the conversation. What does the dashboard actually show for a visit from Claude, literally field by field?

2. The honest disclosure says there are no live customers yet. Is the free trial a live product I can install on my domain today, or is this a waitlist?

3. If the attribution is client-side and uses "metadata the user chose to share," are you relying on a referrer header that Claude or ChatGPT actually passes, or something else? Because that header is not always present and I want to know what my coverage rate would realistically be.

## Verdict: on-the-fence

The pain point is real and I would genuinely pay $29 a month to understand my AI traffic better. But the page contradicts itself on the most important technical claim, and the business-idea-marketplace framing halfway down makes me unsure a working product exists at all. I am not dismissing it, but I am not opening my wallet until I see the actual dashboard.

---
*Memo by skeptic persona, generated 2026-06-06. Studio breaks own self-grading loop.*