Using Google Ads connector for EC models with CDATA Driver

[GuyRaz]

The Google Adwords native connector is no longer supported because they use Google APIs that are no longer supported by Google.

New installations from 2022.5 and up will no longer contain the Google Adwords native connector. 

Note: The CDATA table/column structure is different from the native drivers

Connect to Google AdWords using the CDATA driver:

1. Download the CDATA driver from https://www.cdata.com/solutions/bi/sisense/#download.
2. Install the driver locally in your environment.
3. Navigate to:
• /Applications/CData/CData JDBC Driver for Google Ads 2021/lib  - for MacOS.
• C:\Program Files\CData\CData JDBC Driver for Google Ads 2021\lib - for Windows.
4. Using a computer with Java installed, double click on the file cdata.jdbc.googleads.jar to pop up driver UI 
5. Add the following parameters in the pop up:
   • /opt/sisense/storage/connectors/GoogleAds/manifest.json
   • C:\Program Files\Sisense\DataConnectors\DotNetContainer\Connectors\GoogleAdwords\manifest.json
   • C:\Program Files\Sisense\DataConnectors\JVMContainer\Connectors\GoogleAdwords\manifest.json
• InitiateOAuth=GETANDREFRESH
• DeveloperToken=myDeveloperToken; NOTE: Set this to the developer token of the AdWords account. You can get a developer token by signing up for the AdWords API. To do this, log in to the AdWords site with your MCC account and navigate to Settings -> Account Settings -> AdWords API Center. Apply for API access and wait for Google to contact you via email with further instructions. You should receive a token with a pending status. This token is only for testing purposes and does not allow you to connect to live data. Google should contact you to fill in a questionnaire and, once this has been received and approved by Google, you will receive your active developer token.
• ClientCustomerId=myClientCustomerId; NOTE: Set this to your Google Ads customer ID. You can find your ClientCustomerId at the bottom of the help menu after clicking the help icon in the top right corner of the Google Ads UI.
• AuthScheme=OAuth;
• OAuthClientId=clientId; NOTE: specify the clientId, which can be retrieved from the manifest.json file of the old connector. Possible locations of the file are:
6. Before clicking “Test connection” in the JAR file, navigate to your Google application using Google API Console and add “http://localhost:33333” to Authorized redirect URIs.
7. Click “Test Connection”. You will be redirected to the web browser.
8. Login to your Google AdWords account - Once authenticated, the connection successful message will appear in the JAR.
9. OAuthSettings.txt will be generated in the following location:
   • Windows - %APPDATA%\\CData\\GoogleAds Data Provider\\OAuthSettings.txtd
   • MacOS - ~/Library/Application
   • If you can’t find the file, set the OAuthSettingsLocation in the JAR itself.
   • Copy OAuthSettings.txt to the Sisense server in:
   • C:\OAuthSettings.txt for Windows deployments.
   • /opt/sisense/storage/data/OAuthSettings.txt for Linux deployments.
10. Copy cdata.jdbc.googleads.jar to the Sisense server. See the following documentation for exact instructions.
11. Connect to Google AdWords using Sisense:
    • Connection string: jdbc:googleads:InitiateOAuth=GETANDREFRESH;DeveloperToken=myDeveloperToken;ClientCustomerId=myClientCustomerId;AuthScheme=OAuth;OAuthClientId=clientId;OAuthClientSecret=clientSecret;OAuthSettingsLocation=/opt/sisense/storage/data/OAuthsettings.txt
    • Jar’s folder: /opt/sisense/storage/data/AdWords
    • Driver class name: cdata.jdbc.googleads.GoogleAdsDriver

See the following CDATA documentation for data model changes:

https://cdn.cdata.com/help/DZG/jdbc/pg_googleadsdatamodel.htm

https://cdn.cdata.com/help/DZG/jdbc/pg_retrievingdata.htm

https://cdn.cdata.com/help/DZG/jdbc/pg_adwordsdatamodel.htm