Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

various updates requested in tickets #152

Merged
merged 1 commit into from
Jul 10, 2024
Merged

various updates requested in tickets #152

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/collections/account-management/en/user-roles-permissions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ this_article_will_help_you:
landing: false
exclude_from_sitemap: false
updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
updated_at: 1715362928
updated_at: 1720214133
---
User permissions define the level of Amplitude access a user in your organization has. Usually, Amplitued bases permissions on a user's role, though [project-level permissions](/docs/admin/account-management/manage-users) and [permission groups](/docs/admin/account-management/manage-permission-groups) are available for Enterprise customers who need the ability to better target levels of security. For more information about permissions in Amplitude Experiment, see [App-level user permissions](/docs/experiment/app-level-permissions).

Expand Down Expand Up @@ -48,7 +48,6 @@ Note that viewers:
Recommended for the majority of Amplitude users in your organization. Members have all viewer-level permissions, plus:

* Create discoverable dashboards, charts, behavioral cohorts, and saved segments
* Mark content as "Official Content"
* Create [custom events](https://help.amplitude.com/hc/en-us/articles/16805886899483-Custom-events)
* Create [team spaces](https://help.amplitude.com/hc/en-us/articles/360016524911)
* Edit [releases](https://help.amplitude.com/hc/en-us/articles/360017800371)
Expand All @@ -68,6 +67,7 @@ Recommended for users who need access to all content created within Amplitude (d
* Remove and edit saved segments
* Create new projects
* Edit project settings
* Mark content as "Official Content"
* Add and edit data sources and data destinations
* Transfer ownership of content they don’t own

Expand Down
32 changes: 18 additions & 14 deletions content/collections/charts/en/group-by.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,30 +1,34 @@
---
title: "Group-bys: How Amplitude prunes and orders chart results"
source: "https://help.amplitude.com/hc/en-us/articles/360031259831-Group-bys-How-Amplitude-prunes-and-orders-chart-results"
id: 3fc06830-001c-4c85-9d1f-6fc7c5ea7a39
blueprint: chart
title: 'Group-bys: How Amplitude prunes and orders chart results'
source: 'https://help.amplitude.com/hc/en-us/articles/360031259831-Group-bys-How-Amplitude-prunes-and-orders-chart-results'
this_article_will_help_you:
- 'Understand when and why Amplitude Analytics truncates group-by query results'
- 'Understand how Amplitude Analytics prioritizes group-by results'
landing: false
exclude_from_sitemap: false
updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
updated_at: 1720212375
---

#### This article will help you:

* Understand when and why Amplitude Analytics truncates group-by query results
* Understand how Amplitude Analytics prioritizes group-by results

In its basic form, Amplitude's **group-by** feature is a tool for categorizing events for aggregation.

![group_by.png](/docs/output/img/charts/group-by-png.png)

When you want to count the number of events by country, for example, you'd use a group-by:
For example, when you want to count the number of events by country, you'd use a group-by:

![group_by_2.png](/docs/output/img/charts/group-by-2-png.png)

Check out our Help Center article for a more detailed look at [group-by visualization in Amplitude's Event Segmentation charts](/docs/analytics/charts/build-charts-add-events).
Check out [this article for a more detailed look at group-by visualization in Amplitude's Event Segmentation charts](/docs/analytics/charts/build-charts-add-events).

## Group-by result limits

For performance purposes, Amplitude sets a maximum limit on the number of groups a query result can return. When this limit is exceeded, the top groups are kept, while the rest are pruned from the query result. The top groups are determined in accordance with the table below.

With a single group-by in the Event Segmentation chart, results may be limited to 100 group-by results. For double group-bys, results may be limited to 500 group by results, in which each group by value pair is counted as a single result.

[See this article for more details about limits in Amplitude](/docs/faq/limits).

## Group ordering

This table shows how Amplitude prioritizes group-bys for display in the Breakdown Table:
Expand All @@ -49,10 +53,10 @@

## Formulas with group ordering

For formulas *without* a group-by, the ordering described above will only be used if every metric in the formula uses the same ordering. Otherwise, Amplitude will use the default formulas ordering.
For formulas *without* a group-by, this ordering is only used if every metric in the formula uses the same ordering. Otherwise, Amplitude uses the default formulas ordering.

For formulas *with* a group-by, Amplitude will rank the groups by the largest overall values *per group* summed across all formulas in a single expression.
For formulas *with* a group-by, Amplitude ranks the groups by the largest overall values *per group* summed across all formulas in a single expression.

Check warning on line 58 in content/collections/charts/en/group-by.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.TooWordy] 'overall' is too wordy. Use a simpler word.

Raw Output:
{"message": "[Amplitude.TooWordy] 'overall' is too wordy. Use a simpler word.", "location": {"path": "content/collections/charts/en/group-by.md", "range": {"start": {"line": 58, "column": 75}}}, "severity": "WARNING"}

{{partial:admonition type='note'}}
If group-by pruning occurs with multiple formula terms combined with operators, formulas may take longer to load because Amplitude will issue additional queries to ensure that all formula terms are querying the same groups.
{{/partial:admonition}}
If group-by pruning occurs with multiple formula terms combined with operators, formulas may take longer to load because Amplitude runs additional queries to make sure that all formula terms are querying the same groups.

Check warning on line 61 in content/collections/charts/en/group-by.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.ComplexWords] Consider using 'more' or 'extra' instead of 'additional'.

Raw Output:
{"message": "[Amplitude.ComplexWords] Consider using 'more' or 'extra' instead of 'additional'.", "location": {"path": "content/collections/charts/en/group-by.md", "range": {"start": {"line": 61, "column": 137}}}, "severity": "WARNING"}
{{/partial:admonition}}
18 changes: 9 additions & 9 deletions ...llections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,22 +5,23 @@
source: 'https://amplitude.zendesk.com/hc/en-us/articles/115002383247'
this_article_will_help_you:
- "Troubleshoot when Amplitude's numbers do not match those provided by other platforms"
updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
updated_at: 1718921805
updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
updated_at: 1720214605
category: other
landing: false
---
Sometimes, Amplitude's numbers may differ from those provided by other vendors (e.g. Google Analytics, Mixpanel, etc). This can happen for a number of different reasons, several of which we will explore in this article.
Sometimes, Amplitude's numbers may differ from those provided by other vendors. This can happen for a number of different reasons.

Check warning on line 13 in content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.Wordiness] Consider using 'many, a few' instead of 'a number of'.

Raw Output:
{"message": "[Amplitude.Wordiness] Consider using 'many, a few' instead of 'a number of'.", "location": {"path": "content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md", "range": {"start": {"line": 13, "column": 101}}}, "severity": "WARNING"}

Check warning on line 13 in content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.TooWordy] 'a number of' is too wordy. Use a simpler word.

Raw Output:
{"message": "[Amplitude.TooWordy] 'a number of' is too wordy. Use a simpler word.", "location": {"path": "content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md", "range": {"start": {"line": 13, "column": 101}}}, "severity": "WARNING"}

## 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 Help Center 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/cdp/sources/instrument-track-unique-users) and on [the definition of a session in Amplitude](/docs/cdp/sources/instrument-track-sessions) before proceeding.

Check warning on line 17 in content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.We] Avoid using first-person plural like 'our'.

Raw Output:
{"message": "[Amplitude.We] Avoid using first-person plural like 'our'.", "location": {"path": "content/collections/faq_and_troubleshooting/en/data-discrepancies-with-other-platforms.md", "range": {"start": {"line": 17, "column": 144}}}, "severity": "WARNING"}

## Data discrepancy checklist

This list of questions acts as a quick troubleshooting checklist for any data discrepancies you may be experiencing. If you can answer "yes" to a question, it's probably not the cause.

{{partial:collapse name="Do the time zones between Amplitude and the other platform align?"}}
If not, be sure to align the time zones before comparing numbers. Data ingested by Amplitude are timestamped in UTC, but you can customize the time zone within our UI.
If not, align the time zones before comparing numbers. Amplitude timestamps the data it ingests in UTC, but you can customize the time zone [within the Amplitude UI](/docs/admin/account-management/manage-orgs-projects#view-and-edit-your-project-information).
{{/partial:collapse}}

{{partial:collapse name="Do the events you currently track in Amplitude reflect what you're tracking in the other platform?"}}
Expand All @@ -32,12 +33,11 @@
{{/partial:collapse}}

{{partial:collapse name="Do the other platform and Amplitude both define the metric of interest the same way?"}}
If not, then it's likely that there will be a discrepancy, since Amplitude and the other platform define the metric differently.
If not, then a discrepancy is more likely.
{{/partial:collapse}}


{{partial:collapse name="Does the other platform merge users like Amplitude does?"}}
If not, then depending on how the other platform merges its users, you may see a discrepancy between your users and sessions numbers, since the user identification differs.
If not, then you may see a discrepancy between your users and sessions numbers, depending on the identifiers the other platform uses to merge its users.
{{/partial:collapse}}

{{partial:collapse name="Is the session timeout window the same between Amplitude and the other platform?"}}
Expand All @@ -50,7 +50,7 @@

## Sessions in Google Analytics

Though Google Analytics and Amplitude track sessions similarly, this table outlines factors that cause a discrepancy in your session numbers.
Though Google Analytics and Amplitude track sessions similarly, certain common events can cause a discrepancy in your session numbers.

| **Scenario** | **Amplitude** | **Google Analytics** | **Source** |
| --- | --- | --- | --- |
Expand Down
13 changes: 7 additions & 6 deletions content/collections/faq_and_troubleshooting/en/limits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,9 +4,10 @@
title: Limits
source: 'https://amplitude.zendesk.com/hc/en-us/articles/115002923888'
this_article_will_help_you:
- 'Ensure you do not experience "missing" data due to exceeding your Amplitude data limits'
updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
updated_at: 1718925693
- 'Understand the limits Amplitude places on the amount of data you can send, and how to avoid exceeding them'
updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
updated_at: 1720211956
landing: false
---
There are some limits to the amount of data that you can send to Amplitude.

Expand Down Expand Up @@ -87,7 +88,7 @@

## CSV download limits

The breakdown data table in the UI will only list the top 100 property values (for when you perform a [group-by](/docs/analytics/charts/group-by)). You can export approximately 10,000 rows as a CSV file. This is specifically a limitation on the number of group-by values you can export.
The breakdown data table in the UI will only list the top 100 property values (for when you perform a [group-by](/docs/analytics/charts/group-by)). You can export approximately 10,000 rows as a .CSV file. This is specifically a limitation on the number of group-by values you can export.

Check warning on line 91 in content/collections/faq_and_troubleshooting/en/limits.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.ComplexWords] Consider using 'about' instead of 'approximately'.

Raw Output:
{"message": "[Amplitude.ComplexWords] Consider using 'about' instead of 'approximately'.", "location": {"path": "content/collections/faq_and_troubleshooting/en/limits.md", "range": {"start": {"line": 91, "column": 164}}}, "severity": "WARNING"}

The group-by limits vary from chart to chart:

Expand All @@ -103,9 +104,9 @@
| Revenue LTV | 300 |
| Data Tables | 10,000 (**see below**) |

For example, in the [Event Segmentation](/docs/analytics/charts/event-segmentation/event-segmentation-build) chart, you can export a CSV of data for 10,000 distinct property values. If you perform a group-by on a property with more than 10,000 possible values, Amplitude would only export the top 10,000 values. However, you can export the full data table to the warehouse of your choice.
For example, in the [Event Segmentation](/docs/analytics/charts/event-segmentation/event-segmentation-build) chart, you can export a .CSV that includes 10,000 distinct property values. If you apply a group-by to a property with more than 10,000 possible values, Amplitude only exports the top 10,000 of those values. However, you can export the full data table to the warehouse of your choice.

As stated in the table, the baseline group-by limit for Data Tables is 10,000. However, there are several exceptions:
The baseline group-by limit for Data Tables is 10,000, with some exceptions:

* The limit is 300 if a conversion metric is involved
* The limit is 100 if a session metric is involved
Expand Down
0 ...trees/collections/account-management.yaml → ...es/collections/en/account-management.yaml
View file
Open in desktop
File renamed without changes.
7 changes: 7 additions & 0 deletions public/docs/output/img/advanced-techniques/.meta/image2-png-1720213553.png.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
data: { }
size: 118569
last_modified: 1720213553
width: 1548
height: 878
mime_type: image/png
duration: null
7 changes: 7 additions & 0 deletions public/docs/output/img/advanced-techniques/.meta/image2-png-1720213582.png.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
data: { }
size: 118569
last_modified: 1720213582
width: 1548
height: 878
mime_type: image/png
duration: null
Binary file added public/docs/output/img/advanced-techniques/image2-png-1720213553.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added public/docs/output/img/advanced-techniques/image2-png-1720213582.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading