Google Ads Developer Blog: php

Removing support for PHP 7 in the Google Ad Manager SOAP API Client Library for PHP

Wednesday, April 26, 2023

In August 2023, the Google Ad Manager SOAP API Client Library for PHP will start requiring PHP version 8.0 or higher. The version of the client library that adds support for Google Ad Manager API v202305 will be the last version that supports PHP 7. We’ll still fix security issues for this client library version until Google Ad Manager API v202305 is sunset, but no new features will be added. All PHP 7 versions reached their end of life in 2022. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to newer versions as soon as possible. Here are useful resources to help with the PHP migration:

The PHP support version calendar

How to migrate from PHP 7.4.x to PHP 8.0.x

If you have any questions regarding this change, feel free to comment directly on the GitHub issue.

Pierrick Voulet, Google Ads API Team

Removing support for PHP 7 in the Google Ads API client library for PHP

Friday, March 10, 2023

July 2023the Google Ads API client library for PHP8.0 or higherlast versionin 2022

The PHP support version calendar

How to migrate from PHP 7.4.x to PHP 8.0.x

GitHub issue

- Thanet Knack Praneenararat, Google Ads API Team

Updating the minimum required PHP version for the Google Ads API client library for PHP (AdWords and Ad Manager)

Friday, January 25, 2019

Starting March 2019, the composer file of all releases of the Google Ads API client library for PHP (AdWords and Ad Manager) will require PHP version 7.1 or later. The latest major version of the client library (v39.0.0) will be the last release that supports PHP 5, with the minimum required PHP version of 5.6. We’ll still fix critical bugs for this major version, but no new features will be added to it in the future.

PHP 5.6 and 7.0 were sunset at the end of 2018. The PHP development team no longer provides security fixes for these versions, so we highly recommend migrating to the latest version (7.3) if possible.

You can see some useful resources below:

As always, if you have any questions, feel free to drop us a line on the Google Ads API or Google Ad Manager API forums.

- Thanet Knack Praneenararat, Google Ads API Team

Reminder to PHP users - upgrade to the new Ads PHP library!

Wednesday, April 5, 2017

Hello PHP developers! In December 2016, we announced the stable release of the new ads PHP library and the deprecation of the old one. This is a reminder to upgrade to the new library by July 31, 2017.

The new PHP library has many improvements such as support of namespaces and Composer installation. It is currently available as the master branch on GitHub. We also provide an upgrading guide to help you during this upgrade.

The old library has been moved to the deprecated branch with reduced support and will reach end of life (EOL) on July 31, 2017. We recommend you complete your upgrade before that date. Past this date, the deprecated branch can still be used until all of the AdWords / DFP API versions it supports are sunset, but we will not add support and examples for new API versions, nor fix any bugs.

If you have questions about upgrading or need help, as always, feel free to ask on the GitHub issues page. If you have questions regarding AdWords or DFP API, please drop us a line on the AdWords or DFP API forums.

- Thanet Praneenararat, Ads Developer Relations Team

Announcing the new ads PHP client library

Wednesday, December 21, 2016

Hello ads PHP developers! Today we're pleased to announce the stable release of the new ads PHP client library. This has been in beta for a while now, is a huge overhaul of the library, and offers the following improvements:

Uses namespaces and conforms to PSR-4 autoloading.

Conforms to PSR-3 for logging.

Supports installation via Composer.

Uses the Google PHP auth library for OAuth2, offering more features, flexibility, and service account support.

Uses Guzzle for non-SOAP HTTP calls, conforming to PSR-7.

Contains better object-oriented library design and stub interfaces, including builders to configure settings.

Contains upgraded and easier to use utilities for AdWords reporting, AdWords batch jobs, and DFP reporting.

Enables SSL by default for SOAP API calls and non-SOAP HTTP API calls.

This library has been pushed to the master branch on GitHub. The old library is now deprecated and moved to a deprecated branch with reduced support until it reaches end of life (EOL) on July 31, 2017. Reduced support details can be found in issue #193. To help you upgrade, we've written an upgrading guide. As always, if you have any questions, feel free to drop us a line on the AdWords or DFP API forums, or the Ads Developer Google+ page.

- Vincent Tsao, Ads API Team

Announcing BETA release of the new Ads PHP Client Library

Monday, February 22, 2016

Today we're pleased to announce that we have released an updated BETA version of the Ads PHP Client Library. This is the first step in completely refactoring the Ads PHP Client Library to adhere to modern PHP standards. Major changes include:

Namespaced and conforms to PSR-4 for autoloading.

Conforms to PSR-3 for logging standards.

Entry point classes use a builder pattern for their construction.

Core class design is composition-based instead of inheritance-based.

Classes generated from WSDLs now use getters and setters for accessing fields.

To get started with this new library, please see the README's "Basic usage" section. As a reminder, since this new client library is in BETA, it is not yet recommended for production usage. We do however recommend that you test it out, play around with it, and give us your feedback on the issue tracker. Stay tuned for more changes to this BETA library in the coming year. As always, if you have any questions, feel free to drop us a line on the AdWords API forums, DFP API forums or the Ads Developer Google+ page.

- Vincent Tsao, DFP API Team

Deprecating PHP 5.2 support for the Ads PHP Client Library

Thursday, July 17, 2014

Starting January 1st, 2015, the PHP Ads client library will stop supporting PHP 5.2:

We will no longer test against PHP 5.2, or fix bugs that only affect PHP 5.2 users
Newer versions of the library may not work with PHP 5.2

This will impact PHP client library users of the AdWords API, the DoubleClick for Publishers API, and the DoubleClick Ad Exchange Buyer APIs.

PHP 5.2 hasn’t been supported since 2011 and should be upgraded to a current, stable version. Upgrading ensures you’ll receive the latest security updates.

In addition, there are numerous issues when using the PHP 5.2 SOAP client, such as:

No support for chunked encoding
Inability to set HTTP protocol version
Inability to set custom HTTP headers

In particular, custom HTTP headers are required for the DoubleClick for Publishers API starting from DoubleClick for Publishers API v201405 - the OAuth 2.0 access token must be passed via the HTTP headers rather than the URL parameter. In this case, PHP 5.2 users must upgrade in order to use DoubleClick for Publishers API v201405.

As always, if you have any questions, drop us a line on the forums (AdWords API, DoubleClick for Publishers API, DoubleClick Ad Exchange Buyer API) or Ads Developers Google+ page.

- Ray Tsang, AdWords API Team

Getting Started With the PHP Client Library

Thursday, January 26, 2012

Recently, we released our first client library walkthrough video for the DoubleClick for Publishers API. This five-minute video guide shows you how to get up and running with the PHP client library from downloading the code to running one of the examples. All you need to get started is a DFP account (production or sandbox) and a machine with PHP 5.2.x and the SoapClient, OpenSSL, and cURL extensions. For new users to the API, it’s a great way to get acquainted with the documentation pages, project site, and client library features.

The video takes you through an explanation of how the getCreativesByStatement example makes an API call and highlights common usage patterns and best practices for the client library. We also show you what happens when a call returns an error and how you can configure logging to get more information and troubleshoot an issue.

Please let us know about any topics you would like us to cover in a video guide or blog by leaving a comment on our forum. You can also chat with us live at one of our DFP API Office Hours Hangouts.

- Jeffrey Sham, DFP API Team

Ads Developer Blog