// Case study / Question formulation
The CTA worked. The question it answered was too shallow.
An analytics engagement for a tattoo studio that started as an implementation brief and became an early lesson in the difference between measuring what’s happening and changing what happens next.
What happened
The tracking worked. The client expected it to create results.
Paper Crane Tattoo had existing organic demand — Search Console showed around 1,400 monthly clicks from “tattoo placement” queries and meaningful impressions on consultation-intent terms. The analytics implementation was technically sound. Then the client asked why they weren’t seeing more traffic and sales from it. That question revealed the misalignment: they expected the tracking to be the strategy, not to inform it.
Context
A tattoo studio does not convert the way an online store does.
The site’s job was not to sell a tattoo. It was to route qualified interest into the consultation process. From there, the artist evaluates fit, style, feasibility, and whether the work aligns with their standards. More form submissions are not automatically better — raw throughput without qualification serves no one. That distinction made the analytics brief more complex than it looked.
Task
The stated brief and the real question were not the same thing.
The stated brief was analytics implementation. The real question — once the client’s expectation surfaced — was closer to: “Why aren’t qualified visitors finding the consultation step?” Accepting the first without excavating the second was the mistake.
“set up analytics”“what decision does this data support?”
buried consultation CTAtop-nav CTA / no developer required
correct implementationbehaviour change
analytics as infrastructureanalytics as a means to a question
Action
The fix was a button. The insight was knowing where to look.
Once the real problem was visible — a misaligned consultation path, not a tracking gap — the intervention was straightforward. Surface the consultation request as the primary CTA. Google Optimize made it deployable without a development ticket. Throughput through the consultation path improved.
Outcome
The fix worked. The understanding didn’t transfer.
- Consultation CTA surfaced via Google Optimize, no development dependency.
- Throughput through the consultation path improved.
- A subsequent site redesign buried the link again.
- No institutional understanding of why it mattered — so it wasn’t protected.
Design lesson
Analytics is a means to a question. Without the question, it’s infrastructure.
The early failure was accepting “set up analytics” without asking “what decision does this data need to support?” Those are different engagements. One ends with a correctly-firing tag. The other ends with a behaviour change.
The tactical fix worked. But a client who doesn’t understand why a CTA placement mattered will undo it in the next redesign. The missing deliverable wasn’t a dashboard — it was the understanding that would make the improvement durable.