fix broken links

content/collections/account-management/en/manage-event-volume.md

@@ -73,7 +73,7 @@ This process does not apply retroactively. Additionally, the following propertie
 
 ### Anonymous users
 
-Although Amplitude prioritizes [identifying and tracking unique users](/docs/cdp/sources/instrument-track-unique-users), ingestion-side sampling can sometimes lead to inaccuracies when it comes to anonymous users. For example, if an anonymous user triggers an event from a new device, that user will be assigned a new Amplitude ID and will be sampled based on that new ID. Even if it's determined at a later time that this user was actually a previous user using a new device, there is **no way** to retroactively link the paired events to the particular user's previous Amplitude ID. Since the **sampling of events is based on the Amplitude ID at the time the event was ingested**, analyses that rely on user behavior on new devices may be inaccurate or skewed.
+Although Amplitude prioritizes [identifying and tracking unique users](/docs/data/sources/instrument-track-unique-users), ingestion-side sampling can sometimes lead to inaccuracies when it comes to anonymous users. For example, if an anonymous user triggers an event from a new device, that user will be assigned a new Amplitude ID and will be sampled based on that new ID. Even if it's determined at a later time that this user was actually a previous user using a new device, there is **no way** to retroactively link the paired events to the particular user's previous Amplitude ID. Since the **sampling of events is based on the Amplitude ID at the time the event was ingested**, analyses that rely on user behavior on new devices may be inaccurate or skewed.
 
 ## Accuracy benchmarks
 

content/collections/analytics/en/marketing-analytics.md

@@ -17,9 +17,9 @@ This article explains how Amplitude defines sessions and related metrics, the fu
 
 Events are at the core of Amplitude Analytics, but tracking users and sessions also help to build the full picture of user engagement and the customer journey:
 
-* **Users**: Distinct individuals who interact with your product. Amplitude identifies users through cookies, device IDs, or other tracking mechanisms. [Read more about how Amplitude tracks unique users in this article](/docs/cdp/sources/instrument-track-unique-users).
+* **Users**: Distinct individuals who interact with your product. Amplitude identifies users through cookies, device IDs, or other tracking mechanisms. [Read more about how Amplitude tracks unique users in this article](/docs/data/sources/instrument-track-unique-users).
 * **Events**: Individual actions or interactions that occur within the product, such as page views, button clicks, form submissions, or purchases. Each event is timestamped and carries relevant attributes that Amplitude calls properties. [See the article on determining events to track for more details](/docs/get-started/select-events).
-* **Sessions**: A series of events that represent a user's visit or engagement with your product. Think of sessions like chapters in a book that group events together chronologically. Sessions typically have a start time (the first event) and an end time (after a period of inactivity). [See the session definition article for more information](/docs/cdp/sources/instrument-track-sessions).
+* **Sessions**: A series of events that represent a user's visit or engagement with your product. Think of sessions like chapters in a book that group events together chronologically. Sessions typically have a start time (the first event) and an end time (after a period of inactivity). [See the session definition article for more information](/docs/data/sources/instrument-track-sessions).
 
 To better understand the differences between users, events, and sessions, look at an example of how they’re tracked.
 
@@ -73,7 +73,7 @@ Amplitude also tracks the following session-based metrics:
 * **Session Entries**: The first non-null property value observed within a session, also known as the entry point for the session.
 * **Session Exits**: The final non-null property value observed within a session, also known as the exit point for the session.
 
-These session-based measures help to better grasp how users first engage with or last engage with your product, as well as how much time they’re spending within it. [See the session definition article for more information](/docs/cdp/sources/instrument-track-sessions).
+These session-based measures help to better grasp how users first engage with or last engage with your product, as well as how much time they’re spending within it. [See the session definition article for more information](/docs/data/sources/instrument-track-sessions).
 
 The next example showcases sessions for User 1 and User 2, but notice the channel for each event, as well as each session’s entry and exit points:
 

content/collections/analytics/en/session-replay.md

@@ -76,7 +76,7 @@
 * **Event Segmentation**: Session replay is available for all six measures.
 * **Funnel Analysis**: Session replay is only available for the conversion measure.
 * **Journeys**: Session replay is available on the Pathfinder and Journey Map visualizations.
-* **User Sessions**: Session replay is available for all six measures. This chart won’t allow session replays for [custom defined sessions](/docs/cdp/sources/instrument-track-sessions).
+* **User Sessions**: Session replay is available for all six measures. This chart won’t allow session replays for [custom defined sessions](/docs/data/sources/instrument-track-sessions).
 
 **NOTE**: For Funnel Analysis charts, the order of events will appear in chronological order (oldest to newest).
 
