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


#1

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 “www.example.com/foo/bar”, 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)

www.example.com/foo/bar
www
example
com
foo
bar
example.com/foo/bar

The “www.example.com/foobarbaz” example is also confusing as “www.example.com/foobarbaz” 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 “…tumblr.com/post/…”, but I’ts hard to be sure.

Did I misunderstand or are the docs wrong?

[0] https://dev.twitter.com/discussions/20254
[1] https://dev.twitter.com/docs/streaming-apis/parameters#track
[2] https://dev.twitter.com/docs/streaming-apis/keyword-matching