add migration-specific section

Author: forstisabella

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

@@ -6,7 +6,10 @@ hide-dossier: false
 id: 60ae8b97dcb6cc52d5d0d5ab
 ---
 
-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 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. 
+
+> warning "Upload Enhanced Conversion (Legacy) Actions will be deprecated after June 30th, 2024"
+> Segment will automatically migrate all enabled Upload Enhanced Conversion (Legacy) actions to the updated Upload Conversion Adjustment mappings on June 7th, 2024. For more information, see the [Automatic migration from Upload Enhanced Conversion (Legacy) Action](#automatic-migration-from-upload-enhanced-conversion-legacy-action) documentation.
 
 > 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. 
@@ -20,24 +23,20 @@ The Google Ads Conversions destination enables you to upload offline conversions
 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).
 
-> warning "Upload Enhanced Conversion (Legacy) Action Deprecation"
-> Google plans to sunset the Google Enhanced Conversion Legacy API on June 30th 2024. After that, Google will no longer let data flow and will no longer maintain the API.
->
-> Segment recommends users to transition to the "Upload Click Conversion," "Upload Call Conversion," and "Upload Conversion Adjustment" actions, to send data through the new Google Ads API. 
->
-> [Use these steps](#migrate-your-upload-enhanced-conversion-legacy-action) to migrate your Upload Enhanced Conversion (Legacy) Action subscriptions. 
-
 {% include components/actions-fields.html settings="true"%}
 
-## Migrate your Upload Enhanced Conversion (Legacy) Action
+## Migrate from your legacy Upload Enhanced Conversion Action
 
 To migrate from the legacy Upload Enhanced Conversion Action to the updated Upload Conversion Adjustment Action: 
 
-1. Fill out your Conversion ID and Customer ID settings.
-2. Fill out the required fields for the Upload Conversion Adjustment Action: 
+1. Navigate to the Google Ads Conversions destination in your warehouse and select the **Settings** tab. 
+2. On the Settings tab, enter your Conversion ID and Customer ID into the named fields. 
+2. Update the following fields for the Upload Conversion Adjustment Action mapping: 
     - Conversion Action ID
     - Adjustment Type
-3. Replicate as many fields from your original mapping as possible, using the table below for reference. Review the [Upload Conversion Adjustment Action](/docs/connections/destinations/catalog/actions-google-enhanced-conversions/#upload-conversion-adjustment) section for more details about each field. 
+3. Replicate as many fields from your original mapping as possible, using the following table for reference. 
+
+Review the [Upload Conversion Adjustment Action](/docs/connections/destinations/catalog/actions-google-enhanced-conversions/#upload-conversion-adjustment) section for more details about each field.
 
 | Upload Enhanced Conversion (Legacy)| Upload Conversion Adjustment | Default Mapping                      |
 |------------------------|----------------------------|--------------------------------------|
@@ -64,6 +63,15 @@ To migrate from the legacy Upload Enhanced Conversion Action to the updated Uplo
 | N/A | restatement_currency_code | Default Not Available     |
 
 
+### Automatic migration from Upload Enhanced Conversion (Legacy) Action
+The Upload Enhanced Conversion action relies on the Google Enhanced Conversion Legacy API, which will be deprecated on June 30th, 2024.
+
+On June 7, 2024, Segment will migrate all enabled legacy Upload Enhanced Conversion mappings to the new Upload Conversion Adjustment mapping, preserving as many mapping fields as possible. After this migration occurs, you must enter your Conversion ID and Customer ID into the settings for your Google Enhanced Conversions destination, update the Conversion Action and Adjustment Type fields in the Upload Conversion Adjustment mapping, and enable the mapping to prevent data loss.
+
+To migrate your mapping yourself, use the steps in the [Migrate from your legacy Upload Enhanced Conversion Action](#migrate-from-your-legacy-upload-enhanced-conversion-action) documentation. 
+
+Segment will deprecate all legacy Upload Enhanced Conversion legacy actions after June 30th, 2024.
+
 ## Consent mode
 [Consent mode](https://support.google.com/analytics/answer/9976101?hl=en){:target="_blank"} is a feature provided by Google in the context of its products, particularly the Gtag library and Google Analytics. As of March 6, 2024, Google announced that consent mode must function for European Economic Area (EEA) users, otherwise data from EEA users won't process.