Technical Data & Other Definitions - STILINGUE

Index:

1. Introduction
2. STILINGUE Smart Care and Proprietary Metrics
3. Listening
4. SLA for non-proprietary channels 
5. Social metrics
6. Number of followers 
7. Additional collections
8. Technical restrictions

 

Introduction 

Understand how the collection time operates in each STILINGUE module and how it relates to your research.

STILINGUE operates transparently so that you can access relevant data about your research. See below the main information about the collection time (SLA) and other technical details in different areas of the platform.

Customized Services: Need assistance in calculating and setting goals based on market analyses/trends? We can assist you! Our team of experts is ready to assist you. Contact your STILINGUE account manager to gain access to this and several other services.

 

STILINGUE Smart Care and Proprietary Metrics

For both modules, all collection channels have a 95% SLA between the average time and the time limit (indicated below). The collection expectation is 99.0% of posts within 24 hours after the time limit. These percentages should be calculated using a 24-hour filter for each type of publication and without any other restrictions on the filter, i.e., the overall volume should be analyzed for each type of interaction. 

 

 

Listening

It is guaranteed that 95% of the Survey Configuration data will be collected between the average time and the deadline, and 99% of the collected posts within 24 hours after the deadline. These percentages should be calculated using a 7-day filter for each channel and without any other restrictions on the filter: in other words, the overall volume should be analyzed for each channel.

 

SLA for non-proprietary channels 

 

1 Collection of comments or specific posts not belonging to the priority list is not guaranteed.

2 Additional time to the collection time of the previous table (Proprietary Metrics and STILINGUE Smart Care).

3 The priority list is managed in the Search Configuration. The user needs to input the link, blog RSS, or the username in the case of social media.

4 The Bluesky API documentation does not specify its delivery SLA. Based on the technical validations we conducted, we identified that we have access to approximately over 90% of the data. With this, we internally calculated an average collection time of between 1 and 2 hours. It is important to emphasize that since the API itself does not define a collection timeframe, there is still a possibility of not meeting this average.

 

Social metrics

Update of interactions on a post: likes, comments, shares, and video views.

 

*Minimum number of followers for the user making the post for social metrics to be updated.

Important: We have a block in our data collection flow for competitor pages (as we do not collect proprietary data for competitors), and the client should not list their page as a competitor page, as this will block the collection of metrics. Additionally, posts that have already been collected once cannot undergo retroactive collections (as they are already in our database), and all metrics will be updated within a 30-day period.

 

Number of followers 

The number of followers for a profile is updated each time the post is collected, provided that the profile making the post has a minimum number of followers according to each platform:

 

Additional collections

 

* When making changes to the configuration of a created search dashboard, this is the time it takes for the team to reorganize the previously collected data based on the new settings. 

Technical restrictions

Proprietary Channels (Proprietary Metrics and STILINGUE Smart Care)

• Update of posts on proprietary pages: 

Only in the last 100 posts from the last 30 days. This condition is valid for all channels across all social media networks. To increase the number of updated posts or the time interval, it is necessary to notify your account manager (CS) in advance for feasibility analysis.

• Comments on old Instagram and YouTube posts: 

For proprietary posts, only those made in the last 100 posts of the past 30 days are considered. Therefore, comments on old posts are not collected. Comments on non-proprietary pages are not delivered through the API. 

• On Instagram, the API grants STILINGUE access to the latest 150 comments on a post. If the number of comments in a collection cycle exceeds 150, there may be loss due to limitations in the network's API.
• Collection of posts and comments on connected pages: 

There will be a loss of data collection on pages not associated with a dashboard or pages that have lost authentication. Warnings are sent daily to clients when the system detects authentication failures.

 

Non-proprietary Channels (Listening)

• Twitter Collection:

 We collect the latest 300 posts/mentions at a time. If the number of posts in a collection cycle exceeds 300, there may be loss. In these cases (large sports events, real-time shows, debates, or high-viewership TV programs), we recommend strengthening via Twitter GNIP Powertrack (Twitter Enterprise), as a complement. By subscribing to the Twitter PowerTrack API, there is a 100% delivery guarantee for items. By default, the collection of RTs is disabled, but if there is a need to collect this data, you can request the activation of the service at no additional cost. 

 

Collection limits 

What factors are taken into account in the collection limit of publications? 

 The consumption of the publication collection limit for each plan is influenced by several variables that depend on what has been contracted by the client.

To calculate the collection limit, it is necessary to sum the total number of publications from all modules contracted in the system. New modules contracted by the client or launched by STILINGUE in the future will always consume the contracted collection limit. Currently, the modules that consume the publication collection limit are: STILINGUE Smart Care, Proprietary Metrics, Listening, and the Compare Fanpages (Facebook) section within Proprietary Metrics.

When the total collection limit of the panel is reached, the customer will be notified by email, and their collection will be paused. The customer is responsible for managing and utilizing the collection panel. It is advisable to prevent the panel from reaching the limit, as this may result in potential collection losses due to insufficient space. 

STILINGUE is not responsible for data losses caused by a lack of panel limit management. Customers can delete posts or upgrade their plan to avoid collection pauses.

 

Technical requirements 

STILINGUE's data is replicated on the platform in real-time to ensure integrity in cases of failures at specific points. Furthermore, a backup policy has been developed to allow data recovery in the event of major failures. 

The STILINGUE War-Room platform is exclusively marketed under the SaaS (Software as a Service) model, a form of software distribution and commercialization. Within this model, STILINGUE is responsible for providing the necessary infrastructure for the customer. 

The technical requirements for the STILINGUE platform are as follows:

1. Official support for Google Chrome and Microsoft Edge browsers in their latest versions (other browsers may have compatibility, but official support is limited to the ones mentioned above).
2. The official version is supported by the manufacturers of Microsoft Windows and Apple Mac OS operating systems.
3. ALL operators must have a computer with a minimum of 4GB of RAM (8GB recommended) and internet with a minimum speed of 10 Mbps. Recommended: 30 Mbps.
4. It is necessary for ALL operators to have an email for login and INDIVIDUAL use of the tool.
5. The release of some tools/plugins that assist us in monitoring usage and system bugs is mandatory for all operators. They are:
6. Zendesk (ticket tool) *.zendesk.com. *.zendesk.com.br
7. Logrocket (tool for automatic bug reproduction): *.logrocket.com, *.logrocket.io 
8. Sentry (automatic bug tracking tool): *.ravenjs.com
9. Social Networks (Facebook, Instagram, Twitter, YouTube):*.facebook.com , *.instagram.com , *.twitter.com, *.google.com ,*.cdninstagram.com, *.facebook.net, *.tenor.co , *.fbcdn.net , *.ggpht.com
10. SendGrid (Platform email dispatch tool): em2572.stilingue.com.br, url7811.stilingue.com.br 
11. STILINGUE : *.stilingue.com.br
12. The release of other tools/plugins is desirable:
    1. Google Analytics *.doubleclick.net , *.google-analytics.com
    2. Github *.github.io 

For more information, visit the discussion on the subject at our community or videos on our channel. 😃