How it works

The long answer.

The short one: ask for customers, say yes, and it judges every ad by real buyers on your site. This is the long one, for people who want to know what happens after they ask, what the script records, how the AI makes its call, and what happens to their visitors' data.

$49 a month · free for 7 days · cancel anytime

What happens after you ask.

One: you ask. You type what you want into the ad chat, in plain words. “Get me customers with ads.” is enough.

Two: it reads your site. Before it writes a single ad or judges a single visitor, TribeMap reads every page of your site and writes a description of your business. What you sell, who for, what your key pages are for, and what counts as somebody taking you seriously. Everything else is measured against that description.

Three: one line of code watches visits. About 5 KB, and it loads in the background, so your page never waits for it. It records which pages someone saw, in what order, how long they stayed, how far they scrolled, what they clicked, and where they came from. It never reads what anybody types.

Four: an AI reads each visit as a story. Not a row of counters. It sees that somebody arrived from a LinkedIn ad, read two feature pages, opened pricing, left, and came back the next day straight to pricing. Then it decides how serious that was: real buyer, just looking, or gone. And it writes down why.

Five: it plans the ads. Google Search and LinkedIn. It picks the page the ads should point at and writes the ad words from that page's own words, so it never adds a number the page doesn't say. It makes the pictures, picks the search words or the LinkedIn audiences, and suggests a daily budget. Every search word is checked against Google's Keyword Planner numbers, and words you've blocked stay out.

Six: you say yes, then it launches. Nothing launches until you do. The ads run on your own Google and LinkedIn accounts, and Google and LinkedIn bill you directly. TribeMap never touches the ad money.

Seven: it checks who really showed up. Every night it reads Google's numbers, down to the exact words people searched, and judges each ad and search word by what those visitors did on your site. Leads from LinkedIn lead forms are counted too. You also get a report every morning at 7:00 and a briefing every week.

Eight: it brings you a plan. Pause this search word, add or restart that one, block a word, change the budget. You read it first. Say yes and it's done. Say no and nothing moves.

Every step works today. The ad side has its own page: AI ad automation. Everything below is the hard part underneath. If your question is not here, ask us in the chat.

Why it checks every click.

Lots of ad clicks are junk. Bots click. People tap by mistake and leave in two seconds. Forms fill up with fake names. Google and LinkedIn count every one as a win, then ask for more money.

So TribeMap doesn't take their word for it. It checks.

Checking takes four things, and they are the rest of this page: its own record of every visit, a way to tell a real buyer from a passer-by, a description of your business you can correct, and rules about your visitors' data that we don't bend.

Where the data comes from.

Not from what Google or LinkedIn say happened. TribeMap keeps its own record of every visit.

Are you just taking data from Google Analytics?

No. TribeMap has no connection to your Google Analytics account and never reads from it. It has its own script and its own record of every visit, collected first-party on your domain. If you deleted Google Analytics tomorrow, nothing here would change.

Then what does it read from Google and LinkedIn?

Your ad numbers, once you connect your accounts. Every night it reads Google's numbers for your ads, down to the exact words people searched, and it counts the leads from LinkedIn lead forms. That says what the ad did. Its own record says what the visitor did next.

So do I have to replace Google Analytics?

No, and most people don't. They answer different questions: analytics counts what happened, TribeMap judges who mattered. Run both. We do.

What does the script actually record?

Page paths in sequence with time on page. Clicks, scroll depth, and a count of typing activity, never its contents. Referrer, UTM parameters and ad click identifiers, which is how a visit gets tied to the ad that brought it. Browser, operating system and screen size. An approximate city, derived from the IP address at the moment the event arrives.

Will it slow my site down?

It loads asynchronously and never blocks rendering: about 5 KB gzipped with zero third-party dependencies. The tag you paste is a small loader that pulls in TribeMap's own versioned SDK; beyond that it loads no third-party scripts, pixels or trackers, and it doesn't touch your DOM beyond inserting its own tag. If our service is unreachable, your site is unaffected.

How long until it tells me anything?

Paste the line of code and give it a night. The first visits are sorted as they arrive; the first proper report needs a day of traffic behind it. On a quiet site, give it a week before you judge a channel or an ad.

What about bots?

Filtered in two places: in the browser, on headless and automation signals, and on our servers, on datacenter traffic. Bot sessions are kept separate rather than quietly inflating your numbers, so the bots it catches never pass for buyers.

How it decides who was serious.

This is the call every ad gets judged by.

What is it actually judging?

The shape of a visit, against what your business is for. Depth and order of pages, time spent, whether they reached the pages that matter, whether they came back, and what brought them. A visitor is sorted into one of three groups: real buyer, just looking, or gone.

How does that judge an ad?

