In most cases our analytics reporting relies on 3rd party APIs (Facebook, Twitter and LinkedIn).

For example, in order to determine how many Likes a specific post on LinkedIn has received, our system has to use the LinkedIn API to request that information from the LinkedIn servers.

In the specific case of clicks - our system can track those in real time.

We are governed by the respective API platforms in terms of how many times we are allowed to make requests in a day.

That means we need to balance the number of API calls against how many likes, comments and shares we expect for a particular piece of content.

If you create a social media post - obviously there is higher level of propensity for engagement as soon as you post it. Meaning, it's unusual that someone will interact with something you posted 6 months ago.

Another way to think of this would be to think in terms of engagement decay. As time passes, there is less and less frequency of engagement.

Accordingly, our systems polls the respective APIs using a "rate of decay". More specifically, that means we poll more frequently during the first 12 hours (the most likely time you'll get engagement) and we poll less frequently as time passes.

Listed below is the rate of engagement decay polling that we have established for Social Horsepower.

Reporting Frequency