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
- Go to https://ads.google.com 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 https://console.developers.google.com/apis/credentials
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 pre-fills-out a bunch of stuff
- 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”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:
- Navigate to https://app.faraday.io/destinations/new in the app and find the "Create destination" button.
- Find "Google Ads (formerly AdWords)" type and begin filling out the fields in the flow.
- It will ask for:
Google Ads "Oauth Playground" output
hint: 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"
}Google Ads client ID
Google Ads account ID
Google Ads client secret
Google Ads campaign ID
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.
Once your Account Manager or Project Manager confirms everything is all set up on our end, Google Ads will be available as a destination in Reach, the Faraday tool used for delivering audiences to their destinations. Different campaigns will be identified by their ID
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 ads.microsoft.com
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 campaigns you want to sync (it defaults to all)
5. Choose what to import, by default, it will copy over the bid modifers 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 in the same screen, Microsoft helpfully provides an error file for anything 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 zipcodes and bid adjustments
