AI recommended you. Someone showed up. You have no idea who.

An AI assistant compares vendors, picks yours, and sends a buyer to your site. They read three pages and leave without filling in anything. In your analytics it's a direct visit. Identify resolves that visit to a real company, links it back to the prompt you were cited on, and writes the account into your CRM.

Every other tool in this category stops at the answer

AI visibility platforms tell you how often you're mentioned, which sources get cited, and where competitors beat you. All of that ends at the moment the answer is generated.

What happens next is the part that matters commercially. The buyer clicks. They arrive. And the connection between the answer that won them and the pipeline they become is severed — because nothing on your side knows the two are related.

Identify keeps the thread attached. The prompt, the citation, the landing page, the session, the account, the CRM record: one chain, end to end.

From prompt to CRM record

1. 1
   The prompt run

   You already track the prompts your buyers ask. Citation forensics records which sources the model used to answer each one.
2. 2
   The citation

   Each cited page of yours is a known landing point for that prompt.
3. 3
   The arrival

   The tracking script records the visit and the signals around it: referrer, campaign parameters, landing URL, and the behaviour that follows.
4. 4
   The resolution

   The visit resolves to a company. In the US it can resolve to a person.
5. 5
   The record

   The account is written to your CRM with the originating prompt and citation attached, plus an intent score built from what they actually did on your site.

A standalone visitor-identification tool can tell you a company visited. It cannot tell you which AI answer sent them, because it has no prompt-run data underneath. That's the difference.

Three capabilities

What we can and cannot resolve

Identity resolution is regulated differently depending on where your visitor is, and being specific about that is the point.

Resolution is not universal anywhere. Traffic behind consumer ISPs, VPNs, mobile networks and privacy browsers frequently resolves to nothing useful, and small companies resolve less reliably than large ones. When we can't identify a visit with confidence, we report it as unidentified rather than guessing.

Built for the jurisdiction you're actually in

Targetlytics is operated by EYT Eesti OÜ, an Estonian company, under EU law.

• Lawful basis. Visitor identification and business-lead scoring are processed under legitimate interest, Article 6(1)(f) GDPR — stated in our privacy policy, not buried in a DPA.
• Named provider. Identity resolution is performed through Warmly.ai and the data sources it licenses. We name our provider because you're accountable for it too.
• Geographic split. EEA visitors: company-level only. US visitors: individual-level available.
• Your obligation. The tracking script sets a first-party cookie so a returning visitor is recognisable. You are the data controller for your own site, so obtaining consent where your jurisdiction requires it is your responsibility. We give you a consent hook to wire into your consent manager, and attribution keeps running with the cookie disabled.
• Data subject requests. One month, no charge, handled by us.