Skip to main content

Twitter Data Collected - Proprietary Metrics

  • Updated

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

Proprietary Metrics is the area of STILINGUE where you can access various metrics that display information about the performance of your proprietary page according to the desired date range.

 

Platform data collection SLA

All collection channels have a 95% SLA between the average time and the time limit (shown below). The expected collection rate is 99.0% of posts within 24 hours after the time limit.

Note: the “Update” column should also be considered to identify the date range and amount of data collected when the proprietary page is connected.

 

Metrics Do we collect it? Collected via webhook Limitation Automatic Backfill
Posts from connected pages Yes No   The last 100 posts from the last 7 days. Collected every 15 minutes.
Dark Post - Twitter No      
Lives Yes No Data is collected after the Live ends. The last 100 posts from the last 7 days. Collected every 15 minutes.
Number of Replies No   The data is currently collected, but we are still developing its inclusion in the platform.  
Quotes* on a post Yes   Data is collected if it is available in the timeline. The last 250 posts from the last 30 days. Collected every 12 hours.
Interactions Do we collect it? Collected via webhook Limitation Automatic Backfill
Likes Yes No   The last 100 posts from the last 30 days. Every 15 minutes.
Messages in the inbox Yes Yes   The last 100 inboxes from the last 7 days, every 15 minutes.
Mentions of the proprietary page Yes Yes For backfill, only the 800 most recent mentions can be retrieved due to API limitations.
Replies and quotes count toward this volume.

Collects up to 100 mentions every 15 minutes.

Collection is sampled due to platform limitations. Therefore, collection of all mentions is not guaranteed. 
Impressions Yes The metric is collected but displayed only in the export. It does not appear in the platform interface. The last 250 posts from the last 30 days. Collected every 12 hours.
Engagement** with the tweet Yes Data is collected if it is available in the timeline. The last 250 posts from the last 30 days. Collected every 12 hours.
Encrypted messages in the inbox Yes Yes

See the Encrypted Messages section

 The last 100 conversations, with up to 100 messages per conversation, every 15 minutes.

*Quotes are RTs with comments

**The engagement counted here is the sum of all possible actions on a tweet. If someone undoes an action, the engagement continues to be counted.

 

Encrypted Messages

X (formerly Twitter) offers some accounts an additional security feature called "private and protected conversations" (Additional Message Privacy). When this feature is enabled, X begins end-to-end encrypting certain interactions received via Inbox — such as direct messages (DMs) — as an additional layer of protection against unauthorized access.

However, this encryption also prevents tools such as Stilingue from automatically reading the content of these conversations through the API. Therefore, for Stilingue to collect these protected interactions, you must provide the 4-digit PIN that was registered when the private conversations feature was enabled on the X account. Protected messages only begin to be collected after the PIN is registered. If the PIN provided is incorrect, the messages continue to be collected but remain encrypted until the correct PIN is registered.

Important points about this PIN:

  • It is defined by the user when enabling the feature on X, and is not generated by Stilingue.

  • It is unique to each connected page — in other words, if Stilingue is integrated with more than one X account/page, each one will have a different PIN, which must be registered individually.

  • Without the correct PIN, protected messages continue to be collected but remain encrypted. On the platform, an encrypted message notice appears instead of the original content.

  • After the correct PIN is registered, Stilingue attempts to automatically decrypt messages that have already been collected, which then display the original content. This is only not possible in two scenarios:

    • the PIN was changed on the X account;

    • the conversation contact forced the conversation's encryption keys to be changed.
      In these two cases, Stilingue cannot decrypt messages that have already been collected.

  • If the user does not remember the PIN, they must access the privacy and security settings of their own X account to reset it, since it cannot be recovered or viewed by Stilingue. Attention: resetting the PIN on X is one of the scenarios in which messages that have already been collected may not be decrypted

 

For more information, see the discussion about this topic in our community or the videos on our channel. 😃

Related articles