Loading Profile...
Disparities in your numbers.
Just signed up. Intrigued by disparities in your numbers. For examples:
- You show I have 175 Twitter followers; Twitter says 204.
- You show 10 page views of today's blog post; bit.ly says 46.
What's the reason for these disparities?
- You show I have 175 Twitter followers; Twitter says 204.
- You show 10 page views of today's blog post; bit.ly says 46.
What's the reason for these disparities?
I’m happy
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Francis, the twitter followers count appears to be slightly out of sync on twittercounter API. It periodically syncs -- we'll look to see if we can make those numbers sync up faster.
For pageviews, the reason you see fewer pageviews is because Google Analytics does not show real-time data. Rather, it usually lags by a few hours. The numbers will catch up once Google processes the data.
So in both of those cases the discrepancy is due to the third party API's which are not real-time.
For the engagement metrics (twitter mentions, etc) the data is real-time as it comes from the PostRank system itself.
Hope that makes sense, and let us know if you have any other questions!
2 Comments
Add a comment
This solves the problem
-
Thanks for getting back to me, Ilya.
Your explanation of pageviews makes perfect sense; your explanation of Twitter follows less so.
I understand you believe it to be a synchronization issue but I assume you're synching at least weekly given that you report followers for this week and last. At a minimum, then, your numbers ought to be off by no more than a week. However, they are off by well more than that. Perhaps your "periodic" is less frequent than a week, in which case, yes, you really should do that faster.
Thanks,
Francis. -
Francis, we're working on a fix for this. We have a different strategy which will avoid this problem all together. Stay tuned!
EMPLOYEE
