From 806b178450594934253baaabaaf0d1f95c1c4cbf Mon Sep 17 00:00:00 2001 From: markzegarelli Date: Fri, 13 Sep 2024 14:47:17 -0700 Subject: [PATCH 1/3] DOC-253 fix 404s --- .../analytics/en/product-analytics.md | 2 +- .../en/event-segmentation-in-line-events.md | 16 +++------- .../experiment/en/cohort-targeting.md | 16 +++++----- .../en/funnel-analysis.md | 10 +++--- .../get-started/en/create-a-new-account.md | 2 +- .../get-started/en/create-project.md | 2 +- .../get-started/en/identify-users.md | 6 ++-- .../en/journeys-understand-visualizations.md | 26 +++++++-------- .../migration/en/migrate-from-segment.md | 30 +++++++++--------- .../en/other-charts-amplitude-sql.md | 2 +- .../source-catalog/en/databricks.md | 2 +- ...uV9aQYptZJ85vQ9rLDYpxgKNCf9ckaFHhwdFU.png} | Bin 12 files changed, 52 insertions(+), 62 deletions(-) rename public/docs/output/img/faq/{QpwKm80Os8pLe1u4k8s8ap7S-yHmN9wey71-xrChVBwH3pzyw4ISEdutcCkbd6FmB__jtY4kyllLD5BmxggVTDriQivEsW8vanXFvtNPKhSfB430v3uV9aQYptZJ85vQ9rLDYpxgKNCf9ckaFHhwdFU => QpwKm80Os8pLe1u4k8s8ap7S-yHmN9wey71-xrChVBwH3pzyw4ISEdutcCkbd6FmB__jtY4kyllLD5BmxggVTDriQivEsW8vanXFvtNPKhSfB430v3uV9aQYptZJ85vQ9rLDYpxgKNCf9ckaFHhwdFU.png} (100%) diff --git a/content/collections/analytics/en/product-analytics.md b/content/collections/analytics/en/product-analytics.md index 0bcc925f4..98f025bd1 100644 --- a/content/collections/analytics/en/product-analytics.md +++ b/content/collections/analytics/en/product-analytics.md @@ -19,7 +19,7 @@ This feature is available on all Amplitude plans. For more information, see the On the Basic Settings page, select the event that represents an active action in your product. By default, Amplitude sets `[Amplitude] Any Active Event` as the event. -Next, select the retention intervals that are most meaningful to you. Set both Daily and Weekly intervals. Use Amplitude's [usage interval analysis](docs/analytics/charts/retention-analysis/retention-analysis-usage-interval) to determine how long users go between triggering your critical event. +Next, select the retention intervals that are most meaningful to you. Set both Daily and Weekly intervals. Use Amplitude's [usage interval analysis](/docs/analytics/charts/retention-analysis/retention-analysis-usage-interval) to determine how long users go between triggering your critical event. Configure breakdown properties for the Product Overview, Onboarding, and Retention views. Select up to three. diff --git a/content/collections/event-segmentation/en/event-segmentation-in-line-events.md b/content/collections/event-segmentation/en/event-segmentation-in-line-events.md index c48abe2e2..45ff0c218 100644 --- a/content/collections/event-segmentation/en/event-segmentation-in-line-events.md +++ b/content/collections/event-segmentation/en/event-segmentation-in-line-events.md @@ -19,26 +19,20 @@ Follow these steps to add a custom event: 1. Click *More Options* in the *Events* side control and select *Combine events inline*. -![](/docs/output/img/event-segmentation/-4kwHCRJq_nvW0E9oN9Y_JbirBp57tTdA5TE09o5UHb3XWt3Vx_rWP6A0e4C87r9LLOIk14GvHYr5554HS8HD1HPjYk0D9-O_qWjTZaswL24ICTPq5ti88C6sOXme80Qcj4Y77J8AyoPQZqsLrCA-uc) - 2. Next, click *Add event inline* to add a custom event. Add any number of custom events. -![](/docs/output/img/event-segmentation/rFM_7I88rsHivl7dYUFlLxirvXBSxjBv0yilzSTzFeznNiL4mVchXd5brDg0Xay_nsnlJx6jjm8arG1yu5g_FQUVjr6clxac2oNyh1Z32iSoncl0PHk3PzcvK8AixQXFA7qRX_iFmjMv8zU9aBrXK28) - -{{partial:admonition type='note'}} - The in-line event that you create will only be relevant to that specific chart and will not be accessible anywhere else unless it is saved as a custom event.  -{{/partial:admonition}} + {{partial:admonition type='note'}} + The in-line event that you create is relevant to that specific chart and isn't be accessible anywhere else unless you save it as a custom event.  + {{/partial:admonition}} 3. If desired, hover on the event and click *Filter* to add event properties. Add as many filter properties as needed for each in-line event. -![](/docs/output/img/event-segmentation/2qGAw9uAmao0tp6ZE4c0Hyo3VXKt6VApaZNJE0LKdXPKLt2i-yeaFyfSM_vn_d0EtYOiVS2SxFmBNLPZy1cAFuTN5WNp_Aj6dQfWT1sMG63QJfh4i44oHfaHYs4KTzOZLN93vEmKMepdCZHkLT23e_w) - 4. Save the in-line events as a [custom event](/docs/analytics/charts/group-events) to use it in other charts. Click **More Options** and choose *Save Custom Event*. -![inline_to_custom.png](/docs/output/img/event-segmentation/inline-to-custom-png.png) + ![inline_to_custom.png](/docs/output/img/event-segmentation/inline-to-custom-png.png) 5. Click *Remove* to remove properties and in-line events, as needed. {{partial:admonition type="note" heading=""}} -Custom events can't contain other custom events. Also, *Show User Journeys*, *Explore Conversion Drivers* and *Show User Paths* aren't available via the Microscope for in-line event steps in funnels. +Custom events can't contain other custom events. Also, *Show User Journeys*, *Explore Conversion Drivers* and *Show User Paths* aren't available on the Microscope for in-line event steps in funnels. {{/partial:admonition}} \ No newline at end of file diff --git a/content/collections/experiment/en/cohort-targeting.md b/content/collections/experiment/en/cohort-targeting.md index 188cd0633..8708cded0 100644 --- a/content/collections/experiment/en/cohort-targeting.md +++ b/content/collections/experiment/en/cohort-targeting.md @@ -8,19 +8,19 @@ updated_by: c0ecd457-5b72-4dc9-b683-18a736413d32 updated_at: 1723477635 --- -A cohort is a static or dynamic set of users defined in Amplitude. For experiment use cases, cohorts are particularly useful for advanced audience targeting. That said, cohorts are not always the best solution for targeting, so understanding how cohort targeting works with [local](./local-evaluation.md) vs [remote](./remote-evaluation.md) evaluation is important. +A cohort is a static or dynamic set of users defined in Amplitude. For experiment use cases, cohorts are particularly useful for advanced audience targeting. That said, cohorts aren't always the best solution for targeting, so understanding how cohort targeting works with [local](/docs/experiment/local-evaluation) vs [remote](/docs/experiment/remote-evaluation) evaluation is important. Experiment cohort targeting currently only supports targeting **user** cohorts. ## Remote evaluation -When you target a cohort in a remote evaluation flag, the cohort is automatically synced to the *Amplitude Experiment* destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in remote evaluation are **not real-time**. For example, if you target a cohort of users who performed a `Sign Up` event, users will be targeted within an hour of performing the event--not immediately after. +When you target a cohort in a remote evaluation flag, the cohort is automatically synced to the *Amplitude Experiment* destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in remote evaluation aren't real-time. For example, if you target a cohort of users who performed a `Sign Up` event, users are targeted within an hour of performing the event--not immediately after. -Cohorts targeted for remote evaluation may have a propagation delay on the initial sync or large change depending on the size of the difference. E.g. syncing a cohort of 10 million users for the first time will take some time to initially sync fully. +Cohorts targeted for remote evaluation may have a propagation delay on the initial sync or large change depending on the size of the difference. For example, syncing a cohort of 10 million users for the first time will take some time to initially sync fully. **Use remote evaluation cohort targeting if...** -- You are targeting users based on user behavior or properties which are not available in Experiment targeting segments. +- You are targeting users based on user behavior or properties which aren't available in Experiment targeting segments. - You are ok with some targeting delay introduced by cohort sync intervals. **Don't use remote evaluation cohort targeting if...** @@ -29,15 +29,15 @@ Cohorts targeted for remote evaluation may have a propagation delay on the initi ## Local evaluation -Local evaluation flags and experiment that are deployed to up-to-date server-side SDKs can also target cohorts. When you target a cohort in a local evaluation flag, the cohort is automatically synced to the *Experiment Local Evaluation* destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in local evaluation are **not real-time**. For example, if you target a cohort of users who performed a `Sign Up` event, users will be targeted within an hour of performing the event--not immediately after. +Local evaluation flags and experiment that are deployed to up-to-date server-side SDKs can also target cohorts. When you target a cohort in a local evaluation flag, the cohort is automatically synced to the *Experiment Local Evaluation* destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in local evaluation aren't real-time. For example, if you target a cohort of users who performed a `Sign Up` event, users will be targeted within an hour of performing the event--not immediately after. {{partial:admonition type="note" heading="Cohorts only support User IDs"}} -Local evaluation cohorts currently only sync **User IDs** to the SDKs. This means that in order to target cohorts in local evaluation flags, you **must** include a User ID in the user object passed to the evaluate function. +Local evaluation cohorts currently only sync **User IDs** to the SDKs. This means that to target cohorts in local evaluation flags, you **must** include a User ID in the user object passed to the evaluate function. {{/partial:admonition}} ### SDK Support -Server-side SDKs can target cohorts if configured to do so. Client-side SDKs do not currently support local evaluation cohort targeting. +Server-side SDKs can target cohorts if configured to do so. Client-side SDKs don't currently support local evaluation cohort targeting. On initialization, configure the cohort sync configuration with the project API and Secret key to enable local evaluation cohort downloading and targeting. @@ -119,7 +119,7 @@ experiment = AmplitudeExperiment.initialize_local('DEPLOYMENT_KEY', ## Troubleshooting -Troubleshooting cohort targeting can challenging due to the asynchronous nature of dynamic cohorts and cohort syncs in general. If you find that users that should be in the targeted cohort are not being targeted... +Troubleshooting cohort targeting can challenging due to the asynchronous nature of dynamic cohorts and cohort syncs in general. If you find that users that should be in the targeted cohort aren't being targeted... - For local evaluation, check that the SDK version supports local evaluation cohort targeting, and that **the cohort sync config has been set on initialization**. - Check that **the cohort has the required sync** (*Amplitude Experiment* for remote evaluation, *Experiment Local Evaluation* for local evaluation). diff --git a/content/collections/faq_and_troubleshooting/en/funnel-analysis.md b/content/collections/faq_and_troubleshooting/en/funnel-analysis.md index d36256065..82174e378 100644 --- a/content/collections/faq_and_troubleshooting/en/funnel-analysis.md +++ b/content/collections/faq_and_troubleshooting/en/funnel-analysis.md @@ -7,7 +7,7 @@ category: charts --- This article covers frequently asked questions about the [Funnel Analysis](/docs/analytics/charts/funnel-analysis) chart. -## Funnel Metrics +## Funnel metrics {{partial:collapse name="Do funnels count by unique users or by event totals?"}} Either one. To switch from unique users to event totals, select *Totals* from the *Counting by* dropdown: @@ -21,13 +21,13 @@ For event totals, the earliest-longest logic no longer applies. Amplitude consid You can use the Holding Property Constant feature to count by unique user-property pairs as well. For example, if you hold `Session ID` constant, you can count a user multiple times if they performed the funnel events in different sessions. {{partial:admonition type='note'}} -In order to hold a property constant, it must exist in all events of the funnel. +To hold a property constant, it must exist in all events of the funnel. {{/partial:admonition}} {{/partial:collapse}} {{partial:collapse name="Do funnel charts count conversion in 24-hour windows or by calendar dates?"}} -The conversion window uses a **24-hour window** when looking at conversion from Step 1 to Step 2. It is not based on strict calendar dates. +The conversion window uses a **24-hour window** when looking at conversion from Step 1 to Step 2. It's not based on strict calendar dates. ![funnels_FAQ_24_hour_window.png](/docs/output/img/faq/funnels-faq-24-hour-window-png.png) {{/partial:collapse}} @@ -63,11 +63,9 @@ See more in [this help center article](/docs/analytics/charts/funnel-analysis/fu {{partial:collapse name="How is the median time to convert calculated?"}} -When the funnel chart looks at the median time to convert in distribution view, it only takes the first conversion per user in the entire date range into account. When you switch to the time to convert over time view, we take the first conversion of each user in each day of the date range (e.g. If users can convert more than once in a day, only the first conversion of that day is considered). +When the funnel chart looks at the median time to convert in distribution view, it only takes the first conversion per user in the entire date range into account. When you switch to the time to convert over time view, we take the first conversion of each user in each day of the date range (for example, if users can convert more than once in a day, only the first conversion of that day is considered). In both cases, we use [an approximate algorithm](https://metamarkets.com/2013/histograms/) to estimate the median time to convert. The median time to convert is only an approximation. - -![](/docs/output/img/faq/dpaf3D_0L1RNCWkqjfbc-I8KU0Wv12nsedi50Y7wlC0uukjqOmY9T4cMVwiSYvhA_qvCozNmAoZgvS2D3CF4n_UkMQMzwvJzpZgo7w5H8TVf_0FBeosPEBfG7grX5tnIJNkVYM8NpYKRbu_JOtDrlHE) {{/partial:collapse}} diff --git a/content/collections/get-started/en/create-a-new-account.md b/content/collections/get-started/en/create-a-new-account.md index 36e28b8df..3f713b479 100644 --- a/content/collections/get-started/en/create-a-new-account.md +++ b/content/collections/get-started/en/create-a-new-account.md @@ -34,7 +34,7 @@ When Amplitude verifies that it can receive events, click *Next* to create your ## Other ways to install -Amplitude supports other [integrations](/docs/data/source-catalog), [SDKs](/docs/sdks/analytics), and [API](docs/apis/analytics/http-v2) to help you start sending data. +Amplitude supports other [integrations](/docs/data/source-catalog), [SDKs](/docs/sdks/analytics), and [API](/docs/apis/analytics/http-v2) to help you start sending data. For these methods, view the associated documentation for help getting started. diff --git a/content/collections/get-started/en/create-project.md b/content/collections/get-started/en/create-project.md index dca84ef86..fc1542820 100644 --- a/content/collections/get-started/en/create-project.md +++ b/content/collections/get-started/en/create-project.md @@ -12,7 +12,7 @@ exclude_from_sitemap: false this_article_will_help_you: - 'Create a project in Amplitude' --- -Once your [organization is set up](/docs/get-started/create-org) and users have joined it, you can begin adding **projects**. Each analysis you create belongs to a specific project. In Amplitude, a project is a way to subdivide your Amplitude organization into distinct territories—for example, you might want to create individual projects for different products, or for different areas or sections of your app. It’s a useful way to keep related analyses grouped together. +Once your organization is set up and users have joined it, you can begin adding **projects**. Each analysis you create belongs to a specific project. In Amplitude, a project is a way to subdivide your Amplitude organization into distinct territories—for example, you might want to create individual projects for different products, or for different areas or sections of your app. It’s a useful way to keep related analyses grouped together. Each project in Amplitude has its own separate API key for sending data. For example, if you have one iOS project and one Android project within your organization, each app sends data to their respective API keys. diff --git a/content/collections/get-started/en/identify-users.md b/content/collections/get-started/en/identify-users.md index d7b1fd10f..436f44f3b 100644 --- a/content/collections/get-started/en/identify-users.md +++ b/content/collections/get-started/en/identify-users.md @@ -15,9 +15,9 @@ Amplitude uses a combination of three different methods to identify your users: In Amplitude, a user ID is a unique identifier applied to individual users. Using them is optional, but recommended: your product should set a user ID once a user has created an account, logged in, or is otherwise identified in your product. -Amplitude can use a user ID to reconcile events across multiple devices under the same user ID. Additionally, Amplitude merges a user's event data on the backend: this connects the correct user ID to any anonymous events the user generated before the assignment of their user ID. For this reason, you can wait to assign user IDs if that makes sense for your product. Conversely, this is also why you should **not** set user IDs for anonymous users. +Amplitude can use a user ID to reconcile events across multiple devices under the same user ID. Additionally, Amplitude merges a user's event data on the backend: this connects the correct user ID to any anonymous events the user generated before the assignment of their user ID. For this reason, you can wait to assign user IDs if that makes sense for your product. Conversely, this is also why you shouldn't set user IDs for anonymous users. -Once set, user IDs in Amplitude **cannot be changed**. +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. @@ -28,4 +28,4 @@ Before continuing on to the next step, be sure to see [this article about how Am * **Don't set the user ID if there isn't one.** For example, if you set the user ID to the string `None` for multiple users, Amplitude doesn't recognize those users as separate users. Instead, it assumes all those users are actually the **same** user, and it groups all events for those users together under that `None` user ID. As stated earlier, you can always set the user ID later. * **Don't assign a user ID that might change.** User IDs are fixed forever: don't, for example, set a user's email address as their user ID—email addresses change. * **User IDs are case-sensitive.** If you set a user ID in a different case, Amplitude tracks two separate profiles for the same user. -* **Assigning user IDs server-side can be tricky.** If you're running into issues assigning user IDs, [contact Amplitude Support](/docs/hc/en-us/requests/new). \ No newline at end of file +* **Assigning user IDs server-side can be tricky.** If you're running into issues assigning user IDs, [contact Amplitude Support](https://support.amplitude.com). \ No newline at end of file diff --git a/content/collections/journeys/en/journeys-understand-visualizations.md b/content/collections/journeys/en/journeys-understand-visualizations.md index 9cff97221..e131d16b6 100644 --- a/content/collections/journeys/en/journeys-understand-visualizations.md +++ b/content/collections/journeys/en/journeys-understand-visualizations.md @@ -8,7 +8,7 @@ landing_blurb: 'Learn the difference between the three different Journey visuali updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0 updated_at: 1717103599 --- -Each Journeys chart consists of the Pathfinder and Journey Map visualizations. Both views will tell you something different about the customer journey your users are experiencing. Navigate between them by selecting the appropriate tab along the top of the chart area. +Each Journeys chart consists of the Pathfinder and Journey Map visualizations. Both views tell you something different about the customer journey your users are experiencing. Navigate between them by selecting the appropriate tab along the top of the chart area. In any of these analyses, you can: @@ -18,9 +18,9 @@ In any of these analyses, you can: * Measure paths within a specific conversion window * Analyze by a single segment -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 will carry over to the others. +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 do not 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 will generate 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/cdp/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. @@ -52,7 +52,7 @@ To filter paths by a property, select *Any Event* and specify the property you'd ## Journey Map -The Journey Map will help you understand how conversions happen in your product, and when you know user friction exists somewhere in the user journey but not what’s actually causing it. +The Journey Map helps you understand how conversions happen in your product, and when you know user friction exists somewhere in the user journey but not what’s actually causing it. Imagine a product manager who wants to better understand the initial activation flow taken by her product’s users. So she opens Journeys and flips to the Journey Map. Here she finds an interesting path she wasn’t expecting, so she clicks on it to dig deeper. The map shows her the average time it takes a user to convert, as well as specific paths taken by individual users. @@ -61,14 +61,14 @@ From here, she might develop a hypothesis about why users are behaving in a way The Journey Map does the hard work of surfacing these patterns for you; all you have to do is follow the insights and keep asking follow-up questions. {{partial:admonition type='note'}} -You cannot create cohorts for event paths that include `Dropped off` or `Did not perform an event`. +You can't create cohorts for event paths that include `Dropped off` or `Did not perform an event`. {{/partial:admonition}} ## Read a path across both charts Both visualizations in any Journeys analysis are all measuring the same paths, just in slightly different ways. Let’s look at an example, starting with the Pathfinder. -Our starting event is `charts: create new chart`. This is 100%, because users had to trigger this event in order to be included in the path. If a user didn’t trigger this event, they are not relevant to this analysis and are not included in the charts. +Our starting event is `charts: create new chart`. This is 100%, because users had to trigger this event to be included in the path. If a user didn’t trigger this event, they're not relevant to this analysis and aren't included in the charts. Of these users, 55.4% of them triggered `event explorer: hide event explorer` next. The vast majority of those users—55.2% of the total number of users included in this path, in fact—then triggered `navigation: new chart`. @@ -76,25 +76,23 @@ Note that each percentage on this chart refers to the percentage of all users in Next, 20.7% of all users triggered `taxonomy: view event detail panel`, followed by 17.5% triggering `open event dropdown`. This 17.5% represents 2,725 users. -We can see the same progressions in the Journey Map. Here we can also see that those 2,725 users took an average of 1 hour and 48 minutes to progress all the way through the path. - -![](/docs/output/img/journeys/oSpPJfbuxyBQuRxC8FLdP_AnO-r0zLvxZ-sd3et_csda79xP-0VWqz_MqUNdQ6jgksbElHtCtXRlPWo-n6cyqd1P5oktPkzVEe9c4fpHfOkDtJ3o31JS7f6awZmcH1muu75inKY3Z2-aUUcYc3eaZkA) +Notice the same progressions in the Journey Map. Here we can also see that those 2,725 users took an average of 1 hour and 48 minutes to progress all the way through the path. ## Differences from the legacy versions of these charts * There is a change to the logic from the legacy Pathfinder chart. Imagine the following set of events, with a one-day conversion window: - 1. Event A, April 1st, 9:00 a.m. - 2. Event A, April 1st, 10:00 a.m. - 3. Event B, April 2nd, 9:30 a.m. + 1. Event A, April 1st, 9:00 AM. + 2. Event A, April 1st, 10:00 AM. + 3. Event B, April 2nd, 9:30 AM. The legacy Pathfinder chart limited its analysis to events that occurred within the conversion window; because the first event in this sequence is outside that conversion window, legacy Pathfinder would have used the second event as the beginning of the path. - Instead, the new Journeys logic begins by looking at the first occurrence of the start event. If it's in the conversion window, it will count as a conversion; if it's not, it counts as a drop-off. + Instead, the new Journeys logic begins by looking at the first occurrence of the start event. If it's in the conversion window, it counts as a conversion; if it's not, it counts as a drop-off. * In the new version, the Pathfinder visualization will match the numbers in the legacy Pathfinder through Step 2. After Step 2 the numbers will differ. In the legacy version, the % shown for an event after Step 2 represents a cumulative sum of all prior events in the step before it; because of the branching experience in the new version, the % shown for any event after Step 2 is specifically related to the event that occurred before it in the same path. -This was done in order to align the Pathfinder and Journeys visual numbers, as well as to provide users with faster exploration capabilities. +This was done to align the Pathfinder and Journeys visual numbers, and provide users with faster exploration capabilities. * The legacy Journeys chart collapsed events by default, without providing the ability to change this. The new Journeys chart enables you to collapse or expand events whenever you need to. * The legacy Journeys chart required both starting and ending events, as it was created directly from a funnel. With the new Journeys chart, you can provide only one or the other. \ No newline at end of file diff --git a/content/collections/migration/en/migrate-from-segment.md b/content/collections/migration/en/migrate-from-segment.md index 8be832e3d..a6361d0e6 100644 --- a/content/collections/migration/en/migrate-from-segment.md +++ b/content/collections/migration/en/migrate-from-segment.md @@ -16,11 +16,11 @@ This document covers the necessary steps to: Review the offerings that are available for Segment and how that stacks up to Amplitude. -| Segment | Amplitude | -| ----------- | ----------- | +| Segment | Amplitude | +| ------------------------------------------------------- | ------------------------------------------------------------------------------------- | | [Connections](https://segment.com/product/connections/) | [Sources](/docs/data/source-catalog) & [Destinations](/docs/data/destination-catalog) | -| [Profiles](https://segment.com/product/profiles/) | [Audiences](/docs/cdp/audiences) | -| [Protocols](https://segment.com/product/protocols/) | [Data Management](/docs/cdp) | +| [Profiles](https://segment.com/product/profiles/) | [Audiences](/docs/cdp/audiences) | +| [Protocols](https://segment.com/product/protocols/) | [Data Management](/docs/data) | {{partial:admonition type="info" heading="Recommended best practice"}} Follow a strict release process and [configure multiple environments](/docs/data/amplitude-data-settings). Validate changes within each environment before deploying. @@ -41,17 +41,17 @@ For detailed instructions, see the documentation for the [source](/docs/data/sou Both Segment and Amplitude SDKs capture first party data by tracking user interactions. Other than some nuances around syntax, they work similarly. Here is high level mapping of concepts between Segment & Amplitude. -| Segment | Amplitude | Notes | -|-----------|-----------|--------------------------------------------| -| write_key | api_key | Unique key to validate source of the data. | -| Workspace | Project | [Projects](/docs/admin/account-management/manage-orgs-projects) allow you to organize your data. | -| User | User | User who is performing action. | -| Identify | Identify | Identify updates properties/attributes of the user.| -| Track | Event | [Event](/docs/apis/analytics/http-v2/) in Amplitude tracks the action user is performing.| -| Screen | Event | Create an Event to track Screen views.| -| Page | Event | Create an Event to track Page views.| -| Group | Group | Group is a collection of users. In Amplitude one user could belong to multiple groups. Each group can have properties/attributes that are then available to query/forward on actions performed by any user in the group.| -| Plugins | Plugins | Plugins let you extend Amplitude by running a sequence of custom code on every event.| +| Segment | Amplitude | Notes | +| --------- | --------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | +| write_key | api_key | Unique key to validate source of the data. | +| Workspace | Project | [Projects](/docs/admin/account-management/manage-orgs-projects) allow you to organize your data. | +| User | User | User who is performing action. | +| Identify | Identify | Identify updates properties/attributes of the user. | +| Track | Event | [Event](/docs/apis/analytics/http-v2/) in Amplitude tracks the action user is performing. | +| Screen | Event | Create an Event to track Screen views. | +| Page | Event | Create an Event to track Page views. | +| Group | Group | Group is a collection of users. In Amplitude one user could belong to multiple groups. Each group can have properties/attributes that are then available to query/forward on actions performed by any user in the group. | +| Plugins | Plugins | Plugins let you extend Amplitude by running a sequence of custom code on every event. | {{partial:tabs tabs="Browser, iOS, Android"}} diff --git a/content/collections/other-charts/en/other-charts-amplitude-sql.md b/content/collections/other-charts/en/other-charts-amplitude-sql.md index 801265e4e..c3e9ab054 100644 --- a/content/collections/other-charts/en/other-charts-amplitude-sql.md +++ b/content/collections/other-charts/en/other-charts-amplitude-sql.md @@ -32,7 +32,7 @@ Find Amplitude SQL through *Create > Chart > View additional chart types.* You c This feature doesn't support queuing data for [Portfolio Views](/docs/admin/account-management/portfolio). {{/partial:admonition}} -You can also connect directly to your Snowflake database through a terminal or 3rd-party application, like SQL Workbench or the [Snowflake connector for Python](https://docs.snowflake.net/manuals/user-guide/python-connector.html). [Contact Amplitude Support](/docs/hc/en-us/requests/new) or your Success Manager for your Snowflake credentials.  +You can also connect directly to your Snowflake database through a terminal or 3rd-party application, like SQL Workbench or the [Snowflake connector for Python](https://docs.snowflake.net/manuals/user-guide/python-connector.html). [Contact Amplitude Support](https://support.amplitude.com) or your Success Manager for your Snowflake credentials.  ## Set up and syntax diff --git a/content/collections/source-catalog/en/databricks.md b/content/collections/source-catalog/en/databricks.md index 21210e5f2..a6f052326 100644 --- a/content/collections/source-catalog/en/databricks.md +++ b/content/collections/source-catalog/en/databricks.md @@ -148,7 +148,7 @@ To add Databricks as a source in Amplitude, complete the following steps. For the **Event** data type, optionally select **Sync User Properties** or **Sync Group Properties** to sync the corresponding properties *within* an event. 2. Configure the SQL command that transforms data in Databricks before Amplitude imports it. - - Amplitude treats each record in the SQL execution output as an event to be import. See the Example body in the [Batch Event Upload API](/docs/apis/analytics/batch-upload) documentation to ensure each record you import complies. + - Amplitude treats each record in the SQL execution output as an event to be import. See the Example body in the [Batch Event Upload API](/docs/apis/analytics/batch-event-upload) documentation to ensure each record you import complies. - Amplitude can transform / import from only the tables you specify in step 1 above. - For example, if you have access to tables `A`, `B` and `C` but only selected `A` in step 1, then you can only import data from `A`. - The table names you reference in the SQL command must match exactly the name of the table you select in step 1. For example, if you select `catalog.schema.table1`, use that exact value in the SQL. diff --git a/public/docs/output/img/faq/QpwKm80Os8pLe1u4k8s8ap7S-yHmN9wey71-xrChVBwH3pzyw4ISEdutcCkbd6FmB__jtY4kyllLD5BmxggVTDriQivEsW8vanXFvtNPKhSfB430v3uV9aQYptZJ85vQ9rLDYpxgKNCf9ckaFHhwdFU b/public/docs/output/img/faq/QpwKm80Os8pLe1u4k8s8ap7S-yHmN9wey71-xrChVBwH3pzyw4ISEdutcCkbd6FmB__jtY4kyllLD5BmxggVTDriQivEsW8vanXFvtNPKhSfB430v3uV9aQYptZJ85vQ9rLDYpxgKNCf9ckaFHhwdFU.png similarity index 100% rename from public/docs/output/img/faq/QpwKm80Os8pLe1u4k8s8ap7S-yHmN9wey71-xrChVBwH3pzyw4ISEdutcCkbd6FmB__jtY4kyllLD5BmxggVTDriQivEsW8vanXFvtNPKhSfB430v3uV9aQYptZJ85vQ9rLDYpxgKNCf9ckaFHhwdFU rename to public/docs/output/img/faq/QpwKm80Os8pLe1u4k8s8ap7S-yHmN9wey71-xrChVBwH3pzyw4ISEdutcCkbd6FmB__jtY4kyllLD5BmxggVTDriQivEsW8vanXFvtNPKhSfB430v3uV9aQYptZJ85vQ9rLDYpxgKNCf9ckaFHhwdFU.png From 875fb741503bacc15008bf48f13a5cbb6a6d0388 Mon Sep 17 00:00:00 2001 From: markzegarelli Date: Fri, 13 Sep 2024 15:04:44 -0700 Subject: [PATCH 2/3] DOC-253 one more --- .../collections/source-catalog/en/google-tag-manager-legacy.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/collections/source-catalog/en/google-tag-manager-legacy.md b/content/collections/source-catalog/en/google-tag-manager-legacy.md index 56d6f35be..571313e55 100644 --- a/content/collections/source-catalog/en/google-tag-manager-legacy.md +++ b/content/collections/source-catalog/en/google-tag-manager-legacy.md @@ -19,7 +19,7 @@ This is a legacy GTM template. Use the [latest template](/docs/data/source-catal ## Migration -The Amplitude Analytics Legacy template, currently utilizing the [Maintenance Amplitude JavaScript SDK](/docs/sdks/analytics/browser/javascript-sdk) for data collection, is only slated for bug fixes until its eventual deprecation. use the [latest GTM template](../google-tag-manager-client/) that uses Amplitude's Marketing Analytics SDK for data collection. This not only ensures better support but also offers access to a host of new features. +The Amplitude Analytics Legacy template, currently utilizing the [Maintenance Amplitude JavaScript SDK](/docs/sdks/analytics/browser/javascript-sdk) for data collection, is only slated for bug fixes until its eventual deprecation. use the [latest GTM template](/docs/data/source-catalog/google-tag-manager) that uses Amplitude's Marketing Analytics SDK for data collection. This not only ensures better support but also offers access to a host of new features. - The latest template isn't backwards compatible with this legacy template due to the non-backwards compatibility of the internal SDK. It does a cookie migration logic to help the transition of legacy cookies information to the latest cookie storage system. - For a comprehensive migration guide, see the [Migration guide](/docs/sdks/analytics/browser/migrate-from-javascript-sdk-to-browser-sdk-1-0). From bd545b898c2cc30aa742ecb59c8a568055919cf4 Mon Sep 17 00:00:00 2001 From: markzegarelli Date: Mon, 16 Sep 2024 10:02:08 -0700 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: SpencerFleury <159941756+SpencerFleury@users.noreply.github.com> --- content/collections/analytics/en/product-analytics.md | 2 +- .../en/event-segmentation-in-line-events.md | 4 ++-- content/collections/experiment/en/cohort-targeting.md | 10 +++++----- .../journeys/en/journeys-understand-visualizations.md | 2 +- 4 files changed, 9 insertions(+), 9 deletions(-) diff --git a/content/collections/analytics/en/product-analytics.md b/content/collections/analytics/en/product-analytics.md index 98f025bd1..46aa396ef 100644 --- a/content/collections/analytics/en/product-analytics.md +++ b/content/collections/analytics/en/product-analytics.md @@ -19,7 +19,7 @@ This feature is available on all Amplitude plans. For more information, see the On the Basic Settings page, select the event that represents an active action in your product. By default, Amplitude sets `[Amplitude] Any Active Event` as the event. -Next, select the retention intervals that are most meaningful to you. Set both Daily and Weekly intervals. Use Amplitude's [usage interval analysis](/docs/analytics/charts/retention-analysis/retention-analysis-usage-interval) to determine how long users go between triggering your critical event. +Next, select the retention intervals that are most meaningful to you. Set both Daily and Weekly intervals. Use Amplitude's [usage interval analysis](/docs/analytics/charts/retention-analysis/retention-analysis-usage-interval) to learn how long users go between triggering your critical event. Configure breakdown properties for the Product Overview, Onboarding, and Retention views. Select up to three. diff --git a/content/collections/event-segmentation/en/event-segmentation-in-line-events.md b/content/collections/event-segmentation/en/event-segmentation-in-line-events.md index 45ff0c218..390db95e9 100644 --- a/content/collections/event-segmentation/en/event-segmentation-in-line-events.md +++ b/content/collections/event-segmentation/en/event-segmentation-in-line-events.md @@ -22,7 +22,7 @@ Follow these steps to add a custom event: 2. Next, click *Add event inline* to add a custom event. Add any number of custom events. {{partial:admonition type='note'}} - The in-line event that you create is relevant to that specific chart and isn't be accessible anywhere else unless you save it as a custom event.  + The in-line event that you create is relevant to that specific chart and isn't accessible anywhere else unless you save it as a custom event.  {{/partial:admonition}} 3. If desired, hover on the event and click *Filter* to add event properties. Add as many filter properties as needed for each in-line event. @@ -34,5 +34,5 @@ Follow these steps to add a custom event: 5. Click *Remove* to remove properties and in-line events, as needed. {{partial:admonition type="note" heading=""}} -Custom events can't contain other custom events. Also, *Show User Journeys*, *Explore Conversion Drivers* and *Show User Paths* aren't available on the Microscope for in-line event steps in funnels. +Custom events can't contain other custom events. Also, *Show User Journeys*, *Explore Conversion Drivers* and *Show User Paths* aren't available from the Microscope for in-line event steps in funnels. {{/partial:admonition}} \ No newline at end of file diff --git a/content/collections/experiment/en/cohort-targeting.md b/content/collections/experiment/en/cohort-targeting.md index 8708cded0..f4d29caa2 100644 --- a/content/collections/experiment/en/cohort-targeting.md +++ b/content/collections/experiment/en/cohort-targeting.md @@ -16,11 +16,11 @@ Experiment cohort targeting currently only supports targeting **user** cohorts. When you target a cohort in a remote evaluation flag, the cohort is automatically synced to the *Amplitude Experiment* destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in remote evaluation aren't real-time. For example, if you target a cohort of users who performed a `Sign Up` event, users are targeted within an hour of performing the event--not immediately after. -Cohorts targeted for remote evaluation may have a propagation delay on the initial sync or large change depending on the size of the difference. For example, syncing a cohort of 10 million users for the first time will take some time to initially sync fully. +Cohorts targeted for remote evaluation may have a propagation delay on the initial sync or large change, depending on the size of the difference. For example, the first sync of 10-million-user cohort is likely to take a lot more time than later syncs. **Use remote evaluation cohort targeting if...** -- You are targeting users based on user behavior or properties which aren't available in Experiment targeting segments. +- You are targeting users based on user behavior or properties that aren't available in Experiment targeting segments. - You are ok with some targeting delay introduced by cohort sync intervals. **Don't use remote evaluation cohort targeting if...** @@ -32,14 +32,14 @@ Cohorts targeted for remote evaluation may have a propagation delay on the initi Local evaluation flags and experiment that are deployed to up-to-date server-side SDKs can also target cohorts. When you target a cohort in a local evaluation flag, the cohort is automatically synced to the *Experiment Local Evaluation* destination. For dynamic cohorts, this sync runs hourly by default. This means that dynamic cohorts targeted in local evaluation aren't real-time. For example, if you target a cohort of users who performed a `Sign Up` event, users will be targeted within an hour of performing the event--not immediately after. {{partial:admonition type="note" heading="Cohorts only support User IDs"}} -Local evaluation cohorts currently only sync **User IDs** to the SDKs. This means that to target cohorts in local evaluation flags, you **must** include a User ID in the user object passed to the evaluate function. +Local evaluation cohorts currently only sync **user IDs** to the SDKs. This means that to target cohorts in local evaluation flags, you **must** include a user ID in the user object passed to the evaluate function. {{/partial:admonition}} ### SDK Support Server-side SDKs can target cohorts if configured to do so. Client-side SDKs don't currently support local evaluation cohort targeting. -On initialization, configure the cohort sync configuration with the project API and Secret key to enable local evaluation +On initialization, configure the cohort sync configuration with the project API and secret key to enable local evaluation cohort downloading and targeting. | SDK | Cohort Targeting | Version | @@ -119,7 +119,7 @@ experiment = AmplitudeExperiment.initialize_local('DEPLOYMENT_KEY', ## Troubleshooting -Troubleshooting cohort targeting can challenging due to the asynchronous nature of dynamic cohorts and cohort syncs in general. If you find that users that should be in the targeted cohort aren't being targeted... +Troubleshooting cohort targeting can challenging due to the asynchronous nature of dynamic cohorts and cohort syncs in general. If you find that your experiment isn't targeting users who should be in the targeted cohort ... - For local evaluation, check that the SDK version supports local evaluation cohort targeting, and that **the cohort sync config has been set on initialization**. - Check that **the cohort has the required sync** (*Amplitude Experiment* for remote evaluation, *Experiment Local Evaluation* for local evaluation). diff --git a/content/collections/journeys/en/journeys-understand-visualizations.md b/content/collections/journeys/en/journeys-understand-visualizations.md index e131d16b6..bb9f11c03 100644 --- a/content/collections/journeys/en/journeys-understand-visualizations.md +++ b/content/collections/journeys/en/journeys-understand-visualizations.md @@ -76,7 +76,7 @@ Note that each percentage on this chart refers to the percentage of all users in Next, 20.7% of all users triggered `taxonomy: view event detail panel`, followed by 17.5% triggering `open event dropdown`. This 17.5% represents 2,725 users. -Notice the same progressions in the Journey Map. Here we can also see that those 2,725 users took an average of 1 hour and 48 minutes to progress all the way through the path. +Notice the same progressions in the Journey Map. Those 2,725 users took an average of 1 hour and 48 minutes to progress all the way through the path. ## Differences from the legacy versions of these charts