diff --git a/src/connections/destinations/catalog/actions-1flow/index.md b/src/connections/destinations/catalog/actions-1flow/index.md
index 72fe57e8b1..0f3fe68ff4 100644
--- a/src/connections/destinations/catalog/actions-1flow/index.md
+++ b/src/connections/destinations/catalog/actions-1flow/index.md
@@ -19,7 +19,7 @@ When you use the 1Flow Web (Actions) Destination, Segment loads the [1Flow SDK](
 2. Search for and select **1Flow  Web (Actions) Destination**.
 3. Select the web source that will send data to 1Flow web (Actions) and follow the steps to name your destination. The web source chosen must use [Analytics.js 2.0](/docs/connections/source/catalog/libraries/website/javascript).
 4. On the **Settings** tab, input your 1Flow **PROJECT API KEY** and other destinations settings.
-5. Follow the step in the Destinations Actions docs to [customizing mappings](/docs/connections/destinations/action/#customizing-mappings).
+5. Follow the step in the Destinations Actions docs to [customize your mappings](/docs/connections/destinations/action/#customize-mappings).
 6. Enable the destination and configured mappings.
 
 {% include components/actions-fields.html %}
diff --git a/src/connections/destinations/catalog/actions-adobe-target-cloud/index.md b/src/connections/destinations/catalog/actions-adobe-target-cloud/index.md
index d17cdeb9b2..901f1558ba 100644
--- a/src/connections/destinations/catalog/actions-adobe-target-cloud/index.md
+++ b/src/connections/destinations/catalog/actions-adobe-target-cloud/index.md
@@ -23,7 +23,7 @@ The Adobe Target Cloud Mode destination sends user information to the Adobe Targ
 3. Click **Configure Adobe Target Cloud Mode** in the top-right corner of the screen.
 4. Select the source that will send data to Adobe Target Cloud Mode and follow the steps to name your destination.
 5. On the **Settings** tab, input your Adobe Target destination settings.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Enable the destination and configured mappings.
 
 {% include components/actions-fields.html %}
diff --git a/src/connections/destinations/catalog/actions-adobe-target-web/index.md b/src/connections/destinations/catalog/actions-adobe-target-web/index.md
index f08742cdb5..aee557867d 100644
--- a/src/connections/destinations/catalog/actions-adobe-target-web/index.md
+++ b/src/connections/destinations/catalog/actions-adobe-target-web/index.md
@@ -23,7 +23,7 @@ The Adobe Target Web destination loads Adobe's `at.js` script for you in order t
 3. Click **Configure Adobe Target Web** in the top-right corner of the screen.
 4. Select the web source that will send data to Adobe Target Web and follow the steps to name your destination. The web source chosen must use [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/).
 5. On the **Settings** tab, input your Adobe Target destination settings.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Enable the destination and configured mappings.
 
 {% include components/actions-fields.html %}
diff --git a/src/connections/destinations/catalog/actions-amplitude/index.md b/src/connections/destinations/catalog/actions-amplitude/index.md
index e543879bf8..62cb81fb0f 100644
--- a/src/connections/destinations/catalog/actions-amplitude/index.md
+++ b/src/connections/destinations/catalog/actions-amplitude/index.md
@@ -33,7 +33,7 @@ Amplitude (Actions) provides the following benefits over the classic Amplitude d
 4. Click the "Amplitude" item to select it and click **Configure**.
 5. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)
 
-Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 
 ### Log Purchases in existing destination instances
 
@@ -208,7 +208,7 @@ To use Amplitude's groups with Segment, you must enable the following Action set
 Keep the following in mind if you plan to move to Amplitude (Actions) from a classic Amplitude destination.
 
 > info ""
-> In some cases, Amplitude Classic uses different default mappings than Amplitude (Actions). For example, the `Viewed Home Page` event in Amplitude Classic will be `Viewed Home` in Amplitude Actions, unless you configure it as `Viewed Home Page`. Be sure to follow the steps in the Destination Actions documentation to [customize your mappings](/docs/connections/destinations/actions/#customizing-mappings). Review how events appear in each destination, and configure the Actions' mappings properly to maintain continuity between Classic and Actions destinations.
+> In some cases, Amplitude Classic uses different default mappings than Amplitude (Actions). For example, the `Viewed Home Page` event in Amplitude Classic will be `Viewed Home` in Amplitude Actions, unless you configure it as `Viewed Home Page`. Be sure to follow the steps in the Destination Actions documentation to [customize your mappings](/docs/connections/destinations/actions/#customize-mappings). Review how events appear in each destination, and configure the Actions' mappings properly to maintain continuity between Classic and Actions destinations.
 
 ### Amplitude (Actions) uses Amplitude's HTTP API v2
 
diff --git a/src/connections/destinations/catalog/actions-blackbaud-raisers-edge-nxt/index.md b/src/connections/destinations/catalog/actions-blackbaud-raisers-edge-nxt/index.md
index 12891893d3..b93cf22327 100644
--- a/src/connections/destinations/catalog/actions-blackbaud-raisers-edge-nxt/index.md
+++ b/src/connections/destinations/catalog/actions-blackbaud-raisers-edge-nxt/index.md
@@ -20,7 +20,7 @@ your Blackbaud Developer account.
 6. Visit the Blackbaud ["My subscriptions"](https://developer.blackbaud.com/subscriptions/){:target="_blank"}
 page, copy your **Primary access key**, and paste the value into the **Blackbaud API Subscription Key** field.
 7. Follow the steps in the Destinations Actions documentation on
-[Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings). You must select which
+[Customizing mappings](/docs/connections/destinations/actions/#customize-mappings). You must select which
 Event Types and/or Event Names will trigger each mapping.
 8. Enable the destination and configured mappings.
 
diff --git a/src/connections/destinations/catalog/actions-facebook-conversions-api/index.md b/src/connections/destinations/catalog/actions-facebook-conversions-api/index.md
index 313e6514a9..a745137faf 100644
--- a/src/connections/destinations/catalog/actions-facebook-conversions-api/index.md
+++ b/src/connections/destinations/catalog/actions-facebook-conversions-api/index.md
@@ -60,7 +60,7 @@ Set up your Pixel to work with the Facebook Conversions API (Actions) destinatio
 3. Click **Configure Facebook Conversions API (Actions)** in the top-right corner of the screen.
 4. Select the source that will send data to Facebook Conversions API and follow the steps to name your destination.
 5. On the **Settings** tab, enter in your Pixel ID and click **Save**.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 
 {% include components/actions-fields.html %}
 
diff --git a/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md b/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md
index 1252047838..b76120d11a 100644
--- a/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md
+++ b/src/connections/destinations/catalog/actions-google-analytics-4-web/index.md
@@ -28,7 +28,7 @@ To connect the Google Analytics 4 Web destination:
 3. Click **Configure Google Analytics 4 Web**.
 4. Select the web source that will send data to Google Analytics 4 and follow the steps to name your destination. The web source chosen must use [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/). For mobile source tracking, view the [Firebase Destination](/docs/connections/destinations/catalog/firebase/).
 5. On the **Settings** tab, under **Basic Settings**, enter in the [Measurement ID](https://support.google.com/analytics/answer/9539598){:target='_blank'} associated with your GA4 web stream.
-6. Set up your event mappings by following the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Set up your event mappings by following the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Analytics.js requires an initial Page call to send data to Google Analytics 4 Web. The [Segment snippet](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/#step-2-add-the-segment-snippet) includes this initial call by default.
 8. For GA4 to accept events on page, enable Set Configuration Mapping triggered by the first Segment event called after analytics.load(). Set Configuration Mapping calls the gtag(‘config’) command to enable tracking to your GA4 Measurement ID. 
 
diff --git a/src/connections/destinations/catalog/actions-google-analytics-4/index.md b/src/connections/destinations/catalog/actions-google-analytics-4/index.md
index b5def32221..56fc932513 100644
--- a/src/connections/destinations/catalog/actions-google-analytics-4/index.md
+++ b/src/connections/destinations/catalog/actions-google-analytics-4/index.md
@@ -44,7 +44,7 @@ To add the Google Analytics 4 Cloud destination:
 3. Click **Configure Google Analytics 4 Cloud** in the top-right corner of the screen.
 4. Select the source that will send data to Google Analytics 4 and follow the steps to name your destination.
 5. On the **Settings** tab, enter in the [Measurement ID](https://support.google.com/analytics/answer/9539598){:target='_blank'} for web streams or the [Firebase App ID](https://developers.google.com/analytics/devguides/collection/protocol/ga4/reference?client_type=firebase#payload_query_parameters){:target='_blank'} for mobile streams. Next, enter in the API Secret associated with your GA4 stream and click **Save**. To create a new API Secret, navigate in the Google Analytics UI to Admin > Data Streams > choose your stream > Measurement Protocol > Create.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 
 
 {% include components/actions-fields.html %}
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 14ada365cd..96fb82a4d6 100644
--- a/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
+++ b/src/connections/destinations/catalog/actions-google-enhanced-conversions/index.md
@@ -17,19 +17,101 @@ hide_action:
     name: 'Upload Enhanced Conversion (Legacy)'
 ---
 
-The Google Ads Conversions destination enables you to upload offline conversions and conversion adjustments to Google Ads in a privacy safe way. With this server-side destination, you can upload conversions to the [Google Ads API](https://developers.google.com/google-ads/api/docs/conversions/overview){:target="_blank"} and tie them to a user's online click or phone call. In addition, you can improve the accuracy of your conversion measurement by sending conversion enhancements, restatements, and retractions.
+The Google Ads destination allows users to upload [conversions](https://developers.google.com/google-ads/api/docs/conversions/upload-clicks){:target="_blank"}, [conversion adjustments](https://developers.google.com/google-ads/api/docs/conversions/upload-adjustments){:target="_blank"}, and [customer match lists](https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started){:target="_blank"} in a privacy-safe manner. Marketers can use this integration to re-engage users across Search, Shopping, Gmail, YouTube, and Display by combining conversion data with customer match lists for more effective targeting.
 
 > info "Consent mode"
 > Google enforced consent on March 6, 2024 for European Economic Area (EEA) users. Learn more about [consent mode](/docs/connections/destinations/catalog/actions-google-enhanced-conversions/#consent-mode) and how to set it up.
 
 ## Getting started
-1. From the Segment web app, click **Catalog**, then click **Destinations**.
-2. Search for “Google Ads Conversions” in the Destinations Catalog, and select the destination.
-3. Click **Configure Google Ads Conversions** in the top-right corner of the screen.
-4. Select the source that will send data to Google Ads Conversions and follow the steps to name your destination.
-5. On the **Settings** tab, enter your account-level Conversion ID and/or Customer ID and click **Save**.
-6. On the **Settings** tab, authenticate with Google using OAuth. Click **Connect to Google Ads Conversions**. Follow the prompts to authenticate using OAuth, with a Google account that is a member of your Google Ads account.
-7. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+
+> info ""
+> You can connect the Google Ads Conversions Destination to an event source, Reverse ETL source, or Engage space. 
+
+### Prerequisites
+* A Google Ads account and the account ID of your Google Ads Account. This should be 10-digits and in XXX-XXX-XXXX format.  
+* For sending data to a Google [Customer Match list](https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started){:target="_blank"}, you will either need   
+  * An [Engage Audience](/docs/engage/audiences/) configured which you can connect to this destination  
+  * A Reverse ETL source already set up. If you don’t yet have a Reverse ETL source, follow the instructions in Segment’s [Reverse ETL documentation](/docs/connections/reverse-etl/setup/).
+
+### Connect to Google Ads
+1. From the Segment web app, navigate to **Catalog > Destinations**.
+2. Search for “Google Ads Conversions” in the Destinations Catalog and select the destination.
+3. Click **Add destination**.
+4. Select the source that will send data to Google Ads Conversions. 
+  * If you select an Engage space, you'll be redirected to Engage to complete the following steps.
+  * If you select a Reverse ETL source, you must enter a name for your destination and click **Create destination**.
+5. On the **Settings** tab for your Google Ads Conversions destination:
+  * Enter your account-level Conversion ID and/or Customer ID and click **Save**.
+  * Click **Connect to Google Ads Conversions** to authenticate with Google. Follow the prompts to authenticate using OAuth, with a Google account that is a member of your Google Ads account.
+7. Follow the steps in the Destinations Actions documentation to [customize your mappings](/docs/connections/destinations/actions/#customize-mappings).
+
+
+### Connect to Google Ads Customer Match lists
+
+Segment users can send data to [Google Ads Customer Match](https://developers.google.com/google-ads/api/docs/remarketing/audience-types/customer-match){:target="_blank"} lists using [Engage Audiences](#connect-engage-audiences-to-google-ads-customer-match) or [Reverse ETL](#connect-reverse-etl-to-google-ads-customer-match). 
+
+#### Connect Engage Audiences to Google Ads Customer Match
+
+1. Navigate to the Engage Audience you'd like to connect to Google Ads and click **Add destination**.  
+2. Select the instance of Google Ads you added to your Engage space.  
+3. Complete your Audience settings.  
+4. Disable **Send Identify** and enable **Send Track**.  
+    _Optional_: Configure your event settings and opt in to [Trait Enrichment](/docs/engage/trait-activation/trait-enrichment/).  
+6. Click **Save**.  
+7. Navigate to the destination’s mappings tab and click **View all destination settings**.  
+8. Navigate to the Mappings tab.  
+9. Click **+ New Mapping**.  
+10. Configure your mappings and use the **Show test record** preview toggle to verify your mappings.  
+11. Click **Save** and enable your mapping.
+
+#### Connect Reverse ETL to Google Ads Customer Match
+
+After you’ve connected your Google Ads destination to Segment, set up [Reverse ETL mappings](/docs/connections/reverse-etl/setup/#step-4-create-mappings) to sync to a Google Customer Match List.
+
+##### Add users to your Google Customer Match User List  
+1. From your Segment workspace, navigate to your Reverse ETL source.
+2. Select the Reverse ETL model you'd like to sync with Google Ads.
+3. Click **Add Mapping**.
+4. Select the Google Ads Conversions destination and click **Next**.
+5. Select the **Customer Match User List** action and the **Adds users to the connected Google Customer Match User List** sync mode.
+6. Select an existing List ID or provide a name for the list that Segment creates for you.
+7. Select an External ID Type, configure your mappings, and click **Next**. 
+8. Enter a name for your mapping, set your sync schedule, and click **Save**.  
+9. On the mapping's overview page, set the Status toggle to **Enabled**.  
+
+##### Remove users from the connected Google Customer Match User List  
+1. From your Segment workspace, navigate to your Reverse ETL source.
+2. Select the Reverse ETL model you'd like to sync with Google Ads.
+3. Click **Add Mapping**.
+4. Select the Google Ads Conversions destination and click **Next**.
+4. Select the **Customer Match User List** action and the **Remove users from the connected Google Customer Match User List** sync mode. 
+5. Select the List ID that you configured when you set up the [Add users to your Google Customer Match User List](#add-users-to-your-google-customer-match-user-list) mapping.
+6. Select an External ID Type, configure your mappings, and click **Next**. 
+9. Enter a name for your mapping, set your sync schedule, and click **Save**.  
+10. On the mapping's overview page, set the Status toggle to **Enabled**.  
+
+## Data normalization
+
+To improve match rates, Segment built in normalization and hashing for common fields to align with Google's best practices outlined in Google's [Prepare data for upload](https://developers.google.com/google-ads/api/docs/conversions/enhanced-conversions/leads#prepare-data){:target="_blank"} and [Add customer data](https://developers.google.com/google-ads/api/docs/remarketing/audience-segments/customer-match/get-started#add-user){:target="_blank"} documentation.
+
+### Normalization 
+
+Segment automatically strips whitespace and converts the following fields to lowercase:
+  * Email
+  * First name
+  * Last name
+
+Segment normalizes the Phone field by removing any non-numeric symbols. Segment also converts each phone number to [E.164](https://en.wikipedia.org/wiki/E.164){:target="_blank"} format before hashing. E.164 format represents a phone number as a number up to fifteen digits in length starting with a + sign.
+
+### Hashing
+
+Google requires you to hash all PII before sending it to the Google API. 
+
+Segment automatically hashes any of the following fields that are not already hashed at egress:
+ * Email
+ * Phone number
+ * First name
+ * Last name
 
 {% include components/actions-fields.html settings="true"%}
 
diff --git a/src/connections/destinations/catalog/actions-hubspot-web/index.md b/src/connections/destinations/catalog/actions-hubspot-web/index.md
index 40e4dcb665..eca750f76f 100644
--- a/src/connections/destinations/catalog/actions-hubspot-web/index.md
+++ b/src/connections/destinations/catalog/actions-hubspot-web/index.md
@@ -32,7 +32,7 @@ HubSpot Web (Actions) provides the following benefits over the classic HubSpot d
 3. Click **Configure HubSpot Web (Actions)**.
 4. Select the web source that will send data to HubSpot Web (Actions) and follow the steps to name your destination. The web source chosen must use [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/).
 5. On the **Settings** tab, input your HubSpot Hub ID and configure the other destination settings.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Enable the destination and configured mappings.
 
 {% include components/actions-fields.html settings="true"%}
diff --git a/src/connections/destinations/catalog/actions-intercom-web/index.md b/src/connections/destinations/catalog/actions-intercom-web/index.md
index bcbd869c67..f57cbbc62d 100644
--- a/src/connections/destinations/catalog/actions-intercom-web/index.md
+++ b/src/connections/destinations/catalog/actions-intercom-web/index.md
@@ -51,7 +51,7 @@ To access the Intercom Messaging Box, you'll need to configure and connect the I
 3. Click **Configure Intercom Web (Actions)**.
 4. Select the web source that will send data to Intercom Web (Actions) and follow the steps to name your destination. The web source chosen must use [Analytics.js 2.0](/docs/connections/sources/catalog/libraries/website/javascript/).
 5. On the **Settings** tab, input your Intercom App ID and other destination settings.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Enable the destination and configured mappings.
 
 > info "Regional Data Hosting in the EU and Australia"
diff --git a/src/connections/destinations/catalog/actions-pardot/index.md b/src/connections/destinations/catalog/actions-pardot/index.md
index 73d0d29705..dc312f2de8 100644
--- a/src/connections/destinations/catalog/actions-pardot/index.md
+++ b/src/connections/destinations/catalog/actions-pardot/index.md
@@ -34,7 +34,7 @@ To get started using Pardot with Segment:
 4. Accept the Beta terms.
 5. Select the source that will send data to Pardot (Actions) and follow the steps to name your destination.
 6. On the **Settings** tab, authenticate with Salesforce Pardot using OAuth. Input the Pardot Business Unit ID associated with your Pardot Account, and click **Save**.
-7. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+7. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 8. Enable the destination and configured mappings.
 
 {% include components/actions-fields.html %}
diff --git a/src/connections/destinations/catalog/actions-salesforce-marketing-cloud/index.md b/src/connections/destinations/catalog/actions-salesforce-marketing-cloud/index.md
index 3d34244d78..18e13a6bb4 100644
--- a/src/connections/destinations/catalog/actions-salesforce-marketing-cloud/index.md
+++ b/src/connections/destinations/catalog/actions-salesforce-marketing-cloud/index.md
@@ -53,7 +53,7 @@ Once you save the API integration and add permissions, you will see a Summary pa
 3. Click **Configure Salesforce Marketing Cloud (Actions)** in the top-right corner of the screen.
 4. Select the source that will send data to SFMC and follow the steps to name your destination.
 5. On the **Settings** tab, input your SFMC Account ID (MID). In the Installed Package you created above, locate your Subdomain, Client ID, and Client Secret and input these settings. Your Subdomain can be found under "REST Base URI." Your Subdomain should be a 28-character string starting with the letters `mc`. Do not include the `.rest.marketingcloudapis.com` part of the URL.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 7. Enable the destination and configured mappings.
 
 {% include components/actions-fields.html settings="true"%}
diff --git a/src/connections/destinations/catalog/actions-salesforce/index.md b/src/connections/destinations/catalog/actions-salesforce/index.md
index 14b99750ae..ae3e9b4ff0 100644
--- a/src/connections/destinations/catalog/actions-salesforce/index.md
+++ b/src/connections/destinations/catalog/actions-salesforce/index.md
@@ -33,7 +33,7 @@ Before you connect Segment to Salesforce, please ensure you have a Salesforce ac
 3. Click **Configure Salesforce** in the top-right corner of the screen.
 4. Select the source that will send data to Salesforce, follow the steps to name your destination, and select **Actions** as the destination framework.
 5. On the **Settings** tab, authenticate with Salesforce using OAuth.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings). You must select which Event Types and/or Event Names will trigger each mapping.
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings). You must select which Event Types and/or Event Names will trigger each mapping.
 7. Enable the destination and configured mappings.
 
 > info "Salesforce (Actions) authentication limitations"
diff --git a/src/connections/destinations/catalog/actions-snap-conversions/index.md b/src/connections/destinations/catalog/actions-snap-conversions/index.md
index 0ef7f67187..15b55d104a 100644
--- a/src/connections/destinations/catalog/actions-snap-conversions/index.md
+++ b/src/connections/destinations/catalog/actions-snap-conversions/index.md
@@ -24,7 +24,7 @@ The Snapchat Conversions API destination provides the following benefits:
 5. On the **Settings** tab, authenticate with Snap using OAuth. Click **Connect to Snapchat Conversions API**. Follow the prompts to authenticate using OAuth, with a Snapchat login that is a member of the Snapchat Ads account you want to connect.
 6. Add your [Snap Pixel ID](https://businesshelp.snapchat.com/s/article/pixel-website-install?language=en_US){:target="_blank"} *if you plan to send web or offline events*. *If you plan to send app events,* add your [Snap App ID](https://businesshelp.snapchat.com/s/article/snap-app-id?language=en_US​){:target="_blank"} and App ID.
 7. Enable the destination and click **Save**.
-8. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+8. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 
 > warning ""
 > To send events to Snap, you **must** add a Pixel ID for web and offline conversions or a Snap App ID and App ID for mobile conversions. If missing, events will fail.
diff --git a/src/connections/destinations/catalog/tiktok-conversions/index.md b/src/connections/destinations/catalog/tiktok-conversions/index.md
index b7671dfa06..5781a88ea5 100644
--- a/src/connections/destinations/catalog/tiktok-conversions/index.md
+++ b/src/connections/destinations/catalog/tiktok-conversions/index.md
@@ -38,7 +38,7 @@ The TikTok Conversions destination is configured to use the TikTok Events API. T
 3. Click **Configure TikTok Conversions**.
 4. Select the source that will send data to TikTok Conversions and follow the steps to name your destination.
 5. On the Settings tab, enter in your TikTok Access Token and Pixel Code and click **Save**.
-6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+6. Follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 
 {% include components/actions-fields.html %}
 
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/amplitude-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/amplitude-swift.md
index 291c2366b6..91f3e099b4 100644
--- a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/amplitude-swift.md
+++ b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/amplitude-swift.md
@@ -13,7 +13,7 @@ strat: swift
 4. Click the "Amplitude" item to select it and click **Configure**.
 5. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)
 
-Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 
 The Amplitude Swift plugin doesn't send events to Amplitude from the client side. It instead adds Amplitude session data and then sends it server side from the Amplitude Actions destination.
 
diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/amplitude-kotlin-android.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/amplitude-kotlin-android.md
index cc791696d6..2ae13db570 100644
--- a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/amplitude-kotlin-android.md
+++ b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/amplitude-kotlin-android.md
@@ -14,7 +14,7 @@ perform, you can gain a better understanding to drive retention, engagement, and
 4. Click the "Amplitude" item to select it and click **Configure**.
 5. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)
 
-Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customize-mappings).
 
 The Amplitude Kotlin plugin doesn't send events to Amplitude from the client side. It instead adds Amplitude session data and then sends it server side from the Amplitude Actions destination.
 
diff --git a/src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native.md b/src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native.md
index 0b53e0b2ad..092a8faa86 100644
--- a/src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native.md
+++ b/src/connections/sources/catalog/libraries/mobile/react-native/destination-plugins/amplitude-react-native.md
@@ -13,7 +13,7 @@ strat: react-native
 4. Click the "Amplitude" item to select it and click **Configure**.
 5. Choose which of your sources to connect the destination to. (You can connect more sources to the destination later.)
 
-Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/#customizing-mappings).
+Once you have a mapping, you can follow the steps in the Destinations Actions documentation on [Customizing mappings](/docs/connections/destinations/actions/customize-mappings).
 
 The Amplitude React Native plugin doesn't send events to Amplitude from the client side. It instead adds Amplitude session data and then sends it server side from the Amplitude Actions destination.