Home/Analytics/Marketing Analytics Tools That End in a Decision

Know which marketing work brings signups

Among marketing analytics tools, Tin gives your coding agent a PostHog brief to use when deciding what needs work. The decision is to ship a change, repair measurement or wait. Our people can set up that reading and discuss it with you weekly.

Book a call

Read PostHog from the coding agent
Analytics in Tin
Tin's System view: scheduled and available workflows for a project

What are marketing analytics tools?

Marketing analytics tools record visits, traffic sources, events and signups, then show them in charts, funnels and reports. These views help a team follow what happens between a marketing visit and a useful action. A funnel shows where people leave a sequence of steps. Paths and event histories show what happened around that point, giving the team evidence for the next page or product decision.

Web analytics shows visits and sources. Product analytics such as PostHog follows events and funnels. Ad and attribution reports help a team examine campaign activity. Tin adds a workflow that reads one PostHog project and writes a brief for deciding whether to ship, repair or wait. Compare these approaches by whether the reading ends with a decision someone can act on this week, with evidence they can check.

Charts without a decision cost your team review time

A dashboard shows a jump or a drop. Someone still has to connect that movement to a visitor, a journey and a possible change.

  • Test visits pass for buyers. An agent's browser tests counted as traffic on one of our projects, adding activity that said nothing about demand.
  • Reviews drift into browsing. Without a question to settle, the team can spend the review scanning charts for interesting movement.
  • The decision stays open. A change in a chart leaves the founder to determine whether the page, tracking or campaign needs attention.

A brief with a written decision gives that review an end point and a next action.

Each brief shows its sources and leaves your traffic out

Tin records how it reached each number. Event meanings, exclusions and queries stay available for checking the brief before acting on it.

Activation in order

The repository tells your coding agent which events the app fires. It uses that code to fill in what the events mean. Tin can then order the activation funnel around those definitions, showing the sequence that takes a person toward using the product.

Order events by their product meaning
Activation event mapping
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Team traffic left out

Company visits and browser tests can be left out of the report. For example, ask Tin to exclude everyone using the company email domain. Those exclusions apply to the reporting period, so activity from your own team is kept separate when you read the response from other people.

Separate buyer activity from testing
Traffic exclusions
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Reproducible numbers

A number in the brief has a query behind it, and that query comes with the report. You can inspect how a traffic count, trend or error signal was measured. When the team questions a conclusion, the calculation is there to examine alongside it.

Check the query behind each number
Queries and evidence
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Read-only queries

Select one PostHog project for the reading. Tin uses bounded, read-only queries to produce the brief from that project, and saves the report for the team. The reading can run on a schedule, ready to consult when a product or tracking change needs a decision.

Schedule a bounded project reading
Analytics brief schedule
A week of a growth system in Tin: research, writing, checks, paid ads, email, review and measurement, day by day

One decision at the end

The review ends by choosing whether to ship a change, repair measurement or wait. It also states the condition for leaving the product as it is. If the run measured nothing, the brief records that fact, so the team can see what the reading could establish.

Tin's workflows also read revenue, ads and search

Review the project

Bring the project's work into a weekly brief for the next discussion. Browse workflows

Read paying customers

Build a paying-customer segment from Stripe to inform the next outreach work. Browse workflows

Check ad campaigns

Use Google Ads campaign check-ups to examine paid search alongside other work. Browse workflows

Audit public pages

Check technical SEO and AI visibility with findings and supporting evidence. Browse workflows

Inspect product features

Run a feature audit to examine the product alongside the analytics reading. Browse workflows

Schedule the analytics brief

Read PostHog on demand, daily or weekly, according to the question. Browse workflows

  • PostHog
  • Google Search Console
  • Stripe
  • Google Ads
  • GitHub
  • Claude Code
  • Codex
  • Cursor

Start with a weekly brief on one PostHog project

Choose a recurring question about the product. Tin can read the selected project on a schedule and save the brief for that discussion.

Connect the agent to a weekly brief
PostHog brief setup
Tin's System view: scheduled and available workflows for a project

Connect the coding agent

Add Tin to Codex, then ask for a weekly PostHog brief excluding everyone on the company email domain.

codex mcp add tin --url https://app.tin.computer/mcp
Match events to product actions
Product event meanings
Tin's Files view: the project's knowledge base, reports and drafts as plain files

Map the product events

Let the agent read the code and identify which event means signup, so the funnel follows the product's definitions.

Set the reading around the decision
Recurring analytics review
A week of a growth system in Tin: research, writing, checks, paid ads, email, review and measurement, day by day

Choose when to read

Run the brief before a specific decision, or set a daily or weekly schedule for the recurring review.

The analytics workflow is open code you can change

Inspect the workflow

Open its folder to inspect the steps, data it reads and actions it is allowed to take.

Change a workflow

Edit the PostHog brief's file to ask different questions, then send it back.

Run it in-house

Your team can also run the system on its own machine, using its own keys.

Use the source

Open source, Apache 2.0.

Talk to Tin

We can set up the analytics and conversion tracking, separate agent traffic and check the funnel. Let's discuss how a weekly reading with our team could help settle your next decision.

Book a call

FAQ

Can the brief change anything in our PostHog project?

It reads the selected project through bounded, read-only queries and writes its report in Tin. Nothing is sent outside Tin. The team can inspect that report and its evidence before deciding on a product change or a repair to the events being counted.

Which PostHog projects does it work with?

The brief works with PostHog Cloud in the US and EU. Each reading uses a single selected project, including its events, properties and definitions. The event mapping tells it what those events mean for the product, and exclusions let it leave company and test activity out of the counts.

What if our events are messy?

Your agent can read the code to identify the events and fill their meanings into the mapping. If the captured events still cannot connect the relevant steps, the review calls for a measurement repair. That identifies the missing count or connection needed before judging the page or channel.

Does it read website traffic as well as the product?

Yes. Supply the website hosts as an input and the brief can read that traffic over the selected reporting window. The same exclusions can keep team activity and browser tests out. Its figures come with the queries used to produce them, so the website reading can be checked too.

Talk about the decision your analytics should settle

Meet the founders and engineers who set up Tin and run the analytics work. We can discuss the question your team needs to answer, which events could support it and how a recurring brief would fit the review.

Book a call