# Google Ads Offline Conversions Cloud Mode Integration


After you have successfully instrumented Google Ads Offline Conversions as a destination in RudderStack, follow this guide to correctly send your events to Google Ads Offline Conversions in [cloud mode]({{< ref "/destinations/rudderstack-connection-modes.md#cloud-mode" >}}).

## How to use the integration

This section gives an overview of how to use the Google Ads Offline Conversions cloud mode integration with RudderStack:

1. **Dashboard setup**: Set up the [Google Ads Offline Conversions destination]({{< ref "destinations/streaming-destinations/google-ads-offline-conversions/setup-guide.md" >}}) in RudderStack.
2. **Configure event mappings**: Map your RudderStack events to Google Ads conversion types (Click, Call, or Store) in the dashboard settings.
3. **Send track events**: Use the `track` method to send conversion events with the required properties.

## Track

RudderStack associates the [`track`]({{< ref "event-spec/standard-events/track.md" >}}) event with the event name defined in the **Map your events with Google Ads Offline Conversions** dashboard setting.

RudderStack supports the following conversion types:

### Click conversion

You can create a conversion action to [upload offline click conversions](https://developers.google.com/google-ads/api/docs/conversions/upload-clicks) into Google Ads. The [Google Ads Click Conversion API](https://developers.google.com/google-ads/api/reference/rpc/v13/ConversionUploadService#uploadclickconversions) processes these click conversions.

A sample `track` call for a click conversion is shown below:

```javascript
rudderanalytics.track('sign up completed', {
  gclid: "gclid_value",
  conversionDateTime: "2022-05-20 12:32:45-08:00"
});
```

The following table lists the property mappings between RudderStack and Google Ads Offline Conversions for the click conversion type:

| RudderStack property | Google Ads Offline Conversions property | Notes |
| :-----| :--------| :--------| 
| `properties.conversionDateTime`<br/>`timestamp`<br/>`originalTimestamp` <br/> <span style="color: #4D4DFF;font-size:12px;">Required</span> | `conversionDateTime` | Date and time at which the conversion occurred. It must be after the click time and must include the timezone offset. <br /><br />The format for this field is `yyyy-mm-dd hh:mm:ss +/- hh:mm`. <br /><br />For example, `2019-01-01 12:32:45-08:00`. |
| `traits.email`<br/>`context.traits.email`| `hashedEmail` | If **User Identifier Source** is set in the dashboard, either `email` or `phone` must be passed. |
| `traits.phone`<br/>`context.traits.phone` | `hashedPhoneNumber` | If **User Identifier Source** is set in the dashboard, either `email` or `phone` must be passed. |
| `properties.gclid` | `gclid` |  -|
| `properties.gbraid` | `gbraid` |  -|
| `properties.wbraid`  | `wbraid` |  -|
| `properties.externalAttributionCredit` | `externalAttributionCredit` |  -|
| `properties.externalAttributionModel` | `externalAttributionModel` |  -|
| `properties.merchantId` | `merchantId` |  -|
| `properties.feedCountryCode` | `feedCountryCode` |  -|
| `properties.feedLanguageCode` | `feedLanguageCode` |  -|
| `properties.localTransactionCost` | `localTransactionCost` |  -|
| `properties.product_id`<br/>`properties.sku` | `productId` |  -|
| `properties.quantity` | `quantity` |  -|
| `properties.price` | `unitPrice` |  -|
| `properties.userIdentifierSource` | `userIdentifierSource` |  -|
| `properties.conversionEnvironment` | `conversionEnvironment` | You can set the value for this parameter in the [dashboard settings]({{< ref "destinations/streaming-destinations/google-ads-offline-conversions/setup-guide.md#event-settings" >}}) — it accepts only the following values: <br /><br /><ul><li>**None** (default)</li> <li>**UNSPECIFIED**</li><li>**UNKNOWN**</li><li>**APP**</li><li>**WEB**</li></ul>|
| `properties.conversionValue`<br/>`properties.total`<br/>`properties.value`<br/>`properties.revenue` | `conversionValue` |  -|
| `properties.currencyCode`<br/>`properties.currency` | `currencyCode` |  -|
| `properties.orderId`<br/>`properties.order_id` | `orderId` |  -|

See [ID parameters](https://developers.google.com/google-ads/api/docs/conversions/upload-clicks#id_parameters) section for detailed guidelines on passing the combinations of `wbraid`, `gbraid`, and `gclid` parameters.

### Call conversion

You can create a conversion action to [upload offline call conversions](https://developers.google.com/google-ads/api/docs/conversions/upload-calls) into Google Ads. The [Google Ads Call Conversion API](https://developers.google.com/google-ads/api/reference/rpc/v13/ConversionUploadService#uploadcallconversions) processes these call conversions.

A sample `track` call for a call conversion is shown below:

```javascript
rudderanalytics.track('login', {
  callerId: "callerId_value",
  callStartDateTime: "2022-08-12 15:01:30+05:30",
  conversionDateTime: "2022-09-24 12:32:45-08:00"
});
```

The following table lists the property mappings between RudderStack and Google Ads Offline Conversions for the call conversion type:

| RudderStack property | Google Ads Offline Conversions property |
| :-----| :--------| 
| `properties.callerId` <br/> <span style="color: #4D4DFF;font-size:12px;">Required</span> | `callerId` |
| `properties.callStartDateTime` <br/> <span style="color: #4D4DFF;font-size:12px;">Required</span> | `callStartDateTime` |
| `properties.conversionDateTime`<br/>`originalTimestamp` <br/> <span style="color: #4D4DFF;font-size:12px;">Required</span>| `conversionDateTime` | 
| `properties.conversionValue`<br/>`properties.total`<br/>`properties.value`<br/>`properties.revenue` | `conversionValue` | 
| `properties.currencyCode`<br/>`properties.currency` | `currencyCode` | 

### Store sales conversion

You can create a conversion action to [upload store sales conversions](https://developers.google.com/google-ads/api/docs/conversions/upload-store-sales-transactions) into Google Ads. The [Google Ads Store Conversion API](https://developers.google.com/google-ads/api/reference/rpc/v13/OfflineUserDataJobService#createofflineuserdatajob) creates an offline user data job.

A sample `track` call for a store sales conversion is shown below:

```javascript
rudderanalytics.track("Product Reviewed",{
    "loyaltyFraction": 1,
    "order_id": "order id",
    "currency": "USD",
    "revenue": "100",
    "store_code": "store code",
    "email": "alex@example.com",
    "gclid": "gclid",
    "conversionDateTime": "2022-01-01 12:32:45-08:00",
    "product_id": "123445",
    "custom_key": "CUSTOM_KEY",
    "CUSTOM_KEY": "CUSTOM_VALUE",
    "quantity": 123
  })
```

The below fields are required to send the store conversions successfully:
- `event`
- Any one of the `properties.total`, `properties.value`, `properties.revenue`, or `properties.currency`
 
See [job creation](https://github.com/rudderlabs/rudder-transformer/blob/develop/src/v0/destinations/google_adwords_offline_conversions/data/TrackCreateJobStoreConversionsConfig.json), [address info](https://github.com/rudderlabs/rudder-transformer/blob/develop/src/v0/destinations/google_adwords_offline_conversions/data/storeAddoperationAddressMap.json), and [conversion mapping](https://github.com/rudderlabs/rudder-transformer/blob/develop/src/v0/destinations/google_adwords_offline_conversions/data/TrackAddStoreConversionsConfig.json) parameter mappings for more information on the optional fields you can send in the payload.

If you specify a user identifier in **The user identifier for store and click conversions** setting but don't include it in the payload, RudderStack looks for the following fields as user identifiers (in the same priority order):
1. Address
2. Email
3. Phone

If none of the above are present, RudderStack sends an empty user identifier.

### Specify consent for click and call conversions

You can specify user consent for leveraging their data for advertisements and personalization in case of [click](#click-conversion), [call](#call-conversion), and [store sales](#store-sales-conversion) conversions. To do so, use the `integrations` object in your `track` event as follows:

```javascript
rudderanalytics.track('Signup Completed', {
  prop1: 'val1',
  gclid: "gclid_value",
  conversionDateTime: "2022-05-20 12:32:45-08:00"
}, {
  "integrations": {
    "GOOGLE_ADWORDS_OFFLINE_CONVERSIONS": {
      "consents": {
        "adUserData": "GRANTED",
        "adPersonalization": "GRANTED"
      }
    }
  }
});
```

Note the following:

- The permissible values for the `adUserData` and `adPersonalization` fields are:
  - `UNSPECIFIED`
  - `UNKNOWN`
  - `GRANTED`
- If you set these fields to any other value, RudderStack automatically changes them to `UNKNOWN`.
- If you do not set the `consents` field in the event payload, RudderStack sets the `adUserData` and `adPersonalization` fields to `UNSPECIFIED` by default.

## FAQ

#### How to check the upload conversions in Google Ads?

To check the upload conversions in Google Ads:

1. Log in to your [Google Ads account](https://ads.google.com/intl/en_IN/home/).
2. Click **Goals** in the left navigation bar. Then, click **Uploads** to view the uploaded conversions.

{{< image src="images/event-stream-destinations/gaoc/gaoc-uploads.webp" alt="Google Ads Offline Conversions" >}}

#### Why am I not seeing the enhanced conversions for my offline events?

Verify if you have accepted the customer data terms in the conversion settings page — follow these steps to do so:

1. Log in to your [Google Ads account](https://ads.google.com/intl/en_IN/home/).
2. Click **Goals** in the left navigation bar. Then, click **Settings**.
3. Click **Customer data terms**.
4. Review and accept the terms, then click **Save**.

{{< image src="images/event-stream-destinations/gaoc/gaoc-customer-data-terms.webp" alt="Google Ads Offline Conversions" >}}

See the [Google Ads documentation](https://support.google.com/google-ads/answer/11956168?hl=en#zippy=%2Cenhanced-conversions-not-in-use) for detailed information on enhanced conversions diagnosis.