# Quicktrends operator list
{% hint style="info" %}
The ***CTRL+F*** command and ***Command+F*** on a Macbook allows you to easily find your filter in the table.
{% endhint %}
{% hint style="success" %}
You can download this page in PDF by clicking on Export as a PDF one the right corner of the screen.
{% endhint %}
### Boolean operators list
| Symbol | Use | Example |
| :---------: | :---------------------------------------------------------------------------------: | :--------------------------------------------------------------------------------------------------------------------------------------: |
| A space | To relate words, equals "AND". | bank scandal
To search for all the posts containing these 2 key-words, no matter their position in the post.
|
| OR | To search for a word or another.
Equals the logical "OR".
| scandal OR boycott
To search for the posts containing at least one of these key-words.
|
| The sign - | To remove a word. | -bank
For not collecting the publications that contain this word.
|
| Brackets () | To bring words together. By default the "AND" (space) has the priority on the "OR". | (scandal OR boycott)
bank
(scandal OR boycott)
(banks OR bank)
scandal bank -(director OR CEO)
|
Each line is independent (a new line equals OR with brackets around the line).
{% hint style="danger" %}
It's not necessary to put all the variants with and without capital letter : Visibrain considers all the letter cases variants. \
\
On the contrary you need to list the different variant of accentuations (é, à, ç, û, ï ...). \
Indeed, Visibrain considers a word with accent differently than the word without accent.
{% endhint %}
#### Operators on the content
| Operator | Explanation | Example |
| ----------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Key-word** | It catches all the posts containing this key-word with or without an hashtag before it. | car
It catches all the posts containing the key-word "car" or the hashtag #car.
|
| **"the exact expression"** | It catches all the posts containing that exact expression, in this order. | "blue car"
It catches all the posts with the key-expression "blue car" in it.
Nevertheless it doesn't catch that : "blue auto and yellow car".
|
| **#hashtag** | It catches all the posts containing the hashtag. | #car
It catches all the posts containing the #car.
|
| **emoji** | It catches all the posts containing a specific emoji. | 😂
It catches all the posts containing the emoji "joy".
|
| **contains:element** | It catches all the posts containing "element" even if it's a part of a word.
It doesn't work for taking datas back.
| contains:account
It catches: account, accounting, accountability ...
But also: unaccountable, unaccountably ...
|
| **lang:xx** | It allows you to catch all the posts in a specific language.
XX = language abbreviation.
The main languages : fr (french), en (english), es (spanish), ja (japanese).
Check the list of available languages.
| moto lang:fr
It catches all the french speaking posts containing the key-word "moto".
moto -lang:ja
It doesn't catch any japanese sepaking post.
|
| url:key-word
url:"the-exact-expression"
| It catches all the internet contents whose URL contains the key-word (or the key-expression). | url:"lemonde.fr"
It catches all the posts from the lemonde.fr website.
|
{% hint style="success" %}
There's no need to write the different variation with or without a capital letter : Visibrain constantly considers all the variants of the case letter.
{% endhint %}
{% hint style="info" %}
On the contrary, you must list all the different accents variations. Indeed, Visibrain makes a difference between a word with an accent and a word without an accent.
{% endhint %}
### Operators on **X (formerly Twitter)** accounts
| Operator | Explanation | |
| --------------------- | ------------------------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **from:user** | It catches all the activity of the X (formerly Twitter) account @user. | from:lemondefr
It catches when @lemondefr tweets are when he retweets an other account.
It doesn't catch when another account retweets @lemondefr.
|
| **retweets\_of:user** | It catches all the retweets (done by other accounts) of the tweets written by @user. | retweets\_of:lemondefr
It catches when @journalist1 retweets a tweet of @lemondefr.
It doesn't catch the initial tweet of @lemondefr.
|
| **@user** | It catches a tweet that mentions @user. | @bouyguestelecom
It catches when a user writes a tweet as " I have a new phone plan @bouyguestelecom" or "@bouyguestelecom I have a question about my phone plan".
It doesn't catch @bouyguestelecom's tweets.
|
| **to:user** | It catches all the answers addressed to the user @user. | to:LDLC
It will catch all the answers addressed to @LDLC's tweets and all the tweets starting with "@LDLC ..."
It doesn't catch @LDLC's tweets.
|
{% hint style="danger" %}
The operators : **from: retweets\_of:** and **url:** are used without the @'s user. \
If you put the @, your rule will not work.
{% endhint %}
{% hint style="info" %}
**Don't forget the operator from:user**\
The operators **retweets-of:user**, **@user** or **to:user** used with nothing else will not catch the @user's tweets. You could get informations that are not relevant. \
We recommend you to constantly use them with the operator **from:**\
For example: \
**from:user**\
**retweets\_of:user**
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://help.visibrain.com/filters-and-helpful-documents/quicktrends-operator-list.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.