Website Visitor Identification Is Not a Store Signal

Website visitor identification resolves anonymous traffic on your own website into a company, and sometimes a person. A script runs on your pages, an IP address or a cookie match is looked up against a vendor's database, and a name comes back. It answers one question well: who has already been to my site. It cannot answer the other question an outbound team has, which is which store out there has just done something worth writing about.

The disclosure belongs at the top rather than in a footer. We build Keaz Signals, which sells store-level buying signals to the people selling to ecommerce stores. We do not do visitor identification, we are not planning to, and we have an obvious interest in the distinction this post draws. Read it with that in mind.

This is written for the agency or software company selling into ecommerce, not for the merchant. The two categories get compared because both are sold as "know who to talk to", and the phrase hides the fact that they are reading completely different things.

One question is about your traffic. The other is about someone else's storefront. Visitor identification starts from a visit that already happened on a property you control. A store-level signal starts from a change on a shop that has never heard of you. Different input, different output, and no overlap in the sales pitch closes that gap.

• Population: one sees only those who came to you; the other sees a market that has not met you.
• Trigger: one fires on interest in you; the other on a decision the store made about itself.
• Ceiling: one is capped by your traffic; the other by how many stores are watched.

The same confusion appears elsewhere: it is why we argued that email tracking measures your outreach, not the store. Both point a camera at your own activity and call it intent.

It decides the size of the pool you can work. Visitor identification is bounded by your own traffic, so the stores it surfaces are the ones already aware of you. That is a warm list and it is worth having. It is also, by construction, the smallest part of your addressable market, and it grows only as fast as your marketing does.

For most agencies selling into ecommerce, the stores worth contacting this month have never visited the site. They are busy running their own business. The thing that makes one of them worth an email is not that they read your pricing page; it is that they just installed a retention tool, rebuilt the storefront, or turned Meta ads back on.

There is a second-order effect worth naming. A team that runs only on visitor identification ends up with outbound that is really delayed inbound, and concludes that outbound does not work. What did not work was a pool defined by people who had already found them.

We do not identify website visitors. We do not place a pixel on your site, hold cookie data, resolve anonymous traffic, or see who is browsing anything you own. There is no roadmap item for it. If de-anonymising your own traffic is the job, we are the wrong tool and nothing in this post should be read as a pitch for it.

What we do is narrower. We watch public storefronts and record what changed between one pass and the next: new Meta ads running, the active ad count rising, a product launch, an email marketing tool installed, social growth, newsletter activity, store and site changes. Contacts come with the store, including founder addresses that are not publicly listed. The full list is in the buying signal catalogue.

The other gaps, stated rather than buried: no registry or firmographic triggers and no hiring signals, both of which are marked planned and neither of which exists today. No LinkedIn signals and no LinkedIn sending, with no plans to add them. No CSV export. Shopify and WooCommerce only, Europe and North America only.

The two approaches collect from different places, and that shapes what each one has to think about. Visitor identification works from behaviour on a site, which means cookies, scripts, IP resolution and consent banners are part of its machinery. Store-level signals work from what a storefront publishes to anyone who loads it, plus contact data attached to the business.

That is a structural difference, not a claim about anyone's compliance. Both approaches can be run carefully and both can be run badly, and which one you use tells a regulator nothing on its own.

Our own position is deliberately narrow, and we are not going to widen it to win an argument: we are GDPR-conscious by design, and responsibility for what you send stays with you. This post is not legal advice, we are not your lawyers, and anyone in this market who tells you their data is lawful for your use case is telling you something they cannot know.

If your site already gets meaningful traffic from the right companies, visitor identification is the better tool and we are not a substitute for it. A prospect reading your pricing page three times this week is a stronger signal than anything we can see from outside, because it is about you specifically. We have no view of that and never will.

It is also the better tool for account-based work on a named list, for routing warm traffic to the right rep, and for measuring whether campaigns are pulling the companies you targeted. None of those are jobs we do.

And our own limits bite here as much as anywhere. If you sell to Magento shops, to marketplaces, or outside Europe and North America, we do not cover them. If you need a file to hand to a partner, we do not export: leads move into campaigns and stay there. Those are real reasons to choose something else.

The honest answer for a team with both problems is that these are complements, not rivals. One works the people who found you; the other works the market that has not.

We are not going to tell you what share of visitors an identification tool resolves, or how accurate the company match is. We have not measured it, we have no way to measure it across vendors, and the figures that circulate are vendor marketing rather than anything traceable to a method. A number we cannot stand behind is worth less to you than this paragraph.

We are also not going to claim that store-level signals convert better than visitor identification. We have not run that comparison. Anyone quoting a reply-rate lift for one category over the other is quoting their own campaign, on their own list, with their own copy.

What we will state, dated: as of September 2026 we watch 4.1 million Shopify and WooCommerce stores across Europe and North America, re-scraped weekly, with roughly 41,200 carrying a fresh signal in any given seven-day window. Those figures move, which is why they carry a date every time we use them.

Write from the event, not from the category. A store that installed a retention tool nine days ago has unfinished work and someone accountable for it; a store that has run the same tool for three years has neither. Segment on the change plus the fit conditions you care about, send while the event is still recent, and write one message per event rather than dripping a static list.

That is the shape the ecommerce leads database is built around: conditions on country, platform and follower count, a live audience estimate, and the change itself as the thing that puts a store into the segment. Sending runs through your own Instantly workspace, and the sales agent writes per-store copy from the signal and your own knowledge base.

If you want to see whether the events are there before committing to anything, signup includes 1,000 free leads, and access is capped per market so the same stores are not sold to everyone.

• Keaz Signals buying signal catalogue — the seven signal types named above, retrieved 19 September 2026
• Our own coverage: 4.1M Shopify and WooCommerce stores watched, ~41,200 with a fresh signal in seven days — as of September 2026
• Weekly re-scrape cadence, no export, no LinkedIn — own product behaviour, September 2026
• Adjacent: intent data by category · state versus change