Metadata-Version: 2.1
Name: pyaw-reporting
Version: 0.0.3
Summary: AdWords API Reporting in Python
Home-page: https://github.com/gmontamat/pyaw-reporting
Author: Gustavo Montamat
License: UNKNOWN
Keywords: adwords adwords-api adwords-reports googleads awql
Platform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Intended Audience :: Developers
Classifier: Topic :: Software Development :: Libraries
Classifier: License :: OSI Approved :: Apache Software License
Classifier: Programming Language :: Python :: 2
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.6
Description-Content-Type: text/markdown
Requires-Dist: googleads

# AdWords API Reporting in Python

An AdWords API large scale reporting tool written in Python. Reports are downloaded as plaintext files but connectivity
with a database engine such as MySQL, PostgreSQL, or MongoDB can be implemented
[upon request](https://github.com/gmontamat/pyaw-reporting/issues).

## Overview

[pyaw-reporting](https://github.com/gmontamat/pyaw-reporting) is an open-source Python package suitable for large
scale AdWords API reporting. Output reports are comma-separated values (CSV) plaintext files. By default, the package
uses 10 threads to download reports simultaneously from different accounts. The number of threads used can be modified
using the `-n` parameter. It has been successfully tested using +100 threads making it useful for heavy load AdWords
Manager Accounts.

### Supported AdWords API version

The latest API version supported by this package is
[v201809](https://ads-developers.googleblog.com/2018/09/announcing-v201809-of-adwords-api.html) with
[googleads 17.0.0](https://pypi.python.org/pypi/googleads). Older versions of the API are not supported, nor the newer
[Google Ads API](https://developers.google.com/google-ads/api/docs/start).

## Quick Start

### Prerequisites

You will need Python 2.7 or 3.5+; this package will install [googleads](https://pypi.python.org/pypi/googleads) as a
dependency. Using a virtual environment is recommended to avoid running the package with `sudo`.

An access token [YAML file](#about-the-yaml-token) with the corresponding AdWords credentials is also necessary. By
default, the package will look for `~/googleads.yaml` unless a different path is passed. The optional parameter
**client\_customer\_id** must be included in this *YAML* file, you should enter your *AdWords Manager Account id*
(formerly known as *MCC id*). This way, all accounts linked to the Manager Account will be retrieved. The sample file
[example.yaml](awreporting/example.yaml) shows how your token should look like.

[AWQL](https://developers.google.com/adwords/api/docs/guides/awql) queries could be either passed in the command line
with the `-a`/`--awql` parameter or stored in a plaintext file and passed via the `-q`/`--query` parameter. There is a
sample query in the file [query.txt](awreporting/query.txt) which will retrieve clicks and impressions per ad for the
last 7 days. Refer to [Report Types](https://developers.google.com/adwords/api/docs/appendix/reports) and
[The AdWords Query Language (AWQL)](https://developers.google.com/adwords/api/docs/guides/awql) for more information
about these queries.

### Installation

```bash
$ pip install pyaw-reporting
```

### Usage

#### Command line

```
usage: awreporting [-h] (-a AWQL | -q QUERY_FILE) [-t TOKEN] [-o OUTPUT]
                   [-n NUM_THREAD] [-v]

AwReporting - Large scale AdWords reporting tool in Python

optional arguments:
  -h, --help                              show this help message and exit
  -t TOKEN, --token TOKEN                 specify AdWords YAML token path
  -o OUTPUT, --output OUTPUT              define output file name
  -n NUM_THREAD, --num-thread NUM_THREAD  set number of threads
  -v, --verbose                           display activity

required arguments:
  -a AWQL, --awql AWQL                    pass AWQL query
  -q QUERY_FILE, --query-file QUERY_FILE  ...or use a query file
```

For example:

```bash
$ awreporting -t example.yaml -a \
  "SELECT ExternalCustomerId, CampaignId, AdGroupId, Id, Date, Clicks, Impressions \
  FROM AD_PERFORMANCE_REPORT WHERE Impressions > 0 DURING LAST_7_DAYS" \
  -o adperformance.csv -n 100
```

Or, with a query file:

```bash
$ awreporting -t example.yaml -q query.txt -o adperformance.csv -n 100
```

If you experience problems downloading reports, check the resulting logs in `awreporting.log` or use the
`-v`/`--verbose` parameter to verify if something is wrong with your token or *AWQL* query.

#### Code

If you prefer embedding this package in your own code, you could do like so:

```python
from awreporting import get_report

query = (
    "SELECT ExternalCustomerId, CampaignId, AdGroupId, Id, Date, Clicks, Impressions "
    "FROM AD_PERFORMANCE_REPORT "
    "WHERE Impressions > 0 "
    "DURING LAST_7_DAYS"
)
get_report('example.yaml', query, 'adperformance.csv', 100)
```

### About the YAML token

The example token file provided [example.yaml](awreporting/example.yaml) is not valid. Refer to
[this guide](https://developers.google.com/adwords/api/docs/guides/first-api-call) if you are using the AdWords API for
the first time.

### Disclaimer

This is neither an official [AdWords API](https://developers.google.com/adwords/api/) repository nor a clone of
[AwReporting](https://github.com/googleads/aw-reporting). Consider using
[AwReporting](https://github.com/googleads/aw-reporting) if you are a Java developer. This framework is both compatible
with Python 2.7 and Python 3.5+ but future releases will support Python 3.5+ only.

### Troubleshooting

We recommend that you try the app with a small number of threads first (the default is 10) and increase the number
accordingly. The AdWords server may complain when many API calls are made at the same time but those exceptions are
handled by the app. We have successfully obtained huge reports using 200 threads.

When using this tool it might be necessary to enable a DNS cache in your system, such as
[nscd](http://man7.org/linux/man-pages/man8/nscd.8.html). This should eliminate DNS lookup problems when repeatedly
calling the AdWords API server. For example, if you find many `URLError: <urlopen error [Errno -2] Name or service
not known>` in your logs, enable the DNS cache.

In some Linux systems `nscd` is not enabled by default but it can be started with:

```
# systemctl start nscd
```

## Useful links

* https://developers.google.com/adwords/api/
* https://github.com/googleads/googleads-python-lib
* https://github.com/googleads/aw-reporting


