From d7b21c10e8845f7d22b73e47b4f74c8ddf039437 Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Tue, 1 Oct 2024 15:55:49 -0400
Subject: [PATCH 1/2] google ads conversions v2

---
 .../index.md                                   | 18 ++++++++++++++++++
 1 file changed, 18 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..7826ae1d14 100644
--- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
+++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
@@ -113,6 +113,24 @@ Segment automatically hashes any of the following fields that are not already ha
  * First name
  * Last name
 
+## Actions v2
+
+Segment’s v2 Actions, [Call Conversion v2](#call-conversion-v2), [Conversion Adjustment v2](#conversion-adjustment-v2), and [Click Conversion v2](#click-conversion-v2), support the following features:
+
+- **Sync modes**: Control how Segment updates your downstream destination by selecting a sync mode, or a strategy for updating your downstream data. 
+- **Dynamic dropdowns**: When creating or updating a mapping in the Segment app, the dropdown auto-populates all of the available properties directly from Google Ads.
+- **Create and modify data**: Use Sync modes to create objects in your downstream destination without having to leave the Segment app.
+
+> warning ""
+> You might need to reauthorize your Google Ads account to use all of the features associated with v2 Actions.
+
+### Sync modes
+
+Sync modes allow users to define how Segment should update the data in your destination.
+
+Sync modes available for v2 Actions include:
+- **Add**: Add records to a list, segment, or journey.
+
 {% include components/actions-fields.html settings="true"%}
 
 ## Consent mode

From 92d9fa59091df1a3ca40dc1c7646d76f3fbab36e Mon Sep 17 00:00:00 2001
From: forstisabella <92472883+forstisabella@users.noreply.github.com>
Date: Tue, 1 Oct 2024 15:57:34 -0400
Subject: [PATCH 2/2] [netlify-build]

---
 .../catalog/actions-google-enhanced-conversions/index.md         | 1 +
 1 file changed, 1 insertion(+)

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 7826ae1d14..5cf0e99016 100644
--- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
+++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
@@ -199,3 +199,4 @@ 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.
+