Google Ads

Google Ads Developer Blog The official blog for information about the Google Ads, Google Ad Manager, Google Mobile Ads SDKs for AdMob and IMA SDKs, and other Google Advertising Platform developer tools.

  • Share your feedback about AdMob and Ad Manager mobile app integration
    by Google Ads Developer Advisor on September 4, 2019 at 5:48 pm

    We’re continuously improving our guides, code samples, and other developer resources for the Google Mobile Ads SDK to help you integrate AdMob and Ad Manager into your mobile apps. To learn more about what’s working well and what could be improved, we’re announcing our second annual developer feedback survey for the Google Mobile Ads SDK. We’d like to hear from you about where we should focus our efforts. SHARE YOUR FEEDBACKYour answers will be completely anonymous. The survey should take about 15 minutes to complete and will close on September 30, 2019. Your feedback is truly important to us. Here are a few highlights of the changes we made based on feedback from last year’s survey: Continuous translations of the developer docs in several languages Continuous build integration of sample applications via Travis CI Launched a Developer tutorials playlist on the Google AdMob YouTube channelLaunched the App Policy Center to help publishers handle policy violationsPlease let us know what you’d like us to focus on next. Thank you in advance for helping us continue to improve the developer experience for everyone.  Eric Leichtenschlag, Mobile Ads Developer Relations […]

  • Structured Data Files v5 now available in the DoubleClick Bid Manager API
    by Google Ads Developer Advisor on September 3, 2019 at 5:01 pm

    Today we’re announcing the general availability of Structured Data Files (SDF) v5 in the DoubleClick Bid Manager API. Highlights of this release include:Updates to environment targetingTrueView for actionRegional location list targetingDeal simplification updatesIO-level budget optimizationAs previously announced, this release introduces a number of breaking changes to SDF v3.1, v4, v4.1, and v4.2. All existing SDF users who rely on legacy targeting fields must now migrate in order to make use of the new, enhanced targeting fields in SDF v5.Retiring older API versionsWe’re also introducing a new deprecation schedule and announcing the deprecation of all SDF versions prior to v5. Moving forward, we will generally only support 3 versions of SDF at a time and sunset the oldest version 4 months after a new release. In order to help developers adjust to this new schedule, we’re providing an extended migration period for these newly deprecated versions and announcing a sunset date of February 28, 2020 for SDF v3.1, v4, v4.1, and v4.2.These versions will remain active and supported until the sunset date, and we encourage you to use this time to update your applications. After the sunset date, requests to these versions will no longer work, preventing you from accessing SDF.Get started with SDF v5All SDF users are encouraged to begin requesting v5 files in order to take advantage of the new features listed above. To do so, simply pass 5 as the value of version when calling For workflows that are dependent on older SDF formats, you can find additional details about the file format changes in the release notes.Questions about this or anything else DV360 related? Contact our support team. – Jonathon Imperiosi, DBM API Team […]

  • Announcing the 2019 London Google Ad Manager Developer Workshop
    by Google Ads Developer Advisor on August 26, 2019 at 6:35 pm

    The Ad Manager Developer Relations team is excited to hop across the pond and bring our Ad Manager Developer Workshop to London on September 26, 2019. If you’re a regular user of the Ad Manager API and Google Publisher Tags, then you’re sure to find something of interest at this event!What is it?A full-day event featuring technical talks by Google engineers and office hours with Google’s Developer Relations team. We will have talks on a range of topics, including Ad Manager API tips and best practices and strategies for faster loading pages and ads.Who is the target audience?The event is targeted toward developers who use the Ad Manager API. The talks will be technical in nature, so a technical background is required for all attendees. You’ll get the most out of some sessions if you come prepared with an API user’s credentials for your network and a laptop. For the full list of sessions, see the event schedule.Where and when?This event will be at Google’s London office at 1 St Giles High St. Doors will open at 9:30 AM and we’ll kick things off at 10 o’clock.How do I sign up?To register, please visit our website for this event. Seating is limited, so after you register, we will reach back out to you to confirm your spot at the workshop. – Donovan McMurray, Ad Manager API Team […]

  • Restricting Payments account usage across manager account hierarchies
    by Google Ads Developer Advisor on August 23, 2019 at 5:56 pm

    Starting September 9, 2019, we are rolling out a change to prevent the same Payments accounts in the Google Ads API (billing accounts in the AdWords API) from being used across manager account hierarchies. Only valid Payments accounts belonging to the Google Ads manager account hierarchy can be used to create and update billing setups in the Google Ads API.How does this affect you?For your authenticated Google Ads client account PaymentsAccountService.ListPaymentsAccounts() will return only valid Payments accounts belonging to your Google Ads manager account hierarchy, and BudgetOrderService.getBillingAccounts() will return only valid billing accounts belonging to your Google Ads manager account hierarchy. Therefore, you may get fewer results from those API calls than before.What do you need to do?Google Ads APIWhen creating/updating a new billing setup, you will need to select a valid Payments account returned by PaymentsAccountService.ListPaymentsAccounts(). If you use an invalid Payments account during the above processes, the INVALID_PAYMENTS_ACCOUNT error will be thrown. AdWords APIWhen creating a new budget order, you will need to specify a valid billingAccountId (the ID of a valid billing account returned by BudgetOrderService.getBillingAccounts()). If you use an invalid billingAccountId during the above process, the BudgetOrderError.INVALID_BILLING_ACCOUNT error will be thrown. As always, if you have any questions, feel free to post your questions on the Google Ads API forum. – Thanet Knack Praneenararat, Google Ads API Team […]

  • Sunsetting accelerated budget delivery
    by Google Ads Developer Advisor on August 21, 2019 at 5:36 pm

    Update (Sep 9, 2019): This post has been updated to include information about error responses that will be returned by the API and scripts. Starting October 14, 2019, accelerated budget delivery will no longer be available for use with search campaigns, shopping campaigns, or shared budgets. This will affect budgets in all versions of the AdWords API, Google Ads API, and Google Ads scripts. All three developer surfaces will stop accepting ACCELERATED delivery method setting on budgets for search campaigns, shopping campaigns, or shared budgets. Campaigns using accelerated delivery with these campaign and budget types will be automatically migrated over to STANDARD delivery, starting October 7, 2019.Note: When a new budget is created using the API or scripts, it is shared by default. Thus, a newly created budget will behave as STANDARD. To explicitly create a budget with ACCELERATED delivery, all of the following conditions will need to be met: The budget’s isExplicitlyShared field is set to false The budget’s delivery method is set to ACCELERATED It is not associated with a search or shopping campaign post creationAffected API and scripts operations After this change goes into effect, API clients and scripts will no longer be able to use the ACCELERATED delivery method setting on search campaigns, shopping campaigns, or shared budgets. Any programmatic operations that create or modify such budgets, or that would result in the following states, may result in errors according to the following criteria.Operation type isExplicitlyShared deliveryMethod Campaign Type Error Creating new budget true ACCELERATED (N/A) BudgetError.CANNOT_SET_ACCELERATED_DELIVERYModifying existing budget true ACCELERATED All BudgetError.CANNOT_SET_ACCELERATED_DELIVERYModifying existing budget false ACCELERATED Search, Shopping BudgetError.CANNOT_SET_ACCELERATED_DELIVERYAttaching existing budget to campaign false ACCELERATED Search, Shopping BudgetError.CANNOT_SET_ACCELERATED_DELIVERY If you have any questions about this change, please don’t hesitate to contact us via the AdWords API and Google Ads API Forum or the Google Ads scripts forum.Adam Ohren, Google Ads API Team […]