Group: http://groups.google.com/group/adsense-api/topics
- Niels Schenk <schenk.niels@gmail.com> Mar 04 05:22AM -0800
Hi,
I'm using the python library to request a report. I'm using quite a lot of
dimensions which reduces many of the reported earnings per row to zero when
rounded to two decimal places. This results in large discrepancies when
adding up all earnings since earnings aren't zero but very small (<0.005).
The solution we're trying out at the moment is calculating earnings based
on INDIVIDUAL_AD_IMPRESSIONS_RPM. The problem is that when calculating the
earnings metric ourselves by
calculating INDIVIDUAL_AD_IMPRESSIONS_RPM/1000*INDIVIDUAL_AD_IMPRESSIONS,
total earnings are off. They're not off by much. The difference is only
0.01 based on reporting for one day. Still, we'd like to see no difference
between total earnings reported by the API and total earnings that we
calculate. Is there any way to make sure that total earnings for a given
date range correspond to total earnings reported for a given date range,
even when requesting a large number of dimensions?
Thanks,
Niels
- "Jose Alcérreca (AdSense API Team)" <adsenseapiadvisor+jose@google.com> Mar 04 06:45AM -0800
Hi Niels,
There's no way to get better EARNINGS I'm afraid, it's always going to be
rounded hence the problems you're experiencing. Your clever hack is going
to be as good as it gets.
Cheers,
Jose
---
Jose Alcérreca
Developer Relations
Google UK Limited
Registered Office: Belgrave House, 76 Buckingham Palace Road, London SW1W
9TQ
Registered in England Number: 3977902
On Tuesday, 4 March 2014 13:22:58 UTC, Niels Schenk wrote:
You received this message because you are subscribed to the Google Groups "AdSense API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to adsense-api+unsubscribe@googlegroups.com.
To post to this group, send email to adsense-api@googlegroups.com.
Visit this group at http://groups.google.com/group/adsense-api.
For more options, visit https://groups.google.com/groups/opt_out.
No comments:
Post a Comment