diff --git a/content/collections/account-management/en/manage-event-volume.md b/content/collections/account-management/en/manage-event-volume.md index b100400a2..fca00a05e 100644 --- a/content/collections/account-management/en/manage-event-volume.md +++ b/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 diff --git a/content/collections/account-management/en/manage-orgs-projects.md b/content/collections/account-management/en/manage-orgs-projects.md index 465144da2..3788a4496 100644 --- a/content/collections/account-management/en/manage-orgs-projects.md +++ b/content/collections/account-management/en/manage-orgs-projects.md @@ -10,7 +10,7 @@ exclude_from_sitemap: false updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae updated_at: 1715292596 --- -Once you've created your [first organization](/docs/get-started/create-org) and your [first project](/docs/get-started/create-project), you will from time to time need to manage and update them. This article explains how to perform common tasks related to organization and project management in Amplitude. +Once you've created your [account](/docs/get-started/create-a-new-account) and your [first project](/docs/get-started/create-project), you will from time to time need to manage and update them. This article explains how to perform common tasks related to organization and project management in Amplitude. {{partial:admonition type='note'}} You may want to take [this course](https://academy.amplitude.com/amplitude-analytics-admin-essentials) on administering Amplitude in our Academy. @@ -22,39 +22,39 @@ This feature is available to users on **all Amplitude plans**. See our [pricing ## Approve and provision new users in your organization -New users joining an existing open organization or who are accepting an invitation to join will receive immediate access. For organizations requiring admin approval, however, new users will be unable to access the organization until approval is granted.  +New users joining an existing open organization or who are accepting an invitation to join receive immediate access. For organizations requiring admin approval, however, new users can't access the organization until they're granted approval.  -Admins will receive email notifications whenever a new user joins. If access requires admin approval, you can approve join requests by opening the email and clicking *Review access request*. Otherwise, you can assign permissions to the new user by clicking on the button in the email (either *Assign Project Permissions* or *Go to Settings*, depending on whether you use project-level permissions). +Admins receive email notifications whenever a new user joins. If access requires admin approval, you can approve join requests by opening the email and clicking *Review access request*. Otherwise, you can assign permissions to the new user by clicking on the button in the email (either *Assign Project Permissions* or *Go to Settings*, depending on whether you use project-level permissions). ## View and edit your project information -Navigate to *Settings* > *Organization* *Settings > Projects* and click the name of the project you’d like to view or edit. This will open the General tab, where you’ll find the following information about your project: - -| **Term** | **Definition** | -| --- | --- | -| Project ID | This is the project’s unique Amplitude-generated ID. | -| API Key | This is the project’s API key, used for calling Amplitude’s APIs. Only admins and managers can view the API key. | -| Secret Key | This is the project's secret key, which is also used for calling Amplitude’s APIs. Only admins and managers can view the secret key. | -| Session Definition | This identifies the value Amplitude is currently using for this project to group events for sessions-based charts. The default setting is *Session ID*, but you can choose to group sessions by an event or user property instead. | -| Query Time Sampling | This enables you to speed up your queries by restricting your analyses to a 10% sample of your users. It is **disabled by default**. | -| Time Zone | This is the time zone displayed on charts for this project. You can edit this value by selecting a new time zone from the drop-down menu; Amplitude will shift the timestamps of this project’s events to match. The default time zone is UTC (Universal Time Coordinated). This setting will affect all Amplitude users and queries, which includes the [Dashboard Rest API](https://developers.amplitude.com/docs/dashboard-rest-api). It will not affect the [HTTP API](https://developers.amplitude.com/docs/http-api-v2) or your raw data, as event ingestion will continue to be in UTC.  | -| Weeks Start On | Specifies the day each week begins.  | -| Quarter Starts In | Specifies the month in which the current quarter begins. | -| Currency Display | [The unit of currency displayed for revenue metrics](https://help.amplitude.com/hc/en-us/articles/15581410157339-Change-the-unit-of-currency-your-project-uses-). | -| User Downloads | This is where you can enable or disable the [download users](https://help.amplitude.com/hc/en-us/articles/236032527#download-users) feature in the Microscope, in the export cohorts feature, and the export breakdown tables. | -| Event Types | Shows your project's current distinct count of event types sent to Amplitude. | -| Event Properties | Shows your project's current distinct count of event properties sent to Amplitude. | -| User Properties | Shows your project's current distinct count of user properties being sent to Amplitude. | -| Events This Month | Shows the number of events your project has sent to Amplitude this month. | -| Events Last Month | Shows the number of events your project sent to Amplitude last month.  | +Navigate to *Settings* > *Organization* *Settings > Projects* and click the name of the project you’d like to view or edit. This opens the General tab, where you’ll find the following information about your project: + +| **Term** | **Definition** | +| ------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Project ID | This is the project’s unique Amplitude-generated ID. | +| API Key | This is the project’s API key, used for calling Amplitude’s APIs. Only admins and managers can view the API key. | +| Secret Key | This is the project's secret key, which is also used for calling Amplitude’s APIs. Only admins and managers can view the secret key. | +| Session Definition | This identifies the value Amplitude is currently using for this project to group events for sessions-based charts. The default setting is *Session ID*, but you can choose to group sessions by an event or user property instead. | +| Query Time Sampling | This enables you to speed up your queries by restricting your analyses to a 10% sample of your users. It's **disabled by default**. | +| Time Zone | This is the time zone displayed on charts for this project. You can edit this value by selecting a new time zone from the drop-down menu; Amplitude shifts the timestamps of this project’s events to match. The default time zone is UTC (Universal Time Coordinated). This setting affects all Amplitude users and queries, which includes the [Dashboard Rest API](https://developers.amplitude.com/docs/dashboard-rest-api). It doesn't affect the [HTTP API](https://developers.amplitude.com/docs/http-api-v2) or your raw data, as event ingestion continues to be in UTC. | +| Weeks Start On | Specifies the day each week begins. | +| Quarter Starts In | Specifies the month in which the current quarter begins. | +| Currency Display | [The unit of currency displayed for revenue metrics](https://help.amplitude.com/hc/en-us/articles/15581410157339-Change-the-unit-of-currency-your-project-uses-). | +| User Downloads | This is where you can enable or disable the [download users](https://help.amplitude.com/hc/en-us/articles/236032527#download-users) feature in the Microscope, in the export cohorts feature, and the export breakdown tables. | +| Event Types | Shows your project's current distinct count of event types sent to Amplitude. | +| Event Properties | Shows your project's current distinct count of event properties sent to Amplitude. | +| User Properties | Shows your project's current distinct count of user properties being sent to Amplitude. | +| Events This Month | Shows the number of events your project has sent to Amplitude this month. | +| Events Last Month | Shows the number of events your project sent to Amplitude last month. | {{partial:admonition type='note'}} -Only admins and managers can edit project settings. All project information except the API key and secret key can be viewed by viewers and members. +Only admins and managers can edit project settings. All project information except the API key and secret key are available to viewers and members. {{/partial:admonition}} -You can add, remove, and edit [annotations](https://help.amplitude.com/hc/en-us/articles/236032527#add-annotation) easily from the *Annotations* tab. +You can add, remove, and edit [annotations](/docs/analytics/microscope#add-annotation) easily from the *Annotations* tab. -With [Insights](https://help.amplitude.com/hc/en-us/articles/115001764612), you can bulk manage your automatic and custom monitors from the *Insights* tab. +With [Insights](/docs/analytics/insights), you can bulk manage your automatic and custom monitors from the *Insights* tab. ## Delete a project @@ -66,28 +66,28 @@ To delete a project, follow these steps: ## Change your name or URL, or delete your organization -If you are a Growth or Enterprise customer, reach out to your CSM to help you change your organization's name or URL, or to help delete your organization.  +If you're a Growth or Enterprise customer, reach out to your CSM to help you change your organization's name or URL, or to help delete your organization.  -If you are unsure who your CSM is or do not have one, follow the steps below to request a change: +If you're unsure who your CSM is or don't have one, follow the steps below to request a change: 1. To request a URL or name change, go to [support.amplitude.com](https://support.amplitude.com/), select *Service Task* as the request type, and then *Org url/name change* as the service task. -You must be an admin of your organization in order to submit this request. If there are no admins with your organization, include that fact in the *Why are you making this change?* section of the form. +You must be an admin of your organization to submit this request. If there are no admins with your organization, include that fact in the *Why are you making this change?* section of the form. -2. To request to delete an org, go to [support.amplitude.com](https://support.amplitude.com/), select *Service Task* as the request type, and then *Org Deletion* as the service task. +1. To request to delete an org, go to [support.amplitude.com](https://support.amplitude.com/), select *Service Task* as the request type, and then *Org Deletion* as the service task. If there are no admins with your organization, include that fact in the *Why are you deleting your Amplitude organization?* section of the form. -3. For each request, you must use the email address that exists on the *Team Members* page. -4. Click *Submit* once you complete the form. You will receive a copy of the submitted request by email. -5. When the request has been processed, you will receive a confirmation email. +1. For each request, you must use the email address that exists on the *Team Members* page. +2. Click *Submit* once you complete the form. Amplitude sends a copy of the submitted request by email. +3. When Support processes the request, they send a confirmation email. {{partial:admonition type='note'}} -The Amplitude Support team responds to these requests the first Monday of each month, or the following Tuesday if Monday is an observed holiday. All requests sent before 9 a.m. Pacific Time on the first Monday of each month will be included in the batch.  +The Amplitude Support team responds to these requests the first Monday of each month, or the following Tuesday if Monday is an observed holiday. The support team includes all requests sent before 9 AM Pacific Time on the first Monday of each month in the batch.  {{/partial:admonition}} ## How to rotate your project's API key or secret key -Amplitude does not support rotating API keys due to the inherent public nature of API keys. Changing this key can affect ingestion and data loss if misused. However, with Admin approval we are able to re-generate your project's secret key on the backend. If you would like to submit a request to change the secret key, submit a support request [here](https://help.amplitude.com/hc/en-us/requests/new) with the following information:  +Amplitude doesn't support rotating API keys due to the inherent public nature of API keys. Changing this key can affect ingestion and data loss if misused. However, with Admin approval Amplitude can re-generate your project's secret key on the backend. If you would like to submit a request to change the secret key, submit a support request [here](https://help.amplitude.com/hc/en-us/requests/new) with the following information:  * The name and ID of the project in question. * Three suggested times within the next three days for Amplitude to make the change. An agent will coordinate the exact time with you. -* Approval from an admin of the project. If you are not an admin, you must copy an admin in the request. \ No newline at end of file +* Approval from an admin of the project. If you're not an admin, you must copy an admin in the request. \ No newline at end of file diff --git a/content/collections/analytics/en/marketing-analytics.md b/content/collections/analytics/en/marketing-analytics.md index 13b7f3ddd..7ed7e8fdd 100644 --- a/content/collections/analytics/en/marketing-analytics.md +++ b/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: diff --git a/content/collections/analytics/en/session-replay.md b/content/collections/analytics/en/session-replay.md index 93ff5d963..5beb9920d 100644 --- a/content/collections/analytics/en/session-replay.md +++ b/content/collections/analytics/en/session-replay.md @@ -76,7 +76,7 @@ Session Replay is available in the following Amplitude chart types, with these r * **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 @@ Some common use cases for Session Replay include: 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 diff --git a/content/collections/analytics/en/user-data-lookup.md b/content/collections/analytics/en/user-data-lookup.md index 786fff51c..9c2906d87 100644 --- a/content/collections/analytics/en/user-data-lookup.md +++ b/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 diff --git a/content/collections/android_sdk/en/android-kotlin-sdk.md b/content/collections/android_sdk/en/android-kotlin-sdk.md index de51bce9e..d1d7b490f 100644 --- a/content/collections/android_sdk/en/android-kotlin-sdk.md +++ b/content/collections/android_sdk/en/android-kotlin-sdk.md @@ -951,7 +951,7 @@ amplitude.getLogger().setLogMode(Logger.LogMode.DEBUG); ### 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: diff --git a/content/collections/billing-use/en/mtu-guide.md b/content/collections/billing-use/en/mtu-guide.md index 435d02410..d66ba0e05 100644 --- a/content/collections/billing-use/en/mtu-guide.md +++ b/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. diff --git a/content/collections/browser_sdk/en/browser-sdk-1.md b/content/collections/browser_sdk/en/browser-sdk-1.md index 4e14f788a..d5d346c94 100644 --- a/content/collections/browser_sdk/en/browser-sdk-1.md +++ b/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 diff --git a/content/collections/browser_sdk/en/javascript-sdk.md b/content/collections/browser_sdk/en/javascript-sdk.md index 08c02fe07..733133cd5 100644 --- a/content/collections/browser_sdk/en/javascript-sdk.md +++ b/content/collections/browser_sdk/en/javascript-sdk.md @@ -467,7 +467,7 @@ Calling `logRevenueV2` generates a revenue event type: - [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 @@ amplitude.getInstance().init(AMPLITUDE_API_KEY, 'USER_ID'); ``` 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: diff --git a/content/collections/charts/en/legacy-charts.md b/content/collections/charts/en/legacy-charts.md index 18cf2415d..5e9305d7d 100644 --- a/content/collections/charts/en/legacy-charts.md +++ b/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 diff --git a/content/collections/data/en/client-side-vs-server-side.md b/content/collections/data/en/client-side-vs-server-side.md index 926fd55ef..c3c4410f7 100644 --- a/content/collections/data/en/client-side-vs-server-side.md +++ b/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 diff --git a/content/collections/data/en/create-tracking-plan.md b/content/collections/data/en/create-tracking-plan.md index 704d195ad..3ba3913c4 100644 --- a/content/collections/data/en/create-tracking-plan.md +++ b/content/collections/data/en/create-tracking-plan.md @@ -29,7 +29,7 @@ You can update your plan in two ways: ### 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: diff --git a/content/collections/data/en/data-backfill.md b/content/collections/data/en/data-backfill.md index 474a05105..e737f4be1 100644 --- a/content/collections/data/en/data-backfill.md +++ b/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 diff --git a/content/collections/destination-catalog/en/amazon-s3-cohort.md b/content/collections/destination-catalog/en/amazon-s3-cohort.md index 16865d4ab..e1c36f1f9 100644 --- a/content/collections/destination-catalog/en/amazon-s3-cohort.md +++ b/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. diff --git a/content/collections/experiment-results/en/experiment-results-dig-deeper.md b/content/collections/experiment-results/en/experiment-results-dig-deeper.md index 5217d4291..96c7d87a7 100644 --- a/content/collections/experiment-results/en/experiment-results-dig-deeper.md +++ b/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 diff --git a/content/collections/experiment/en/remote-evaluation.md b/content/collections/experiment/en/remote-evaluation.md index b24fc12c4..29a939845 100644 --- a/content/collections/experiment/en/remote-evaluation.md +++ b/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 diff --git a/content/collections/experiment_troubleshooting/en/variant-jumping.md b/content/collections/experiment_troubleshooting/en/variant-jumping.md index da12d1977..435b90a8f 100644 --- a/content/collections/experiment_troubleshooting/en/variant-jumping.md +++ b/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. diff --git a/content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md b/content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md index 8b58bc31b..1b3134e01 100644 --- a/content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md +++ b/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 diff --git a/content/collections/faq_and_troubleshooting/en/missing-mobile-attribution-events.md b/content/collections/faq_and_troubleshooting/en/missing-mobile-attribution-events.md index 7b9013a8c..21b257751 100644 --- a/content/collections/faq_and_troubleshooting/en/missing-mobile-attribution-events.md +++ b/content/collections/faq_and_troubleshooting/en/missing-mobile-attribution-events.md @@ -48,7 +48,7 @@ User opt-outs **must be honored**. If you know advertising IDs are tracked prope ### 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 diff --git a/content/collections/faq_and_troubleshooting/en/mutual-exclusion-groups.md b/content/collections/faq_and_troubleshooting/en/mutual-exclusion-groups.md index b4b363d7f..46b9968b6 100644 --- a/content/collections/faq_and_troubleshooting/en/mutual-exclusion-groups.md +++ b/content/collections/faq_and_troubleshooting/en/mutual-exclusion-groups.md @@ -40,7 +40,7 @@ If you're using individual inclusions for cohorts, Amplitude Experiment also app {{partial:collapse name="Why is a user being exposed to more than one experiment with mutual exclusion set up?"}} The same user may be exposed to more than one experiment, even if the experiments are set up for mutual exclusion. This could be due to the way Amplitude orders its operations when assigning users to experiments (see further explanation in the answer to the question above). -Another reason could be due to how [unique users are tracked in Amplitude](/docs/cdp/sources/instrument-track-unique-users). For example, a user could anonymously use more than one device before logging in to Amplitude. Until that user is identified and merged to its existing ID, Amplitude will assume it's a different user that is available for assignment. +Another reason could be due to how [unique users are tracked in Amplitude](/docs/data/sources/instrument-track-unique-users). For example, a user could anonymously use more than one device before logging in to Amplitude. Until that user is identified and merged to its existing ID, Amplitude will assume it's a different user that is available for assignment. Or, the multiple exposures could be a case of [variant jumping](/docs/feature-experiment/troubleshooting/variant-jumping), when a user is exposed to two or more variants for a single flag or experiment. {{/partial:collapse}} \ No newline at end of file diff --git a/content/collections/faq_and_troubleshooting/en/user-counts-from-past-events.md b/content/collections/faq_and_troubleshooting/en/user-counts-from-past-events.md index ea39cfe38..f87494d72 100644 --- a/content/collections/faq_and_troubleshooting/en/user-counts-from-past-events.md +++ b/content/collections/faq_and_troubleshooting/en/user-counts-from-past-events.md @@ -17,6 +17,6 @@ The user count can **increase** when events that occurred in the past are ingest The user count can **decrease** when user records are merged. -Amplitude uses a system of user IDs, device IDs, and Amplitude IDs to [track unique users](/docs/cdp/sources/instrument-track-unique-users). If some of your users don't have user IDs, or if you have a lot of anonymous events, these anonymous events are first assigned to an anonymous profile, and then later merged into a known profile. +Amplitude uses a system of user IDs, device IDs, and Amplitude IDs to [track unique users](/docs/data/sources/instrument-track-unique-users). If some of your users don't have user IDs, or if you have a lot of anonymous events, these anonymous events are first assigned to an anonymous profile, and then later merged into a known profile. Your data will eventually stabilize, as anonymous users come back and merge into existing profiles. The amount of time this takes depends on user behavior (how often they return to your product) as well as your settings (how often you batch events). Users who interact with your product every day will display shorter delays in merging, while those who return less frequently will have longer delays. diff --git a/content/collections/faq_and_troubleshooting/en/user-sessions.md b/content/collections/faq_and_troubleshooting/en/user-sessions.md index 058f3efd9..1defa41b6 100644 --- a/content/collections/faq_and_troubleshooting/en/user-sessions.md +++ b/content/collections/faq_and_troubleshooting/en/user-sessions.md @@ -4,7 +4,7 @@ blueprint: faq_and_troubleshooting title: 'User Sessions' source: 'https://amplitude.zendesk.com/hc/en-us/articles/17645167873691' --- -This article covers frequently asked questions about the [User Sessions](/docs/analytics/charts/user-sessions/user-sessions-track-engagement-frequency) chart and sessions in the event streams. Please also refer to [Track sessions](/docs/cdp/sources/instrument-track-sessions) for how Amplitude defines and calculates sessions. +This article covers frequently asked questions about the [User Sessions](/docs/analytics/charts/user-sessions/user-sessions-track-engagement-frequency) chart and sessions in the event streams. Please also refer to [Track sessions](/docs/data/sources/instrument-track-sessions) for how Amplitude defines and calculates sessions. {{partial:collapse name="Why is my User Sessions chart empty?"}} @@ -17,16 +17,16 @@ There are two likely causes when you see a large number of users in the “0 sec **Potential cause #1: Out-of-session events** -Amplitude considers events sent using the [HTTP API](/docs/cdp/sources/instrument-track-sessions) is calculated based on the formula: +Amplitude considers events sent using the [HTTP API](/docs/data/sources/instrument-track-sessions) is calculated based on the formula: max(client_event_time) - session_id -If you want these events to be considered part of a session, the [session ID](/docs/cdp/sources/instrument-track-sessions) should be a timestamp reflecting the beginning of the session in epoch time. +If you want these events to be considered part of a session, the [session ID](/docs/data/sources/instrument-track-sessions) should be a timestamp reflecting the beginning of the session in epoch time. **Potential cause #2: You're tracking the Start Session event, but no other events** If your project permits sending start or end session events (which you can enable using [Android SDK](https://help.amplitude.com/hc/en-us/articles/115002935588-Android-SDK-Installation#tracking-sessions) or [iOS SDK](https://help.amplitude.com/hc/en-us/articles/115002278527-iOS-SDK-Installation#tracking-sessions)), anytime your app launches in the foreground, it will send a `Start - Session` to Amplitude. If Amplitude receives no other events to log after this, it sets the [session length](/docs/cdp/sources/instrument-track-sessions) to zero. + Session` to Amplitude. If Amplitude receives no other events to log after this, it sets the [session length](/docs/data/sources/instrument-track-sessions) to zero. Amplitude's [Microscope](/docs/analytics/microscope) feature lets you examine a given user’s activity, so you can quickly determine whether either of these potential causes is the issue. {{/partial:collapse}} diff --git a/content/collections/flutter_sdk/en/flutter-sdk.md b/content/collections/flutter_sdk/en/flutter-sdk.md index 344e013bf..e75676636 100644 --- a/content/collections/flutter_sdk/en/flutter-sdk.md +++ b/content/collections/flutter_sdk/en/flutter-sdk.md @@ -457,7 +457,7 @@ These features aren't supported in Flutter web: - `enableCoppaControl` - `disableCoppaControl` -- `trackingSessionEvents`. While Flutter Web doesn’t support the ability to send `Start Session` and `End Session` events automatically, the SDK will automatically track session IDs. You can use this for common session-based analyses like the User Session and Pathfinder charts. See our help docs on tracking sessions in Amplitude to [learn more](/docs/cdp/sources/instrument-track-sessions). +- `trackingSessionEvents`. While Flutter Web doesn’t support the ability to send `Start Session` and `End Session` events automatically, the SDK will automatically track session IDs. You can use this for common session-based analyses like the User Session and Pathfinder charts. See our help docs on tracking sessions in Amplitude to [learn more](/docs/data/sources/instrument-track-sessions). - `useAppSetIdForDeviceId` #### Use diff --git a/content/collections/get-started/en/identify-users.md b/content/collections/get-started/en/identify-users.md index 436f44f3b..c2ae7e2be 100644 --- a/content/collections/get-started/en/identify-users.md +++ b/content/collections/get-started/en/identify-users.md @@ -21,7 +21,7 @@ Once set, you can't change user IDs in Amplitude. If your product doesn't currently assign user IDs, then feel free to skip this section. -Before continuing on to the next step, be sure to see [this article about how Amplitude identifies unique users](/docs/cdp/sources/instrument-track-unique-users) for all the details you need to know. +Before continuing on to the next step, be sure to see [this article about how Amplitude identifies unique users](/docs/data/sources/instrument-track-unique-users) for all the details you need to know. ## Best practices for setting user IDs diff --git a/content/collections/get-started/en/instrumentation-prework.md b/content/collections/get-started/en/instrumentation-prework.md index 823552e7e..68e518a0e 100644 --- a/content/collections/get-started/en/instrumentation-prework.md +++ b/content/collections/get-started/en/instrumentation-prework.md @@ -20,7 +20,7 @@ Start by identifying—as specifically as possible—your business goals. What a ## Understand how Amplitude identifies and tracks users -If you're not properly tracking your users, you can't get what you need from Amplitude. It's as simple as that. Be sure to **read and understand** this article on [how Amplitude identifies and tracks unique users](/docs/cdp/sources/instrument-track-unique-users) before you get started with instrumentation. +If you're not properly tracking your users, you can't get what you need from Amplitude. It's as simple as that. Be sure to **read and understand** this article on [how Amplitude identifies and tracks unique users](/docs/data/sources/instrument-track-unique-users) before you get started with instrumentation. ## Organize events and related properties diff --git a/content/collections/get-started/en/user-property-definitions.md b/content/collections/get-started/en/user-property-definitions.md index c4788c317..ecee2ade3 100644 --- a/content/collections/get-started/en/user-property-definitions.md +++ b/content/collections/get-started/en/user-property-definitions.md @@ -33,7 +33,7 @@ If you send data server-side instead of using an SDK, Amplitude cannot track the | Region | Region (e.g. state, province, county) of the event. This is pulled using GeoIP. "California" | | DMA | Designated Market Area (DMA) of the event. This is pulled using GeoIP. "San Francisco-Oakland-San Jose, CA" | | Language | Language of the device. This is drawn from the user's device settings or browser settings. "English" | -| Paying | Paying is set to null for all users by default. The property value changes to "true" at the time of the user's first revenue event (or first verified revenue event, if [validation](/docs/cdp/sources/instrument-track-revenue#verification) is on). Once a property is set to "true", it will not change. You can manually change this value via Amplitude's [Identify API](/docs/apis/analytics/identify): "true", null/none | +| Paying | Paying is set to null for all users by default. The property value changes to "true" at the time of the user's first revenue event (or first verified revenue event, if [validation](/docs/data/sources/instrument-track-revenue#verification) is on). Once a property is set to "true", it will not change. You can manually change this value via Amplitude's [Identify API](/docs/apis/analytics/identify): "true", null/none | | Platform | Platform of the product. "iOS", "Android", or "Web" | | OS | `OS` = `os_name` + `os_version`. `os_name` is the name of the user's mobile operating system or browser. `os_version` is the version of the users' mobile operating system or browser. "ios 9.1", "Chrome 46" | | Device Family | Family of the device. "Apple iPhone", "Samsung Galaxy Tablet", "Windows" | diff --git a/content/collections/get-started/en/what-is-amplitude.md b/content/collections/get-started/en/what-is-amplitude.md index d18438640..eb15817ce 100644 --- a/content/collections/get-started/en/what-is-amplitude.md +++ b/content/collections/get-started/en/what-is-amplitude.md @@ -40,7 +40,7 @@ Event properties are details about events. For example, when someone presses the A user is the specific individual who completed an interaction with your product. Amplitude analyses depend on accurately tracking **unique users**. This is often trickier than it sounds, because your users can log in and out at will, browse anonymously, or use multiple devices. -Learn more about how to [identify your users](/docs/get-started/understand-user-activity) and [how Amplitude tracks unique users](/docs/cdp/sources/instrument-track-unique-users) by using a combination of device IDs, user IDs, and Amplitude IDs. +Learn more about how to [identify your users](/docs/get-started/understand-user-activity) and [how Amplitude tracks unique users](/docs/data/sources/instrument-track-unique-users) by using a combination of device IDs, user IDs, and Amplitude IDs. #### User properties @@ -50,6 +50,6 @@ User properties are details about users. For example, use them to keep track of A session is the duration a user has your app in the foreground or has your website open. Sessions are useful for understanding the frequency and duration of your users' engagement with your product. Amplitude assigns a session ID to each session, and all events within the same session share the same session ID. To send data, Amplitude SDKs automatically generate and manage session IDs. However, you have to manage session IDs yourself, using HTTP APIs. -You can learn more about [how Amplitude tracks sessions](/docs/cdp/sources/instrument-track-sessions). +You can learn more about [how Amplitude tracks sessions](/docs/data/sources/instrument-track-sessions). If you are new to Amplitude, you should complete [this course](https://academy.amplitude.com/path/getting-started-with-amplitude-analytics-learning-path) to get started and learn more [helpful definitions](/docs/get-started/helpful-definitions). \ No newline at end of file diff --git a/content/collections/ios_sdk/en/ios-sdk.md b/content/collections/ios_sdk/en/ios-sdk.md index 6c40bf9b2..5885bdd50 100644 --- a/content/collections/ios_sdk/en/ios-sdk.md +++ b/content/collections/ios_sdk/en/ios-sdk.md @@ -763,7 +763,7 @@ Calling `logRevenueV2` generates up to 2 different event types in the platform: - `[Amplitude] Revenue`: This event is logged for all revenue events, regardless of whether verification is turned on. - `[Amplitude] Revenue (Verified/Unverified)`: These revenue events contain the actual `$revenue` property. -You can't change the default names given to these client-side revenue events in the raw data, but you can change the [display name](/docs/admin/account-management/account-settings). Learn more about tracking revenue in the [Help Center](/docs/cdp/sources/instrument-track-revenue). +You can't change the default names given to these client-side revenue events in the raw data, but you can change the [display name](/docs/admin/account-management/account-settings). Learn more about tracking revenue in the [Help Center](/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 being sent. @@ -896,7 +896,7 @@ Amplitude.instance().initializeApiKey("API_KEY", userId: "USER_ID") {{/partial:tab}} {{/partial:tabs}} -Don't assign users a user ID that could change, because each unique user ID is a unique user in Amplitude. For more information, see [Track unique users](/docs/cdp/sources/instrument-track-unique-users). +Don't assign users a user ID that could change, because each unique user ID is a unique user in Amplitude. For more information, see [Track unique users](/docs/data/sources/instrument-track-unique-users). ### Debug logging @@ -904,7 +904,7 @@ By default, only critical errors are logged to console. To enable debug logging ### 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. diff --git a/content/collections/ios_sdk/en/ios-swift-sdk.md b/content/collections/ios_sdk/en/ios-swift-sdk.md index 007618f12..1475cb8cf 100644 --- a/content/collections/ios_sdk/en/ios-swift-sdk.md +++ b/content/collections/ios_sdk/en/ios-swift-sdk.md @@ -882,7 +882,7 @@ Amplitude* amplitude = [Amplitude initWithConfiguration:configuration]; {{/partial:tab}} {{/partial:tabs}} -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: diff --git a/content/collections/japanese_translation/jp/create-custom-sql-with-amplitude-query.md b/content/collections/japanese_translation/jp/create-custom-sql-with-amplitude-query.md index be71f382e..40c9e5836 100644 --- a/content/collections/japanese_translation/jp/create-custom-sql-with-amplitude-query.md +++ b/content/collections/japanese_translation/jp/create-custom-sql-with-amplitude-query.md @@ -27,7 +27,7 @@ Amplitude SQLへは、他のチャートタイプと同様に、*[Create New]（ Queryパッケージは、SnowflakeとAmplitude SQL用の簡略化されたテーブルスキーマを使用します。Amplitude SQLは、特定プロジェクトの省略形`$events`を使用して参照できる単一のテーブルスキーマを使用します。他のテーブルにアクセスする場合は、*Show Schema*（スキーマを表示）をチェックすると表示されるフルネームを使用します。 -`$events`テーブルは、[統合されたユーザー](/docs/cdp/sources/instrument-track-unique-users)のマッピングを自動的に処理しますが、統合されたユーザーテーブルのスキーマは、`$events`のスキーマの下でも利用可能になります。これは、1つに統合されたユーザー数を表示したい場合に役立ちます。 +`$events`テーブルは、[統合されたユーザー](/docs/data/sources/instrument-track-unique-users)のマッピングを自動的に処理しますが、統合されたユーザーテーブルのスキーマは、`$events`のスキーマの下でも利用可能になります。これは、1つに統合されたユーザー数を表示したい場合に役立ちます。 ![Screen_Shot_2019-10-30_at_09.59.54.png](/docs/output/img/jp/screen-shot-2019-10-30-at-09-59-54-png.png) @@ -127,7 +127,7 @@ Amplitude SQLは、Amplitudeチャートエクスペリエンスに直接組み * **`$date`：**このショートカットを使用する場合、日付ピッカーによって選択された時間範囲が自動的に適用され、時間とともにクエリが更新されます。イベントのイベント時間を参照し、プロジェクトが設定されたタイムゾーンを適用します。それ以外の場合は、Amplitude SQLはUTCでデータを返します。 * 注：**`$events`**と組み合わせて使用する必要があります。 -* **`$events`：**現在のプロジェクトのテーブルを参照するために使用される省略形。このテーブルを使用する場合、[統合されたユーザー](/docs/cdp/sources/instrument-track-unique-users)は自動的に処理されます。 +* **`$events`：**現在のプロジェクトのテーブルを参照するために使用される省略形。このテーブルを使用する場合、[統合されたユーザー](/docs/data/sources/instrument-track-unique-users)は自動的に処理されます。 * 注：**`$date`**と組み合わせて使用する必要があります。 * **`$amplitude_id`：**ユーザーの元のAmplitude ID。このフィールドを使用して、マージされたユーザーを自動的に処理します。 diff --git a/content/collections/japanese_translation/jp/dig-deeper-into-experimental-data-with-experimental-results.md b/content/collections/japanese_translation/jp/dig-deeper-into-experimental-data-with-experimental-results.md index 914cafbcb..d87952c2d 100644 --- a/content/collections/japanese_translation/jp/dig-deeper-into-experimental-data-with-experimental-results.md +++ b/content/collections/japanese_translation/jp/dig-deeper-into-experimental-data-with-experimental-results.md @@ -22,7 +22,7 @@ source: 'https://help.amplitude.com/hc/ja/articles/360062072631' A/Bテストを作成し、結果を表示するには、次のステップに従ってください： 1. *新規作成>*分析>実験結果を*クリックします*。 -2. プライマリ指標モジュールで、*+ Add Metric*または*+* *Define single-use* metricをクリックして、プライマリ指標の設定を開始します。 3番目のオプションである*インポート*では、[実験設定をJSONとしてインポートできます](/docs/feature-experiment/advanced-techniques/import-export-settings)。 +2. プライマリ指標モジュールで、*+ Add Metric*または*+* *Define single-use* metricをクリックして、プライマリ指標の設定を開始します。 3. シングルユース指標を追加する場合は、ドロップダウンメニューを使用して、**指標を定義***フライアウトパネルで*指標タイプを指定します： * * * * * ユニークコンバージョン diff --git a/content/collections/japanese_translation/jp/pathfinder-find-the-path-a-user-takes-on-the-path-to-conversion.md b/content/collections/japanese_translation/jp/pathfinder-find-the-path-a-user-takes-on-the-path-to-conversion.md index f3e3a98d7..6e605ed04 100644 --- a/content/collections/japanese_translation/jp/pathfinder-find-the-path-a-user-takes-on-the-path-to-conversion.md +++ b/content/collections/japanese_translation/jp/pathfinder-find-the-path-a-user-takes-on-the-path-to-conversion.md @@ -17,7 +17,7 @@ Amplitudeの**パスファインダー**チャートでは、製品内の集計 Amplitudeのユーザーインターフェースの基本について学習するので、[Amplitude](/docs/analytics/charts/build-charts-add-events)でのチャートの構築に関する記事をお読みください。また、Amplitudeの便利な用語集も併せてご参照ください。 -セッションIDとAmplitudeが[セッションをどのようにトラックするかについても読みたいです。カスタムセッション](/docs/cdp/sources/instrument-track-sessions)プロパティの設定に関する指示もあります。 +セッションIDとAmplitudeが[セッションをどのようにトラックするかについても読みたいです。カスタムセッション](/docs/data/sources/instrument-track-sessions)プロパティの設定に関する指示もあります。 パスファインダーのすべてのパスは、個々のセッションでトラックされます。つまり、 HTTP APIなどのパイプラインを通じてAmplitudeにイベントを送っている場合、イベントとあわせて`session_id`を送る必要があります。 session\_idがないと、プロダクトのパスビューは不正確なものになります。 @@ -72,7 +72,7 @@ Amplitudeは、ズームしきい値を下回るノードを単一ノードに パスを開始または終了するイベントを選択すると、Amplitudeは次の条件を満たすすべてのイベントノードパスを（最大15まで）生成します: -1. イベントノードは[[Amplitude]開始セッション](/docs/cdp/sources/instrument-track-sessions)、または、 +1. イベントノードは[[Amplitude]開始セッション](/docs/data/sources/instrument-track-sessions)、または、 2. ノード内のユーザーの割合は、ズームしきい値よりも大きいか、あるいはズームしきい値と同等 サンキーダイアグラム（フローダイアグラム）は、特定のイベントで開始または終了するすべてのパスを表示します。各ステップには、ラベルが付いています。ラベルは、シーケンスでそのステップで発行されたイベントと、シーケンスでそのステージで発行されたイベントの頻度を指示します。 diff --git a/content/collections/japanese_translation/jp/pathfinder-user-chart-know-the-path-your-users-are-taking-in-your-product.md b/content/collections/japanese_translation/jp/pathfinder-user-chart-know-the-path-your-users-are-taking-in-your-product.md index 288f7984e..bd483781a 100644 --- a/content/collections/japanese_translation/jp/pathfinder-user-chart-know-the-path-your-users-are-taking-in-your-product.md +++ b/content/collections/japanese_translation/jp/pathfinder-user-chart-know-the-path-your-users-are-taking-in-your-product.md @@ -47,7 +47,7 @@ Amplitudeの**パスファインダーユーザー**チャートはあなたの ![](/docs/output/img/jp/Screen_Shot_2016-12-02_at_3.01.42_PM.png) -Amplitudeのデフォルトの[`session_id`](/docs/cdp/sources/instrument-track-sessions)を使ってイベントをセッションにグループ化している場合は、1つのセッション内のイベントは`event_time`順に並べられます。  +Amplitudeのデフォルトの[`session_id`](/docs/data/sources/instrument-track-sessions)を使ってイベントをセッションにグループ化している場合は、1つのセッション内のイベントは`event_time`順に並べられます。  ### プロパティ別にイベントを展開する diff --git a/content/collections/japanese_translation/jp/step-2-identify-the-user.md b/content/collections/japanese_translation/jp/step-2-identify-the-user.md index 4bf53d34b..8e081b4ff 100644 --- a/content/collections/japanese_translation/jp/step-2-identify-the-user.md +++ b/content/collections/japanese_translation/jp/step-2-identify-the-user.md @@ -27,7 +27,7 @@ Amplitudeで設定したユーザーIDは**変更できません**。 プロダクトが現時点でユーザIDを割り当てていない場合は、このセクションは飛ばしてください。 -次のステップに進む前に、[Amplitudeが固有ユーザーを特定する方法に関するこちらの記事](/docs/cdp/sources/instrument-track-unique-users)をお読みください。必要なすべての情報がこの記事に記載されています。 +次のステップに進む前に、[Amplitudeが固有ユーザーを特定する方法に関するこちらの記事](/docs/data/sources/instrument-track-unique-users)をお読みください。必要なすべての情報がこの記事に記載されています。 ## ユーザーIDを設定する際のベストプラクティス diff --git a/content/collections/japanese_translation/jp/step-pre-instrumentation-tasks.md b/content/collections/japanese_translation/jp/step-pre-instrumentation-tasks.md index 73ee2adf8..a2d670869 100644 --- a/content/collections/japanese_translation/jp/step-pre-instrumentation-tasks.md +++ b/content/collections/japanese_translation/jp/step-pre-instrumentation-tasks.md @@ -31,7 +31,7 @@ Amplitudeの使用体験のほとんどは、インストルメンテーショ ### Amplitudeでユーザーがどう特定およびトラックされるかを理解する -ユーザーを適切にトラックしていなければ、必要なものをAmplitudeから得ることはできません。それは単純明快です。インストルメンテーションを始める前に、[Amplitudeが固有ユーザーを特定およびトラックする方法](/docs/cdp/sources/instrument-track-unique-users)に関するヘルプセンターの記事を**お読みください**。 +ユーザーを適切にトラックしていなければ、必要なものをAmplitudeから得ることはできません。それは単純明快です。インストルメンテーションを始める前に、[Amplitudeが固有ユーザーを特定およびトラックする方法](/docs/data/sources/instrument-track-unique-users)に関するヘルプセンターの記事を**お読みください**。 ### イベントと関連するプロパティを整理する diff --git a/content/collections/japanese_translation/jp/troubleshooting-mobile-attributes-install-uninstall-events.md b/content/collections/japanese_translation/jp/troubleshooting-mobile-attributes-install-uninstall-events.md index 76beefa65..8e54ac8dd 100644 --- a/content/collections/japanese_translation/jp/troubleshooting-mobile-attributes-install-uninstall-events.md +++ b/content/collections/japanese_translation/jp/troubleshooting-mobile-attributes-install-uninstall-events.md @@ -65,7 +65,7 @@ Amplitudeは、「amplitude\_attribution\_ids」というフィールドの下 計測が広告IDをキャプチャしない問題を解決するには、[広告IDのトラッキング](https://developers.amplitude.com/docs/ios#advertising-id)ドキュメントで説明されているように、広告IDトラッキングが有効になっていることを確認してください。 -JavascriptまたはReact Native SDkを使用している場合、広告IDを自動的に追跡する可能性がない場合は、[HTTP API](/docs/cdp/sources/instrument-track-unique-users)できます）。 +JavascriptまたはReact Native SDkを使用している場合、広告IDを自動的に追跡する可能性がない場合は、[HTTP API](/docs/data/sources/instrument-track-unique-users)できます）。 ### トラブルシューティング：マッピングが72時間以内に作成されなかった diff --git a/content/collections/japanese_translation/jp/understand-the-causes-of-data-discrepancies-between-amplitude-and-third-party-platforms.md b/content/collections/japanese_translation/jp/understand-the-causes-of-data-discrepancies-between-amplitude-and-third-party-platforms.md index 805325343..b264a31c7 100644 --- a/content/collections/japanese_translation/jp/understand-the-causes-of-data-discrepancies-between-amplitude-and-third-party-platforms.md +++ b/content/collections/japanese_translation/jp/understand-the-causes-of-data-discrepancies-between-amplitude-and-third-party-platforms.md @@ -9,7 +9,7 @@ Amplitudeの番号は、他のベンダー（例えば、Google Analytics、Mixp ## 開始する前に -この記事では、Amplitudeがユーザーとセッションをどのようにトラックするかを理解していることを示しています。 理解に自信がない場合は、続行する前に、[ユニークユーザーのトラッキング](/docs/cdp/sources/instrument-track-unique-users)と[Amplitudeのセッションの定義](/docs/cdp/sources/instrument-track-sessions)に関するヘルプセンターの記事をご覧ください。 +この記事では、Amplitudeがユーザーとセッションをどのようにトラックするかを理解していることを示しています。 理解に自信がない場合は、続行する前に、[ユニークユーザーのトラッキング](/docs/data/sources/instrument-track-unique-users)と[Amplitudeのセッションの定義](/docs/data/sources/instrument-track-sessions)に関するヘルプセンターの記事をご覧ください。 ## データ矛盾のチェックリスト diff --git a/content/collections/japanese_translation/jp/user-session-charts-track-the-frequency-and-length-of-engagement.md b/content/collections/japanese_translation/jp/user-session-charts-track-the-frequency-and-length-of-engagement.md index 36ccb1d74..30bd4dc67 100644 --- a/content/collections/japanese_translation/jp/user-session-charts-track-the-frequency-and-length-of-engagement.md +++ b/content/collections/japanese_translation/jp/user-session-charts-track-the-frequency-and-length-of-engagement.md @@ -21,7 +21,7 @@ source: 'https://help.amplitude.com/hc/ja/articles/231275508' ここではAmplitudeのユーザーインターフェースの基本について学習するため、[Amplitudeでのチャートの構築](/docs/analytics/charts/build-charts-add-events)に関する記事をお読みください。また、Amplitudeの便利な用語集も併せてご参照ください。 -セッションIDとAmplitudeがセッションをどのようにトラックするかについても[お読みになりたい場合は、](/docs/cdp/sources/instrument-track-sessions)カスタムセッションプロパティの設定に関する指示もあります。 +セッションIDとAmplitudeがセッションをどのようにトラックするかについても[お読みになりたい場合は、](/docs/data/sources/instrument-track-sessions)カスタムセッションプロパティの設定に関する指示もあります。 ## ユーザーセッションチャートの設定 @@ -79,7 +79,7 @@ Amplitudeはサーバーサイドまたはクライアントサイドでセッ * **クライアントサイド（モバイル）：**AmplitudeのモバイルSDKを使っている場合、デフォルトでは直前のイベントから5分以内に実行されたイベントが現在のセッションにカウントされます。初回のイベントの時刻がセッションの開始時刻となり、最後にトリガーされたイベントがセッションの終了時刻となります。 例えば、初回のイベントは「アプリを開く（Open App）」のイベントかもしれません。さらに、Amplitudeは直前のイベントから5分以内に送られたイベントを現在のセッションにカウントします。 * **クライアントサイド（ウェブ）：**AmplitudeのJavaScript SDKを使っている場合、デフォルトでは直前のイベントから30分以内に実行されたイベントが現在のセッションにカウントされます。初回のイベントの時刻がセッションの開始時刻となり、最後にトリガーされたイベントがセッションの終了時刻となります。 -さらに、[カスタムセッションプロパティ](/docs/cdp/sources/instrument-track-sessions)を設定することで、最初にイベントをインストルメント化することなくセッションを定義できます。 +さらに、[カスタムセッションプロパティ](/docs/data/sources/instrument-track-sessions)を設定することで、最初にイベントをインストルメント化することなくセッションを定義できます。 **注：**イベントとあわせてセッションIDが送られていない場合は、ユーザーセッションチャートにデータのみ表示されます。イベントをセッション外に指定（セッションIDに「-1」の値を割り当て）しない限り、この処理はAmplitudeのSDKによって自動で行われます。ただし、AmplitudeのHTTP APIを使用する場合は、イベントとあわせて`session_id`を明示的に送る必要があります。 diff --git a/content/collections/journeys/en/journeys-understand-visualizations.md b/content/collections/journeys/en/journeys-understand-visualizations.md index bb9f11c03..99e67fb44 100644 --- a/content/collections/journeys/en/journeys-understand-visualizations.md +++ b/content/collections/journeys/en/journeys-understand-visualizations.md @@ -20,7 +20,7 @@ In any of these analyses, you can: You can also hide noisy events, only show specific events, collapse repeated events, and view custom events. Any settings you change while viewing one visualization carry over to the others. -Start and end sessions are also defined the same for all Journeys visualizations, and don't allow cohort generation from dropped off users. This is because the start and end times don't always represent true events. For example, let's say a user logs in and then goes inactive after 30 minutes. By default, Amplitude generates a start session event after the user logs in and an end session event for when the user went inactive. Read more about how Amplitude tracks sessions [here](/docs/cdp/sources/instrument-track-sessions).  +Start and end sessions are also defined the same for all Journeys visualizations, and don't allow cohort generation from dropped off users. This is because the start and end times don't always represent true events. For example, let's say a user logs in and then goes inactive after 30 minutes. By default, Amplitude generates a start session event after the user logs in and an end session event for when the user went inactive. Read more about how Amplitude tracks sessions [here](/docs/data/sources/instrument-track-sessions).  Finally, in any Journeys visualization, you can remove an event, expand an event by property, filter by sequences that include the event and property pair, or create a cohort from an event. Just click the event and select the option you want from the menu that appears. diff --git a/content/collections/legacy-charts/en/legacy-charts-pathfinder-users.md b/content/collections/legacy-charts/en/legacy-charts-pathfinder-users.md index 152d7f25c..cf7d1a36e 100644 --- a/content/collections/legacy-charts/en/legacy-charts-pathfinder-users.md +++ b/content/collections/legacy-charts/en/legacy-charts-pathfinder-users.md @@ -2,6 +2,7 @@ title: "The Pathfinder Users chart: see the paths your users take through your product" source: "https://help.amplitude.com/hc/en-us/articles/235777567-The-Pathfinder-Users-chart-see-the-paths-your-users-take-through-your-product" id: 8a84c13d-eec2-4ad3-a0f8-2d5242390af9 +published: false --- {{partial:admonition type='note'}} @@ -55,7 +56,7 @@ In the chart shown below, the starting event is '[Amplitude] Start Session'. The ![](/docs/output/img/legacy-charts/Screen_Shot_2016-12-02_at_3.01.42_PM.png) -If you're using Amplitude's default [`session_id`](/docs/cdp/sources/instrument-track-sessions) to group events into sessions, events in a given session will be ordered by `event_time` instead.  +If you're using Amplitude's default [`session_id`](/docs/data/sources/instrument-track-sessions) to group events into sessions, events in a given session will be ordered by `event_time` instead.  ### Expand events by property diff --git a/content/collections/legacy-charts/en/legacy-charts-pathfinder.md b/content/collections/legacy-charts/en/legacy-charts-pathfinder.md index 19951c539..ee66c35b6 100644 --- a/content/collections/legacy-charts/en/legacy-charts-pathfinder.md +++ b/content/collections/legacy-charts/en/legacy-charts-pathfinder.md @@ -18,7 +18,7 @@ We recommend using Pathfinder to see the top common paths users can take to conv Be sure to read our article on [building charts in Amplitude](/docs/get-started/helpful-definitions). -You'll also want to read up on [session IDs and how Amplitude tracks sessions,](/docs/cdp/sources/instrument-track-sessions). +You'll also want to read up on [session IDs and how Amplitude tracks sessions,](/docs/data/sources/instrument-track-sessions). You should also keep in mind that all paths in Pathfinder are tracked in individual sessions. This means that if you're sending Amplitude events via the [HTTP API](/docs/apis/analytics/http-v2) or through another pipeline, you must send a `session_id` with the event. If you don't, your product's path views won't be accurate. @@ -64,7 +64,7 @@ Your Pathfinder chart will consist of two separate visualizations: the flowing s Once you've selected an event to begin or end your paths with, Amplitude will generate all event node paths (up to 15) that meet the following conditions: -1. Either the event node is an [[Amplitude] Start Session](/docs/cdp/sources/instrument-track-sessions), or +1. Either the event node is an [[Amplitude] Start Session](/docs/data/sources/instrument-track-sessions), or 2. The percentage of users in the node is greater than or equal to the zoom threshold The sankey diagram (the flow diagram) shows all the paths starting or ending with a specific event. Each step is labeled. The label tells you the event fired at that step in the sequence, as well as the frequency the event was fired at that stage in the sequence. diff --git a/content/collections/migration/en/migrate-from-adobe.md b/content/collections/migration/en/migrate-from-adobe.md index dab99c89d..8af069791 100644 --- a/content/collections/migration/en/migrate-from-adobe.md +++ b/content/collections/migration/en/migrate-from-adobe.md @@ -164,9 +164,9 @@ When you map variables from Adobe Analytics to Amplitude, you must align the ter | Numeric Success Event | Event Property | Currency and Numeric Success Events often map to special numeric and currency Event Properties in Amplitude. When you send Revenue/Purchase events to Amplitude, track specific revenue event properties prepended with a $. These event properties relate to the Purchase event. For more information, see [Track Revenue](https://help.amplitude.com/hc/en-us/articles/115003116888-Track-revenue#h_7a841611-ad4f-459a-98ce-073a4a1fe8e5). | | eVars (Conversion Variables) | Event Properties or User Properties | You can send eVars as either User or Event Properties, depending on the use case. Decide which is more appropriate (for example, based on the context or how often the values change). To decide which is best, decide if the Adobe data variable relates to a user or the events the user is performing. Lastly, user property values can persist to subsequent events like eVars. Event property values don't persist to subsequent events. | | Props (Traffic Variables) | Event Properties | | | -| Visit | [Session](/docs/cdp/sources/instrument-track-sessions) | | | +| Visit | [Session](/docs/data/sources/instrument-track-sessions) | | | | Visitor ID | User ID | | | -| Visitor (Cross-Device Tracking) | Amplitude ID | Amplitude ID is an ID that's used to identify a [particular user](/docs/cdp/sources/instrument-track-unique-users) across multiple User and/or Device IDs | +| Visitor (Cross-Device Tracking) | Amplitude ID | Amplitude ID is an ID that's used to identify a [particular user](/docs/data/sources/instrument-track-unique-users) across multiple User and/or Device IDs | | Conversion Variables | Event Properties, Funnels | | | Segments | Cohorts, Event Segmentation | | | | Instances | Count | | | diff --git a/content/collections/migration/en/migrate-from-mixpanel.md b/content/collections/migration/en/migrate-from-mixpanel.md index 432144f3c..73edf54e4 100644 --- a/content/collections/migration/en/migrate-from-mixpanel.md +++ b/content/collections/migration/en/migrate-from-mixpanel.md @@ -130,7 +130,7 @@ Super properties in Mixpanel are properties that attach to all subsequent events * Mixpanel uses a combination of `distinct_id` (a randomly generated identifier on a specific platform) and `user_id` (explicitly set by the instrumenting teams) to identify a user with the `'mixpanel.identify()'` method. * Amplitude uses a combination of `device_id` (a randomly generated id on a specific platform) and `user_id` (explicitly set by the instrumenting teams) to identify a user with the `'amplitude.identify()'` method. -For more on how Amplitude resolves user identifies, see [Track unique users](/docs/cdp/sources/instrument-track-unique-users) +For more on how Amplitude resolves user identifies, see [Track unique users](/docs/data/sources/instrument-track-unique-users) ### Migrate existing historical data from Mixpanel to Amplitude diff --git a/content/collections/other-charts/en/other-charts-amplitude-sql-schema.md b/content/collections/other-charts/en/other-charts-amplitude-sql-schema.md index 7746b9861..212b181cf 100644 --- a/content/collections/other-charts/en/other-charts-amplitude-sql-schema.md +++ b/content/collections/other-charts/en/other-charts-amplitude-sql-schema.md @@ -16,12 +16,12 @@ landing_blurb: 'Use field shortcuts to query your Snowflake database in Amplitud Because [Amplitude SQL](/docs/analytics/charts/other-charts/other-charts-amplitude-sql) is built directly into the Amplitude chart experience, you can leverage much of the same familiar Amplitude user interface, such as the [datepicker](https://help.amplitude.com/hc/en-us/articles/18133682827419-The-datepicker) chart saving experience. You can do this by using Amplitude SQL's special fields for powerful shortcuts: * **`$date`:** When using this shortcut, the time range chosen by the datepicker is automatically applied and will update the query over time. It refers to the event time on the event and will respect the timezone the project has been set to. Otherwise, Amplitude SQL will return data in UTC. This must be used in conjunction with **`$events`**. -* **`$events`:** The shorthand used to refer to the table in your current project. When using this table, [merged users](/docs/cdp/sources/instrument-track-unique-users) are automatically handled. Note: This must be used in conjunction with **`$date`**. +* **`$events`:** The shorthand used to refer to the table in your current project. When using this table, [merged users](/docs/data/sources/instrument-track-unique-users) are automatically handled. Note: This must be used in conjunction with **`$date`**. * **`$amplitude_id`:** The original Amplitude ID for the user. Use this field to automatically handle merged users. ## Table schema -Amplitude SQL uses a one-table schema. The table, `$events`, handles the [merged user](/docs/cdp/sources/instrument-track-unique-users) mappings automatically. But, the merged users table will also be available to view. This will allow you to quickly see the number of users that have been merged into one. +Amplitude SQL uses a one-table schema. The table, `$events`, handles the [merged user](/docs/data/sources/instrument-track-unique-users) mappings automatically. But, the merged users table will also be available to view. This will allow you to quickly see the number of users that have been merged into one. The following tables show the schema of `$events` and merged users.  @@ -71,7 +71,7 @@ The following tables show the schema of `$events` and merged users.  ### Merged users table -See [this article to learn more about how Amplitude tracks unique users](/docs/cdp/sources/instrument-track-unique-users). +See [this article to learn more about how Amplitude tracks unique users](/docs/data/sources/instrument-track-unique-users). | Column | Data type | Description | | ------------------- | ------------ | ------------------------------------------------------------------------------------------------------------ | diff --git a/content/collections/retention-analysis/en/retention-analysis-calculation.md b/content/collections/retention-analysis/en/retention-analysis-calculation.md index eb58da273..e7ddbf823 100644 --- a/content/collections/retention-analysis/en/retention-analysis-calculation.md +++ b/content/collections/retention-analysis/en/retention-analysis-calculation.md @@ -64,7 +64,7 @@ However, when the analysis is still in progress, the graph can **curve up** and Accordingly, the denominator value in the Microscope for a single day will be the sum of the users who have completed that day’s retention interval. This value is not shown in the breakdown table. -![](/docs/output/img/retention-analysis/i9GRGIY6n-UT9VyUMTrr0fAGUoEDqEwPYAmYaj0G2qMOi4tpTeeyWSB39W051OuDgOxkTAUace1Lureo0GurkEmiA53YwD1OjfcLS8MWagNojgyqhotTHMiOA8qAo2DlaOSBDZaioWWBFxwiwHpyMY4) +![](/docs/output/img/retention-analysis/i9GRGIY6n-UT9VyUMTrr0fAGUoEDqEwPYAmYaj0G2qMOi4tpTeeyWSB39W051OuDgOxkTAUace1Lureo0GurkEmiA53YwD1OjfcLS8MWagNojgyqhotTHMiOA8qAo2DlaOSBDZaioWWBFxwiwHpyMY4.png) ## Return On diff --git a/content/collections/retention-analysis/en/retention-analysis-interpret-usage.md b/content/collections/retention-analysis/en/retention-analysis-interpret-usage.md index fb6d1f31a..dd944c0ae 100644 --- a/content/collections/retention-analysis/en/retention-analysis-interpret-usage.md +++ b/content/collections/retention-analysis/en/retention-analysis-interpret-usage.md @@ -23,7 +23,7 @@ Let's say your product's critical event is `Purchase Song or Video`. You can sel For example, the highlighted data point tells us that 65.4% of your users have a median interval of four days or fewer between each `Purchase Song or Video` event. This inflection point can be interpreted as your usage interval. You can use this usage interval to create a [Return On (Custom)](/docs/analytics/charts/retention-analysis/retention-analysis-interpret) chart or a [Lifecycle](/docs/analytics/charts/lifecycle/lifecycle-track-growth) chart. In this case, it looks like four days is the expected usage interval for active users with the critical event of `Purchase Song or Video`. -![](/docs/output/img/retention-analysis/KiqoU43o_Cws3qYg9f1vK9PBWbnYg2LAREIn_BuYEP7At-hkWclSCblLztzVNe5h3bhd6jNx6pnmbA_Iai8j3fGp-w4aciOz34utjM1-jBlWjsxxK0u5f05c8cFJ4ofmJjQ8bNhmK6_Jfei0-cpoDts) +![](/docs/output/img/retention-analysis/KiqoU43o_Cws3qYg9f1vK9PBWbnYg2LAREIn_BuYEP7At-hkWclSCblLztzVNe5h3bhd6jNx6pnmbA_Iai8j3fGp-w4aciOz34utjM1-jBlWjsxxK0u5f05c8cFJ4ofmJjQ8bNhmK6_Jfei0-cpoDts.png) {{partial:admonition type='note'}} To learn more about how to find your critical event, check out this [blog post](https://blog.amplitude.com/user-retention-app-critical-event). diff --git a/content/collections/retention-analysis/en/retention-analysis-time.md b/content/collections/retention-analysis/en/retention-analysis-time.md index 40551fbfc..989c12c00 100644 --- a/content/collections/retention-analysis/en/retention-analysis-time.md +++ b/content/collections/retention-analysis/en/retention-analysis-time.md @@ -13,7 +13,7 @@ landing_blurb: 'Understand the different ways time can affect your Retention Ana --- In a Retention Analysis chart, there are two ways to define a day: a rolling **24-hour window** or a **strict calendar date**. The method you choose can affect your results. -![](/docs/output/img/retention-analysis/20460042102939) +![](/docs/output/img/retention-analysis/20460042102939.png) Amplitude treats a day as a **rolling 24-hour window** by default, which is different for each user. Each day will be **exactly the same length**, no matter when the user triggered the starting event. For example: diff --git a/content/collections/revenue-ltv/en/revenue-ltv-track-new-user-monetization.md b/content/collections/revenue-ltv/en/revenue-ltv-track-new-user-monetization.md index 686c62d71..a12d555d5 100644 --- a/content/collections/revenue-ltv/en/revenue-ltv-track-new-user-monetization.md +++ b/content/collections/revenue-ltv/en/revenue-ltv-track-new-user-monetization.md @@ -25,7 +25,7 @@ This feature is available to users on **Growth** and **Enterprise plans** only. Events don't appear in any Amplitude charts until instrumentation is complete, so make sure you've got that done. Before you begin, see the article about [building charts in Amplitude](/docs/get-started/helpful-definitions). -See the [tracking revenue](/docs/cdp/sources/instrument-track-revenue) documentation to learn how to track revenue events. For example, if you use [Amplitude's SDKs](/docs/sdks/analytics), call `logRevenueV2()` with the provided revenue interface. If you track in-app purchases (IAPs), use Amplitude's revenue authentication system. +See the [tracking revenue](/docs/data/sources/instrument-track-revenue) documentation to learn how to track revenue events. For example, if you use [Amplitude's SDKs](/docs/sdks/analytics), call `logRevenueV2()` with the provided revenue interface. If you track in-app purchases (IAPs), use Amplitude's revenue authentication system. {{partial:admonition type='note'}} Amplitude doesn't support currency conversion. The revenue value you send Amplitude is what's aggregated and displayed. If you get revenue in different currencies, normalize to a single currency before you send any revenue data to Amplitude. diff --git a/content/collections/sections/en/session-replay.md b/content/collections/sections/en/session-replay.md index 9c58ba84b..03c66279d 100644 --- a/content/collections/sections/en/session-replay.md +++ b/content/collections/sections/en/session-replay.md @@ -71,7 +71,7 @@ Session Replay is available in the following Amplitude chart types, with these r * **Event Segmentation**: Session replay is available for all six measures. * **Funnel Analysis**: Session replay is only available for the conversion measure. For Funnel Analysis charts, the order of events appears in chronological order (oldest to newest). * **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). ### View Session Replay from your homepage @@ -134,7 +134,7 @@ With Session Replay, you can: There are some limitations when using Session Replay: * Session Replay is available for web-based applications only. This includes mobile web. Desktop applications aren't supported. -* Session Replay supports standard session definitions only. [Custom session definitions](/docs/cdp/sources/instrument-track-sessions) aren't supported. +* Session Replay supports standard session definitions only. [Custom session definitions](/docs/data/sources/instrument-track-sessions) aren't supported. * Session Replay can only be used to segment by users, and isn't available for [account-level reporting](/docs/analytics/account-level-reporting). * If you are in a portfolio view, you can see replays for different users under different projects. However, keep in mind that Session Replay doesn't stitch together replays from a single user across multiple projects. If a user begins a session in one project and then continues to a second project, Amplitude Analytics generates separate replays for that user for each project. * Session Replay doesn't capture these unsupported HTML elements: diff --git a/content/collections/session-replay/en/session-replay-plugin.md b/content/collections/session-replay/en/session-replay-plugin.md index a0f74bb14..9362dd9f9 100644 --- a/content/collections/session-replay/en/session-replay-plugin.md +++ b/content/collections/session-replay/en/session-replay-plugin.md @@ -299,7 +299,7 @@ Keep the following limitations in mind as you implement Session Replay: - A known user begins on the marketing site, and logs in to the web application. - Amplitude captures both sessions. - The replay for each session is available for view in the host project. -- Session Replay supports standard session definitions, and doesn't support [custom session definitions](/docs/cdp/sources/instrument-track-sessions). +- Session Replay supports standard session definitions, and doesn't support [custom session definitions](/docs/data/sources/instrument-track-sessions). - Session Replay can't capture the following HTML elements: - Canvas - WebGL diff --git a/content/collections/session-replay/en/session-replay-standalone-sdk.md b/content/collections/session-replay/en/session-replay-standalone-sdk.md index 7b1936503..40db0dfb7 100644 --- a/content/collections/session-replay/en/session-replay-standalone-sdk.md +++ b/content/collections/session-replay/en/session-replay-standalone-sdk.md @@ -284,7 +284,7 @@ Keep the following limitations in mind as you implement Session Replay: - A known user begins on the marketing site, and logs in to the web application. - Amplitude captures both sessions. - The replay for each session is available for view in the host project. -- Session Replay supports standard session definitions, and doesn't support [custom session definitions](/docs/cdp/sources/instrument-track-sessions). +- Session Replay supports standard session definitions, and doesn't support [custom session definitions](/docs/data/sources/instrument-track-sessions). - Session Replay can't capture the following HTML elements: - Canvas - WebGL diff --git a/content/collections/single-sign-on/en/set-up-single-sign-on-sso-for-amplitude-using-another-service.md b/content/collections/single-sign-on/en/set-up-single-sign-on-sso-for-amplitude-using-another-service.md index 0b4b250e1..4ac77e1b3 100644 --- a/content/collections/single-sign-on/en/set-up-single-sign-on-sso-for-amplitude-using-another-service.md +++ b/content/collections/single-sign-on/en/set-up-single-sign-on-sso-for-amplitude-using-another-service.md @@ -13,7 +13,7 @@ You may want to set up single sign-on (SSO) using a custom-built SSO provider, o ## Before you begin -Read the introductory article on [single sign-on in Amplitude](docs/admin/single-sign-on/sso) to get a basic understanding of the basic requirements. +Read the introductory article on [single sign-on in Amplitude](/docs/admin/single-sign-on/sso) to get a basic understanding of the basic requirements. ## Set up SSO for an unlisted ("Other") SSO provider diff --git a/content/collections/source-catalog/en/databricks.md b/content/collections/source-catalog/en/databricks.md index 2ffe2bd76..e0a49a3a1 100644 --- a/content/collections/source-catalog/en/databricks.md +++ b/content/collections/source-catalog/en/databricks.md @@ -152,7 +152,7 @@ To add Databricks as a source in Amplitude, complete the following steps. - [Event](/docs/get-started/what-is-amplitude#events) - [User properties](/docs/get-started/what-is-amplitude#user-properties) - [Group properties](/docs/analytics/account-level-reporting) - - [Profiles](/docs/data/profile-properties) + - [Profiles](/docs/data/profiles) For the `Event` data type, optionally select *Sync User Properties* or *Sync Group Properties* to sync the corresponding properties **within** an event. diff --git a/content/collections/source-catalog/en/segment.md b/content/collections/source-catalog/en/segment.md index 5f5b19227..820ef5352 100644 --- a/content/collections/source-catalog/en/segment.md +++ b/content/collections/source-catalog/en/segment.md @@ -54,7 +54,7 @@ In addition to [Segment's libraries](https://segment.com/docs/sources/), you ca There are advantages and disadvantages to taking the client-side bundled approach. One advantage is that adding Amplitude native SDKs adds session tracking capability and automatic user property tracking: -- Events logged during the same user session are grouped together when viewing that user's stream on Amplitude Dashboard. This also allows for [session length calculations](/docs/cdp/sources/instrument-track-sessions). +- Events logged during the same user session are grouped together when viewing that user's stream on Amplitude Dashboard. This also allows for [session length calculations](/docs/data/sources/instrument-track-sessions). - The SDKs automatically record several user properties such as device type, operating system, and user agent. Here is a list of the [user properties](/docs/get-started/user-property-definitions) tracked automatically by Amplitude's SDKs. - By enabling Track Session Events, you can ensure the SDKs automatically send `Start Session` and `End Session` events to mark the start and end of a user's mobile session. - When Amplitude's SDKs are installed, you can directly interact with them. See the docs for [iOS SDK](/docs/sdks/analytics/ios/ios-swift-sdk) and [Android SDK](/docs/sdks/analytics/android/android-kotlin-sdk) to learn more. diff --git a/content/collections/sources/en/session-length.md b/content/collections/sources/en/session-length.md index fdd7a30e3..8e75bf410 100644 --- a/content/collections/sources/en/session-length.md +++ b/content/collections/sources/en/session-length.md @@ -21,4 +21,4 @@ Event A --> Event B --> Event C --> Event D If Event C and Event D are [hidden, inactive, or deleted](https://help.amplitude.com/hc/en-us/sections/16805649563163-Clean-up-your-data), then the `max(client_event_time)` is taken from Event B instead of Event D.  -Read more about how Amplitude tracks sessions in this [help center article](/docs/cdp/sources/instrument-track-sessions).  +Read more about how Amplitude tracks sessions in this [help center article](/docs/data/sources/instrument-track-sessions).  diff --git a/content/collections/unity_sdk/en/unity-sdk.md b/content/collections/unity_sdk/en/unity-sdk.md index c2c9a8ada..5d97f5399 100644 --- a/content/collections/unity_sdk/en/unity-sdk.md +++ b/content/collections/unity_sdk/en/unity-sdk.md @@ -324,7 +324,7 @@ Calling `logRevenue` generates up to 2 different event types in the platform: - '[Amplitude] Revenue': This event is logged for all revenue events, regardless of whether verification is turned on. - '[Amplitude] Revenue (Verified/Unverified)': These revenue events will contain the actual '$revenue' property. -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 modify the [display name](/docs/admin/account-management/account-settings#events). To learn more about tracking revenue, see the documentation [here](/docs/cdp/sources/instrument-track-revenue). +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 modify the [display name](/docs/admin/account-management/account-settings#events). To learn more about tracking revenue, see the documentation [here](/docs/data/sources/instrument-track-revenue). | Name | Description | | --- | --- | @@ -428,7 +428,7 @@ Amplitude.Instance.init(AMPLITUDE_API_KEY, "USER_ID"); ``` Don't assign users a User ID that could change as each unique User ID is interpreted as a unique user in Amplitude. -See [Track unique users in Amplitude](/docs/cdp/sources/instrument-track-unique-users) for more information. +See [Track unique users in Amplitude](/docs/data/sources/instrument-track-unique-users) for more information. ## Advanced topics diff --git a/content/collections/user-sessions/en/user-sessions-interpret.md b/content/collections/user-sessions/en/user-sessions-interpret.md index 9d49bfc43..13105ffc5 100644 --- a/content/collections/user-sessions/en/user-sessions-interpret.md +++ b/content/collections/user-sessions/en/user-sessions-interpret.md @@ -46,7 +46,7 @@ Amplitude records sessions on either the server side or the client side. Additio * **Client side (mobile):** When using Amplitude's mobile SDKs, events triggered within 5 minutes of each other are, by default, counted towards the current session. The time of the first event marks the start time of a session, and the last event triggered marks the end time of a session. For example, the first event could be marked by an 'Open App' event. In addition, Amplitude will count events sent within five minutes of each other towards the current session. * **Client side (web):** When using Amplitude's JavaScript SDK, events triggered within 30 minutes of each other are, by default, counted towards the current session. The time of the first event marks the start time of a session, and the last event triggered marks the end time of a session. -Additionally, you can define a session without instrumenting your events first, by setting a [custom session property](/docs/cdp/sources/instrument-track-sessions). +Additionally, you can define a session without instrumenting your events first, by setting a [custom session property](/docs/data/sources/instrument-track-sessions). {{partial:admonition type='note'}} The User Sessions chart will only display data if you are sending a session ID with your events. Amplitude's SDKs will handle this for you automatically, unless you flag an event as out-of-session (assigning the session ID a value of '-1'). However, if you're using Amplitude's HTTP API, you'll have to explicitly send a `session_id` with your events. diff --git a/content/collections/user-sessions/en/user-sessions-track-engagement-frequency.md b/content/collections/user-sessions/en/user-sessions-track-engagement-frequency.md index 4b3676c26..2d5b0de09 100644 --- a/content/collections/user-sessions/en/user-sessions-track-engagement-frequency.md +++ b/content/collections/user-sessions/en/user-sessions-track-engagement-frequency.md @@ -25,7 +25,7 @@ This feature is available to users on **all Amplitude plans**. See our [pricing Be sure to read our article on [building charts in Amplitude](/docs/get-started/helpful-definitions). -You'll also want to read up on [session IDs and how Amplitude tracks sessions,](/docs/cdp/sources/instrument-track-sessions). +You'll also want to read up on [session IDs and how Amplitude tracks sessions,](/docs/data/sources/instrument-track-sessions). {{partial:admonition type='note'}} This article describes features that are not yet available to all users. diff --git a/vercel.json b/vercel.json index a89f9803f..5d34dc367 100644 --- a/vercel.json +++ b/vercel.json @@ -1733,7 +1733,7 @@ }, { "destination": "/docs/data/sources/instrument-track-sessions", - "source": "/docs/cdp/sources/instrument-track-sessions", + "source": "/docs/data/sources/instrument-track-sessions", "statusCode": 301 }, { @@ -1763,7 +1763,7 @@ }, { "destination": "/docs/data/sources/instrument-track-revenue", - "source": "/docs/cdp/sources/instrument-track-revenue", + "source": "/docs/data/sources/instrument-track-revenue", "statusCode": 301 }, { @@ -1773,7 +1773,7 @@ }, { "destination": "/docs/data/sources/instrument-track-unique-users", - "source": "/docs/cdp/sources/instrument-track-unique-users", + "source": "/docs/data/sources/instrument-track-unique-users", "statusCode": 301 }, { @@ -2003,7 +2003,7 @@ }, { "destination": "/docs/data/sources/connect-to-source", - "source": "/docs/cdp/sources/connect-to-source", + "source": "/docs/data/sources/connect-to-source", "statusCode": 301 }, { diff --git a/vercel.json.bak b/vercel.json.bak index 58d7f6eac..287dac95f 100644 --- a/vercel.json.bak +++ b/vercel.json.bak @@ -321,7 +321,7 @@ }, { "source": "/docs/hc/en-us/articles/16806069264539", - "destination": "/docs/cdp/sources/connect-to-source", + "destination": "/docs/data/sources/connect-to-source", "statusCode": 301 }, { @@ -676,7 +676,7 @@ }, { "source": "/docs/hc/en-us/articles/115003116888", - "destination": "/docs/cdp/sources/instrument-track-revenue", + "destination": "/docs/data/sources/instrument-track-revenue", "statusCode": 301 }, { @@ -801,7 +801,7 @@ }, { "source": "/docs/hc/en-us/articles/115002323627", - "destination": "/docs/cdp/sources/instrument-track-sessions", + "destination": "/docs/data/sources/instrument-track-sessions", "statusCode": 301 }, { @@ -911,7 +911,7 @@ }, { "source": "/docs/hc/en-us/articles/115003135607", - "destination": "/docs/cdp/sources/instrument-track-unique-users", + "destination": "/docs/data/sources/instrument-track-unique-users", "statusCode": 301 }, { @@ -2836,7 +2836,7 @@ }, { "source": "/docs/hc/en-us/articles/16806069264539-Connect-to-a-source", - "destination": "/docs/cdp/sources/connect-to-source", + "destination": "/docs/data/sources/connect-to-source", "statusCode": 301 }, { @@ -3056,7 +3056,7 @@ }, { "source": "/docs/hc/en-us/articles/115003116888-Track-revenue", - "destination": "/docs/cdp/sources/instrument-track-revenue", + "destination": "/docs/data/sources/instrument-track-revenue", "statusCode": 301 }, { @@ -3126,7 +3126,7 @@ }, { "source": "/docs/hc/en-us/articles/115002323627-Track-sessions", - "destination": "/docs/cdp/sources/instrument-track-sessions", + "destination": "/docs/data/sources/instrument-track-sessions", "statusCode": 301 }, { @@ -3201,12 +3201,12 @@ }, { "source": "/docs/hc/en-us/articles/115003135607-Track-unique-users", - "destination": "/docs/cdp/sources/instrument-track-unique-users", + "destination": "/docs/data/sources/instrument-track-unique-users", "statusCode": 301 }, { "source": "/docs/hc/en-us/articles/115003135607", - "destination": "/docs/cdp/sources/instrument-track-unique-users", + "destination": "/docs/data/sources/instrument-track-unique-users", "statusCode": 301 }, {