If you created Dynamic Text Ads for Google Ads with our Google Ads feature before May 2018, please read this article carefully. From June 2018 onwards, every newly created Text Ad generator will be an Ads generator version 2. You can recognize an Ads generator v2 by the '/v/2' in the URL in your browser. NB: From now on, we'll refer to Channable's Ads generator v2 as Ads v2.
The same, but different
Our Ads v2 still allows you to create and push dynamic text ads to Google Ads. In Ads v2, we have worked hard on the speed and reliability of our ad generators, meaning that our synchronization has been improved.
Next to performance improvements, we've added a few new features:
New synchronization options
In the previous version, you could only specify if you want your new campaigns and ads pushed as enabled or paused. In Ads v2, you can also specify whether you want Channable to overwrite statuses after they have been pushed to Google Ads. This is called the sync status option:
You can choose to:
1. Sync everything: Channable will always override manual status changes in Google Ads to the status known in Channable.
2. Sync everything except campaigns: Channable will not override any campaign status. Ideal if you want to manually manage the status of your campaigns in Google Ads.
3. Sync everything except campaigns and adgroups: Channable will not override any campaign nor adgroup status. Ideal if you want to manually manage the status of your campaigns and adgroups in Google Ads.
Important: Note that we always override ad and keyword status! Manage them carefully in your Channable account. Also, it is no longer possible to "link" ad generators that push different adgroups to the same campaigns. Make sure there is no overlap in campaigns between multiple v2 ad generators.
New features to come
Ads v2 is required for new features that are on our roadmap, e.g. Sitelink Extensions and the option to rename campaigns. More information about this coming soon.
Edit: We edited out the part about supporting campaign name changes. More work appears to be necessary to fully support this functionality. We apologize for any inconvenience caused by the announcement earlier.