​

Setting Up Google Ads Offline Conversions with Hardal

This guide will teach you how to configure Hardal to automatically send your conversion data to Google Ads, helping you track the full customer journey from ad click to offline conversion.

​

How the Integration Works

1. Data Collection: When users visit your website, Hardal’s tracking code captures important information including Google Click IDs (gclid) from your ad campaigns.
2. Event Storage: Hardal stores these events along with user properties in its database.
3. Conversion Forwarding: When you configure the Google Ads Offline Conversions destination, Hardal automatically sends relevant conversion data to Google Ads when offline conversions occur.

​

Step-by-Step Configuration

​

1. Access Custom Destinations

In your Hardal dashboard, locate and select the “Add Custom Destination” option.

​

2. Select Google Ads Offline Conversions

From the templates section under “Analytics,” choose “Google Ads Offline Conversions.”

​

3. Configure the Endpoint

Fill in the required fields:

• Endpoint Label: Create a descriptive name (e.g., “Google Ads Conversions”)
• Endpoint ID: Enter a unique identifier (e.g., “google-ads-conversions”)
• Endpoint URL: Input your Google Ads API endpoint
• Request Method: Keep as “POST”
• Content Type: Maintain as “application/json”

​

4. Understand the Request Format

The pre-configured JSON format maps your Hardal event properties to Google Ads requirements:

{
  "conversions": [
    {
      "conversionAction": "properties.conversion_action",
      "conversionDateTime": "created_at",
      "gclid": "properties.gclid",
      "conversionValue": "properties.value",
      "currencyCode": "properties.currency",
      "userIdentifiers": [
        {
          "hashedEmail": "properties.user.email",
          "hashedPhoneNumber": "properties.user.phone"
        }
      ]
    }
  ]
}

​

Essential Property Mapping

For this integration to work correctly, you must ensure your Hardal events include:

1. gclid: The Google Click ID from the ad. Hardal must be configured to capture and store this value as properties.gclid.
2. conversion_action: Your Google Ads conversion action ID should be stored in Hardal as properties.conversion_action.
3. value: The monetary value of the conversion should be in properties.value.
4. currency: The currency code should be in properties.currency.
5. User identifiers: User email and phone (if available) should be stored in Hardal as properties.user.email and properties.user.phone.

​

Implementation Checklist

1. Verify Hardal code installation is complete on your website.
2. Confirm gclid capture is working in Hardal’s event tracking.
3. Set up conversion events in Hardal to include all required properties.
4. Configure the Google Ads destination as described above.
5. Test the integration by triggering a test conversion and verifying it appears in Google Ads.

​

Troubleshooting

If conversions aren’t appearing in Google Ads:

1. Check that Hardal is correctly capturing the gclid parameter from ad clicks.
2. Verify your conversion events include all required properties with the exact names shown in the request format.
3. Ensure your Google Ads account has offline conversion tracking enabled.
4. Confirm the conversion action ID matches exactly with what’s in your Google Ads account.

By following this guide, your Hardal implementation will automatically send offline conversion data to Google Ads, improving your attribution modeling and campaign optimization without requiring manual data uploads.