Tag Archives: Migration

Google Ads Scripts migration office hours

The new experience for Google Ads scripts has been available for a while, so hopefully you've had a chance to try it out and enjoy all the benefits it has to offer. There are a few differences from the old scripts API, which we've documented in our migration guide.

If you've given those a go, reached out on our forum or to our support alias for assistance, and are still having any difficulties understanding the changes or having problems migrating a particular script, we are launching a limited series of office hours sessions on a first come, first serve basis.

If you're interested, check out more information on our office hours information page.

As a reminder, we will begin migrating scripts automatically to the new experience starting in September of this year, and will be migrating all scripts to use the new scripts experience in October.

If you have any questions or feedback regarding the new experience, please leave a post on our forum or send a message to our support alias [email protected] so that we can help.

Performance Max upgrade has started

As we announced in January and again in March, existing and future Smart Shopping campaigns (SSC) will automatically upgrade to Performance Max campaigns between July and September 2022. The self-upgrade started in April 2022. The automatic upgrade has commenced (related blog post) and should complete by September 30, 2022. This blog post adds details for our API developers.

Starting July 25, 2022, accounts without active or paused SSCs (including new accounts) will no longer be able to create SSCs.

Once an account with active or paused SSCs has been automatically upgraded from SSC to Performance Max, no new SSC creation will be permitted in any surface including the UI, the API, Google Ads Scripts or Google Ads Editor.

The Google Ads API v11 included a new UpgradeSmartShoppingCampaignToPerformanceMaxRecommendation recommendation type to allow developers to upgrade a given SSC to a Performance Max campaign. This can still be applied to an account that has not yet automatically upgraded.

As mentioned in the January blog post, Local campaigns will also be automatically upgraded to Performance Max. An upcoming release of the Google Ads API will include a new recommendation type to allow developers to upgrade an eligible Local campaign to a Performance Max campaign.

Additional information

If you have any questions or need additional help, contact us via the forum.

Smart Shopping campaign upgrade to Performance Max – update

As we announced in January, existing and future Smart Shopping campaigns (SSC) will automatically upgrade to Performance Max campaigns between July and September 2022.

As mentioned in the prior blog post, users will be able to self-upgrade in the UI starting April 2022. Developers will be able to self-upgrade in the API before the end of June. We expect the vast majority of accounts managed by the API will opt to wait to self-upgrade once the tool is available in the API in June. However, campaigns may be upgraded manually by advertisers in the UI starting in April. We recommend you implement Performance Max in your application now to ensure support for any new or upgraded Performance Max campaigns.

An upgraded SSC will be marked as REMOVED status (metrics will continue to be available in the legacy campaign for historical purposes). There will also be a mapping from the previous campaign ID to the new Performance Max campaign ID. Budgets, assets, and settings of the existing SSC are preserved.

The prior blog post had April / May 2022 as the estimated availability date for the API's new self-upgrade recommendation type. This will be available before the end of June. There will still be a six week period between availability of the new recommendation type in the API and the start of auto-upgrades.

Note that once a campaign has been upgraded, either by the UI or API, there is no means to revert the upgrade. Metrics will continue to be available in the legacy campaign for historical purposes.

Additional information

If you have any questions or need additional help, contact us via the forum.

Google Ads API v10 RMF Update

Effective with Google Ads API version 10, we updated the Required Minimum Functionality (RMF) to use the Google Ads API. This is to reflect the evolution of the Google Ads platform, including the upgrade of Smart Shopping and Local Campaigns to Performance Max. We also published the requirements for Standard Shopping, Hotel-only and App Promotion-only tools.

There is a new product specific RMF for Smart Campaigns. This is not a requirement for all tools, only those that implement Smart Campaigns. If you use Smart Campaigns, this defines the minimum set of features that are required.

The minimum set of features for Performance Max campaigns are now available.

These changes will affect the following tools:
  • Shopping-only, Smart Shopping-only API tools
  • Special purpose tools that offer campaign creation or management functionality
These changes will not affect full-service, Hotel-only, App Promotion-only or reporting-only tools.

For precise details, see the updated Google Ads API Required Minimum Functionality.

Requirements for the AdWords API remain unchanged.

Standard Shopping Campaigns
With the release of Google Ads API v9, we simplified RMF requirements for Full-service tools. We are now making the same changes to Standard Shopping Campaigns.

The following features are still required but simplified or reduced in scope:
Item Number Functionality Change
C.190 Create ad group Optional: ability to create multiple ad groups
C.525 Add first (root) product partition This is a required step for creating a shopping campaign and it is done automatically. It is not separately invoked by the merchant. A new campaign should have a root partition otherwise it would not serve.
M.10 Edit campaign settings Only settings required at creation time would be required at change time (e.g. NetworkSettings would not be required to edit, since C.50 is no longer a requirement).
R.10 Customer Optional if only implementing one campaign.

The following features are no longer required. Developers may continue to use these features (unless already sunset), but they are no longer required in order to maintain compliance with the Terms & Conditions of using the Google Ads API. All these features, unless already sunset, are considered optional.

Item Number Functionality
C.14 Set mobile platform bid adjustment
C.15 Set tablet and desktop platform bid adjustments
C.21 Enable distance targeting
C.25 Set geo bid adjustment
C.50 Opt in/out of networks
C.90 Set bidding option: Manual CPC
C.95 Set bidding option: Enhanced CPC
C.101 Set bidding option: Maximize clicks (Portfolio)
C.140 Set delivery method
C.191 Set ad group max CPC bid
C.192 Set ad group max CPA
C.193 Set ad group target ROAS
C.320 Account-level tracking template
C.321 Campaign-level tracking template
C.325 Campaign-level custom parameters
C.326 Ad group-level custom parameters
C.328 Account-level final URL suffix
C.329 Campaign-level final URL suffix
C.700 Create ad group/campaign criterion that targets/excludes user list
C.710 Set userlist targeting bid adjustment for search network campaigns and ad groups
M.15 Edit mobile, tablet, and desktop platform bid adjustments
M.20 Edit ad group settings (all ad group-related required settings in Creation Functionality)
M.25 Edit geo bid adjustment
M.101 Edit bidding option: Maximize clicks (Standard)
M.120 Pause / enable / remove ad group
M.180 Edit product partition max CPC*
M.320 Manage all tracking templates in creation functionality
M.325 Manage all custom parameters in creation functionality
M.328 Manage all final URL suffixes in creation functionality
M.700 Edit ad group/campaign criterion that targets/excludes user list
M.710 Edit userlist targeting bid adjustment for search network campaigns and ad groups
R.30 Ad Group
R.80 Geographic View
R.150 Campaign Audience View
Ad Group Audience View

For more information
If you have questions specific to RMF, please contact the Google Ads API Compliance team at https://services.google.com/fb/forms/apicontact/.

If you have any questions or need additional help with the API, contact us via the forum.

Smart Shopping and Local Campaigns upgrading to Performance Max

Starting July 2022, existing and future Smart Shopping campaigns (SSC) will begin automatic upgrades to Performance Max campaigns. Local campaigns (LC) will begin automatic upgrades starting August 2022. If you manage and/or report on SSC and/or LC, you should implement Performance Max campaign features as early as possible in order to avoid loss of functionality. Closer to July, we will provide more details and precise timing.

We recommend you begin to build integrations now to ensure adequate preparation for migration.

New retail and local campaigns

Performance Max has been available in the Google Ads API since v9. We recommend you use Performance Max today for any new campaigns with online, offline or omnichannel sales goals.

SSC can be created without conversion tracking. While Performance Max campaigns, including retail, do not require conversion tracking, it is highly recommended.

Ways to upgrade

Here are the ways you will be able to upgrade existing campaigns to Performance Max:
  • [Recommended] Self-upgrade through API recommendations. In an upcoming Google Ads API release later this year, a new recommendation type will be available for per-campaign or bulk upgrades. You can use this to control the sequence of campaign upgrades or apply all recommendations at one time. There will be equivalent upgrade options available in the Google Ads UI. Self- and auto-upgraded campaigns will carry forward some learnings from the legacy campaign to help ensure continuity.
  • Auto-upgrade. Starting July 2022, SSC will be auto-upgraded to Performance Max on a rolling basis. Starting August 2022, LC will be auto-upgraded on a rolling basis.
  • Create a new Performance Max campaign through the API. This would involve creating a new Performance Max campaign with the same attributes and properties as an existing SSC or LC. Should you choose to create a new Performance Max campaign, the new campaign may not utilize the learnings of the existing SSC or LC to the same extent.

Upgrade impact on existing campaigns

An upgraded campaign, whether by self-upgrade or auto-upgrade, will:
  • Preserve budgets, assets, and settings of the existing SSC and LC
  • Mark the legacy campaign as REMOVED status (metrics will continue to be available in the legacy campaign for historical purposes)
  • Contain a mapping from the previous campaign ID to the new campaign ID
Upgraded campaigns will function like your previous campaigns and use existing assets to run on additional inventory that drives your conversion goals. We recommend adding additional assets to get the most value out of Performance Max.

Timeline


