This is not the case when using the Search API.
For example, if your rule includes url:"", and a Tweet contains that URL, any Quote Tweets of that Tweet will be included in the results. Note: When using PowerTrack or Historical PowerTrack, this operator will match on URLs contained within the original Tweet of a Quote Tweet. While generally not recommended, if you want to match on a specific protocol, enclose in double-quotes: url:"". Tokens and phrases containing punctuation or special characters should be double-quoted. Performs a tokenized (keyword/phrase) match on the expanded URLs of a tweet (similar to url_contains). See HERE for methods for looking up numeric Twitter Account IDs. The value must be the user’s numeric Account ID or username (excluding the character). Matches any Tweet that is in reply to a particular user. See HERE or HERE for methods for looking up numeric Twitter Account IDs. The value must be the user’s Twitter numeric Account ID or username (excluding the character). Note that this operator is only available in the enterprise search APIs. Can have any number of keywords in quotes. N cannot be greater than 6. If the keywords are in the opposite order, they can not be more than N-2 tokens from each other.
Note: This operator will match on both URLs and unwound URLs within a Tweet.Ĭommonly referred to as a proximity operator, this matches a Tweet where the keywords are no more than N tokens from each other. Note: Punctuation is not tokenized and is instead treated as whitespace.įor example, quoted “#hashtag” will match “hashtag” but not #hashtag (use the hashtag # operator without quotes to match on actual hashtags.įor example, quoted “$cashtag” will match “cashtag” but not $cashtag (use the cashtag $ operator without quotes to match on actual cashtags.įor example, "Love Snow" will match "#love #snow"įor example, "#Love #Snow" will match "love snow" Matches the tokenized and ordered phrase within the body or urls of a Tweet. This is a tokenized match, meaning that your keyword string will be matched against the tokenized text of the Tweet body – tokenization is based on punctuation, symbol, and separator Unicode basic plane characters. Note that if an emoji has a variant, you must use “quotations” to add to a rule. These tokens would then be compared to the emoji used in your rule. For example, a Tweet with the text “I like 🍕” would be split into the following tokens: I, like, 🍕. Emojis are a tokenized match, meaning that your emoji will be matched against the tokenized text of the Tweet body – tokenization is based on punctuation, symbol/emoji, and separator Unicode basic plane characters. Matches an emoji within the body of a Tweet. Note: This operator will match on both URLs and unwound URLs within a Tweet. Note: With the Search API, accented and special characters are normalized to standard latin characters, which can change meanings in foreign languages or return unexpected results:įor example, "músic" will match “music” and vice versa.įor example, common phrases like "Feliz Año Nuevo!" in Spanish, would be indexed as "Feliz Ano Nuevo", which changes the meaning of the phrase.
To match strings containing punctuation (for example, coca-cola), symbol, or separator characters, you must use a quoted exact match as described below. These tokens would then be compared to the keyword string used in your rule. For example, a Tweet with the text “I like coca-cola” would be split into the following tokens: I, like, coca, cola. This is a tokenized match, meaning that your keyword string will be matched against the tokenized text of the Tweet body – tokenization is based on punctuation, symbol, and separator Unicode basic plane characters. Matches a tokenized keyword within the body or urls of a Tweet. Below is a list of all operators supported in Twitter's premium and enterprise search APIs:įor a side-by-side comparison of available operators by product see HERE.
0 kommentar(er)
