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

Tickets for Sept 12 #270

Merged
merged 4 commits into from
Sep 13, 2024
Merged

Tickets for Sept 12 #270

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
64334f7
Tickets for Sept 12
SpencerFleury Sep 12, 2024
0860cdc
Update content/collections/sources/en/instrument-track-sessions.md
SpencerFleury Sep 13, 2024
a0712b7
Update content/collections/analytics/en/account-level-reporting.md
SpencerFleury Sep 13, 2024
6d2fd9c
Update content/collections/analytics/en/account-level-reporting.md
SpencerFleury Sep 13, 2024
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
6 changes: 3 additions & 3 deletions content/collections/analytics/en/account-level-reporting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,8 +9,8 @@
- "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.

Expand Down Expand Up @@ -113,7 +113,7 @@

![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
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](/docs/data/source-catalog/salesforce), 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

Check warning on line 116 in content/collections/analytics/en/account-level-reporting.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.Will] Future tense! Avoid using 'will find'.

Raw Output:
{"message": "[Amplitude.Will] Future tense! Avoid using 'will find'.", "location": {"path": "content/collections/analytics/en/account-level-reporting.md", "range": {"start": {"line": 116, "column": 5}}}, "severity": "WARNING"}
SpencerFleury marked this conversation as resolved.
Show resolved Hide resolved
manager`, `plan type`, `renewal date`, etc.).
SpencerFleury marked this conversation as resolved.
Show resolved Hide resolved

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.
Expand Down
4 changes: 2 additions & 2 deletions content/collections/analytics/en/releases.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,15 +8,15 @@ 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.

![release_line_chart.png](/docs/output/img/analytics/release-line-chart-png.png)

### 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

Expand Down
4 changes: 2 additions & 2 deletions content/collections/data/en/data-access-control.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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.
Expand Down
8 changes: 6 additions & 2 deletions content/collections/sources/en/instrument-track-sessions.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,8 +8,8 @@
- '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). 

Expand Down Expand Up @@ -40,6 +40,10 @@

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:00PM and ends on May 18th at 1:30AM. 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.

Check failure on line 45 in content/collections/sources/en/instrument-track-sessions.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.AMPM] Use 'AM' or 'PM' (preceded by a space).

Raw Output:
{"message": "[Amplitude.AMPM] Use 'AM' or 'PM' (preceded by a space).", "location": {"path": "content/collections/sources/en/instrument-track-sessions.md", "range": {"start": {"line": 45, "column": 62}}}, "severity": "ERROR"}

Check failure on line 45 in content/collections/sources/en/instrument-track-sessions.md

View workflow job for this annotation

GitHub Actions / runner / vale 

[vale] reported by reviewdog 🐶
[Amplitude.AMPM] Use 'AM' or 'PM' (preceded by a space).

Raw Output:
{"message": "[Amplitude.AMPM] Use 'AM' or 'PM' (preceded by a space).", "location": {"path": "content/collections/sources/en/instrument-track-sessions.md", "range": {"start": {"line": 45, "column": 93}}}, "severity": "ERROR"}
SpencerFleury marked this conversation as resolved.
Show resolved Hide resolved

### 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.
Expand Down
53 changes: 50 additions & 3 deletions content/collections/user-sessions/en/marketing-metrics-recipes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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)
![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)
0 content/trees/collections/sources.yaml → content/trees/collections/en/sources.yaml
View file
Open in desktop
File renamed without changes.
7 changes: 7 additions & 0 deletions public/docs/output/img/user-sessions/.meta/ad-network-clicks-definition.png.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
data: { }
size: 29608
last_modified: 1726161367
width: 589
height: 366
mime_type: image/png
duration: null
Binary file added public/docs/output/img/user-sessions/ad-network-clicks-definition.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