Merge pull request #8076 from segmentio/sucess-tip

forstisabella · web-flow · commit 9c10901506e7 · 2025-10-21T09:20:42.000-04:00
Success tip
diff --git a/src/api/config-api/tutorial-javascript-google-analytics.md b/src/api/config-api/tutorial-javascript-google-analytics.md
@@ -33,8 +33,8 @@ See the [Authentication](/docs/api/config-api/authentication/) doc for more info
 
 To set up Segment Protocols through the API you first need to create a personal access token with **full access** to your workspace through the `workspace` scope.
 
-> success ""
-> **Tip**: As best practice, tokens should be assigned the least permissions needed to perform a required API action, however for simplicity in this demo, we'll select Workspace Owner. You may want to delete the token once you've finished this demo.
+> info "Tip"
+> As best practice, tokens should be assigned the least permissions needed to perform a required API action, however for simplicity in this demo, we'll select Workspace Owner. You may want to delete the token once you've finished this demo.
 
 1. Log in to your Segment workspace.
 2. Click **Settings** in the left navigation bar.
diff --git a/src/connections/destinations/catalog/adobe-analytics/mobile.md b/src/connections/destinations/catalog/adobe-analytics/mobile.md
@@ -17,8 +17,8 @@ Before you start sending data from your mobile application to Adobe Analytics, y
 - Download these settings as the `ADBMobileConfig.json` file by clicking the **Config JSON** link at the bottom of the same tab. Follow the instructions in Adobe's [Configuration documentation](https://developer.adobe.com/client-sdks/home/base/mobile-core/configuration/){:target="_blank”}.
 - Finally, follow the instructions below for each mobile environment to bundle Segment's Adobe Analytics SDK in your project.
 
-> success ""
-> **Tip**: Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
+> info "Tip"
+> Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
 
 #### For Android
 
diff --git a/src/connections/destinations/catalog/adobe-analytics/settings.md b/src/connections/destinations/catalog/adobe-analytics/settings.md
@@ -7,8 +7,8 @@ This page explains in detail how to configure your Segment Adobe Analytics Desti
 
 Segment uses a user-action data model, which uses different types of calls to track a user's different activities on a website or app. Adobe Analytics uses page views as the basic unit of activity, and specific data variables such as "props", eVars, lVars, and hVars to add details that allow more granular analysis. The Adobe Analytics destination settings in the Segment App allow you to create mappings between properties in your Segment calls and Adobe's expected format.
 
-> success ""
-> **Tip**: Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings. See the [Segment Adobe Analytics Mobile documentation](/docs/connections/destinations/catalog/adobe-analytics/mobile) to learn more.
+> info "Tip"
+> Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings. See the [Segment Adobe Analytics Mobile documentation](/docs/connections/destinations/catalog/adobe-analytics/mobile) to learn more.
 
 ## Implementing Success Events
 
diff --git a/src/connections/destinations/catalog/amplitude/index.md b/src/connections/destinations/catalog/amplitude/index.md
@@ -89,8 +89,8 @@ When you use the **Track Named Pages** or **Track Categorized Pages** settings,
 
 When you use the **Track All Pages** setting, Segment sends a `Loaded a Page` event type to Amplitude. When you use the generic event name, it is applied to all Page and Screen calls, so you don't hit the event type limit in your project in Amplitude. The page or screen name is still available as an attribute of the `Loaded a Page` event, and you can query it as an event property. The `Loaded a Page` event is counted as one event type, and Amplitude does not place any limits on the number of unique event property values in Amplitude.
 
-> success ""
-> **Tip**: These settings also apply to mobile Cloud-mode connections.
+> info "Tip"
+> These settings also apply to mobile Cloud-mode connections.
 
 ### Event Type settings for iOS
 
@@ -308,8 +308,8 @@ For Segment's Analytics.js (device-mode), iOS, and Android sources, if you do no
 
 In Segment's Analytics.js, iOS and Android sources, if `properties.price` isn't present, Segment falls back to `revenue` and sends that as `price`. The Segment iOS and Android sources also do an additional fallback to `total`, if `revenue` isn't present either.
 