@@ -118,7 +118,7 @@
 There are some limitations when using Session Replay:
 
 * Session Replay is available for web-based applications only. This includes mobile web.
-* Session Replay supports standard session definitions only. [Custom](/docs/cdp/sources/instrument-track-sessions) session definitions are not supported.
+* Session Replay supports standard session definitions only. [Custom](/docs/data/sources/instrument-track-sessions) session definitions are not supported.
 * You can replay captured sessions for up to three months after they occur.
 * Some HTML elements are not supported and will not be captured as part of the replay:
 	* Canvas

content/collections/analytics/en/user-data-lookup.md

@@ -99,7 +99,7 @@ The *Cohorts* tab enables you to check if the user is in any of your project's c
 
 ### Experiments
 
-The Experiments tab shows any [experiments](/docs/experiment) of which the user is a part.
+The Experiments tab shows any [feature experiments](/docs/feature-experiment) or [web experiments](/docs/web-experiment) of which the user is a part.
 
 ### Flags
 

content/collections/android_sdk/en/android-kotlin-sdk.md

@@ -951,7 +951,7 @@
 
 ### Logged out and anonymous users
 
-Amplitude [merges user data](/docs/cdp/sources/instrument-track-unique-users), so any events associated with a known `userId` or `deviceId` are linked the existing user.
+Amplitude [merges user data](/docs/data/sources/instrument-track-unique-users), so any events associated with a known `userId` or `deviceId` are linked the existing user.
  If a user logs out, Amplitude can merge that user's logged-out events to the user's record. You can change this behavior and log those events to an anonymous user instead.
 
 To log events to an anonymous user:

content/collections/billing-use/en/mtu-guide.md

@@ -25,7 +25,7 @@ MTU-based pricing is available for all Amplitude plans. Customers who use sampli
 
 ## Track your MTUs
 
-The first step in setting up MTU tracking is to understand [how Amplitude tracks unique users](/docs/cdp/sources/instrument-track-unique-users). The best way to ensure accurate counting of MTUs is to support a one-to-one correlation between user IDs and actual users.
+The first step in setting up MTU tracking is to understand [how Amplitude tracks unique users](/docs/data/sources/instrument-track-unique-users). The best way to ensure accurate counting of MTUs is to support a one-to-one correlation between user IDs and actual users.
 
 {{partial:admonition type='note'}}
 If you're using test data and generating fictitious user IDs for testing purposes, **each** of these test users are also included in your MTU count.

content/collections/browser_sdk/en/browser-sdk-1.md

@@ -324,7 +324,7 @@ amplitude.init(API_KEY, OPTIONAL_USER_ID, {
 });
 ```
 
-A session is the period of time a user has your website open. See [How Amplitude defines sessions](/docs/cdp/sources/instrument-track-sessions) for more information. When a new session starts, Amplitude tracks a session start event is and is the first event of the session. The event type for session start is `[Amplitude] Start Session`. When an existing session ends, Amplitude tracks `[Amplitude] End Sessions`, which is the last event of the session.
+A session is the period of time a user has your website open. See [How Amplitude defines sessions](/docs/data/sources/instrument-track-sessions) for more information. When a new session starts, Amplitude tracks a session start event is and is the first event of the session. The event type for session start is `[Amplitude] Start Session`. When an existing session ends, Amplitude tracks `[Amplitude] End Sessions`, which is the last event of the session.
 
 ### Track form interactions
 

content/collections/browser_sdk/en/javascript-sdk.md

@@ -467,7 +467,7 @@
 - [Amplitude] Revenue: This event is logged for all revenue events, regardless of whether verification is enabled.
 
 You can't change the default names given to these client-side revenue events in the raw data but you do have the option to change the [display name](/docs/admin/account-management/account-settings).
- To learn more about tracking revenue, see the documentation [here](/docs/cdp/sources/instrument-track-revenue).
+ To learn more about tracking revenue, see the documentation [here](/docs/data/sources/instrument-track-revenue).
 
 {{partial:admonition type="note" heading=""}}
 Amplitude doesn't support currency conversion. Normalize all revenue data to your currency of choice before sending it to Amplitude.
@@ -540,11 +540,11 @@
 ```
 
 Don't assign users a user ID that could change, because each unique user ID represents a unique user in Amplitude. For more information see
