We pull your traffic numbers and statistics via Google Analytics' API (What is an API? Read more here).
Google chooses to calculate the numbers it displays in its interface differently to how it calculates the numbers that it makes available through its API.
For example, if you look at the "Unique Users" metric in your native Google Analytics account (at analytics.google.com), the number that you see does not include duplicate users when reported for an aggregate time period. Google strip these duplicates out before they report the aggregate number in their interface.
As a result, you'll notice that the graph that they provide for this metric reports a different number than you would get if you added the unique users reported for each day.
On the other hand, the number that Google make available to developers via their API does include duplicate users. Google does not strip them out.
As a result, the graph that we display for the "Users" metric does equal the total that you would get if you added up the unique users reported for each day.
Note that this is a daily unique user count: If one of those users returns on a different day, Google chooses to count them as a new "unique" user when sending your data via their API. The user is not flagged as a duplicate when they send your data.
This is why some metrics can be different when looking at weekly or monthly data passed through Google's API, compared to what Google choose to display in their own interface at analytics.google.com.
In short: Google crunch the numbers differently when they report them internally (at analytics.google.com), compared to when they make that same data available to developers via their API. If you have a developer on your team, they can verify this themselves by accessing your data via Google's API.
Although "Users" is used as an example above, this can also apply to other metrics for the same reason.