Google Ad Manager primarily uses a SOAP API. The key points are:
The Ad Manager API uses SOAP (Simple Object Access Protocol).
Google offers client libraries for Java, .NET, Python, PHP, and Ruby to help developers work with the SOAP-based Ad Manager API.
The SOAP API requires authentication using OAuth 2.0.
Google has also introduced a REST API for Ad Manager, which is currently in Beta. This REST API allows developers to read Ad Manager data and run reports.
The REST API is available alongside the existing SOAP API, giving developers options depending on their needs and preferences.
Based on the search results provided, it does not appear that the official Google Ad Manager API offers webhooks or event subscriptions. The search results do not contain any specific information about webhooks or events for the Google Ad Manager API.
The key points to consider are:
The search results primarily focus on getting started with the Google Ad Manager API, including setting up credentials, configuring the API access, and using client libraries.
There is information about webhooks and event subscriptions for other Google services like the Webhook connector for Google Cloud Integration, but this is not specific to the Ad Manager API.
The search results mention some event-related functionality for the Google Mobile Ads SDK, but this is for mobile app ad integration rather than the Ad Manager API itself.
There is no mention of specific events or webhooks that can be subscribed to for the Ad Manager API.
Given the lack of information about webhooks or event subscriptions in the official documentation provided in the search results, it appears that the Google Ad Manager API does not offer native webhook functionality or event subscriptions.
If you need real-time updates or notifications from Ad Manager, you may need to consider alternative approaches such as:
It's important to note that API capabilities can change over time, so it's always a good idea to check the most up-to-date official documentation or contact Google support for the most accurate information about current API features.
Here are the key API rate limits for the Google Ad Manager API:
Exceeding this limit results in a QuotaError.EXCEEDED_QUOTA error [1].
There are additional quotas for resource-intensive systems like reporting and forecasting, which can result in errors like:
There are no exact figures provided for QPS (queries per second) limits, as they can vary based on overall server load [3].
The API enforces daily operation limits based on the access level of the developer token. Basic access allows 15,000 API operations per day [2].
Requests that are rejected with a GoogleAdsFailure still count against the daily operation quota [2].
There are limits on things like number of active ad units (100,000), active placements (60,000), key-value pairs (2,500,000), etc. [5]
For Dynamic Ad Insertion, there are soft limits like 25,000 manifest requests per second that can be adjusted by contacting your account team [5].
The key is to follow best practices, implement proper error handling and retries, and contact the Google Ads API team if you need higher limits for your use case. Monitoring your usage and staying well under the limits is recommended.
Based on the search results provided, here is the most up-to-date information about the Google Ad Manager API version:
The most recent version of the Google Ad Manager API is v202402.
Key points to consider:
This version was announced in February 2024 [4].
The upgrade from version 202311 to 202402 was implemented in April 2024 [5].
As part of the upgrade to v202402, new columns were added, including:
ad_server_cpm_and_cpc_revenue_gross
ad_server_all_revenue_gross
[5]Google regularly releases new versions of the Ad Manager API, typically following a pattern of YYYYMM (year and month) for version numbering.
It's important for developers using the Google Ad Manager API to stay updated with the latest versions, as they often include new features, deprecations, and changes to existing functionality.
Best practices:
Regularly check the Google Ad Manager API documentation and release notes for updates.
Plan for upgrades to newer API versions to take advantage of new features and ensure compatibility.
Be aware of any deprecations or changes that might affect your existing implementations when upgrading to a new version.
Test your integrations thoroughly when upgrading to a new API version to ensure everything works as expected.
Here are the key steps to get a developer account for Google Ad Manager to create an API integration:
Sign up for a Google Ad Manager account if you don't already have one.
Make note of your network code, which you can find in the URL when signed into your Ad Manager account.
Enable API access for your Ad Manager network:
Create authentication credentials:
Set up OAuth 2.0 authentication:
Apply for a developer token:
Configure your authentication settings in your code/application:
Review the API documentation and start making requests:
Based on the search results provided, here is a list of data models you can interact with using the Google Ad Manager API, along with what is possible for each:
It's important to note that the Google Ad Manager API provides a comprehensive set of services to interact with these data models, allowing you to perform operations like creating, modifying, retrieving, and deleting entities, as well as pulling reports and performance data.