Faraday’s pre-built integration with Google Ads as a destination allows us to push bid modifiers for high-propensity ZIP codes, counties, or states, depending on your targeting strategy, directly into your Google Ads campaigns.
Note: Smart campaigns are not supported.
Faraday can only push bid modifiers to certain campaign types, due to limitations Google's API. More information can be found here.
Ultimately, we are not able to push bid modifiers to the following campaign types:
Adwords Express/Smart Campaigns
But the most common campaigns types are supported:
Display (standard or Gmail)
Search
Discovery
Granting access within Google Ads
Navigate to your Google Ads console and go to Campaigns on the sidebar.
2. Build a new campaign, or find the campaign you want us to provide bid-modifiers for. Note the GOOGLE ADS ACCOUNT ID for the desired campaign. Copy into a text file to keep the parameters organized:
3. Click the Campaign name
Then copy the GOOGLE ADS CAMPAIGN ID from the URL into a text file.
Note: Faraday cannot push bid modifiers to Adwords Express/Smart campaigns, since they are read-only. A "normal" Google Ads campaign ID must be provided.
3. Go to the Credentials section of the Google Developer console.
If you see Configure consent screen, click it. Otherwise, we can skip to step 4.
Click Internal if you can, otherwise External is fine, then Create.
Start filling out app information: the only required fields are App name, User support email, and Developer contact information.
"Faraday" is fine for "App name", and your own email for "User support email" and "Developer contact information."
Click Save and Continue.
Nothing on the next three screens (Scopes, Optional info, and Summary) is required.
Click Save and Continue on Scopes and Optional info, then finally Back to Dashboard on Summary.
If you "Testing" under "Publishing Status", click "Publish App"
4. Now select Credentials from the left-hand sidebar (or you should already be here if you skipped step 3)
Create credentials → OAuth client ID
Web application
Name: Faraday Adwords
Authorized redirect URIS: https://developers.google.com/oauthplayground
5. Click Create, then copy GOOGLE ADS CLIENT ID and GOOGLE ADS CLIENT SECRET into a text file.
6. Go to the OAuth playground (see screenshots below)
This link is special and it auto-fills some info
You have to fill in the GOOGLE ADS CLIENT ID and GOOGLE ADS CLIENT SECRET from above
Then hit Authorize APIs
Then choose the user if it asks
Grant it permission to talk to Adwords
Click Exchange authorization code for tokens and copy the output highlighted below
Screenshots of Oauth Playground process
7. Go to https://console.developers.google.com/apis/credentials, click into the credentials you just created, and remove the OAuth playground from authorized redirect URIs:
Sending credentials securely to Faraday:
Go to the Faraday app’s Destinations console, click Create destination at the top.
Search for Google Ads as a Destination location, enter a descriptive name, and click Next.
Enter your credentials here, and click Next. You'll be asked for:
Note on Google Ads Oauth Playground output: everything in the Oauth output's payload must be included. From "{" to "}", like so:
{
"access_token": "XXX",
"scope": "https://www.googleapis.com/auth/adwords",
"token_type": "Bearer",
"expires_in": 3599,
"refresh_token": "YYY"
}
Under Finalize, click Create destination. Faraday can now begin the integration process. Once your Account Manager confirms everything is all set up, Google Ads will be available as a destination in Reach, the Faraday tool used for delivering audiences to their destinations!
All fields are text-entry so if you have multiple campaign IDs you wish for us to utilize, you can put them all in, separated by commas!
Following setup, you will be receiving an account access request from Faraday's Google Ads Manager account. This will allow us to provide you attribution reporting based on performance.
What if I want to de-authenticate and/or remove all record of this connection?
A. It's as simple as doing one, but possibly two steps here:
Visit the developer console.
Find the OAuth 2.0 Client IDs credentials.
Delete them using the trash can symbol all the way to the right.
B. And if you want to remove the project that holds this data?
Visit Cloud Resource Manager.
Find the appropriate organization and project.
All the way to the right, click the vertical dots and then Delete.
(note: you must have sufficient permissions for your user to complete this task)
Deliveries to Google Ads
Deliveries to Google Ads will set bid-modifiers on up to 10k zip codes. Open the campaign delivered to, then click Locations on the left-hand sidebar.
2. You should see a list of zipcodes and Bid adjustments under Targeted.
Importing to Bing
Bing has a native “Import from Google Ads” tool, which allows a client to copy their Google Ads campaigns (with our bid modifiers) easily into their Microsoft Advertising (Bing) account.
1. Login into Microsoft Ads.
2. In the header navigation, Import Campaigns → Import from Google Ads
3. Follow the ensuing wizard. It will ask to authenticate your Google Ads account by logging in.
4. Next you will choose the Ad account, and then the campaigns you want to sync (it defaults to all).
5. Choose what to import. By default, it will copy over the bid modifiers and locations from your Google Ads campaigns.
6. Finally, you can set the import schedule.
7. If you view the import schedule, it gives you the option to run now.
8. You can also see the import history on the same screen. Microsoft helpfully provides an error file for any campaigns/locations that failed to copy over.
9. Copied campaigns will show in the left-hand sidebar. Click Settings → Locations under the campaign details to see the selected zip codes and bid adjustments.