Every visit carries what brought it: the ad, and on Google the exact words searched. So each ad and each search word ends up with real people behind it: how many were real buyers, and how many left in two seconds.

Isn't that just a rules engine with "AI" written on it?

A rules engine can't know that your /integrations page is where serious buyers go and your /careers page isn't. That's the difference: TribeMap reads your pages first, so the judgement is about your business rather than about generic thresholds someone picked.

What if it gets somebody wrong?

Every call it makes stores its reasoning, so you can open a visitor and read why it decided what it decided. If the reasoning is wrong, it is usually wrong because the business description is wrong, and you can edit that yourself. See the next section.

Does it get better over time?

Yes, and without work from you. It builds up claims about what your serious buyers do, tests them against new traffic, and drops the ones that stop holding. That is why the answers on day 30 are sharper than the ones on day 3.

The part you can change.

This is the question people ask second and should probably ask first. The AI's understanding of your business is editable.

When you add a website, TribeMap reads it and writes a business description: what you sell, who your customer is, what your important pages are for, and what counts as a real conversion. Open your domain's settings and you can read that description in full.

If it's wrong, you correct it. There is an override you can write yourself, and when it exists it is what the AI uses. Every judgement made afterwards is made against your version.

This matters more than it sounds. If your product page is full of jargon, if your real conversion is a demo booking rather than a signup, or if half your traffic is job applicants you don't care about, the description is where you say so, and the judgements change to match.

The same description shapes your ads: which page they point at, and what they say. For the ads you can set two more things. Blocked words your ads must never show up for. And standing rules, like “never mention price”, which it remembers.

Rule of thumb: if the answers feel wrong, read the description before blaming the AI. It is nearly always the description.

Privacy, in specifics.

Checking every visit only works if you can trust what it keeps. Here is exactly what it keeps, and what it never does.

Do you store IP addresses?

No. There is no IP column anywhere in our database. The IP is used in memory at the moment an event arrives, for three things: working out an approximate city from a local geolocation database, filtering datacenter traffic, and rate limiting. It is not sent to any third-party lookup service.

Do you read what people type?

Typing is counted, never captured. The script does not read form field values, and password, email and search inputs are left out of activity counting entirely. We collect no names, emails, phone numbers or addresses of your visitors.

What about cookies?

One first-party cookie, scoped to your domain: a random ID so a returning visitor counts as one person rather than two. It expires after 12 months. No third-party cookies, no advertising cookies, and no cross-site tracking. If a visitor blocks cookies, a salted hash holds a single day together; the salt is rotated every 48 hours, so the hash can't be linked across rotations or reversed. Expired salts are then deleted by a daily cleanup once they have been expired for a further 72 hours.

Is it GDPR compliant?

For your visitors' data you are the controller and we are your processor, under a data processing agreement. We work to UK GDPR, EU GDPR and CCPA/CPRA. You are responsible for your own privacy notice and for any consent your visitors' jurisdictions require for the first-party cookie. Full detail is in the privacy policy.

What gets sent to the AI providers?

Behavioural data only: page paths, sequence and timing, referrer and source, device type, approximate city. IP addresses are never sent to a model, and neither are names, emails or anything typed, because we never collect them. Providers are OpenAI and Google, and under both of their API terms the data is not used to train their models.

Can I get the data deleted?

Yes. Deleting a website from your account deletes all of its visitor data. On account closure your data is deleted, apart from billing records we're legally required to keep. You can ask for an export or a deletion at any time at team@tribemap.ai. The security page has the rest.

Honest limits.

Which ad platforms does it work with?

Google and LinkedIn, and nothing else yet. That means no Meta, so no Facebook or Instagram ads.

Will it ever act on its own?

No. It always asks before it spends money or changes an ad. That's a choice we made, not something we haven't built yet.

Can you show me ad results from other customers?

Not yet. The ad side is new, and we won't put numbers on this site that we haven't seen. Where our pages show a month of ads, it is labelled as an example.

Does it record people's screens?

No. There is no session replay. It records which pages someone saw, in what order, and what they clicked, not a video of their screen.

Does it work on very low traffic?

It will sort every visit from day one, but a judgement about a channel or an ad needs enough visitors to mean anything. With a handful of visits a week you'll get useful individual dossiers and unreliable channel rankings. Read them as signals, not verdicts.

Can it tell me who the visitor is?

No, and it is not trying to. Visitors are pseudonymous behavioural profiles, not identified people. This is not a tool for putting a company name and an email against an anonymous visit.

Does it replace my whole analytics stack?

No. If you need exact pageview counts, custom event pipelines or product analytics inside a logged-in app, keep the tool you have. TribeMap answers a narrower question: which of these people mattered, and what brought them.

Easier to see than to read about.

Paste one line of code. Give it a night. Then ask for customers.

$49 a month · free for 7 days · cancel anytime