- [Track unique users in Amplitude](/docs/cdp/sources/instrument-track-unique-users) in the Help Center.
+ [Track unique users in Amplitude](/docs/data/sources/instrument-track-unique-users) in the Help Center.
 
 ## Logged out and anonymous users
 
-Amplitude [merges user data](/docs/cdp/sources/instrument-track-unique-users), so any events associated with a known `userId` or `deviceId` are linked the existing user.
+Amplitude [merges user data](/docs/data/sources/instrument-track-unique-users), so any events associated with a known `userId` or `deviceId` are linked the existing user.
  If a user logs out, Amplitude can merge that user's logged-out events to the user's record. You can change this behavior and log those events to an anonymous user instead.
 
 To log events to an anonymous user:

content/collections/charts/en/legacy-charts.md

@@ -1,6 +1,5 @@
 ---
 id: e19e3759-e9a5-4209-b392-ca8728fc9da0
-published: false
 blueprint: chart
 title: 'Legacy Charts'
 landing: true

content/collections/data/en/client-side-vs-server-side.md

@@ -40,7 +40,7 @@ Amplitude's server-side sources include these SDKs and APIs:
 
 ## Third-party sources
 
-Third-party is another kind of source. These sources let you import data from other platforms into Amplitude. These sources all require that you have an account with the third-party sources, and each have different setup requirements. You can see all third-party sources in the [Source catalog](../../sources/).
+Third-party is another kind of source. These sources let you import data from other platforms into Amplitude. These sources all require that you have an account with the third-party sources, and each have different setup requirements. You can see all third-party sources in the [Source catalog](/docs/data/source-catalog).
 
 ## How to choose
 

content/collections/data/en/create-tracking-plan.md

@@ -29,7 +29,7 @@
 
 ### Create a source
 
-[Sources](/docs/cdp/sources/connect-to-source) represent the originating source of the data being sent to Amplitude. (For example, your iOS, Android, Web, and Backend.) When using the [Ampli Developer experience](/docs/sdks/ampli), you’ll need to create a source to generate the correct tracking library.
+[Sources](/docs/data/sources/connect-to-source) represent the originating source of the data being sent to Amplitude. (For example, your iOS, Android, Web, and Backend.) When using the [Ampli Developer experience](/docs/sdks/ampli), you’ll need to create a source to generate the correct tracking library.
 
 To create a source, follow these steps:
 

content/collections/data/en/data-backfill.md

@@ -24,7 +24,7 @@ Typically you don't need to check historical data often, but still want it to be
  As a result, if Amplitude records a user as new on June 1 2021 and you backfill the data for the user from February 1 2021, then Amplitude defines the user is new on February 1 2021.
 - Backfilling can compromise your app data. If there is a mismatch between the current user ID and the backfilled user ID, then Amplitude interprets the two distinct User IDs as two distinct users. 
 As a result, users are double counted. Because Amplitude can't delete data after it's recorded, you may have to create a new project to prevent data issues. 
-- Amplitude uses the Device ID and User ID fields to compute the Amplitude ID. For more information, see [Track unique users](/docs/cdp/sources/instrument-track-unique-users).
+- Amplitude uses the Device ID and User ID fields to compute the Amplitude ID. For more information, see [Track unique users](/docs/data/sources/instrument-track-unique-users).
 - Events in the backfill count toward your monthly event volume.
 
 ## Limits 

content/collections/destination-catalog/en/amazon-s3-cohort.md

@@ -79,4 +79,4 @@ Each CSV file contains a list of users, with data broken into the following colu
 
 - ` amplitudeID`: The internal Amplitude identifier for the user.
 - ` userID`: Your unique database identifier for the user.