-> success ""
-> **Tip** If your site allows users to perform a single transaction with multiple products (such as a shopping cart checkout), Segment recommends that you use an [Order Completed](/docs/connections/destinations/catalog/amplitude/#order-completed) event to track revenue with Amplitude.
+> info "Tip"
+> If your site allows users to perform a single transaction with multiple products (such as a shopping cart checkout), Segment recommends that you use an [Order Completed](/docs/connections/destinations/catalog/amplitude/#order-completed) event to track revenue with Amplitude.
 
 
 
diff --git a/src/connections/destinations/catalog/doubleclick-floodlight/index.md b/src/connections/destinations/catalog/doubleclick-floodlight/index.md
@@ -113,8 +113,8 @@ If you want to set this flag, you can send an integration option namespaced as `
 Analytics.with(context).track("Free El", new Properties().putValue("show", "Stranger Things").putValue("source", "Netflix").putValue("greatestShowEver", true), new Options().setIntegrationOptions("DoubleClick Floodlight", new ValueMap().putValue("coppaCompliant", true)));
 ```
 
-> success ""
-> **Tip**: This flag was previously called `copaCompliant` (a typo) instead of `coppaCompliant`. The method has been aliased to preserve the old functionality, and you do not need to update it if you used the old spelling.
+> info "Tip"
+> This flag was previously called `copaCompliant` (a typo) instead of `coppaCompliant`. The method has been aliased to preserve the old functionality, and you do not need to update it if you used the old spelling.
 
 ## Sending Personally Identifiable Information (PII)
 
diff --git a/src/connections/destinations/catalog/mixpanel/index.md b/src/connections/destinations/catalog/mixpanel/index.md
@@ -667,8 +667,8 @@ To send computed traits or audiences to Mixpanel, connect the destination to you
 3. Enter your API Secret and Token for the integration.
 4. Enable the "Use Mixpanel People” toggle. This allows Engage to send `identify` calls to Mixpanel.
 
-> success ""
-> **Tip**: Mixpanel now accepts Identify calls by default. Previously, this was an additional paid feature.
+> info "Tip"
+> Mixpanel now accepts Identify calls by default. Previously, this was an additional paid feature.
 
 
 ![A screenshot of the settings page for the Mixpanel destination.](images/pers-12-settings-people.png)
diff --git a/src/connections/destinations/catalog/moesif-api-analytics/index.md b/src/connections/destinations/catalog/moesif-api-analytics/index.md
@@ -19,8 +19,8 @@ This destination is maintained by Moesif. For any issues with the destination, [
  your [Moesif account](https://www.moesif.com){:target="_blank"} and navigating to the extensions settings.
 4. Once integrated, Segment data shows up in Moesif in a few seconds.
 
-> tip ""
-> **Tip**: You can use Segment's [Replay feature](/docs/guides/what-is-replay/) to sync historical events sent through Segment into your Moesif app.
+> info "Tip"
+> You can use Segment's [Replay feature](/docs/guides/what-is-replay/) to sync historical events sent through Segment into your Moesif app.
 
 ## Identify
 
diff --git a/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md b/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md
@@ -275,8 +275,8 @@ In order to do this, you must have access to **Engage**. To learn more, [contact
 
 ### Set up Engage with SFMC in Segment
 
-> info ""
-> **Tip**: Segment recommends that you use [SFMC batching](#optional-set-up-sfmc-batching) with Engage to help reduce the number of API calls that you send to SFMC, but this is optional. If you choose to set up batching, do this _before_ you set up the SFMC destination in your Segment workspace.
+> info "Tip"
+> Segment recommends that you use [SFMC batching](#optional-set-up-sfmc-batching) with Engage to help reduce the number of API calls that you send to SFMC, but this is optional. If you choose to set up batching, do this _before_ you set up the SFMC destination in your Segment workspace.
 
 Engage sends audience membership and computed trait values to SFMC using Identify calls. To integrate Engage with SFMC:
 1. [Create a Data Extension to store Identify calls](#create-a-data-extension-in-sfmc-to-store-identify-calls) if you haven't already.
diff --git a/src/connections/integration_error_codes.md b/src/connections/integration_error_codes.md
@@ -1,6 +1,5 @@
 ---
 title: Integration Error Codes
-id: integrationerrors
 ---
 
 | Error Codes                                                                                                                                                                                                   | Reason                                                                                                                                                                                                                                                                                                                                     |
diff --git a/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md b/src/connections/sources/catalog/libraries/mobile/apple/destination-plugins/adobe-swift.md
@@ -25,8 +25,8 @@ Before you start sending data from your Swift application to Adobe Analytics, co
 3. Download these settings as the `ADBMobileConfig.json` file by clicking the **Config JSON** link at the bottom of the same tab. Follow the instructions in Adobe's [Core implementation and lifestyle](https://marketing.adobe.com/resources/help/en_US/mobile/ios/dev_qs.html){:target="_blank”} documentation. 
 4. Follow the instructions below for each mobile environment to add the Adobe Analytics dependency to your project.
 
-> success ""
-> **Tip**: Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
+> info "Tip"
+> Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
 
 
 ## Adding the dependency
diff --git a/src/connections/sources/catalog/libraries/mobile/ios/quickstart.md b/src/connections/sources/catalog/libraries/mobile/ios/quickstart.md
@@ -71,8 +71,8 @@ configuration.recordScreenViews = YES; // Enable this to record screen views aut
 {% endcodeexampletab %}
 {% endcodeexample %}
 
-> success ""
-> **Tip**: You don't need to use initialization config parameters to track lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and screen views automatically, but we highly recommend that you do so you can start off already tracking some important core events. See [the track call info](/docs/connections/sources/catalog/libraries/mobile/ios/quickstart/#track) for more info.
+> info "Tip"
+> You don't need to use initialization config parameters to track lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) and screen views automatically, but we highly recommend that you do so you can start off already tracking some important core events. See [the track call info](/docs/connections/sources/catalog/libraries/mobile/ios/quickstart/#track) for more info.
 
 Import the SDK in the files that you use it by adding the following line:
 
diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/adobe-kotlin-android.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/adobe-kotlin-android.md
@@ -25,8 +25,8 @@ Before you start sending data from your Kotlin application to Adobe Analytics, c
 3. Download these settings as the `ADBMobileConfig.json` file by clicking the **Config JSON** link at the bottom of the same tab. Follow the instructions in Adobe's [Core implementation and lifestyle](https://github.com/Adobe-Marketing-Cloud/mobile-services/blob/master/docs/android/getting-started/dev-qs.md){:target="_blank”} documentation. 
 4. Follow the instructions below for each mobile environment to add the Adobe Analytics dependency to your project.
 
-> success ""
-> **Tip**: Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
+> info "Tip"
+> Mobile implementations use the `ADBMobileConfig.json` file to store the settings that you would otherwise enter in the Adobe Analytics destination settings in the Segment app. You can change these settings from the Manage App Settings tab in your Adobe Mobile Services dashboard, and can download the file from that same tab. This file includes the Report Suite ID, Timestamp Option, Tracking Server Secure URL, Tracking Server URL, and Use Secure URL for Server-side settings.
 
 
 ## Adding the dependency
diff --git a/src/connections/sources/catalog/libraries/server/ruby/index.md b/src/connections/sources/catalog/libraries/server/ruby/index.md
@@ -467,8 +467,8 @@ AppAnalytics = Segment::Analytics.new({
 AppAnalytics.flush
 ```
 
-> success "" 
-> **Tip**: When you call `flush`, the call blocks execution on the thread until it finishes processing all the messages in the queue. If you want to call `flush` during the normal operation of your application, you can spawn a local worker thread and call flush on the worker. This prevents the call from blocking the main thread.
+> info "Tip" 
+> When you call `flush`, the call blocks execution on the thread until it finishes processing all the messages in the queue. If you want to call `flush` during the normal operation of your application, you can spawn a local worker thread and call flush on the worker. This prevents the call from blocking the main thread.
 
 
 ## Turbolinks
diff --git a/src/connections/sources/visual-tagger.md b/src/connections/sources/visual-tagger.md
@@ -63,8 +63,8 @@ As you click each event, you're prompted to select the part of the website that
 
 You are now ready to tag events on your website!
 
-> success ""
-> **Tip**: If you ever need to get back to this screen, you can navigate to the JavaScript website source again, click the **Visual tagger** tab, then click **Add Event**.
+> info "Tip"
+> If you ever need to get back to this screen, you can navigate to the JavaScript website source again, click the **Visual tagger** tab, then click **Add Event**.
 
 
 ## Step 1: Choose the event type and select an element
@@ -112,8 +112,8 @@ When you click on an element on your website, a window appears where you can ent
 
 Once you're satisfied with the event name and properties, click **Add**.
 
-> success ""
-> **Tip**! You can create more than one event before you move on to the next step.
+> info "Tip"
+>! You can create more than one event before you move on to the next step.
 
 ![Edit Event Details](images/vt-docs-5.png)
 
diff --git a/src/connections/spec/best-practices-identify.md b/src/connections/spec/best-practices-identify.md
@@ -33,7 +33,7 @@ Ideally, the `userId` could be a database ID. For example, if you're using Mongo
 
 We do **not** recommend using simple email addresses or usernames as a user ID, as these can change over time. We recommend that you use static IDs instead, so the IDs *never* change. When you use a static ID, you can still recognize the user in your analytics tools, even if the user changes their email address. You can also link your analytics data with your own internal database.
 
-> success "**Tip**"
+> info "Tip"
 > Though we don't recommend using an email address or a username as a user ID, you can still send that identifying information in your Identify call as a [trait](/docs/connections/spec/identify#traits).
 
 ## When to call Identify
diff --git a/src/getting-started/03-planning-full-install.md b/src/getting-started/03-planning-full-install.md
@@ -153,8 +153,8 @@ For an Ecommerce company, however, the main events might be something like:
 - **Product Added**
 - **Order Completed**
 
-> success ""
-> **Tip**: As mentioned [above](#shortcut-check-if-a-business-spec-meets-your-needs), Segment has a set of “reserved” event names specifically for ecommerce, called the [Ecommerce Spec](/docs/connections/spec/ecommerce/v2). Check it out to see which events Segment covers and how they are used in downstream destinations.
+> info "Tip"
+> As mentioned [above](#shortcut-check-if-a-business-spec-meets-your-needs), Segment has a set of “reserved” event names specifically for ecommerce, called the [Ecommerce Spec](/docs/connections/spec/ecommerce/v2). Check it out to see which events Segment covers and how they are used in downstream destinations.
 
 An online community, on the other hand, has an entirely different set of actions that indicate engagement, as listed below. For example, a community might want to track actions like:
 
@@ -209,8 +209,8 @@ Once you have an initial list of the destination tools your organization uses, y
 
 Additionally, you should check [which connection modes each tool supports](/docs/connections/destinations/cmodes-compare/), so you know ahead of time which destinations may need to be bundled.
 
-> success ""
-> **Tip**: If you know you're looking for a tool for a specific purpose, but haven't chosen one yet, you can also check the [Connection Modes by category page](https://segment.com/docs/connections/destinations/category-compare/){:target="_blank"} to see which tools might be compatible with the least implementation changes.
+> info "Tip"
+> If you know you're looking for a tool for a specific purpose, but haven't chosen one yet, you can also check the [Connection Modes by category page](https://segment.com/docs/connections/destinations/category-compare/){:target="_blank"} to see which tools might be compatible with the least implementation changes.
 
 
 
diff --git a/src/guides/intro-user.md b/src/guides/intro-user.md
@@ -40,8 +40,8 @@ To set up a destination:
 6. On the next page, configure your destination by entering the API key, token, and any other information.
    The configuration page shows both required information, and any extra settings.
 
-> success ""
-> **Tip**: Segment usually is able to translate data into a format that the destination expects, however some destinations (such as Adobe Analytics) may require manual mapping steps to configure properly. If you see additional fields for mapping configuration, read the documentation for that destination to learn more.
+> info "Tip"
+> Segment usually is able to translate data into a format that the destination expects, however some destinations (such as Adobe Analytics) may require manual mapping steps to configure properly. If you see additional fields for mapping configuration, read the documentation for that destination to learn more.
 
 <!--
 
diff --git a/src/protocols/starter.md b/src/protocols/starter.md
@@ -100,8 +100,8 @@ If you haven't yet implemented Segment tracking in your app or site, there are t
 - **You can download a JavaScript code snippet for each Event** in the tracking plan by clicking the **more (...)** menu. You can then paste these snippets into your site or app code and replace the example properties in these snippets with variables from your code.
 
 <!--
-> success ""
-> **Tip**! If you are using [Typewriter](https://segment.com/docs/protocols/apis-and-extensions/typewriter/), you can export your tracking plan to a format Typewriter can use.
+> info "Tip"
+>! If you are using [Typewriter](https://segment.com/docs/protocols/apis-and-extensions/typewriter/), you can export your tracking plan to a format Typewriter can use.
 -->
 
 
diff --git a/src/segment-app/iam/membership.md b/src/segment-app/iam/membership.md
diff --git a/src/segment-app/iam/scim.md b/src/segment-app/iam/scim.md
