The namesake problemYour product has a name. So does a film, a hotel and a word in the dictionary.
Keyword alerts match all of them, and a dashboard built on keyword alerts counts all of them. That is why most listening tools are mostly noise.
Signal deals with it twice. When it sets up, the agent tells you what it expects your names to collide with, before a single post is read. After that every post is read against what your company actually is, and anything that is not about you stays out of your counts, your share of voice and your brief. It is not deleted: you can see what was ruled out, and why.
Example — Northwind sells a product called MeridianNamesakes we’ll filter outProposed at setup · from the model’s knowledge
- Film
Meridian — a feature film of the same name
- Word
meridian — the ordinary word, in geography and acupuncture
- Company
Meridian — a hotel group
xX@filmnight·1 hour ago
Just saw Meridian on opening night. That last scene. Still thinking about it.
Not about Northwind 0.97Kept out of counts
WhyAbout a film called Meridian, not the product. Nothing in it touches software or Northwind.
YHacker Newscomment·4 hours ago
Is Meridian’s API rate limit per workspace or per key? The docs don’t say and we’re about to roll it out to three teams.
About Northwind: yes 0.91QuestionSupport
WhyAsks about the API of Northwind’s Meridian product, ahead of a rollout.