From 0d3cca5c3b686fea3402f7ba8ecbe177a1039a9f Mon Sep 17 00:00:00 2001
From: Panandhan22 <115441424+Panandhan22@users.noreply.github.com>
Date: Mon, 30 Sep 2024 18:33:16 +0800
Subject: [PATCH 1/2] Click conversion v2
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

### what is the difference between the action "Upload Click Conversions" and "Click Conversion V2"?
The only difference with the new "Click Conversion v2" action is the rollout of [sync modes]([https://developers.google.com/google-ads/api/reference/rpc/v15/ConversionUploadErrorEnum.ConversionUploadError#invalid_conversion_action_type](https://segment.com/docs/connections/destinations/#sync-modes)){:target="_blank”}. And these sync mode options will not be available for the "Upload click conversion" actions mapping over the UI. Other than that, both action mappings will work in the same way.
---
 .../catalog/actions-google-enhanced-conversions/index.md      | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
index 96fb82a4d6..cb525d041b 100644
--- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
+++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
@@ -181,3 +181,7 @@ To resolve this, ensure that the ConversionActionType value in Google Ads is cor
 ### `The required field was not present., at conversions[0].gclid` Error
 
 Events going to Google for this integration require a `GCLID` field, an `email`, or a `phone_number`. If one of those identifiers isn't being sent properly, then you may see the `The required field was not present., at conversions[0].gclid` error. To fix this, double check that at least one of those fields is being passed to Google on each payload.
+
+### what is the difference between the action "Upload Click Conversions" and "Click Conversion V2"?
+The only difference with the new "Click Conversion v2" action is the rollout of [sync modes]([https://developers.google.com/google-ads/api/reference/rpc/v15/ConversionUploadErrorEnum.ConversionUploadError#invalid_conversion_action_type](https://segment.com/docs/connections/destinations/#sync-modes)){:target="_blank”}. And these sync mode options will not be available for the "Upload click conversion" actions mapping over the UI. Other than that, both action mappings will work in the same way.
+

From 068957c27589d8f5b7c47716bb9f1a863a335490 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Thu, 19 Dec 2024 10:11:00 -0500
Subject: [PATCH 2/2] Update
 src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

---
 .../catalog/actions-google-enhanced-conversions/index.md      | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
index cb525d041b..5af54aac79 100644
--- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
+++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
@@ -182,6 +182,6 @@ To resolve this, ensure that the ConversionActionType value in Google Ads is cor
 
 Events going to Google for this integration require a `GCLID` field, an `email`, or a `phone_number`. If one of those identifiers isn't being sent properly, then you may see the `The required field was not present., at conversions[0].gclid` error. To fix this, double check that at least one of those fields is being passed to Google on each payload.
 
-### what is the difference between the action "Upload Click Conversions" and "Click Conversion V2"?
-The only difference with the new "Click Conversion v2" action is the rollout of [sync modes]([https://developers.google.com/google-ads/api/reference/rpc/v15/ConversionUploadErrorEnum.ConversionUploadError#invalid_conversion_action_type](https://segment.com/docs/connections/destinations/#sync-modes)){:target="_blank”}. And these sync mode options will not be available for the "Upload click conversion" actions mapping over the UI. Other than that, both action mappings will work in the same way.
+### What are the differences between the Upload Click Conversions and Click Conversion V2 Actions?
+The only difference between the Upload Click Conversions and Click Conversion V2 Actions is that the Click Conversion V2 Action has [sync modes](/docs/connections/destinations/#sync-modes).