Skip to content

Commit a056ab7

Browse files
Merge pull request #7104 from segmentio/google-ads-v2
Google Ads Conversions Destination Actions v2
2 parents e5e171a + 92d9fa5 commit a056ab7

File tree

1 file changed

+19
-0
lines changed
  • src/connections/destinations/catalog/actions-google-enhanced-conversions

1 file changed

+19
-0
lines changed

src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md

Lines changed: 19 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -113,6 +113,24 @@ Segment automatically hashes any of the following fields that are not already ha
113113
* First name
114114
* Last name
115115

116+
## Actions v2
117+
118+
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:
119+
120+
- **Sync modes**: Control how Segment updates your downstream destination by selecting a sync mode, or a strategy for updating your downstream data.
121+
- **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.
122+
- **Create and modify data**: Use Sync modes to create objects in your downstream destination without having to leave the Segment app.
123+
124+
> warning ""
125+
> You might need to reauthorize your Google Ads account to use all of the features associated with v2 Actions.
126+
127+
### Sync modes
128+
129+
Sync modes allow users to define how Segment should update the data in your destination.
130+
131+
Sync modes available for v2 Actions include:
132+
- **Add**: Add records to a list, segment, or journey.
133+
116134
{% include components/actions-fields.html settings="true"%}
117135

118136
## Consent mode
@@ -181,3 +199,4 @@ To resolve this, ensure that the ConversionActionType value in Google Ads is cor
181199
### `The required field was not present., at conversions[0].gclid` Error
182200

183201
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.
202+

0 commit comments

Comments
 (0)