1025962 - Figure out how Affiliates can access Bouncer logs for tracking downloads

Status: VERIFIED WONTFIX

(Firefox Affiliates Graveyard :: affiliates.mozilla.org, defect)

Description

[Osmose [:osmose, :mkelly]]

We'd like to track the number of downloads an Affiliate banner triggers (bug 760663). To do so, we'd like to have mozilla.org add an extra query parameter to links pointing to download.mozilla.org. The parameter would be something like "affiliate_banner=2957".

Once that's done, we need a way for an automatic cronjob to run on Affiliates and pull the data from download.mozilla.org with each banner ID that came in from the query parameter, and how many hits came in with that parameter. For example, if 6 users downloaded with "affiliate_banner=4" and 2 users with "affiliates_banner=92" then we'd expect the data to look like:

+-----------+------+
| banner_id | hits |
+-----------+------+
| 4         | 6    |
| 92        | 2    |
+-----------+------+

aphadke: Can existing metrics infrastructure provide this data, without sampling, and in a way that a cronjob on Affiliates could pull the data once a day, or perhaps even more often?

Comment 1

[Anurag Phadke[:[e-mail]]]

mkelly - The existing infrastructure allows to have a cron job that can pull data once a day and send it as a report (email, csv etc.)
For more granular frequencies (by hour / by minute), we will have to push changes to our existing code base. If we have the specifics (the interval and domain/s) by end of Q2, then we should have a solution deployed by early Q3. 

-anurag

Comment 2

[ekariv]

mkelly - Looking through this bug it looks like you got the answer you were looking for. Is once a day good enough? Can this bug be marked resolved?

Comment 3

[Osmose [:osmose, :mkelly]]

This bug can be marked as resolved, but mainly because I've decided to follow a different route for getting this data. We won't be using metrics infrastructure for this.

Thanks for the catch, and thanks anurag for the info!

Comment 4

[Matt Brandt [:mbrandt]]

Bumping to verified wontfix per comment 1 and comment 3