Repository navigation
Document how post analytics likes and unlikes are counted - #523
Draft
tcaldwell-x wants to merge 1 commit into
Draft
tcaldwell-x wants to merge 1 commit into
tcaldwell-x wants to merge 1 commit into
Conversation
GET /2/tweets/analytics metrics are organic event totals inside an hour-snapped, end-exclusive window. likes - unlikes is not a like count and can be negative. Documents API 2.174, where likes and unlikes count only user like and unlike events.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Explains how
GET /2/tweets/analyticsmetrics are counted on the post analytics page (x-api/posts/get-post-analytics.mdx):start_timeis rounded down to the hour andend_timeup to the next hour. The page includes examples.end_timeis exclusive after rounding.end_timeat most 1 year in the past and no later than the end of the current hour.unlikesfromlikes. The difference can be negative. There's a table pointing topublic_metrics.like_count/organic_metrics.like_countfor current like counts.likesandunlikescount only user like and unlike events. Earlier versions also count internal corrections that hide or restore a like. Callers opt in withx-api-minor-version: 174.DEVREL-994.
Merge only after 2.174 ships
The 2.174 section describes behavior that isn't deployed yet. It needs:
exclude_archival_correctionstoget_post_analytics)Open questions for reviewers
x-api-minor-versionheader that I could find. If version pinning shouldn't be documented yet, I'll drop the last sentence.