diff --git a/content/collections/analytics/en/account-level-reporting.md b/content/collections/analytics/en/account-level-reporting.md index e33489c09..50a7b5ab4 100644 --- a/content/collections/analytics/en/account-level-reporting.md +++ b/content/collections/analytics/en/account-level-reporting.md @@ -9,8 +9,8 @@ this_article_will_help_you: - "Use the account-level reporting feature\_when using certain Amplitude integrations, like Segment or Salesforce" landing: false exclude_from_sitemap: false -updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0 -updated_at: 1717696950 +updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae +updated_at: 1726176421 --- In Amplitude, the default level of reporting is the **individual user**, meaning your charts and analyses will all be based on data drawn from individual users. In some cases, you may need reports built around an **aggregated** unit of measurement—say, accounts, order IDs, or charts. @@ -113,8 +113,13 @@ Clicking on an account will take you to that account’s page, where you can vie ![account_level_account_page.png](/docs/output/img/analytics/account_level_account_page.png) -You will find the account’s most recent properties in the top panel. The account’s properties can be set three different ways: the [Group Identify API](https://www.docs.developers.amplitude.com/analytics/apis/group-identify-api/), the [Salesforce integration](https://www.docs.developers.amplitude.com/data/sources/salesforce-group/), and by using Event Segmentation to create dynamic properties. These properties can be used to describe the account as whole (e.g. `30 day active users`, `account - manager`, `plan type`, `renewal date`, etc.). +Find the account’s most recent properties in the top panel. Set the account's properties with one of the following: + +- the [Group Identify API](/docs/apis/analytics/group-identify) +- the [Salesforce integration](/docs/data/source-catalog/salesforce) +- Event Segmentation to create dynamic properties. + +Use these properties to describe the account as whole (for example, `30 day active users`, `account manager`, `plan type`, or `renewal date`) If you're using the User Look-up to verify events and the properties set with them, they will not be visible in the *Info* view. You can find them by clicking *Raw* instead. diff --git a/content/collections/analytics/en/releases.md b/content/collections/analytics/en/releases.md index b664bb514..3d4edfa90 100644 --- a/content/collections/analytics/en/releases.md +++ b/content/collections/analytics/en/releases.md @@ -8,7 +8,7 @@ this_article_will_help_you: landing: false exclude_from_sitemap: false updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae -updated_at: 1724883801 +updated_at: 1726163151 --- In Amplitude, a **release** represents a change in your product. It can be a major update like the launch of a new feature, a minor patch to fix a small bug, or the launch of an experiment. Releases are shown as a marker in your time-series charts when they occur. @@ -16,7 +16,7 @@ In Amplitude, a **release** represents a change in your product. It can be a maj ### Feature availability -This feature is available to users on **all Amplitude plans**. See the [pricing page](https://amplitude.com/pricing) for more details. +This feature is available to users on **some Amplitude plans only**. See the [pricing page](https://amplitude.com/pricing) for more details. ## Create a release diff --git a/content/collections/data/en/data-access-control.md b/content/collections/data/en/data-access-control.md index fb76b9433..4af96fef3 100644 --- a/content/collections/data/en/data-access-control.md +++ b/content/collections/data/en/data-access-control.md @@ -7,7 +7,7 @@ this_article_will_help_you: landing: false exclude_from_sitemap: false updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae -updated_at: 1723581892 +updated_at: 1726163345 --- Enterprise-level organizations often collect data that can include revenue data, personally identifiable information (PII), and other sensitive information. Amplitude’s **data access control (DAC)** feature enables these organizations to easily manage access to these categories of data, in a way that prevents unauthorized users from gaining access to it, and that helps prevent the data from inadvertently leaking out. @@ -27,7 +27,7 @@ The user can then exclude the restricted data and view the chart (or cohort, das ## Set access for specific categories of sensitive data -Setting access levels is a two-stage process. First, y**classify** your data. When that’s complete, you can set up **permissions**. +Setting access levels is a two-stage process. First, **classify** your data. When that’s complete, you can set up **permissions**. {{partial:admonition type='note'}} DAC applies only to properties. It **doesn’t** apply to definitions or metadata. diff --git a/content/collections/sources/en/instrument-track-sessions.md b/content/collections/sources/en/instrument-track-sessions.md index 40e9baf4e..dc46a4a83 100644 --- a/content/collections/sources/en/instrument-track-sessions.md +++ b/content/collections/sources/en/instrument-track-sessions.md @@ -8,8 +8,8 @@ this_article_will_help_you: - 'Learn how to best incorporate sessions into your analyses' landing: false exclude_from_sitemap: false -updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0 -updated_at: 1718136903 +updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae +updated_at: 1726162729 --- In Amplitude, sessions are a useful metric for understanding the frequency and duration of your users' engagement with your product. The most direct way to build a session-based analysis is with the [User Sessions chart](/docs/data/user-properties-and-events).  @@ -40,6 +40,10 @@ This commonly occurs when sending data to Amplitude from Segment through a cloud Events included in the same session are connected with a blue line, as shown above. +Amplitude assigns a session to a specific date based on its actual start time. The start time must fall within a chart's selected date range in order for Amplitude to include it on that chart. + +For example, consider a session that begins on May 17th at 8:00 PM and ends on May 18th at 1:30 AM. This session appears on charts where the selected date range includes the date on which the session began. In this example, that date range can begin no later than May 17th, **and** end no earlier than May 17th. If the chart's date range begins on May 18th, this session doesn't appear on the chart, even though the session was still active on that date. + ### Start Session and End Session events By default, Amplitude tracks `Start Session` and `End Session` events using the beginning and ending times of each session by session ID. Amplitude also uses session ID to calculate session lengths. If you use session IDs, Amplitude doesn't add extra events to your monthly event volume limit. diff --git a/content/collections/user-sessions/en/marketing-metrics-recipes.md b/content/collections/user-sessions/en/marketing-metrics-recipes.md index f73ea35d7..1e241ce42 100644 --- a/content/collections/user-sessions/en/marketing-metrics-recipes.md +++ b/content/collections/user-sessions/en/marketing-metrics-recipes.md @@ -6,8 +6,8 @@ this_article_will_help_you: - 'Use Amplitude charts to analyze common marketing metrics' landing: false source: /hc/en-us/articles/23990255180443-Marketing-metrics-recipes -updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0 -updated_at: 1718945038 +updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae +updated_at: 1726161979 --- Amplitude Analytics provides a multitude of insights into the success of your product's marketing efforts. This article highlights the ingredients needed to recreate common marketing metrics using [Event Segmentation](/docs/analytics/charts/event-segmentation/event-segmentation-build) or [User Sessions](/docs/analytics/charts/user-sessions/user-sessions-track-engagement-frequency) charts. @@ -196,4 +196,51 @@ If desired, filter results by a specific domain or URL of sessions A and B:  This User Sessions chart is set up to calculate the 30-day exit rate for the `Page URL` ampli.com/home. The chart’s group-by property value `Page Title` is seen as different colored lines in the chart. The exit rate for March 4th was 16.1 percent for the `Log In` property value. -![exitRate_wDomain.png](/docs/output/img/user-sessions/exitrate-wdomain-png.png) \ No newline at end of file +![exitRate_wDomain.png](/docs/output/img/user-sessions/exitrate-wdomain-png.png) + +## Performance marketing metrics + +Amplitude supports the use of several common performance marketing metrics. [Create these metrics](/docs/analytics/charts/data-tables/data-tables-create-metric#create-and-configure-a-new-metric) by following the recipes in this section. + +### Ad network clicks +* Metric type: `Formula` +* Event: `Daily ad metric` +* Grouped by: `ad_metrics.clicks` +* Formula: `PROPSUM(A)` + +![ad-network-clicks-definition.png](/docs/output/img/user-sessions/ad-network-clicks-definition.png) + +### Ad network impressions +* Metric type: `Formula` +* Event: `Daily ad metric` +* Grouped by: `ad_metrics.impressions` +* Formula: `PROPSUM(A)` + +### Ad network costs +* Metric type: `Formula` +* Event: `Daily ad metric` +* Grouped by: `ad_metrics.costs` +* Formula: `PROPSUM(A)` + +### Return on ad spending +* Metric type: `Formula` +* Event A: `Complete purchase` + * Grouped by: `Revenue` +* Event B: `Daily ad metric` + * Grouped by: `ad_metrics.cost` +* Formula: %: `PROPSUM(A) / PROPSUM(B)` + +### Customer acquisition cost +* Metric type: `Formula` +* Event A: `Daily ad metric` + * Grouped by: `ad_metrics.cost` +* Event B: `User Sign Up` +* Formula: $: `PROPSUM(A) / TOTALS(B)` + +### Clickthrough rate +* Metric type: `Formula` +* Event A: `Daily ad metric` + * Grouped by: `ad_metrics.impressions` +* Event B: `Daily ad metric` + * Grouped by: `ad_metrics.clicks` +* Formula: %: `PROPSUM(A) / PROPSUM(B) \ No newline at end of file diff --git a/content/trees/collections/sources.yaml b/content/trees/collections/en/sources.yaml similarity index 100% rename from content/trees/collections/sources.yaml rename to content/trees/collections/en/sources.yaml diff --git a/public/docs/output/img/user-sessions/.meta/ad-network-clicks-definition.png.yaml b/public/docs/output/img/user-sessions/.meta/ad-network-clicks-definition.png.yaml new file mode 100644 index 000000000..02a787385 --- /dev/null +++ b/public/docs/output/img/user-sessions/.meta/ad-network-clicks-definition.png.yaml @@ -0,0 +1,7 @@ +data: { } +size: 29608 +last_modified: 1726161367 +width: 589 +height: 366 +mime_type: image/png +duration: null diff --git a/public/docs/output/img/user-sessions/ad-network-clicks-definition.png b/public/docs/output/img/user-sessions/ad-network-clicks-definition.png new file mode 100644 index 000000000..57c64dd32 Binary files /dev/null and b/public/docs/output/img/user-sessions/ad-network-clicks-definition.png differ