E-commerce
Campaigns, orders and the revenue they bring in.
Which campaigns bring in orders, and what do the available cost inputs tell us?
Explore this setupEarly access · Hands-on setup
Connect your campaigns to orders, leads and revenue in your own cloud. We set up trackin.gg for you, so you can explore the results in the app and inside Meta Ads Manager.
Paid setup + monthly subscription + your cloud costs. Agreed before we build.
We focus the first setup on a specific question and the sources needed to answer it. Each integration is confirmed individually.
Campaigns, orders and the revenue they bring in.
Which campaigns bring in orders, and what do the available cost inputs tell us?
Explore this setupFollow leads beyond the first form submission.
What happened to the leads after they entered our pipeline?
Explore this setupConnect acquisition to what happens after signup.
Which campaigns brought in the signups that later became paying accounts?
Explore this setupStart with one client and a clearly scoped setup.
Can we explain the campaign report using the data behind it?
Explore this setupYou are tech-comfortable and want your attribution reports where your team works: Claude, Codex or any MCP-compatible client.
trackin.gg exposes your configured reports as read-only MCP tools. Ask a question in plain language, let the client read your setup and run the query, and see the rows behind every answer. One token per account, revocable at any time.
See how it answersA paid implementation with a defined first milestone. You work directly with the person building the product.
You know what is included before the work starts.
Your existing tracking stays in place while we validate the agreed setup alongside it.Implementation takes real work, and the infrastructure has real costs. Your proposal sets out three charges before you commit.
Scoped and quoted individually
Monthly fee agreed in your proposal
Your usage, at cost
No free trial or free implementation audit. We agree the scope and price first; setup is paid work. Additional integrations or development are quoted separately.
A useful first setup, with a clear way to evaluate it.
We agree the data sources, reports and validation checks in advance. We do not guarantee recovered sales, perfect attribution or a lift in ad performance.I’m building trackin.gg to connect advertising data with what happens in the business, in an environment the customer owns. The app is working, and I’m now developing and validating it with our first customers.
I’ll show you what works today, tell you what is still being built, and agree what I can deliver for your setup. Your feedback will help shape what comes next.
There is a working app that can be deployed in a customer environment, plus a Chrome reporting extension and an early MCP interface. The product is still being developed. Integrations, report coverage and reliability are validated for each setup; we explain the known limitations before you buy.
The agreed implementation: configuring your environment, connecting the scoped sources, validating the initial reports and onboarding you. This is paid work. The proposal also states the subscription fee, when billing begins and the estimated infrastructure costs.
No. You can see the product and discuss whether your setup is a fit before accepting a proposal. Implementation, access to a configured environment and detailed technical auditing are paid work.
We do not promise either. Data coverage depends on consent, identifiers and the integrations available. Attribution follows agreed rules and does not prove that an ad caused a sale. The first goal is to make the connected data usable and explain how the reports are calculated.
We can build the environment for you or deploy into a suitable existing one. Setup responsibilities, access and ongoing maintenance are agreed in the proposal. You pay the infrastructure provider directly.
It displays trackin.gg reporting inside Meta Ads Manager. Displaying those numbers is separate from sending conversion events to Meta for bidding. Event forwarding is only included if explicitly confirmed in your implementation scope.
The early MCP interface makes supported data available to compatible AI tools. We confirm the available queries, access permissions and tool compatibility for your setup. An AI answer should be checked against the source data before acting on it.
Data stored in your own environment remains there. Your proposal explains what happens to app access, the extension, MCP access, maintenance and handover. Keeping infrastructure running can still incur provider charges and require technical maintenance.
We check your tools first and tell you what is available, what needs custom work and what we cannot currently support. Development outside the agreed scope needs a separate estimate and agreement.
Agree a practical first setup with the founder. See what is ready, what it costs and what happens next.
An early product. Paid implementation. Scope and terms agreed before work starts.