Merge pull request #6348 from segmentio/DOC-857

Adding replace function to consent mode docs [DOC-857]

Author: forstisabella

src/connections/destinations/actions.md

@@ -193,7 +193,9 @@ If necessary, click **New Mapping** to create a new, blank action.
 
 The coalesce function takes a primary value and uses it if it is available. If the value isn't available, the function uses the fallback value instead. 
 
+### Replace function
 
+The replace function allows you to replace a string, integer, or boolean with a new value. You have the option to replace up to two values within a single field.
 
 ### Conditions
 

src/connections/destinations/catalog/actions-google-analytics-4-web/index.md

@@ -113,7 +113,7 @@ To enable consent mode for your Google Analytics 4 Web destination:
             * Ad User Data Consent State
             * Ad Personalization Consent State
             You can manually select `Granted` or `Denied` from the dropdown menu for Advanced consent mode settings, and type in `granted` or `denied` for basic consent mode settings.
-        5. *(Option 2)* Under the **Select mappings** section, create an event variable to directly grab the value from the payload (for example, `properties.adStorageConsentState`). Ensure it translates to `granted` or `denied`. You can use an insert function to translate to `granted` or `denied`. Use the replace function if it's a string. Do this for these fields:
+        5. *(Option 2)* Under the **Select mappings** section, create an event variable to directly grab the value from the payload (for example, `properties.adStorageConsentState`). Ensure it translates to `granted` or `denied`. You can use an insert or [replace function](/docs/connections/destinations/actions/#replace-function) to translate other values to `granted` or `denied`. Do this for these fields:
             * Ads Storage Consent State
             * Analytics Storage Consent State
             * Ad User Data Consent State

src/connections/destinations/catalog/actions-google-analytics-4/index.md

@@ -75,7 +75,7 @@ To enable consent mode for your Google Analytics 4 Cloud destination, you must u
 	2. Go to the **Mappings** tab of the destination.
 	3. Select the mapping you want to edit. 
 	4. Under the **Select mappings** section, find **Ad User Data Consent State**.
-	5. Select the **Event Variables** tab and create an event variable to directly grab the value from the payload. Ensure it translates to `GRANTED` or `DENIED`. You can use an insert function to translate to `GRANTED`or `DENIED` if your consent values are booleans. You can use the replace function if it's a string.
+	5. Select the **Event Variables** tab and create an event variable to directly grab the value from the payload. Ensure it translates to `GRANTED` or `DENIED`. You can use an insert or [replace function](/docs/connections/destinations/actions/#replace-function) to translate other values to `GRANTED`or `DENIED`. 
 	6. Repeat step 5 for **Ad Personalization Consent State**. 
 
 

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

@@ -87,7 +87,7 @@ To enable consent mode for your Google Ads Conversions destination, you must upd
     1. Navigate to **Connections > Destinations** and select your Google Ads Conversion destination. 
     2. Go to the **Mappings** tab of the destination.
     3. Select the mapping you want to edit. 
-    4. In the **Select mappings** section, for **Ad User Data Consent State** and **Ad Personalization Consent State**, select the **Event Variables** tab and create an event variable to directly grab the value from the payload. Ensure it translates to `GRANTED`, `DENIED`, or `UNSPECIFIED`. You can use an insert function to translate to `GRANTED`, `DENIED`, or `UNSPECIFIED` if your consent values are booleans. You can use the replace function if it's a string.
+    4. In the **Select mappings** section, for **Ad User Data Consent State** and **Ad Personalization Consent State**, select the **Event Variables** tab and create an event variable to directly grab the value from the payload. Ensure it translates to `GRANTED`, `DENIED`, or `UNSPECIFIED`. You can use an insert or [replace function](/docs/connections/destinations/actions/#replace-function) to translate other values to `GRANTED`, `DENIED`, or `UNSPECIFIED`.
 
 If you send `DENIED` for any of the two consent states, it results in an error and the data won't send to Google. For more information, see [FAQ about the EU user consent policy for Customer Match upload partners](https://support.google.com/google-ads/answer/14310715?hl=en){:target="_blank"}.