Google Ad Manager

The Lyftron Provider for Google Ad Manager offers the most natural way to access Google Ad Manager data from Lyftron with ease and also enables to connect with BI, MDM & ML tools, Data warehouses, Databases and other SAAS based applications with zero code and zero infrastructure requirements. The provider wraps the complexity of accessing Google Ad Manager data into easy-to-integrate relational fully managed ANSI Sql format. Make faster and better business decisions with Lyftron’s Google Ad Manager data provider and automatically build your data migration pipelines in minutes, not months

The provider hides the complexity of accessing data and provides additional powerful security features, smart caching, batching, socket management, and more.

Key Features

• Comprehensive Delta load mechanism.
• Real-time access to Google Ad Manager.
• Comprehensive full support of ANSI Sql to query data with ease.
• Collaborative query processing.

Prerequisites

The user must have credentials for Google Ad Manager, Lyftron and your destination data warehouse, lake or database to perform the data pipeline operation with Lyftron

Establishing a Connection with Lyftron's Quickstart Steps

Create your Google Ad Manager connection with Lyftron by following the 5 easy steps show below:

Step1. Add your connection

Click on Connect section on the left panel →  Click on Add Connection button

Step2. Select your connector

In the connector selection panel, search and click Google Ad Manager for your connection 

Step3. Enter your connection details

In the Connection String section enter the values of the below parameters. The following connection string is required to establish Google Ad Manager connection with Lyftron.

InitiateOAuth=GETANDREFRESH;OAuthClientId=[your_clientID];OAuthClientSecret=[your_clientsecret];

Key	Value	Field
Connection Name	Enter your connection details	Required
InitiateOAuth	GETANDREFRESH	Required
Logfile**	Use the logfile option to debug your job and provide your connection name to generate the log file.  [ConnectionConfigurationPath]\Connection_name_log.tx	Optional
Verbosity**	Choose verbosity 1-5 based on the severity of debugging	Optional

** For more information, check the Lyftron logging and debugging section.

If you want more detailed information about how to establish a connection with Lyftron, click on Lyftron Connection Quick Start guide.

Step4. Test your connection

Once you are done entering your connection details, simply click on the Test Connection button to test the connectivity. In case your connection fails, add Logfile and Verbosity parameters and check the Lyftron logging and debugging section, to debug the error.

 Step5. Save your connection

Hurray! Now you have successfully connected with the Lyftron Google Ad Manager connector and can utilize the connector to Extract, Warehouse, Analyze, Visualize and Share your data.

Data Model

The Lyftron Provider for Google Ads Manager models Google Ads Manager objects as relational tables and views. A Google Ads Manager object has relationships to other objects; in the tables, these relationships are expressed through foreign keys. The following sections show the available API objects and provide more information on executing SQL to Google Ads Manager APIs.

Schemas for most database objects are defined in simple, text-based configuration files. However, schemas for Saved Query Reports are dynamically obtained.

Accessing Saved Query Reports

When you connect, the provider retrieves the list of reports and the metadata for the tables by calling the appropriate web services. Any changes you make to the Saved Query Reports, such as adding a new report, adding new fields, or changing the data type of a field, will immediately be reflected when you connect using the provider.

The provider offloads as much of the SELECT statement processing as possible to the Google Ads Manager APIs and then processes the rest of the query in memory. See SupportEnhancedSQL for more information on how the provider circumvents API limitations with in-memory client-side processing.

Inserting custom fields

When executing an Insert statement and you've specified a custom field, the value of the custom field must be an aggregate. The aggregate must contain the ID of the custom field and the value that you want to give it. You can get custom fields' IDs by querying CustomFields table. Currently, only custom fields of type "Text" are supported for Insert. Other types are not insertable/updatable.

Below is an example of inserting into Orders table while specifying the "MyOwnCustomField" custom field. The ID of the custom field is 1238676 and its value is "Sample text here".