Sources that mean something
Search, paid campaigns, social, email, referrals and AI assistants are grouped into sources the team can actually discuss.
You changed the site.
Did it work?
See which sources, pages and content lead to form contacts, what happened after each publish, and where to make the next improvement — on the same site.
Built into every published site. No analytics setup.
Traffic is context.
Contacts are the outcome.
Compare visits across sources and campaigns, and form contacts and contacts per 100 visits across pages, devices and countries.
Sources & outcomesRate, not just volume
Compare contacts per 100 visits instead of assuming the page with the most traffic is the most valuable.
Small numbers stay small
Tandmade shows the underlying count instead of turning one extra contact into a dramatic percentage.
Every publish
has an after.
Tandmade knows what went live and when. Compare the periods around a publish and see whether the contact rate improved, fell or still needs more data.
Publish impactSee what went out
Each result stays connected to the pages and changes included in that publish.
Compare before and after
Use the periods around a publish instead of trying to remember when the website changed.
No false certainty
If the sample is too small, Tandmade says so instead of inventing a conclusion.
See the result
where the work lives.
Open any page or content item to see its visits, entrances and form contacts in context — then edit the same thing.
Pages & contentOne page, its real contribution
See whether a page attracts visits, starts journeys through the site and leads to contact.
Content beyond page views
Know which articles people open, which ones bring visitors into the site and which ones contribute to an enquiry.
Write. Publish. Measure. Improve — in the same system.
See how visits
move through the site.
Explore where aggregate visits arrive, where they go next, when they lead to contact and where they leave.
PathsFollow the route, not the person
Tandmade shows aggregate movement between pages without building profiles of individual visitors.
Find the next change.
Make it here.
Analytics should not end in another report or ticket. Tandmade turns findings into actions inside the same website.
Needs attentionA 404 becomes a redirect
See which missing addresses receive traffic and fix the route without leaving Tandmade.
A finding becomes the next edit
Open the affected page, make the precise change directly or hand the larger task to the agent.
The report does not become another ticket
The people reading the result work in the same system as the people changing the website.
See who — and what —
is finding the site.
AI & search
AI assistants as a source
See visits arriving from AI-powered search and assistants alongside search, campaigns, email and referrals.
See what crawlers read
Know which search and AI crawlers request the pages, sitemap, robots.txt and llms.txt.
Analytics starts
with the site.
Tandmade measures the published site on the server. No analytics snippet, separate account or reporting project to connect.
Built inNo analytics cookies
Tandmade Analytics does not use cookies to recognize visitors.
No personal profiles
It does not store IP addresses, browser fingerprints or the contents of form fields.
Clean production data
Review links, editor previews, bots and link previews do not inflate the visitor numbers.
90 days of history
Analyze keeps up to three months of website data.
No analytics cookies. No analytics setup.
A standalone dashboard sees the traffic.
Tandmade knows what changed.
Pages, publishes, content, forms and analytics live in one system. Every result stays connected to the work that produced it — and to the next edit.
Publish the change. See what happened. Open the page. Make the next change.
Questions
Do I need to install an analytics script?
No. Tandmade Analytics is built into every published Tandmade site and measures the public website on the server.
What does Tandmade Analytics measure?
Visits, sources, campaigns, pages, form contacts, devices, countries, 404s, search and AI crawlers, and the impact of individual publishes.
Does it use cookies?
Tandmade Analytics does not use analytics cookies, store IP addresses or create browser fingerprints. Other services you add to the website, such as advertising or third-party analytics tools, have their own requirements.
Does it track individual visitors?
No. Analyze reports aggregate visits, page transitions and outcomes. It does not build profiles of individual people or show person-level journeys.
What counts as a contact?
In the current server-side analytics, a contact is a stored form submission attributed to the page it was sent from.
Can I compare results before and after a publish?
Yes. Tandmade connects each publish with the pages and changes that went out, then compares the relevant periods. When there is too little data, it says so.
Are review-link visits included?
No. Analyze counts the published website. Review links and editor previews are excluded.
How long is analytics history kept?
Up to 90 days.
Does it include heatmaps or scroll depth?
Not currently. Click maps, heatmaps, scroll depth, time on page and browser-side performance data are not part of the current production analytics.
Can clients see Analyze?
Yes. People with access to the website can read its analytics. Connected agents can also read the data through MCP when their permissions allow it.
Make the next change
with evidence.
Start with the website you have. Publish one real change, see what brings form contacts and improve the same page without leaving Tandmade.