Track phrases matches "too many" URLs - Misleading documentation?


This is related to this discussion [0] , but regarding the path in the URL, not the sub(domain).

After reading the docs[1] I thought “foo” would not match “”, but according to “Streaming API keyword matching” [2] it does:

Terms that would match this tweet: (the tracking terms are made lowercase before comparison, fullwidth and halfwith are considered different)

The “” example is also confusing as “” is listed under “Will not match…” but listed as a match by the tool :slight_smile:

I also think see this in practice with tweets matching “post” because a link contains “……”, but I’ts hard to be sure.

Did I misunderstand or are the docs wrong?