Date Event
Now Start implementing Performance Max in your application. When possible, start new campaigns with Performance Max instead of SSC or LC.
April 27, 2022 Sunset of AdWords API
April 2022 Self-upgrade period begins in the UI
April / May 2022 Self-upgrade period begins with the API's new recommendation type
July 2022 Start of SSC auto-upgrade
August 2022 Start of LC auto-upgrade
September 30, 2022 Completion of most SSC and LC auto-upgrades


Guidance for AdWords API developers

The AdWords API will sunset on April 27, 2022. Developers using SSC via the AdWords API should migrate to the Google Ads API using SSC as early as possible. The self-migration by the Google Ads API will only be available after the sunset of the AdWords API.

Additional information



For additional information, see the Google blog post about this upgrade.
If you have any questions or need additional help, contact us via the forum.

Reducing RMF to help migration to the Google Ads API

Effective with the Google Ads API v9, we’re significantly reducing the Required Minimum Functionality (RMF) to use the Google Ads API. This is to help accelerate your migration to the new API prior to the sunset of the AdWords API on April 27, 2022 while decreasing the burden on your engineering team. Requirements for the AdWords API remain unchanged.

This will affect the following tools:
  • Full-service
  • Shopping-only, Smart Shopping-only, Hotel-only and App Promotion-only API tools
  • Special purpose tools that offer campaign creation or management functionality
  • Reporting-only tools
This will not affect Internal-only tools because they are not subject to RMF.

For precise details, see the updated Google Ads API Required Minimum Functionality.

The following features are not changing and are still required:
Item Number Functionality
C.10 Create campaign
C.96 Set bidding option: Target CPA (Portfolio and Standard)
C.97 Set bidding option: Target ROAS (Portfolio and Standard)
C.98 Set bidding option: Maximize Conversions (Standard)
C.120 Set budget
C.260 Add keyword
C.300 Set keyword match type
M.96 Edit bidding option: Target CPA (Portfolio and Standard)
M.97 Edit bidding option: Target ROAS (Portfolio and Standard)
M.98 Edit bidding option: Maximize Conversions (Standard)
M.110 Pause / enable / remove campaign
M.130 Pause / enable / remove ad
M.140 Pause / enable / remove keyword
R.40 Ad Group Ad
R.50 Keyword View
R.70 Search Term View
R.130 Bidding Strategy

The following features are still required but simplified or reduced in scope:
Item Number Functionality Change
C.20 Enable geo targeting Required. Optional to expose to the user if only one country is relevant for the user base.
C.30 Enable language targeting Required. Optional to expose to the user if only one language is relevant for the user base.
C.65 Create website / call conversion and generate code snippet Requires at least one type of conversion tracking.
C.75 Callout extensions Required account level only.
C.80 Callout extensions Required account level only.
C.190 Create ad group Optional: ability to create multiple ad groups.
C.270 Add ad group negative keywords Change from Ad Group level to Campaign level.
M.10 Edit campaign settings Only settings required at creation time would be required at change time (e.g. NetworkSettings would not be required to edit, since C.50 is no longer a requirement).
R.10 Customer Optional if only implementing one campaign.
R.20 Campaign Remove requirements for segments.ad_network_type and segments.device.
R.100 Dynamic Search Ads Search Term View Required only if implementing Dynamic Search Ads.

The following features are no longer required. Developers may continue to use these features (unless already sunset), but they are no longer required in order to maintain compliance with the Terms & Conditions of using the Google Ads API. All these features, unless already sunset, are considered optional.

