Google Ads Destination

Google Ads Features

The Ours Google Ads feature allows you to track conversions and other allowed events in Google Ads in a HIPAA-compliant manner. We proxy all events through our server to ensure Google never directly interacts with your clients' browsers or sees their IP addresses.

This setup allows your Google Ads account to receive essential conversion data while maintaining strict privacy and compliance standards.

Configuring Google Ads

  • To add a Google destination, click on Destinations from your Ours platform.
  • Click the Add destination button and select Google as the destination type to add.
  • Click the Click to Authenticate Google button and sign into your account through Google.
  • After authenticating, select your Google Ads Account.

The Two Google Ads Destinations

Ours supports two types of Google Ads destinations:

  1. Google Ads (default)
  2. Google Ads Advanced Upload

Both methods are capable of being HIPAA compliant and neither directly loads any Google scripts or cookies. The differences are:

Google AdsGoogle Ads Advanced Upload
Conversion Type: "Website"Conversion Type: "Import Click"
Requires events to be sent over in a shorter time windowAllows 30 day old events to be collected
Requires authentication with ad accountOptional authentication with ad account

If you are trying to re-use conversion events that already exist in your Google Ads account, you may wish to select the Google Ads type that works with the "type" of your existing conversion events.

Syncing Ours Event Names with Google Conversion Actions

For both Google Ads and Google Ad Advanced Upload, you can authenticate with your Google Ad account and have Ours automatically syncing your allowed events to Google.

In the Google Ads (default) destination, authenticating Google Ads is optional. Authenticating will allow you to automatically create and link conversion actions in Google Ads with your Ours events. If you choose not to authenticate or cannot authenticate, you can still link conversion actions between Ours and Google Ads by manually adding the event's Conversion ID and Conversion Label and pressing Save Data:

If you're using the Google Ads Advanced Upload destination, you must authenticate. Adding the Conversion ID and Conversion Label is not supported for this destination.

Tracking Events

To start tracking events through Ours, you’ll first need to create and allowed events you want to track. Common events include conversions such as form submissions, sign-ups, and purchases. After you enable a few allowed events and potentially rename them, you can click the "Sync" button to sync them with Google Ads.

If you wish to create the conversion events in Google Ads yourself, you should create them before clicking the Sync button.

Example Google Conversion Sync Action

This will automatically create a conversion action in your Ad Account of the correct type

Example Google Ad Rename


Additional Information

Find your Google Ads Customer ID

Google Ads with a Manager account

If you used your Google Manager account email to authenticate Google and configure Google as a destination on behalf of your client, you will need to input your manager account id.

  1. Go to Google Ads
  2. In the Google Ads dashboard, look at the top of the page, near the profile icon or in the account selector dropdown
  3. The Google Ads account ID is displayed prominently at the top of the page. It’s a 10-digit number formatted as three groups of three digits, like this: 123-456-7890. If you're managing multiple accounts, ensure you select the correct account, as each account has a unique ID
  4. Copy and paste that Google Ads Customer ID into the Ours destination settings under the manager account id.

Tracking Events

After you set up your Google Ads Customer ID and API Key, you can track conversion events using:

ours('track', "ConversionEventName");

This will send an event named "ConversionEventName" to the Ours platform. From there, you can allow it for the Google Destination and potentially rename it before it's sent to Google.

Common Google events and their properties

Below is a list of common/standard events Google has special additional event properties defined for. You can send any event name to Google Ads via the Ours integration. But, these events have special optional properties Google defines.


Sales categories

Conversion goals that directly relate to revenue-generating actions on your website. These actions typically involve the user moving through stages of the purchase funnel, from showing intent to making a final transaction.

Conversion Goal

Required Parameters

Recommended Parameters

Purchase

value currency

transaction_id items

Add to Cart

None strictly required, but value is often recommended for better ROI tracking

value currency items

Begin Checkout

None

value transaction_id currency items

Subscribe

None

value currency


Examples

ours("track", "Purchase", {
  value: 100,
  currency: "USD",
  transaction_id: "123456",
});
ours("track", "Add to Cart", { value: 75, currency: "USD" });
ours("track", "Begin Checkout", {
  value: 150,
  currency: "USD",
  transaction_id: "78901",
});
ours("track", "Subscribe", { value: 200, currency: "USD" });

Leads categories

Captures user actions that indicate potential future sales or customer interest but do not involve an immediate purchase. For example: filling out contact forms, signing up for services, or booking appointments. The value parameter here is typically the estimated value of the contact action, if applicable.

Conversion GoalRequired ParametersRecommended Parameters
ContactNonevalue
Submit Lead FormNonevalue
Book AppointmentNonevalue
Sign UpNonevalue
Request QuoteNonevalue
Get DirectionsNonevalue
Outbound ClickNonevalue

Examples

ours("track", "Contact");
ours("track", "Submit Lead Form");
ours("track", "Book Appointment");
ours("track", "Sign Up");
ours("track", "Request Quote");
ours("track", "Get Directions");
ours("track", "Outbound Click");

Other categories

Conversions that are generally less tied to direct sales or leads but are still important indicators of user engagement and website activity.

Conversion GoalRequired ParametersRecommended Parameters
Page ViewNonevalue
OtherNonevalue

Examples

ours("track", "Page View");
ours("track", "Page View", { value: 100 });

When It Dispatches

Our Google Ads integration dispatches events automatically when the required data properties are present. Specifically:

  1. Necessary Properties: An event will be dispatched if it includes a valid Google Ads Customer ID, authentication data, and a unique identifier (gclid, gbraid, or wbraid). Additionally, if the visitor’s email is provided without a wbraid, a hashed version is included as part of the event data.

  2. Event Type: Dispatch occurs only if the event name matches a allowed event on your Google Ads destination

  3. Automatic Retry: If the Google Ads API returns an internal error or instructs to retry the request, the system will automatically attempt to re-dispatch the event.

Get Started Today

Implement Ours Privacy effortlessly with our simple copy-and-paste installation script. Begin optimizing your ads and tracking analytics without compromising privacy.