The Twitter data in your Falcon Dashboards might differ from the data that Twitter itself reports through their Twitter Analytics tool. This article explains the causes for these discrepancies.
Your Content Performance Widget in Falcon can report on the Total Impressions for all Tweets in a given date range. The Widget shows this total at the top of your Impressions column. If this data is compared to the same metric in Twitter Analytics, it is likely that the Twitter number is higher.
The cause for this discrepancy is the fact that Twitter automatically includes the impressions for Replies, as well as your Tweets. Replies are the Tweets that are made as a reply to another Tweet so that a Twitter thread is created. These replies can receive Impressions and Twitter automatically includes them in your totals.
At Falcon, we've chosen to exclude the impressions from Replies since it aligns with how other networks, such as Facebook, report on Impressions.
Date Range Definition
If you report on the same date range in Twitter as in Falcon, there might also be discrepancies due to differences in how the date range includes or excludes content.
In Falcon, the date range determines which posts are included in the calculation of your data. For Twitter, it only pertains to when the data itself was generated. To make this easier to understand, here's an example:
Let's say your date range in Falcon and on Twitter is set to the last 4 days. In Falcon, this means that all posts that were created in the last 4 days are included in your reporting. Any total metrics, such as Total Impressions, are calculated based on all the Impressions for the posts that were created in the last 4 days.
In contrast, Twitter will not take the creation date of a post into account. It will simply look at the total number of Impressions you received in the last 4 days. If a post was created 10 days ago, but received Impressions in the last 4 days, it will still appear in the report and it will be counted towards the Total Impressions metric for the last 4 days.
Finally, a third cause for slight discrepancies could be stemming from the limitations of some of the Twitter APIs that Falcon uses to retrieve your data.
Falcon can track the performance of each Tweet for a period of 7 days. If the content receives impressions and engagement after this 7-day period, the data is not reflected in Falcon.
Please bear in mind that almost all Tweets show a very steep decline in impressions and engagement after a few hours to a few days, which means that the impact of this limitation on reporting is minimal.
When reporting natively on Twitter, Engagements is defined as: All clicks on your Tweet. However, in Falcon, Engagements considers only your Tweet's likes, replies and retweets. Clicks are not included. To include clicks in your reporting, choose Interactions instead.