tomayac / adwords-reports-nodejs-lib

The project adwords-reports-nodejs-lib provides a simple AdWords reporting library for pulling ad hoc reports described in the AdWords Query Lanaguage (AWQL) directly from the AdWords API.

           ████████
          ███▄███████
          ███████████
          ███████████
          ██████
          █████████
█       ███████
██    ████████████
███  ██████████  █
███████████████
███████████████
 █████████████
  ███████████
    ████████
     ███  ██
     ██    █
     █     █
     ██    ██

I'm a Developer Advocate at Google Hamburg working on the Chrome team, focused on making the Web a better place through standardization, creating and sharing best practices, and doing research. I blog at blog.tomayac.com and tweet as @tomayac. If you feel like, you can ♥️ sponsor me.

adwords-reports-nodejs-lib's Issues

Oauth2 System is inflexible

I, like many people, am searching for a decent NPM module to be able to do API interactions with Google Adwords. I already have a refresh token, and my authorized client id is of a Web type, not 'native', and cannot use your library because it expects your specific account setup (which is not documented). Have you looked at how the googleapis client handles authentication? It provides access to the oauth2client directly, so you can adjust to any methodology the developer chooses without forcing them down a path like your library does. If you're open to this sort of thing I don't mind submitting a PR.

https://github.com/google/google-api-nodejs-client

Can't go through proxy

This adwords library uses the node js https library. I have modified it to use the newer npm request module instead. I think it works better. Let me know if you want/need this revised version, and I can submit a PR.

TOKEN_INVALID_HEADER Error

Hi!

I trying to connect to adrword api trough your library, i have my CLIENT_ID, CLIENT_SECRET of an Oauth 2 Credentials generated from Google API Console, and my DEVELOPER_TOKEN from Adwords API Developer Center and written all these data in a .env file in root, but when i execute the "example.js" script, shows the following:

Error, status code 400

And the body of the response have the following:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <reportDownloadError> <ApiError> <type>QuotaCheckError.INVALID_TOKEN_HEADER</type> <trigger></trigger> <fieldPath></fieldPath> </ApiError> </reportDownloadError>

I've verified the developer token is the same that adwords developer api center gives me, and the version used is 'v201702'

Maybe it's something that i've made wrong, hope your help. Thanks.

Get back a binary response

When I do a simple query, I'm getting back a binary response.

        var adwords = require('adwords-reports-nodejs-lib');
        adwords.getReport({
                // Change to a real Customer ID.
                cid: customer_id,
                // Change AWQL query according to the grammar published at
                // https://developers.google.com/adwords/api/docs/guides/awql.
                //
                // Check https://developers.google.com/adwords/api/docs/appendix/reports/all-reports
                // for the available report types and fields.
                awql: 'SELECT Cost,Name FROM CAMPAIGN_PERFORMANCE_REPORT DURING LAST_WEEK'
        }).then(function(data) {
                console.log(data);
        }).catch(function(err) {
                throw(err);
        });

data in the .then() function is binary data. What am I doing wrong here?

Action required: Greenkeeper could not be activated 🚨

🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet.
We recommend using:

• CircleCI
• Travis CI
• Buildkite
• CodeShip
• Azure Pipelines
• TeamCity
• Buddy
• AppVeyor
  But Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.