Shopping-only features (indicated by *) are still required for shopping-only tools, but are no longer required for Full-service tools.
Item Number Functionality
C.14 Set mobile platform bid adjustment
C.15 Set tablet and desktop platform bid adjustments
C.21 Enable distance targeting
C.25 Set geo bid adjustment
C.41 Set Expanded Dynamic Search Ads
C.42 Set campaign DSA settings
C.50 Opt in/out of networks
C.70 Location extensions
C.72 App extensions
C.90 Set bidding option: Manual CPC
C.95 Set bidding option: Enhanced CPC
C.101 Set bidding option: Maximize clicks (Portfolio)
C.140 Set delivery method
C.191 Set ad group max CPC bid
C.192 Set ad group max CPA
C.193 Set ad group target ROAS
C.200 Add expanded text ad
C.290 Set keyword max CPC
C.311 Set keyword final URL
C.320 Account-level tracking template
C.321 Campaign-level tracking template
C.325 Campaign-level custom parameters
C.326 Ad group-level custom parameters
C.328 Account-level final URL suffix
C.329 Campaign-level final URL suffix
C.500 Create shopping campaign*
C.505 Set merchant identifier*
C.506 Set sales country*
C.510 Set inventory filter*
C.520 Create product ad*
C.525 Add first (root) product partition*
C.530 Local inventory ads*
C.610 Call ads
C.700 Create ad group/campaign criterion that targets/excludes user list
C.710 Set userlist targeting bid adjustment for search network campaigns and ad groups
M.15 Edit mobile, tablet, and desktop platform bid adjustments
M.20 Edit ad group settings (all ad group-related required settings in Creation Functionality)
M.25 Edit geo bid adjustment
M.35 Enable ad rotation
M.40 Edit keyword max CPC
M.100 Edit expanded text ad
M.101 Edit bidding option: Maximize clicks (Standard)
M.120 Pause / enable / remove ad group
M.150 Edit inventory filter*
M.160 Subdivide (add product partition)*
M.170 Remove product partition*
M.180 Edit product partition max CPC*
M.190 Exclude product partition (delegate)*
M.320 Manage all tracking templates in creation functionality
M.325 Manage all custom parameters in creation functionality
M.328 Manage all final URL suffixes in creation functionality
M.700 Edit ad group/campaign criterion that targets/excludes user list
M.710 Edit userlist targeting bid adjustment for search network campaigns and ad groups
R.30 Ad Group
R.80 Geographic View
R.110 Shopping Performance View*
R.120 Product Group View*
R.150 Campaign Audience View
Ad Group Audience View

* These features are not required for Full-service tools. Shopping-only RMF tools still need to implement these features.

If you have questions specific to RMF, please contact the Google Ads API.
If you have any questions or need additional help about the API, contact us via the forum.

Four areas of open source contributions from Cloud Databases

Open Cloud enables you to develop software faster, innovate more easily, and scale more efficiently—while also reducing technology risk. Google has a long history of leadership in open source, and today, I want to look back at our activities around open source projects, for databases, over the past year.

Give developers the best tools to be efficient

Developers choose to build applications with managed database services on Google Cloud to benefit from velocity, scalability, security, and performance. To enable you to be most efficient and deliver your best possible work, we deliver tools and frameworks that work with your preferred development environments, no matter if you develop in the cloud or on premises. To make local testing, building and continuous integration easier for our cloud-native databases, we released emulators for Cloud Spanner, Firestore, and Cloud Bigtable so that you can test your code wherever you develop it - without the need to create or re-create cloud infrastructure with every test run.

Another area where we are helping developers is with instrumentation of Cloud SQL for easier debugging and performance tuning. With Cloud SQL Insights it is easier than ever to pinpoint underperforming SQL statements. That said, without additional instrumentation, it can be cumbersome to identify the source code or microservice that issued that SQL - let alone tying a SQL statement to a client session and its context. So we released Sqlcommenter as an open source library that will automatically add this instrumentation as SQL comments in queries that are generated by popular ORMs like Hibernate, Django, Sqlalchemy, and others (repo blog). We didn’t stop there, but merged Sqlcommenter with OpenTelemetry (blog) to add SQL insights from instrumented queries back to OpenTelemetry traces.

Lastly, we want to broaden access to our differentiated offerings, like Spanner. The recently announced Spanner PostgreSQL interface allows organizations to access Spanner’s industry-leading consistency and availability at scale using tools and skills from the popular PostgreSQL ecosystem. This new way of working with Spanner provides familiarity for developers and portability for administrators. (blog) Learn more in the documentation or sign up for the preview today.

Provide connectivity that is simple and secure

Connecting to APIs and databases from an application running in the cloud should be simple and secure. That’s why we recommend using IAM and Application Default Credentials when authenticating to other services. The Cloud SQL Proxy (repo) has been doing this and also setting up firewalls for you for a while. It works by running a local client either inside your VM or a GKE cluster. This year, we added libraries for Java (repo) and Python (repo) that can provide similar functionality without the overhead of running an extra client such as the proxy.

Cloud Spanner also offers an open source adapter for its new PostgreSQL interface (repo). This local proxy allows tools, starting with psql, to connect to a Spanner database using the PostgreSQL wire protocol.

Image 1: White pipes in datacenter

Manage cloud infrastructure with the tools of your choice

When it comes to provisioning, monitoring, and managing your cloud database services, flexibility and choice are important. We provide you with our cloud console, gcloud cli, and APIs as well as our own Deployment Manager. That said, you may prefer different ways to manage cloud infrastructure - whether through interactive tools or scripts or embedded into CI/CD pipelines that support GitOps or other controls, checks, and balances. Terraform is one of those open tools that is very popular - and we ensure that our cloud databases can be managed from it as documented in this blog about creating Spanner instances with Terraform.

