This documentation is not using the current rendering mechanism and will be deleted by December 31st, 2020. The extension maintainer should switch to the new system. Details on how to use the rendering mechanism can be found here.
Google Ads Integration¶
|Description:||Creation and basic reports of Google Ads based on pages managed by TYPO3.|
|Author:||TYPO3 GmbH Development Team|
|License:||Open Content License available from www.opencontent.org|
The content of this document is related to TYPO3,
a GNU/GPL CMS/Framework available from www.typo3.org
Table of Contents
What is this about¶
With this extension, and a Google Ads account, you can now create Ads directly from the Backend. This means, for the pure task of composing an Ad start its delivery into the Google Search network, you don’t need to log into the Google Ads UI anymore. The process in itself is way easier, because it makes use of the data you put into your pages already. So you don’t start on an empty page, but with a pre-filled form that you can adjust as you wish. Once satisfied, the delivery starts a little while later, during which Google Ads runs its default checks on your ad, the same way it would if you would have created via Google Ads UI.
Find more information on our homepage.
This extension is only part of the system, but it brings all the functionality into the TYPO3 Backend.
First, you need a fully configured Google Ads account. This means especially: A valid credit card has to be introduced with your Google Ads account. Without it, no ads can be delivered.
Second, you need an account on Google Ads for TYPO3 . This is the tool that handles all requests both to and from any instance and also to and from Google Ads. No consumer instance will use the Google Ads API directly, what makes it so small and lightweight and easy to use. The installation will guide you through the necessary steps.
Third, you need this TYPO3 extension active and configured in your TYPO3 instance.
Last, but not least, you need to have your instance running with SSL. If your backend will not run with a https:// domain, the extension will itself block from being configured. If your frontend only will not feature an https:// domain, most probably Google will never deliver your ads. Using http:// domains is considered insecure, the internal algorithm of Google will punish its usage. So to take full advantage of the powerful Google Ads online advertising, make sure your instance can be considered secure.
This is what you need to create relevant ads from your Backend into Google Search.