Google Ads Node

Google Ads API client library for Node.js

⚠️ Warning ⚠️

You're probably looking for our easy-to-use Google Ads API client library google-ads-api.

This library (google-ads-node) is the compiled output of the experimental Google Ads API Bazel build files, and will require some work to use as a standalone library, for which we currently provide no documentation.

Install

npm install google-ads-node

Requires Node.js 22 or newer.

Upgrading API Versions

1. Update to the latest gapic-tools version in /package/googleads-nodejs/package.json (re-apply after make protos, which regenerates this file).
2. Update to the latest google-gax version in /package/googleads-nodejs/package.json & /package.json.
3. Update GOOGLE_ADS_VERSION in the Makefile to the latest version (if required).
4. Run make protos to pull in the new protos and compile them. This command will take around 10 minutes. There are often errors here that need to be fixed due to changes in bazel, the docker image, or the protos themselves. Fix these errors as they come up.
5. Check for request parameters that the Dockerfile's sed rules do not convert to snake_case: grep -hE 'request\.[a-z]+[A-Z][A-Za-z]*' package/googleads-nodejs/src/v*/*.ts | grep -vE '^\s*\*' should print nothing (the second grep drops JSDoc lines, which legitimately contain camelCase names). Add a sed rule to the Dockerfile for anything it prints.
6. If upgrading to a new major version delete the old version folders from package/googleads-nodejs/protos/google/ads/googleads/{OLD_VERSION}, package/googleads-nodejs/src/{OLD_VERSION} and package/googleads-nodejs/samples/generated/{OLD_VERSION}.
7. Run yarn to prepare the package and install the latest dependencies.
8. You may find that the tsc build fails because of camelcase issues. If so, make sure that the compile-protos command in /package/googleads-nodejs/package.json includes all required arguments, like so: compileProtos --keep-case --force-number src
9. Update any references to old version numbers in tests/protos.js and tests/esm.mjs.
10. Run yarn test to make sure everything worked.
11. Double check that any files that should have been updated have been.
12. Update the readme to reflect the new Google Ads API version number
13. Make a pull request, get it approved and merged into master.
14. Publish to npm.

About Opteo

This library is developed and maintained by Opteo, the Advertising Efficiency Manager (AEM) for paid media teams working across Google Ads, Meta Ads, Microsoft Advertising, LinkedIn Ads and TikTok Ads.

Opteo brings together live account data, business context, skills, and specialist marketing tools in one workspace. Connect your marketing accounts, analyse your data with professional-grade tools, build expert marketing agents, and implement changes that increase ROAS.

Learn more about Opteo.