Skip to main content

Collected Data - Proprietary Metrics

  • Updated

Learn which metrics are collected and which are not collected by each channel in Proprietary Metrics.

Proprietary Metrics is the STILINGUE area where you will have access to various metrics displaying information about the performance of your proprietary page within the desired date range.

In an effort to enhance the analysis strategies of your proprietary pages, STILINGUE provides comprehensive documentation on all data collected by the platform. It specifies which metrics and interactions are collected, how their updates function, and if there are any network limitations:

Operating conditions for proprietary collections

STILINGUE connects to various social networks to bring data from its connected pages and display them in STILINGUE Smartcare, Proprietary Metrics, Studio, etc. To make these connections, there are mainly two options:

  1. Webhooks: this is the ideal type of connection where the social network sends the data to our system, "like a mailman"; whenever there is something new, we are notified by the social network and perform the collection. This type of connection is ideal because it guarantees total volume and real-time collection. It is noteworthy that, in this type of operation, the responsibility for ensuring delivery lies entirely with the social network, since our system is available to receive the data. Thus, STILINGUE is not responsible for non-delivery or delays resulting from any social network problem, as even the network itself does not take responsibility or stipulate an exact SLA for this type of service.

  2. API: In this type of connection, Stilingue makes a request to the social network that searches for the last N (for example 100) comments of a post/inboxes of an account/posts of an account/ads of an adaccount, etc. In this case, it is not possible to request this data continuously because there are usage limits for each page's token, our application, or general restricted limits for using the APIs. Therefore, we perform collections at specific intervals (for example, every 15 minutes). Thus, if the volume of available data is greater than the amount requested in each request, the surplus will not be collected.

     

Operating conditions for responses in SmartCare

Meta (Instagram and Facebook): If your pages are connected to another system other than Stilingue with permission to respond to inboxes/private messages, it will not be possible to use Stilingue because only one application can perform this operation due to API limitations.

Delayed collections

As explained, STILINGUE performs two types of connections with social networks whenever possible to ensure agility and completeness in data delivery within the research panels. When analyzing cases of delay, it is important to note whether the type of collection in question has integrated webhooks, as ideally, it should have been collected this way. If it was not collected within the expected time, this data was collected through our API calls to attempt to guarantee collection redundancy; however, as mentioned previously, it is not possible to perform this process at all times.

About retroactive collections:

  1. Whenever there is a response in Smartcare for: Comments on Instagram, Facebook, and YouTube (of any nature), a small retroactive of the latest comments is performed to try to ensure this redundancy. It is known that there are factors that can, occasionally, cause the non-delivery of some comments on social networks, generally in low volumes and frequencies. These comments may stop being sent by webhooks or take time to appear in the APIs, becoming “visible” only after some time.

  2. For Facebook, in addition to the retroactive mentioned above, whenever new interactions arrive on old posts, a retroactive is triggered to ensure that no interaction is lost. This behavior is intentional and serves as a workaround for dynamic collections and cross-posts that cannot be automatically differentiated. This logic does not apply to Instagram, which has different retroactive rules and date filtering.

This can occur for various reasons already identified in support tickets with the social networks themselves, such as:

  • User privacy: a private profile that makes a comment/inbox and eventually may become public again;

  • Violation of a social network policy or guideline;

  • Deletion/hiding of comments that cause others to return to the list of the last N collected via API (various reasons for being hidden or not delivered, such as the two items above);

  • Unavailability by region: in some cases, we have identified zero comment collection, mainly in mentions, when the person mentioning restricts the region of access to the post data;

  • Unidentified age: on TikTok, we received feedback that they execute automatic age detection on profiles, and when they cannot identify the age, the data is not delivered.

For all these cases, we have never received detailed explanations regarding the cause of the failures or deadlines for correction. These behaviors can still be observed to this day, but it is important to highlight that these were exactly the responses obtained when we made contact to question the origin and recurrence of the problem.

Signs of incidents

This documentation is not intended to exempt STILINGUE from the responsibility of investigating eventual occurrences, but rather to clarify transparently the functioning of connections with social networks—processes that, by nature, may present variations and limitations outside of our control.

Should you identify evidence of slowness or setbacks involving collection that impact your operation, whether by volume or frequency, please contact our support team. Whenever possible, attach the observed evidence so we can expedite diagnosis and resolution.

¹Check which collections have webhooks here on their respective pages. 

²Check the documentation on how much each collection collects here on their respective pages. 

³The Documentation of SLA time for collections is made available here.

 

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

Related articles