-- ` userProperty`: The value for a user property you added in step 3 of the [send a cohort section](/data/destinations/amazon-s3-cohort/#send-a-cohort); there is one column for each user property. In portfolio projects, there is a separate column for each source app.
+- ` userProperty`: The value for a user property you added in step 3 of the [send a cohort section](#send-a-cohort); there is one column for each user property. In portfolio projects, there is a separate column for each source app.

content/collections/experiment-results/en/experiment-results-dig-deeper.md

@@ -26,7 +26,7 @@ There is also an [Experiment Results FAQ article](/docs/faq/experiment-analysis)
 To create an A/B test and see the results, follow these steps:
 
 1. Navigate to *Create* > *Chart* > *More* > *Experiment Results*.
-2. In the Primary Metric module, click *+ Add Metric* or *+* *Define single-use metric* to begin setting up your primary metric. A third option, *Import*, allows you to [import your experiment settings as JSON](/docs/feature-experiment/advanced-techniques/import-export-settings).
+2. In the Primary Metric module, click *+ Add Metric* or *+* *Define single-use metric* to begin setting up your primary metric.
 3. If adding a single-use metric, use the drop-down menu to specify the **metric type** in the *Define Metric* fly out panel:
 
       * Unique conversions

content/collections/experiment/en/remote-evaluation.md

@@ -39,7 +39,7 @@ Remote evaluation resolves the user within Amplitude and appends additional info
 
 Amplitude ID resolution happens before additional [user enrichment](#user-enrichment), and is required if [bucketing](/docs/feature-experiment/implementation#consistent-bucketing) by Amplitude ID.
 
-[Learn more about Amplitude's advanced identity resolution.](/docs/cdp/sources/instrument-track-unique-users)
+[Learn more about Amplitude's advanced identity resolution.](/docs/data/sources/instrument-track-unique-users)
 
 ### User enrichment
 

content/collections/experiment_troubleshooting/en/variant-jumping.md

@@ -57,7 +57,7 @@ Enabling sticky bucketing before making targeting changes prevents variant jumpi
 
 The way Amplitude handles anonymous users can sometimes lead to variant jumping. Specifically, Amplitude merges anonymous IDs with the correct existing user IDs (if one exists) as soon as it has enough information to do so. This may happen if a user uses your app on different devices without logging in, or if the device ID regenerates upon logout.
 
-[Learn more about Amplitude's identity resolution and merging users.](/docs/cdp/sources/instrument-track-unique-users)
+[Learn more about Amplitude's identity resolution and merging users.](/docs/data/sources/instrument-track-unique-users)
 
 To identify this type of variant jumping, look for the assignment event where the user jumped between variants. Then compare the value of the Amplitude ID for both events. If it's different for both events, it's probably the result of anonymous identity merging.
 
@@ -98,7 +98,7 @@ If you keep a consistent device ID across logins, you can easily check for this
 
 ### Inconsistent identity input between assignment and exposure
 
-In Amplitude, the user ID and device ID properties are essential to identify your user and [resolve their Amplitude ID](/docs/cdp/sources/instrument-track-unique-users). If the device ID or user ID used to fetch and evaluate assignments is different from the device ID and user ID used to track the exposure event, you may see variant jumping, SRMs, and inconsistent or unexpected bucketing behavior.
+In Amplitude, the user ID and device ID properties are essential to identify your user and [resolve their Amplitude ID](/docs/data/sources/instrument-track-unique-users). If the device ID or user ID used to fetch and evaluate assignments is different from the device ID and user ID used to track the exposure event, you may see variant jumping, SRMs, and inconsistent or unexpected bucketing behavior.
 
 For example, you may be sending events through a proxy or CDP that masks IDs before sending to Amplitude. In this case, the identity used to fetch variants would be different from the identity included in the exposure events.
 

content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md

@@ -14,7 +14,7 @@ Sometimes, Amplitude's numbers may differ from those provided by other vendors.
 
 ## Before you begin
 
-This article assumes that you understand how Amplitude tracks users and sessions. If you don't feel confident in your understanding, check out our articles on [tracking unique users](/docs/cdp/sources/instrument-track-unique-users) and on [the definition of a session in Amplitude](/docs/cdp/sources/instrument-track-sessions) before proceeding.
+This article assumes that you understand how Amplitude tracks users and sessions. If you don't feel confident in your understanding, check out our articles on [tracking unique users](/docs/data/sources/instrument-track-unique-users) and on [the definition of a session in Amplitude](/docs/data/sources/instrument-track-sessions) before proceeding.
 
 ## Data discrepancy checklist
 

content/collections/faq_and_troubleshooting/en/missing-mobile-attribution-events.md

@@ -48,7 +48,7 @@
 
 ### Solution: Tracking advertising IDs
 
-If you are using the Javascript—which lack the ability to track advertising IDs automatically—you will have to send an Amplitude event with the advertising ID via the [HTTP API](/docs/cdp/sources/instrument-track-unique-users).
+If you are using the Javascript—which lack the ability to track advertising IDs automatically—you will have to send an Amplitude event with the advertising ID via the [HTTP API](/docs/data/sources/instrument-track-unique-users).
 
 ## Troubleshoot: Mapping was not made within 72 hours