# Google Ads

## Extension Configuration

This extension does not have any extension configuration to migrate. However, since the [Adobe-built Google Gtag extension](/analytics/adobe-launch/gtag/migration-guides/google-gtag.md) is a required extension to make the Adobe-built Google Ads extension work properly, that extension [should be migrated](/analytics/adobe-launch/gtag/migration-guides/google-gtag.md) to ensure the Acronym-built Gtag is configured correctly.

## Rule Actions

The Adobe-built extension only has one rule action to migrate: Track Conversion.

### Track Conversion

The track conversion rule action sends conversion data to Google Ads. 

![Settings for the track conversion action](/files/-MMptKu1AOsABW-9fm97)

The Track Conversion action is equivalent to the [Send an event action](/analytics/adobe-launch/gtag/actions/event.md) the gtag extension provides. There are five fields that should be migrated over:

#### Conversion ID

The conversion ID is the same as the Account ID in the gtag extension (starts with `AW-` or `DC-`). If you haven't already done so for this conversion ID, [create a new account](/analytics/adobe-launch/gtag/configuration.md#accounts) in the gtag extension.

#### Conversion Label

The conversion label should be migrated to the new Acronym-built gtag action, under the [Conversion Label field](/analytics/adobe-launch/gtag/actions/event.md#account-specific-settings) for the Ads account.

#### Conversion Value

The conversion value should be migrated to the [Value field ](/analytics/adobe-launch/gtag/actions/event.md#event-value)for the event action.

#### **Currency Code & Order ID**

Both currency code and order ID will need to be migrated as an [event parameter](/analytics/adobe-launch/gtag/actions/event.md#custom-data-fields) in the event action. You should use the field names `currency` and `transaction_id`, respectively. 

{% hint style="info" %}
**Note:** If you're only using Google Ads for this rule, then you may need to add the [event name](/analytics/adobe-launch/gtag/actions/event.md#event-name-action), which wasn't previously required in the Track Conversion action. If you're using Google Analytics as well, then you likely already have an event name to use!
{% endhint %}

####

#### Example

Below is an example of what a successful migration would look like for the Track Conversion action:

![The existing Google Ads settings to send a conversion event.](/files/-MRWl0qqMBpV7LIo_9oA)

![The migrated conversion event, now using the gtag extension.](/files/-MRWhU4VxY73C63UHoHM)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.acronym.com/analytics/adobe-launch/gtag/migration-guides/google-ads.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.