What a win is
A win is the first time an engine names your brand, or links to your own site, in an answer to a prompt it had been answering without you. It is recorded per prompt and per engine, so ChatGPT naming you on a prompt and Perplexity naming you on the same prompt are two wins. There are two kinds, and each is its own first:
An engine can name a brand it never links, and link a page while recommending somebody else, so one does not stand in for the other. Each (prompt, engine, kind) can be a win once, ever.
A win says what happened and when we started reading. It never says why. The message reads “for the first time since we started reading this prompt”, not “after we shipped” or “because of our work”.
What counts
Every hour, a pass reads the last three days of your readings, in your workspace’s time zone. It is arithmetic over the same numbers your dashboard shows, with no model involved, so the same readings always produce the same wins. A naming is a win only when all of these are true:1
The prompt does not name your brand
A prompt that names you (“is Acme any good”) is a question about you, and being named in its answer is not news. The prompt’s text is checked against your brand’s name, your domain and your domain’s bare name, as whole words. A prompt that names a competitor (“Acme vs Curve”) still counts: that is a question a buyer asks.
2
You still track it, on that engine
A prompt you deleted, or an engine you removed from a prompt, produces no wins.
3
We had read it for at least three earlier days
Before the day you were named, at least three earlier days carried at least one successful reading of that prompt on that engine.
4
No earlier day had you in it
On no earlier day with a successful reading did the answer name you (for a named win) or link to you (for a linked win). Every earlier day is checked, not only the last three.
Failed reads never count
A day counts only if at least one reading of the prompt on that engine succeeded. A day of failed reads and a day with no reading at all are the same to this pass: silence. A failed day cannot be one of the three earlier days, and it cannot be the day you were named.What is never announced
- Names from before detection started. The first pass on a workspace records everything you are already named or linked for as a baseline and announces nothing. Turning detection on does not announce months-old news as a first.
- A naming we could not call a first. If an engine named you on a prompt before we had three successful earlier days of reading it, or had named you on it before, that (prompt, engine, kind) is recorded as a baseline. It is never announced and never becomes a win later.
The win message
When the pass finds new wins, you get at most one message per workspace per day in your workspace’s time zone, listing every win not told yet. A win found after that day’s message went out is in the next day’s message. Each win is told in one sentence:ChatGPT named Acme for the first time since we started reading this prompt on 2 September 2026, in an answer to ‘best dental software’ on 28 September 2026.“Since we started reading” is the first day we have a successful reading of that prompt on that engine. A linked win says “linked to acme.com” instead of “named Acme”. Under the sentence:
- The quote. The engine’s own words, verbatim, cut from the answer we read: at most 400 characters around the first mention of your brand (or the cited link, for a linked win). When the quote is cut from a longer answer, it is shown with ”…” at both ends. A quote is never edited or summarised. If no answer that day yields a quote that contains the mention and passes our honesty check, the win has no quote rather than a tidied one.
- Related work, only when it is true. If a piece of work that lists this question went live in the 90 days before the win, the message adds “Work on this question: title, live since date.” as a separate line. When the win is linked to a change, that change is the work named, even if newer work on the question went live after it. It does not claim the work caused the win, and work that is not live yet is never mentioned.
The instant win alert
The day’s message waits for the day. The alert does not: the hourly pass that finds a win writes its alert in that same pass, before the hour is out. The alert is the same words as the message, for that one win:- the win’s sentence, unchanged,
- the quote, when there is one,
- the related-work line, when it is true, as its own line,
- Share card: a link that opens the win’s share card page.
win_detected event, so anything that listens to your events gets it as soon as the win is stored.
It is also emailed to you, in that same pass, at most one alert per question per day (a brand named for the first time on three engines for one question in one day is one alert). Its button opens the share card. The day’s win message still comes as well, at most once per workspace per day, listing every new win. A win with no share link sends no alert; the day’s message still tells it. See Alerts.
Where it goes
The message goes by email, and the app shows it too. See Notifications. The win email is its own notification category, so you can unsubscribe from it without turning off anything else.How a win is linked to a change
Each win records the shipped change it came after, when there is one. It is a sequence, never a cause: the change went live, and later an engine named or linked you. Told in one sentence:Shipped 6 Oct, then ChatGPT linked it on 12 Oct, the first time since we started reading.A change links to a win only when it went live before the win’s day, in your workspace’s time zone. A change that went live on the day of the win, or after it, never links, however well it matches. There are three strengths, strongest first. A win keeps the strongest one it has:
A linked win is about a page, so it links only on its page. A named win whose answer cited no page of yours can only link
prompt_only.
A change’s pages are where the delivered work lives (the deliverable’s location), the page the change was aimed at, and any page where our crawl saw the change land and matched it to our work. A change you made yourself, that we did not ship, is never linked.
Pages are compared on host and path. http and https are the same page, as are www. and the bare domain, a trailing / and none. The query string and the # part are ignored, so ?utm_source=chatgpt.com does not make a different page. A different path is always a different page, and path letters keep their case.
When more than one change matches with the same strength, the win is linked to the one that went live last before it. The link is checked when a win is stored and again every hour against newly shipped work, and checking again never changes a link that is already right.
Wins with no change: “not linked to our work”
Every win ends up either linked to a change or saying it is not. A win that is more than 24 hours old and still has no change gets the strengthnone with the note “not linked to our work”: we looked, and nothing we shipped came before it on its page or prompt. That is a normal answer, not an error. Engines name brands for many reasons, and we only put a change beside a win when the change came first.
none is not final. If a change that went live before the win’s day is recorded later, the hourly check replaces none with that change.
Wins stored before linking existed were linked once, all at the same time, by the same rules. That one-time pass picks up where it left off if it is interrupted, so no win is skipped and none is linked twice.
Setting a win’s link yourself
You can put a win beside one of your changes, or mark it not linked to our work, from the win in the dashboard, withPOST /v1/wins/{id}/link, or over MCP with act on the win (relink or unlink; act is not listed to MCP clients yet). The same rule holds: you can only link a change that went live in your workspace before the win’s day. What you set is the win’s link until you set another. The hourly check and the 24-hour “not linked to our work” pass never change it.
The win card in the dashboard
The newest win nobody in your workspace has seen yet appears as a card on New chat, in today’s thread under Needs you, and at the end of every project’s feed. Most visits have none, and then nothing is drawn. The N new wins line there takes you to the card.- Shown once. The card counts as seen as soon as it is on screen, so it does not come back on your next visit.
- Share in one tap. The card carries LinkedIn and Copy link; see Sharing a win card for what the link is.
- Close takes the card off the screen. The win stays in your list of wins, and its link, if it has one, keeps working. Dismiss puts the win away for good and, when it has a link, turns that link off in the same step. The button says Dismiss and turn off the link when there is one.
The referral offer
After you share a win, and in the card’s place when you close or dismiss it, you may see Give a month, get a month: your referral link to send to a team that should be in AI answers too. When they start a plan with it, you each get a month. It appears only after a win, and only when your organisation is eligible; Not now hides it for the rest of that visit. See Referrals for who qualifies, the link and the rules.Sharing a win card
A win card shows the quote, the engine, the prompt and the date. Sharing it to LinkedIn or copying its link makes a public link to the card.- One win, one link. The first share makes the link and every later share reuses it, so a LinkedIn post and a copied link open the same card. On LinkedIn, the link is opened in LinkedIn’s own share box; Attensira does not post anything for you.
- Permanent until you turn it off. The link has no expiry of its own. It stops working when you unshare the win or dismiss it. Dismissing puts the win away and turns off its link in the same step.
- A turned-off link stays off. Sharing the win again makes a new link. The old one never works again.
- A dismissed win cannot be shared.
What a stranger sees
The person who opens the link needs no account. The page shows only your brand, your domain, your logo (when your brand profile has one), the engine, the prompt, the quote and the date. It shows no ids, no counts, nothing else from your workspace, and no Attensira branding, so an agency can share a client’s card as it is. A link that was turned off, or was never a win card, shows “This card is not available”.The win_detected event
Every win is also recorded as one win_detected event, with the win’s id as its subject. Its payload carries:
Today no automation you create reacts to it.
win_detected is not one of the event types you can pick in the dashboard, over MCP or over REST, and each of those asks for at least one type, so a new event automation never listens for it. The built-in Event responder does not listen for it either. Only an automation saved with an empty event list would, because an empty list means every event type.
Reading your wins
- Over MCP, the
list_winstool returns your wins newest first, each with the same sentence the message uses, the quote, the date, “since we started reading” and the share link when there is one. - In the morning brief, the Monday edition counts the week’s wins.
- In the dashboard, the newest unseen win is a card in project feeds. See The win card in the dashboard.