> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nekt.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Stilingue as a data source

> Bring your Stilingue (Blip) Listening posts and reports, owned page posts and metrics, and Smart Care service data to Nekt.

Stilingue (now part of Blip) is a social listening and customer care platform. Its Warroom collects posts about your brand from social networks, news and blogs (**Listening**), measures the pages your brand owns (**Owned Metrics**, Métricas Proprietárias) and lets your team answer customers on social networks (**Smart Care**). This connector reads all three through the Stilingue API.

![](https://mintcdn.com/nekt/43FsQ37QF_gxIqKI/assets/logo/logo-blip.png?fit=max\&auto=format\&n=43FsQ37QF_gxIqKI\&q=85\&s=c682618ef0f95b44b41ce64b594e3342)

> [!NOTE]
>
> The connector only reads data. It never answers, classifies, tags or changes anything in Stilingue.

## Before you start

* **The API module must be contracted.** Ask your Stilingue CSM to enable API access for the search (panel) you want to sync.
* **One token per search.** Stilingue creates the API token for one search, and the same token reads that search's Listening, Owned Metrics and Smart Care. To sync several searches, create one Nekt source per search.
* **Only a Master user can create the token.** In Warroom, open **Otimizar > Editar pesquisa** (or `https://warroom.stilingue.com.br/editarpesquisa/ACCOUNT_ID/PANEL_ID`), find the section **Crie a API-Token para essa pesquisa** and click **Criar API-Token**. If the section does not appear, the API module is not contracted for that search.
* **Stilingue may delete tokens that are not used for a while.** If the sync log says the token was rejected, create a new one and update the source.

## Configuring Stilingue as a Source

In the [Sources](https://app.nekt.ai/sources) tab, click on the "Add source" button located on the top right of your screen. Then, select the Stilingue option from the list of connectors.

Click **Next** and you'll be prompted to add your access.

### 1. Add account access

The following configurations are available:

* **API Token**: The API token of the Stilingue search, created as described above.
* **Start Date**: The earliest date read on the first sync and on full syncs. We recommend **at most 90 days** back (see the tip below).
* **Lookback Days** (advanced, default 3): How many days before the last sync are read again on every sync, so late changes reach your tables (posts collected or reclassified later, Smart Care cases updated). Owned post metrics and owned daily charts are always refreshed for the last 30 days.

| Tables | What the search's API contract must include |
| - | - |
| `listening_*` | Listening |
| `owned_*` | Owned Metrics (Métricas Proprietárias), with the brand's pages connected to the search |
| `smartcare_*` | Smart Care |

> [!WARNING]
>
> If Stilingue refuses one of these products for the token, its tables are skipped (the sync log names them) and the other tables keep syncing. Ask your Stilingue CSM to include the product in the search's API contract, or deselect those tables. If Stilingue refuses only one connected page, or one chart of a page, only that page or chart is left out (the sync log names it) and the rest of Owned Metrics is read.

> [!TIP]
>
> The first sync reads the daily reports one day at a time. With every table selected, each day of history costs about 16 requests to Stilingue, which can take up to 60 seconds to answer a query: 90 days take about 1,500 requests (usually 30 to 75 minutes), a year about 6,000 requests (several hours). Later syncs only read the last days again (about 130 requests). Start with 90 days or less, and deselect the tables you do not need.

Once you're done, click **Next**.

### 2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis. You can select entire groups of streams or pick specific ones.

> Tip: The stream can be found more easily by typing its name.

Select the streams and click **Next**.

### 3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.

* **Layer**: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
* **Folder**: a folder can be created inside the selected layer to group all tables being created from this new data source.
* **Table name**: we suggest a name, but feel free to customize it. You have the option to add a **prefix** to all tables at once and make this process faster!
* **Sync Type**: you can choose between INCREMENTAL and FULL\_TABLE.
  * Incremental: every time the extraction happens, we'll get only the new data, which is good if, for example, you want to keep every record ever fetched.
  * Full table: every time the extraction happens, we'll get the current state of the data, which is good if, for example, you don't want to have deleted data in your catalog.

> [!TIP]
>
> Keep the tables as INCREMENTAL. As FULL\_TABLE, every sync reads everything again from the Start Date, one request per day for the daily reports.

Once you are done configuring, click **Next**.

### 4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters.

To define your [Trigger](https://docs.nekt.com/runs/scheduling-and-triggers.md), consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).

Optionally, you can define some additional settings:

* Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource [here](https://docs.nekt.com/get-started/core-concepts/resource-control).
* Determine when to execute an **Additional [Full Sync](https://docs.nekt.com/get-started/core-concepts/types-of-sync#additional-full-sync)**. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.

Once you are ready, click **Next** to finalize the setup.

### 5. Check your new source

You can view your new source on the [Sources](https://app.nekt.ai/sources) page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.

> [!WARNING]
>
> For you to be able to see it on your [Catalog](https://app.nekt.ai/catalog), you need at least one successful source run.

# Streams and Fields

## Available streams

The table below lists every stream and its **slug** (the exact identifier to pass when creating the source via API).

| Stream | Slug | Description |
| - | - | - |
| Listening Posts | `listening_posts` | Posts collected by the search (Warroom > Publicações): posts, comments, mentions, with metrics and classification. Synced by the time Stilingue last changed them. |
| Listening Press Posts | `listening_press_posts` | Press clippings (Mural de imprensa): news portals and blogs imported from clipping services. |
| Listening Overview | `listening_overview` | Daily overview of the search (Visão Geral): collected posts, users, reach, sentiment indexes. |
| Listening Posts Over Time | `listening_posts_over_time` | Number of posts collected per day. |
| Listening Sentiment by Themes / Groups / Searches / Tags / Hashtags / Domains / Links / Terms | `listening_sentiment_by_themes`, `listening_sentiment_by_groups`, `listening_sentiment_by_searches`, `listening_sentiment_by_tags`, `listening_sentiment_by_hashtags`, `listening_sentiment_by_domains`, `listening_sentiment_by_links`, `listening_sentiment_by_terms` | Positive, negative and neutral posts per day, channel and item. The channel `all` sums every channel. |
| Listening Sentiment by Regions | `listening_sentiment_by_regions` | Sentiment per day by country, state, mesoregion and city. |
| Listening Top Influencers | `listening_top_influencers` | Influencer ranking (Ranking AAA) of each day. |
| Listening Headlines | `listening_headlines` | News headlines shared on Facebook and Twitter (Manchetes sociais), per day. |
| Owned Pages | `owned_pages` | Pages connected to the search (Facebook, Instagram, LinkedIn, YouTube, Twitter, TikTok...). |
| Owned Posts | `owned_posts` | Posts of the connected pages with their metrics (impressions, reach, interactions, paid or organic). |
| Owned Page Daily Metrics | `owned_page_daily_metrics` | Every daily chart of Métricas Proprietárias, one row per page, chart, metric, post type and day. |
| Smart Care Cases | `smartcare_cases` | Smart Care cases of each day, with status, SLA and times to answer and close. |
| Smart Care Conversations | `smartcare_conversations` | Smart Care conversations of each day, with their SLA figures. |
| Smart Care Interactions | `smartcare_interactions` | Messages, comments and mentions handled in Smart Care. |
| Smart Care Status Changes | `smartcare_status_changes` | Every status change of a conversation, with operator and SLA. |

## Things to know

* **Days.** Daily tables have one row per Brasília calendar day (`report_date`). Today is read too, and read again on the next sync. Each sync reads the last **Lookback Days** again, because Stilingue keeps collecting and classifying posts after they are published.
* **Owned metrics keep changing for 30 days.** Stilingue updates post metrics for 30 days and credits interactions to the day the post was published, so `owned_posts` and `owned_page_daily_metrics` re-read the last 30 days on every sync.
* **Owned charts per channel.** `owned_page_daily_metrics` reads, for Facebook pages: posts x interactions, fan base, organic and paid impressions, interactions, page likes, interaction rate, reach and engagement, activated posts, paid vs organic posts and the Facebook page metrics (Meta metric names, such as `page_impressions`); for Instagram: posts x interactions, interactions volume, fan base, reach, impressions and views over time (split by post type) and story interactions (Instagram keeps only the last 30 days); for LinkedIn, YouTube, Twitter and TikTok: posts x interactions and interactions volume. A chart that Stilingue does not provide or does not allow for a page is left out (the sync log says so). Averages over a period shown in Warroom are not loaded; compute them from the daily rows.
* **Smart Care cases are figures of the day.** Cases and conversations come from the Smart Care report of each day, so their key includes `report_date`. Their status is the status when the report was read; days with cases still open are read again on later syncs (for up to 30 days) until those cases are closed or ignored. A case closed after that still appears in `smartcare_status_changes`, as the status change that closed it (on the day of the change); a Full sync also refreshes the older days of `smartcare_cases` and `smartcare_conversations`.
* **Listening posts can be many.** A search that collects a lot of posts produces a large `listening_posts` table, and posts come back every time Stilingue updates their metrics. Select it only if you need the posts themselves; the daily report tables already summarize them.
* **Not available through the API.** Benchmarks, and the Warroom charts that only rearrange data already in these tables (Onde/Quando estão falando, Ranking Evolutivo, Temas e Tópicos, Termos correlacionados), are not synced.
* **Personal data.** Stilingue removes some personal data of social network users for compliance (some fields are always empty). Smart Care tables include data of your customers (names, usernames, messages). Handle them according to your data protection policies.

## Fields by stream

Below you'll find all available data streams from Stilingue and their corresponding fields:

> [accordion] Listening Posts
>
> Stream `listening_posts`. Incremental on `updated_at`; key `pid`.
>
> * `pid` - Unique identifier of the post (pid); comments, mentions and inbox messages are posts too
> * `updated_at` - Last time Stilingue changed the post (metrics, classification, tags, annotations), from long\_updated\_at
> * `posted_at` - When the post was published on the social network (UTC)
> * `crawled_at` - When Stilingue collected the post (UTC)
> * `metrics_updated_at` - Last time the post's metrics were updated (UTC)
> * `long_posted_at` - Publication time as a UNIX timestamp in milliseconds
> * `long_updated_at` - Last update time as a UNIX timestamp in milliseconds
> * `aaa_score` - Stilingue's AAA score: relevance of the author as a potential influencer
> * `anonymous_user` - Whether the author is anonymous
> * `attachments` - Media attached to the post (videos, images): id, name, size, media\_type, type, url, storage\_url (JSON)
> * `channel` - Source channel of the post (e.g. Twitter, Instagram, InstagramComments, Facebook, FacebookComments, YouTube, News, Blogs, Linkedin, Tiktok)
> * `primary_channel` - Social network where the post was made (Twitter, Instagram, Facebook, YouTube, News, Blogs, Linkedin)
> * `title` - Title of the post (may be empty)
> * `text` - Text content of the post
> * `text_append` - Additional information about the post or interaction (e.g. 'Comentado em: \[video name]' for YouTube comments)
> * `type` - Type of the post: video, image, carrossel (Instagram only) or post
> * `lang` - Language of the post: pt, en, es
> * `post_url` - URL of the root post
> * `post_id` - Root post id when this post is an interaction on another post (e.g. a comment)
> * `root_id` - Id of the root (main) publication
> * `reply_pid` - pid of the post this post replied to (for a reply to a comment, the comment's pid)
> * `is_root` - Whether this is the main message of the conversation
> * `uid` - Identifier of the author (user) of the post
> * `username` - Username of the account that made the post
> * `name` - Name of the author (available only for some channels)
> * `gender` - Gender of the author: empty, Homem, Mulher or Marca (brand)
> * `verified` - Whether the author's account is verified
> * `followers` - Number of followers of the author or page
> * `location` - Location of the author
> * `user_url` - URL of the author's account
> * `user_image_url` - URL of the author's profile picture
> * `post_user_image_url` - URL of the profile picture of the page that made the post
> * `image_url` - URL of the post's image
> * `url_content` - Direct URL of the post's video (when type is video)
> * `comments` - Number of comments on the post
> * `likes` - Number of likes on the post
> * `dislikes` - Number of dislikes on the post
> * `shares` - Number of shares of the post
> * `reactions` - Number of reactions to the post
> * `interactions` - Total interactions on the post (comments, likes, shares, etc.)
> * `videoplays` - Number of times the video was played (when type is video)
> * `reaction_like` - Facebook 'like' reactions
> * `reaction_love` - Facebook 'love' reactions
> * `reaction_haha` - Facebook 'haha' reactions
> * `reaction_wow` - Facebook 'wow' reactions
> * `reaction_sad` - Facebook 'sad' reactions
> * `reaction_angry` - Facebook 'angry' reactions
> * `reaction_pride` - Facebook 'pride' reactions
> * `reaction_thankful` - Facebook 'thankful' reactions
> * `reaction_total` - Total Facebook reactions
> * `sentiment` - Sentiment of the post: -1 negative, 0 neutral, 1 positive
> * `critical_level` - Criticality level assigned to the post
> * `hot` - Internal score of how much the post keeps resonating on the network
> * `hot_post` - Whether the post is among the 20 hottest posts
> * `groups` - Search groups associated with the post
> * `themes` - Themes associated with the post
> * `tags` - Tags applied to the post
> * `hashtags` - Hashtags in the post
> * `mentions` - Usernames mentioned in the post
> * `interests` - Interests of the author (e.g. Tecnologia & Computação)
> * `features` - Internal processing markers (FEED, REELS)
> * `contact_reasons` - Contact reasons assigned to the post (only for some accounts)
> * `pages` - Ids of the connected pages the post belongs to
> * `page_id` - Id of the connected owned page that made the post
> * `page_comment` - Whether the interaction or post was made by the page
> * `interacted_page_id` - Id of the page that interacted with the post
> * `interacted_page_name` - Name of the page that interacted with the post
> * `processed_by_performance` - True for owned posts (connected pages), false for listening posts
> * `fb_pid` - Facebook id of the post
> * `fb_uid` - Facebook id of the author
> * `favorite` - Whether the post is marked as checked in Warroom
> * `spam` - Whether the post was marked to be deleted (spam)
> * `hidden_by_user` - Whether the message was hidden by the user
> * `is_hidden` - Whether the post is private
> * `is_dynamic_post` - Whether the post is dynamic
> * `status` - Conversation status: Ignorado, Pendente, Aberto, Em Espera, Respondido, Fechado
> * `sac_type` - Conversation type: posts, comentarios, inbox, postvisitantes, comentariosvisitantes, reviews, comentariosreview, mentions, comentariosmentions
> * `sac_call_id` - Stilingue internal id of the main interaction of the conversation
> * `talk_id` - Conversation id
> * `operator_id` - Id of the Smart Care operator who answered the conversation
> * `operator_name` - Name of the Smart Care operator who answered the conversation
> * `replier` - Who answered the conversation
> * `replier_name` - Name of who answered the conversation
> * `receiver` - Recipient/sender of an inbox message: id, email, name, image\_url (JSON)
> * `to` - Recipient of the message (inbox)
> * `update_time_ago` - How long ago the post was edited (or 'Nunca editado')
> * `machine_learning` - Machine-learning data associated with the post (JSON)
> * `emotion` - Deprecated emotion value (unused since 2018)
> * `extra_fields` - Fields the API returned that this connector does not map to a column yet, keyed by their original names (JSON)

> [accordion] Listening Press Posts
>
> Stream `listening_press_posts`. Incremental on `posted_at`; key `pid`.
>
> * `pid` - Unique identifier of the post (pid); comments, mentions and inbox messages are posts too
> * `updated_at` - Last time Stilingue changed the post (metrics, classification, tags, annotations), from long\_updated\_at
> * `posted_at` - When the post was published on the social network (UTC)
> * `crawled_at` - When Stilingue collected the post (UTC)
> * `metrics_updated_at` - Last time the post's metrics were updated (UTC)
> * `long_posted_at` - Publication time as a UNIX timestamp in milliseconds
> * `long_updated_at` - Last update time as a UNIX timestamp in milliseconds
> * `aaa_score` - Stilingue's AAA score: relevance of the author as a potential influencer
> * `anonymous_user` - Whether the author is anonymous
> * `attachments` - Media attached to the post (videos, images): id, name, size, media\_type, type, url, storage\_url (JSON)
> * `channel` - Source channel of the post (e.g. Twitter, Instagram, InstagramComments, Facebook, FacebookComments, YouTube, News, Blogs, Linkedin, Tiktok)
> * `primary_channel` - Social network where the post was made (Twitter, Instagram, Facebook, YouTube, News, Blogs, Linkedin)
> * `title` - Title of the post (may be empty)
> * `text` - Text content of the post
> * `text_append` - Additional information about the post or interaction (e.g. 'Comentado em: \[video name]' for YouTube comments)
> * `type` - Type of the post: video, image, carrossel (Instagram only) or post
> * `lang` - Language of the post: pt, en, es
> * `post_url` - URL of the root post
> * `post_id` - Root post id when this post is an interaction on another post (e.g. a comment)
> * `root_id` - Id of the root (main) publication
> * `reply_pid` - pid of the post this post replied to (for a reply to a comment, the comment's pid)
> * `is_root` - Whether this is the main message of the conversation
> * `uid` - Identifier of the author (user) of the post
> * `username` - Username of the account that made the post
> * `name` - Name of the author (available only for some channels)
> * `gender` - Gender of the author: empty, Homem, Mulher or Marca (brand)
> * `verified` - Whether the author's account is verified
> * `followers` - Number of followers of the author or page
> * `location` - Location of the author
> * `user_url` - URL of the author's account
> * `user_image_url` - URL of the author's profile picture
> * `post_user_image_url` - URL of the profile picture of the page that made the post
> * `image_url` - URL of the post's image
> * `url_content` - Direct URL of the post's video (when type is video)
> * `comments` - Number of comments on the post
> * `likes` - Number of likes on the post
> * `dislikes` - Number of dislikes on the post
> * `shares` - Number of shares of the post
> * `reactions` - Number of reactions to the post
> * `interactions` - Total interactions on the post (comments, likes, shares, etc.)
> * `videoplays` - Number of times the video was played (when type is video)
> * `reaction_like` - Facebook 'like' reactions
> * `reaction_love` - Facebook 'love' reactions
> * `reaction_haha` - Facebook 'haha' reactions
> * `reaction_wow` - Facebook 'wow' reactions
> * `reaction_sad` - Facebook 'sad' reactions
> * `reaction_angry` - Facebook 'angry' reactions
> * `reaction_pride` - Facebook 'pride' reactions
> * `reaction_thankful` - Facebook 'thankful' reactions
> * `reaction_total` - Total Facebook reactions
> * `sentiment` - Sentiment of the post: -1 negative, 0 neutral, 1 positive
> * `critical_level` - Criticality level assigned to the post
> * `hot` - Internal score of how much the post keeps resonating on the network
> * `hot_post` - Whether the post is among the 20 hottest posts
> * `groups` - Search groups associated with the post
> * `themes` - Themes associated with the post
> * `tags` - Tags applied to the post
> * `hashtags` - Hashtags in the post
> * `mentions` - Usernames mentioned in the post
> * `interests` - Interests of the author (e.g. Tecnologia & Computação)
> * `features` - Internal processing markers (FEED, REELS)
> * `contact_reasons` - Contact reasons assigned to the post (only for some accounts)
> * `pages` - Ids of the connected pages the post belongs to
> * `page_id` - Id of the connected owned page that made the post
> * `page_comment` - Whether the interaction or post was made by the page
> * `interacted_page_id` - Id of the page that interacted with the post
> * `interacted_page_name` - Name of the page that interacted with the post
> * `processed_by_performance` - True for owned posts (connected pages), false for listening posts
> * `fb_pid` - Facebook id of the post
> * `fb_uid` - Facebook id of the author
> * `favorite` - Whether the post is marked as checked in Warroom
> * `spam` - Whether the post was marked to be deleted (spam)
> * `hidden_by_user` - Whether the message was hidden by the user
> * `is_hidden` - Whether the post is private
> * `is_dynamic_post` - Whether the post is dynamic
> * `status` - Conversation status: Ignorado, Pendente, Aberto, Em Espera, Respondido, Fechado
> * `sac_type` - Conversation type: posts, comentarios, inbox, postvisitantes, comentariosvisitantes, reviews, comentariosreview, mentions, comentariosmentions
> * `sac_call_id` - Stilingue internal id of the main interaction of the conversation
> * `talk_id` - Conversation id
> * `operator_id` - Id of the Smart Care operator who answered the conversation
> * `operator_name` - Name of the Smart Care operator who answered the conversation
> * `replier` - Who answered the conversation
> * `replier_name` - Name of who answered the conversation
> * `receiver` - Recipient/sender of an inbox message: id, email, name, image\_url (JSON)
> * `to` - Recipient of the message (inbox)
> * `update_time_ago` - How long ago the post was edited (or 'Nunca editado')
> * `machine_learning` - Machine-learning data associated with the post (JSON)
> * `emotion` - Deprecated emotion value (unused since 2018)
> * `summary_text` - HTML content of the publication's text
> * `computer_vision` - Text found in images of the publication, when any (JSON)
> * `extra_fields` - Fields the API returned that this connector does not map to a column yet, keyed by their original names (JSON)

> [accordion] Listening Overview
>
> Stream `listening_overview`. Incremental on `report_date`; key `report_date`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `date_range` - Date range echoed by Stilingue for the request (AAAAMMDDHHmm|AAAAMMDDHHmm)
> * `collected_mentions` - Number of posts collected in the day
> * `collected_mentions_variation` - Variation (%) of collected posts against the previous period of the same length
> * `previous_collected_mentions` - Posts collected in the previous period
> * `previous_date_range` - Date range of the previous period used for the variations
> * `total_localized_mentions` - Number of collected posts with a location
> * `total_users` - Total number of distinct users
> * `total_users_variation` - Variation (%) of the total users against the previous period
> * `potential_reach` - Potential reach
> * `potential_reach_variation` - Variation (%) of the potential reach against the previous period
> * `previous_potential_reach` - Potential reach of the previous period
> * `net_promoter_score` - Sentiment index
> * `net_promoter_score_variation` - Variation (%) of the sentiment index against the previous period
> * `previous_net_promoter_score` - Sentiment index of the previous period
> * `net_sentiment` - Net sentiment (positive minus negative posts)
> * `net_sentiment_score` - Net sentiment score
> * `net_sentiment_score_variation` - Variation (%) of the net sentiment score against the previous period
> * `previous_net_sentiment` - Net sentiment of the previous period
> * `previous_net_sentiment_score` - Net sentiment score of the previous period
> * `channels` - Posts per channel (JSON)
> * `general_sentiment` - Distribution of sentiment: positive\_value, negative\_value, neutral\_value, not\_classified\_value (JSON)
> * `influencers_list` - Influencer ranking shown in the overview (JSON)
> * `influencers_static` - Internal flag of the influencer list
> * `talking_about` - Distribution of posts by device, gender and interest (JSON)

> [accordion] Listening Posts Over Time
>
> Stream `listening_posts_over_time`. Incremental on `report_date`; key `report_date`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `posts_count` - Number of posts collected for the day

> [accordion] Listening Sentiment By Themes
>
> Stream `listening_sentiment_by_themes`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the theme
> * `positive` - Posts with positive sentiment for the theme
> * `negative` - Posts with negative sentiment for the theme
> * `neutral` - Posts with neutral sentiment for the theme
> * `not_classified` - Posts without a sentiment classification for the theme
> * `total` - Total posts for the theme
> * `total_polarity_classified` - Posts of the theme with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)

> [accordion] Listening Sentiment By Groups
>
> Stream `listening_sentiment_by_groups`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the group
> * `positive` - Posts with positive sentiment for the group
> * `negative` - Posts with negative sentiment for the group
> * `neutral` - Posts with neutral sentiment for the group
> * `not_classified` - Posts without a sentiment classification for the group
> * `total` - Total posts for the group
> * `total_polarity_classified` - Posts of the group with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)

> [accordion] Listening Sentiment By Searches
>
> Stream `listening_sentiment_by_searches`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the search
> * `positive` - Posts with positive sentiment for the search
> * `negative` - Posts with negative sentiment for the search
> * `neutral` - Posts with neutral sentiment for the search
> * `not_classified` - Posts without a sentiment classification for the search
> * `total` - Total posts for the search
> * `total_polarity_classified` - Posts of the search with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)

> [accordion] Listening Sentiment By Tags
>
> Stream `listening_sentiment_by_tags`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the tag
> * `positive` - Posts with positive sentiment for the tag
> * `negative` - Posts with negative sentiment for the tag
> * `neutral` - Posts with neutral sentiment for the tag
> * `not_classified` - Posts without a sentiment classification for the tag
> * `total` - Total posts for the tag
> * `total_polarity_classified` - Posts of the tag with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)

> [accordion] Listening Sentiment By Hashtags
>
> Stream `listening_sentiment_by_hashtags`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the hashtag
> * `positive` - Posts with positive sentiment for the hashtag
> * `negative` - Posts with negative sentiment for the hashtag
> * `neutral` - Posts with neutral sentiment for the hashtag
> * `not_classified` - Posts without a sentiment classification for the hashtag
> * `total` - Total posts for the hashtag
> * `total_polarity_classified` - Posts of the hashtag with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)

> [accordion] Listening Sentiment By Domains
>
> Stream `listening_sentiment_by_domains`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the domain
> * `positive` - Posts with positive sentiment for the domain
> * `negative` - Posts with negative sentiment for the domain
> * `neutral` - Posts with neutral sentiment for the domain
> * `not_classified` - Posts without a sentiment classification for the domain
> * `total` - Total posts for the domain
> * `total_polarity_classified` - Posts of the domain with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)

> [accordion] Listening Sentiment By Links
>
> Stream `listening_sentiment_by_links`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the link
> * `positive` - Posts with positive sentiment for the link
> * `negative` - Posts with negative sentiment for the link
> * `neutral` - Posts with neutral sentiment for the link
> * `not_classified` - Posts without a sentiment classification for the link
> * `total` - Total posts for the link
> * `total_polarity_classified` - Posts of the link with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)

> [accordion] Listening Sentiment By Terms
>
> Stream `listening_sentiment_by_terms`. Incremental on `report_date`; key `report_date`, `channel`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel the figures refer to, as Stilingue names it ('all' sums every channel)
> * `name` - Name of the term
> * `positive` - Posts with positive sentiment for the term
> * `negative` - Posts with negative sentiment for the term
> * `neutral` - Posts with neutral sentiment for the term
> * `not_classified` - Posts without a sentiment classification for the term
> * `total` - Total posts for the term
> * `total_polarity_classified` - Posts of the term with a sentiment classification
> * `total_posts` - Total posts of the day in the search (all items)
> * `absorbed_names` - Similar words counted together with this term

> [accordion] Listening Sentiment By Regions
>
> Stream `listening_sentiment_by_regions`. Incremental on `report_date`; key `report_date`, `region_level`, `name`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `region_level` - Level of the region as Stilingue names it (Países, Regiões, Estados, Mesorregiões, Cidades...)
> * `name` - Name of the region
> * `positive` - Posts classified as positive
> * `negative` - Posts classified as negative
> * `neutral` - Posts classified as neutral
> * `total` - Total posts of the region
> * `total_classified` - Posts of the region with a sentiment classification
> * `total_posts` - Total posts of the day in the search

> [accordion] Listening Top Influencers
>
> Stream `listening_top_influencers`. Incremental on `report_date`; key `report_date`, `channel`, `uid`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `channel` - Channel of the influencer's profile
> * `uid` - Identifier of the influencer's profile
> * `name` - Name of the influencer's profile
> * `username` - Username of the influencer's profile
> * `url` - URL of the influencer's profile
> * `is_verified` - Whether the profile is verified
> * `occupation` - Interest/occupation of the influencer
> * `position` - Position of the profile in the ranking
> * `rank` - Order of the profile in the day's answer (1 = first)
> * `followers` - Number of followers of the influencer
> * `posts_count` - Number of posts of the influencer in the day
> * `groups` - Search groups the influencer's posts matched
> * `ranking_3as` - AAA ranking score
> * `ranking_harmonic_mean` - AAA ranking (harmonic mean)
> * `afinity_score` - Internal affinity score
> * `afinity_normalized` - Affinity score normalized for the Warroom
> * `assertiviness_score` - Sum of the virality of the posts divided by log10 of the followers
> * `followers_score` - Internal score of how engaged the followers are
> * `reach_score` - Square root of the number of followers
> * `reach_normalized` - Reach normalized for the Warroom
> * `virality_score` - Internal score of how viral the posts are
> * `viralization_normalized` - Virality normalized for the Warroom

> [accordion] Listening Headlines
>
> Stream `listening_headlines`. Incremental on `report_date`; key `report_date`, `channel`, `uid`, `published_at_raw`, `title`.
>
> * `report_date` - Day the figures refer to (a Brasília calendar day, asked as that whole day); used as the incremental replication key
> * `published_at_raw` - Publication time exactly as Stilingue sends it (dd/MM/aaaa HH:mm); part of the key
> * `channel` - Channel where the headline was shared (Facebook or Twitter)
> * `uid` - Identifier of the user that published the headline
> * `user` - Name of the user that published the headline
> * `title` - Title of the shared headline
> * `published_at` - When the headline was published (UTC)
> * `sentiment` - Sentiment of the headline: -1 negative, 0 neutral, 1 positive
> * `weight` - Weight of the headline in the ranking
> * `real_weight` - Real weight of the headline
> * `available_time` - Time the headline has been available

> [accordion] Owned Pages
>
> Stream `owned_pages`. Full table; key `channel`, `id`.
>
> * `id` - Identifier of the connected page on its social network
> * `channel` - Social network of the page, as Stilingue names it (e.g. Facebook, Instagram, TikTok)
> * `username` - Username of the page on that social network
> * `path_channel` - Lowercase channel used by this connector to read the page's posts and charts (empty when the channel is not supported)

> [accordion] Owned Posts
>
> Stream `owned_posts`. Incremental on `posted_at`; key `pid`.
>
> * `pid` - Unique identifier of the post (pid); comments, mentions and inbox messages are posts too
> * `updated_at` - Last time Stilingue changed the post (metrics, classification, tags, annotations), from long\_updated\_at
> * `posted_at` - When the post was published on the social network (UTC)
> * `crawled_at` - When Stilingue collected the post (UTC)
> * `metrics_updated_at` - Last time the post's metrics were updated (UTC)
> * `long_posted_at` - Publication time as a UNIX timestamp in milliseconds
> * `long_updated_at` - Last update time as a UNIX timestamp in milliseconds
> * `aaa_score` - Stilingue's AAA score: relevance of the author as a potential influencer
> * `anonymous_user` - Whether the author is anonymous
> * `attachments` - Media attached to the post (videos, images): id, name, size, media\_type, type, url, storage\_url (JSON)
> * `channel` - Source channel of the post (e.g. Twitter, Instagram, InstagramComments, Facebook, FacebookComments, YouTube, News, Blogs, Linkedin, Tiktok)
> * `primary_channel` - Social network where the post was made (Twitter, Instagram, Facebook, YouTube, News, Blogs, Linkedin)
> * `title` - Title of the post (may be empty)
> * `text` - Text content of the post
> * `text_append` - Additional information about the post or interaction (e.g. 'Comentado em: \[video name]' for YouTube comments)
> * `type` - Type of the post: video, image, carrossel (Instagram only) or post
> * `lang` - Language of the post: pt, en, es
> * `post_url` - URL of the root post
> * `post_id` - Root post id when this post is an interaction on another post (e.g. a comment)
> * `root_id` - Id of the root (main) publication
> * `reply_pid` - pid of the post this post replied to (for a reply to a comment, the comment's pid)
> * `is_root` - Whether this is the main message of the conversation
> * `uid` - Identifier of the author (user) of the post
> * `username` - Username of the account that made the post
> * `name` - Name of the author (available only for some channels)
> * `gender` - Gender of the author: empty, Homem, Mulher or Marca (brand)
> * `verified` - Whether the author's account is verified
> * `followers` - Number of followers of the author or page
> * `location` - Location of the author
> * `user_url` - URL of the author's account
> * `user_image_url` - URL of the author's profile picture
> * `post_user_image_url` - URL of the profile picture of the page that made the post
> * `image_url` - URL of the post's image
> * `url_content` - Direct URL of the post's video (when type is video)
> * `comments` - Number of comments on the post
> * `likes` - Number of likes on the post
> * `dislikes` - Number of dislikes on the post
> * `shares` - Number of shares of the post
> * `reactions` - Number of reactions to the post
> * `interactions` - Total interactions on the post (comments, likes, shares, etc.)
> * `videoplays` - Number of times the video was played (when type is video)
> * `reaction_like` - Facebook 'like' reactions
> * `reaction_love` - Facebook 'love' reactions
> * `reaction_haha` - Facebook 'haha' reactions
> * `reaction_wow` - Facebook 'wow' reactions
> * `reaction_sad` - Facebook 'sad' reactions
> * `reaction_angry` - Facebook 'angry' reactions
> * `reaction_pride` - Facebook 'pride' reactions
> * `reaction_thankful` - Facebook 'thankful' reactions
> * `reaction_total` - Total Facebook reactions
> * `sentiment` - Sentiment of the post: -1 negative, 0 neutral, 1 positive
> * `critical_level` - Criticality level assigned to the post
> * `hot` - Internal score of how much the post keeps resonating on the network
> * `hot_post` - Whether the post is among the 20 hottest posts
> * `groups` - Search groups associated with the post
> * `themes` - Themes associated with the post
> * `tags` - Tags applied to the post
> * `hashtags` - Hashtags in the post
> * `mentions` - Usernames mentioned in the post
> * `interests` - Interests of the author (e.g. Tecnologia & Computação)
> * `features` - Internal processing markers (FEED, REELS)
> * `contact_reasons` - Contact reasons assigned to the post (only for some accounts)
> * `pages` - Ids of the connected pages the post belongs to
> * `page_id` - Id of the connected owned page that made the post
> * `page_comment` - Whether the interaction or post was made by the page
> * `interacted_page_id` - Id of the page that interacted with the post
> * `interacted_page_name` - Name of the page that interacted with the post
> * `processed_by_performance` - True for owned posts (connected pages), false for listening posts
> * `fb_pid` - Facebook id of the post
> * `fb_uid` - Facebook id of the author
> * `favorite` - Whether the post is marked as checked in Warroom
> * `spam` - Whether the post was marked to be deleted (spam)
> * `hidden_by_user` - Whether the message was hidden by the user
> * `is_hidden` - Whether the post is private
> * `is_dynamic_post` - Whether the post is dynamic
> * `status` - Conversation status: Ignorado, Pendente, Aberto, Em Espera, Respondido, Fechado
> * `sac_type` - Conversation type: posts, comentarios, inbox, postvisitantes, comentariosvisitantes, reviews, comentariosreview, mentions, comentariosmentions
> * `sac_call_id` - Stilingue internal id of the main interaction of the conversation
> * `talk_id` - Conversation id
> * `operator_id` - Id of the Smart Care operator who answered the conversation
> * `operator_name` - Name of the Smart Care operator who answered the conversation
> * `replier` - Who answered the conversation
> * `replier_name` - Name of who answered the conversation
> * `receiver` - Recipient/sender of an inbox message: id, email, name, image\_url (JSON)
> * `to` - Recipient of the message (inbox)
> * `update_time_ago` - How long ago the post was edited (or 'Nunca editado')
> * `machine_learning` - Machine-learning data associated with the post (JSON)
> * `emotion` - Deprecated emotion value (unused since 2018)
> * `page_channel` - Channel of the connected page the post was read for (lowercase, as used in the API path)
> * `ig_pid` - Instagram id of the post
> * `fb_impressions` - Facebook impressions of the post
> * `fb_reach` - Facebook reach of the post
> * `kpi_engagement` - Total interactions on the post
> * `kpi_saved` - Number of times the post was saved
> * `is_ads` - True for a paid (dark) post, false for an organic post
> * `comments_answers` - Comments answered by the page and comments with answers: answered, total (JSON)
> * `comments_polarities` - Percentage of positive, neutral and negative comments (JSON)
> * `cvtags` - Tags associated with the post (different from hashtags)
> * `integration_name` - Name of the integration the publication came from
> * `text_header` - Header text of the post
> * `reclame_aqui` - Reclame Aqui data of the post (JSON)
> * `same_text` - Number of posts with the same text as this one
> * `same_text_posts` - Ids of posts with the same text as this one
> * `same_user_posts` - Ids of posts made by the same author
> * `extra_fields` - Fields the API returned that this connector does not map to a column yet, keyed by their original names (JSON)

> [accordion] Owned Page Daily Metrics
>
> Stream `owned_page_daily_metrics`. Incremental on `metric_date`; key `page_id`, `report`, `metric`, `breakdown`, `metric_date`.
>
> * `page_id` - Identifier of the connected page
> * `page_channel` - Channel of the page (lowercase, as used in the API path)
> * `report` - Owned chart the value comes from (e.g. interactions, page\_likes, reach\_over\_time, page\_metrics)
> * `metric` - Metric name as Stilingue returns it (e.g. Reações, Novos Fãs (Orgânicos), page\_impressions)
> * `breakdown` - Post type the value is split by (posts, carousels, reels, stories, dark\_posts) or 'total'
> * `metric_date` - Day of the value; used as the incremental replication key
> * `value` - Value of the metric on the day

> [accordion] Smart Care Cases
>
> Stream `smartcare_cases`. Incremental on `report_date`; key `report_date`, `case_id`.
>
> * `report_date` - Day of the Smart Care report the row comes from (a Brasília calendar day); used as the incremental replication key
> * `case_id` - Identifier of the case: the conversation id plus the case number within the day's report
> * `conversation_id` - Identifier of the conversation
> * `channel` - Channel of the page
> * `page_id` - Identifier of the connected owned page
> * `page_name` - Name of the connected owned page
> * `status` - Status of the case when the report was read (Aberto, Pendente, Em Espera, Respondido, Fechado, Ignorado)
> * `interaction_type` - Type of interaction (Comentário, Menção, Inbox, Publicação de visitante...)
> * `init_at` - When the case started (first interaction, or reopening)
> * `end_at` - When the case was closed or ignored
> * `time_to_first_answer` - Seconds until the first status change to Respondido
> * `time_to_close` - Seconds until the case was closed (sum of the times of every status change)
> * `first_answer_configured_sla_time_seconds` - First-answer SLA configured, in seconds
> * `first_answer_is_inside_sla_time` - Whether the first answer was within the configured SLA
> * `extra_fields` - Fields the API returned that this connector does not map to a column yet, keyed by their original names (JSON)

> [accordion] Smart Care Conversations
>
> Stream `smartcare_conversations`. Incremental on `report_date`; key `report_date`, `conversation_id`.
>
> * `report_date` - Day of the Smart Care report the row comes from (a Brasília calendar day); used as the incremental replication key
> * `conversation_id` - Identifier of the conversation
> * `channel` - Social network of the conversation
> * `page_id` - Identifier of the connected owned page
> * `page_name` - Name of the connected owned page
> * `status` - Current status of the conversation when the report was read
> * `interaction_type` - Type of interaction (Comentário, Menção, Inbox, Publicação de visitante...)
> * `interactions_size` - Total interactions (owned and not owned) of the conversation, whatever their date
> * `init_at` - First interaction of the conversation in the day
> * `end_at` - Last status change to Fechado or Ignorado in the day
> * `time_to_first_answer` - Seconds until the first status change to Respondido or Fechado in the day
> * `time_to_close` - Sum of the times of the status changes, when one of them closed or ignored the conversation
> * `first_answer_configured_sla_time_seconds` - First-answer SLA configured, in seconds
> * `first_answer_is_inside_sla_time` - Whether the first answer was within the configured SLA
> * `extra_fields` - Fields the API returned that this connector does not map to a column yet, keyed by their original names (JSON)

> [accordion] Smart Care Interactions
>
> Stream `smartcare_interactions`. Incremental on `report_date`; key `pid`, `conversation_id`.
>
> * `report_date` - Day of the Smart Care report the row comes from (a Brasília calendar day); used as the incremental replication key
> * `pid` - Unique identifier of the interaction
> * `conversation_id` - Conversation the interaction belongs to (empty when the report gives none)
> * `conversation_ids` - Every conversation the interaction belongs to
> * `case_id` - Case the interaction belongs to
> * `conversation_status` - Status of the conversation
> * `channel` - Channel of the interaction
> * `original_channel` - Original channel of the interaction
> * `page_id` - Identifier of the connected owned page
> * `page_name` - Name of the connected owned page
> * `posted_at` - When the interaction was made
> * `processed_at` - When Stilingue collected and processed the interaction
> * `updated_at` - Last update of the interaction in Stilingue
> * `normalized_updated_at` - Last update as AAAAMMDDHHmm, as Stilingue sends it
> * `normalized_metrics_updated_at` - Last metrics update as AAAAMMDDHHmm, as Stilingue sends it
> * `text` - Text of the interaction
> * `post_url` - URL of the interaction (sometimes the publication's URL)
> * `proprietary` - Whether the interaction was made by the owned page itself
> * `polarity` - Sentiment of the interaction: Positivo, Neutro, Negativo
> * `operator_name` - Smart Care operator who answered (the name at the time)
> * `user_id` - Identifier of the social network user who made the interaction
> * `user_name` - Name of the user who made the interaction
> * `user_username` - Username of the user who made the interaction
> * `user_gender` - Gender of the user who made the interaction
> * `user_followers` - Followers of the user who made the interaction
> * `user_crm_user_id` - CRM identifier of the user
> * `tags` - Tags classified on the interaction
> * `themes` - Themes classified on the interaction
> * `groups` - Search groups of the interaction
> * `hashtags` - Hashtags of the interaction
> * `interaction_type` - Type of interaction (Comentário, Menção, Inbox...)
> * `from_promoted` - Whether the interaction is on a boosted publication
> * `belongs_to_sac_call` - Whether the interaction belongs to a Smart Care call
> * `root` - Whether the interaction is the root of the conversation
> * `root_id` - Identifier of the root interaction
> * `duplicated` - Whether the interaction is a duplicate
> * `hidden_by_user` - Whether the interaction was hidden by the user
> * `is_hidden` - Whether the interaction is private
> * `verified` - Whether the author is verified
> * `outside_date_range` - Whether the interaction is outside the day asked (included because of its conversation)
> * `delay` - Time until collection (in days, as Stilingue reports it)
> * `reaction` - Reaction data of the interaction (JSON)
> * `extra_fields` - Fields the API returned that this connector does not map to a column yet, keyed by their original names (JSON)

> [accordion] Smart Care Status Changes
>
> Stream `smartcare_status_changes`. Incremental on `report_date`; key `id`.
>
> * `report_date` - Day of the Smart Care report the row comes from (a Brasília calendar day); used as the incremental replication key
> * `id` - Identifier of the status change
> * `conversation_id` - Conversation whose status changed
> * `comment_id` - Identifier of the comment of the conversation
> * `case_id` - Case of the status change
> * `case_init_at` - When the case of this status change started
> * `channel` - Channel of the conversation
> * `page_id` - Identifier of the connected owned page
> * `page_name` - Name of the connected owned page
> * `operator_id` - Identifier of the Smart Care operator who made the change
> * `operator_name` - Name of the Smart Care operator who made the change
> * `old_value` - Status before the change
> * `new_value` - Status after the change
> * `created_at` - When the status change was made
> * `time_to_status_change` - Seconds until the status change, by the SLA rules
> * `configured_sla_time_seconds` - SLA configured for this change, in seconds
> * `inside_sla_time` - Whether the change was within the configured SLA
> * `first_answer` - Whether this change was the first answer
> * `ending_status` - Whether the new status ends the case
> * `interaction_type` - Type of interaction (Comentário, Menção, Inbox...)
> * `calendar_id` - Identifier of the SLA calendar
> * `relative_posted_at` - Publication time of the related interaction
> * `relative_processed_at` - Processing time of the related interaction
> * `extra_fields` - Fields the API returned that this connector does not map to a column yet, keyed by their original names (JSON)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.