If you manage the majority of your resources with Kubernetes either directly or through package managers like Helm, then our Kubernetes Config Connector (KCC) might be for you. In a nutshell, KCC exposes Google Cloud services such as Cloud SQL, Spanner, and others as Custom Resources in Kubernetes. This allows you to create and reconcile cloud resources outside of Kubernetes just like K8s native objects.

Once you are managing cloud infrastructure with CI/CD, the next step is to extend that same mechanism to manage objects within your databases such as tables, indexes, and views. To that extent we have released a Liquibase extension for Cloud Spanner.

Help you to move data with confidence

Cloud journeys often involve moving data either in a lift and shift process or sometimes replatforming to a different database. Whatever your journey, we want to simplify the process and give you the confidence that your migration is successful.

For enterprise users with Oracle databases, we have several open source projects. First, we have the Optimus Prime database assessment tool (repo) that queries your database and collects information about schemas and historic performance to be analyzed for migration complexity and consolidation potential. Our own professional services teams have been using this toolset to plan migrations to Bare Metal Solution for Oracle.

Some Oracle users are looking for opportunities to transform their workloads to fit with their bigger strategy of modernizing applications with Kubernetes. For this group we developed and open sourced the El Carro Kubernetes operator for Oracle. This not only automates database lifecycle tasks for systems running on Kubernetes, but also exposes declarative APIs for these operations.

If your application supports replatforming from Oracle to PostgreSQL, then we have a toolset for schema conversion along with dataflow pipelines that will read the output of a change data capture job and load it into a PostgreSQL database. What a great use-case for Datastream - our new serverless change data capture service.

Another case of heterogeneous database migration is to move MySQL or PostgreSQL databases to Cloud Spanner. HarbourBridge helps with the evaluation and data migration, and our latest contribution was adding support for DynamoDB as a source database. Part of every heterogeneous migration should be to validate that the source and target data are matching - we have released the Data Validation Toolkit for that use-case. DVT can connect to a number of source and target databases and compare the data on each side - giving you the confidence that your migration did not miss or change any records.

Conclusion

Whether you are migrating existing databases or you are building your next application in the cloud - we want to make your journey as comfortable and seamless as possible. Open source projects play a big role in meeting you where you are and providing you with the connectivity options, language support, and tools you want for management and migrations.

By Bjoern Rost, Product Manager, Google Cloud Databases

Register for the Google Ads API Migration Workshop

As previously announced, the Google Ads API Migration Workshop is only one week away. Register today to reserve your spot.

As a reminder, the workshop will provide you with knowledge, resources, and support to migrate from the AdWords API to the Google Ads API. We’re offering this live workshop in three regions. Follow the links below to view the full agenda in your region.

Session Dates

We look forward to seeing you!

Announcing The Google Ads API Migration Workshop

Today, we’re announcing The Google Ads API Migration Workshop, which will be presented live in three regions, to provide you with knowledge, resources, and support to migrate from the AdWords API to the Google Ads API.
Session DatesGet to know the team supporting your migration during this three-day virtual workshop as we:
  • Teach you about the new API
  • Walk through interactive demonstrations
  • Help you create a migration plan
  • Discuss best practices for migrating your application

Whether you’re new to the Google Ads API or want to level up your skill set, we'll have a variety of sessions to help you achieve your goals. We’ll be delivering several talks to discuss what’s new in the Google Ads API and explain key concepts. Tune into our interactive sessions as we demonstrate how to migrate components of your application and leverage the suite of developer tools supporting the Google Ads API.


Throughout the workshop, you’ll have the opportunity to interact with our team via live Q&A and breakout sessions. We’ll also host a panel featuring the Tech Leads of the Google Ads API Engineering and Developer Relations teams.


Follow the event link to register for the event and view the full agenda. We look forward to seeing you!

Migrate users and data between G Suite environments more easily

Quick launch summary 

G Suite Migrate, currently available in beta, helps admins assess, plan, and migrate large amounts of content directly into G Suite. It already supports Microsoft Exchange, Microsoft SharePoint, Microsoft OneDrive, file shares, and Box migrations. With this launch, you can now also migrate between G Suite environments. Specifically, you can: 
  • Selectively migrate Gmail, Calendar, Drive, and more data between G Suite environments. 
  • Choose to migrate all users from one environment to another. 
  • Selectively migrate specific user data (organizational units, users, or subsets of data) between G Suite environments. 

Getting started 

Rollout pace 

Availability 

  • Available to G Suite Business, G Suite Enterprise, G Suite Enterprise for Education, and G Suite Essentials customers 
  • Not available to G Suite Basic, G Suite for Education, and G Suite for Nonprofits customers 

Resources