Various tickets

DOC-109
DOC-190
DOC-197
DOC-198
DOC-199

content/collections/billing-use/en/mtu-guide.md

@@ -7,8 +7,8 @@ this_article_will_help_you:
   - 'Understand how Amplitude calculates and charges for MTUs'
 landing: true
 exclude_from_sitemap: false
-updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
-updated_at: 1717697584
+updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
+updated_at: 1723581207
 landing_blurb: 'Learn about how Amplitude bills with Monthly Tracked Users.'
 ---
 Amplitude customers on Scholarship, Starter, and Plus plans bill according to **monthly tracked user (MTU)** count. This option is also available to customers on Growth and Enterprise plans. 
@@ -84,7 +84,7 @@ Regardless of the plan you’re on, you're' be subject to a cap on events per MT
 
 For example, if you purchased *n* MTUs and expect to have *x* events per user, when your event volume *k* exceeds *n*(*x*), you could see a charge for the difference based on the formula
 
-`(* - n(x)) / x = number of excess MTUs`
+`(k - n(x)) / x = number of excess MTUs`
 
 ### Exceeding limits on a free plan
 

content/collections/data/en/data-access-control.md

@@ -6,8 +6,8 @@ this_article_will_help_you:
   - 'Easily prevent users from accessing sensitive or restricted information in Amplitude'
 landing: false
 exclude_from_sitemap: false
-updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
-updated_at: 1722878855
+updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
+updated_at: 1723581892
 ---
 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.
 
@@ -42,7 +42,7 @@ DAC applies only to properties. It **doesn’t** apply to definitions or metadat
 
 ### Set up permissions
 
-1. In Amplitude Data, navigate to *Groups* and click the name of the group you’re interested in. You can also [create a new group](/docs/admin/account-management/manage-permission-groups#create-a-group).
+1. Navigate to *Settings > Organization settings > Groups* and click the name of the group you’re interested in. You can also [create a new group](/docs/admin/account-management/manage-permission-groups#create-a-group).
 2. Open the group’s *Data Access* tab. All three controllable classifications are visible here: PII, revenue, and sensitive.
 3. For each classification, select *Yes* to allow members of the group to view this data, or *No* to deny them access.
 4. When you’re done, click *Save*.

content/collections/event-segmentation/en/event-segmentation-custom-formulas.md

@@ -5,8 +5,8 @@ title: 'Custom formulas: Syntax and definitions'
 source: 'https://help.amplitude.com/hc/en-us/articles/115001163231-Custom-formulas-Syntax-and-definitions'
 this_article_will_help_you:
   - 'Understand and use custom formulas in Amplitude to create exactly the analysis you need'
-updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
-updated_at: 1718057055
+updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
+updated_at: 1723580804
 landing: true
 landing_blurb: 'Understand and use custom formulas in Amplitude to create exactly the analysis you need'
 exclude_from_sitemap: false
@@ -380,12 +380,14 @@ The blue line in this chart shows daily active users and the green line shows th
 * **Event:** Refers to the event you are interested in. This must be a letter that corresponds to an event in the Events card.
 * **Number of intervals:** The number of five-minute intervals, hours, days, weeks, or months to include in the rolling average. For example, a daily chart allows rolling averages over daily intervals only. The maximum ranges for a rolling average are 36 five-minute intervals (this works out to three hours), 72 hours, 90 days, 12 weeks, or 12 months.
 
-Returns the metric for the event selected with a [rolling window](https://help.amplitude.com/hc/en-us/articles/14056975720091#h_d48f96e2-797c-45d9-bf87-6e5a5ac8ad28) of however many days/weeks/months inputted, where a rolling window aggregation is applied *after* a cohort filter, if one is in use. 
+Returns the metric for the event selected with a [rolling window](https://help.amplitude.com/hc/en-us/articles/14056975720091#h_d48f96e2-797c-45d9-bf87-6e5a5ac8ad28) of the number of days, weeks, or months you specify, where a rolling window aggregation is applied *after* a cohort filter, if one is in use. 
 
 For example, this chart first calculates the new users for each time interval and then performs the rolling window aggregation on top of that.
 
 ![rollwin_sidecontrols.png](/docs/output/img/event-segmentation/rollwin-sidecontrols-png.png)
 
+The day (or week, or month) the chart displays is the last day of the window.
+
 ### ROLLWINBEFORE
 
 **Syntax**: ROLLWINBEFORE(metric, event, # of five-minute intervals/hours/days/weeks/months)

content/collections/sections/en/session-replay.md

@@ -5,7 +5,7 @@ title: 'Session Replay'
 author: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
 exclude_from_sitemap: false
 updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
-updated_at: 1721084749
+updated_at: 1723583253
 nav_title: session_replay
 hide_toc: false
 ---
@@ -94,7 +94,11 @@ Filtered results by date or time frame match the project's timezone.
 
 3. To narrow the list with a filter, click *+ Add Filter*. You can filter by cohorts, events, event properties, user properties, and session duration. You can also use multiple filters to further narrow your list.
 
-Once you make your selection, view replays that took place within the selected time frame, or replays that meet your filter specifications. Your search results generate a unique URL that you can share with your team. 
+Once you make your selection, view replays that took place within the selected time frame, or replays that meet your filter specifications. Your search results generate a unique URL that you can share with your team.
+
+{{partial:admonition type='note'}}
+Keep in mind that if you apply a filter to exclude replays with a specific property value, Session Replay search returns results for all replays with a different value for that property, **and** replays with **missing** values for that property.
+{{/partial:admonition}}
 
 The list of results shows a maximum of 100 replays. 
 
@@ -134,6 +138,4 @@ There are some limitations when using Session Replay:
 	* `<object>` elements: Plugins such as Flash, Java, Silverlight, etc., except `<object type="image">`
 	* Lottie Animations (web and mobile)
 	* iFrames not from origin
-	* Assets that require authentication, like fonts, CSS files, and images
-
-
+	* Assets that require authentication, like fonts, CSS files, and images

content/collections/session-replay/en/session-replay-plugin.md

@@ -5,8 +5,8 @@ title: 'Session Replay Plugin'
 source: 'https://www.docs.developers.amplitude.com/session-replay/sdks/standalone/'
 landing: false
 exclude_from_sitemap: false
-updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
-updated_at: 1714686587
+updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
+updated_at: 1723582784
 ---
 {{partial:admonition type="note" heading="Session Replay instrumentation"}}
 Session Replay isn't enabled by default, and requires setup beyond the standard Amplitude instrumentation.
@@ -190,10 +190,6 @@ Once enabled, Session Replay runs on your site until either:
 - The user leaves your site
 - You call `amplitude.remove(sessionReplayTracking.name)`
 
-Call `amplitude.remove(sessionReplayTracking.name)` before a user navigates to a restricted area of your site to disable replay collection while the user is in that area. 
-
-To restart replay collection, call `amplitude.add(sessionReplayTracking)` to re-add the plugin.
-
 {{partial:admonition type="note" heading=""}}
 These examples assume you use the variable `sessionReplayTracking` in your initialization code.
 {{/partial:admonition}}
@@ -202,6 +198,22 @@ Call `amplitude.remove('sessionReplayTracking')` before a user navigates to a re
 
 To restart replay collection, call `amplitude.add('sessionReplayTracking')` to re-add the plugin.
 
+{{partial:admonition type='note'}}
+Always wait for `amplitude.add()` to finish before invoking `amplitude.remove()`. If you don't, you may get an error in the console: `TypeError: Cannot read properties of undefined (reading 'teardown')`. Use the `promise` property to do this, as shown in either of these examples:
+
+```
+await amplitude.add(sessionReplayTracking).promise;
+await amplitude.remove(sesionReplayTracking.name).promise;
+```
+
+```
+const addPromise = amplitude.add(sessionReplayTracking).promise; 
+addPromise.then(() => {
+    amplitude.remove(sessionReplayTracking.name).promise;
+});
+```
+{{/partial:admonition}}
+
 You can also use a feature flag product like Amplitude Experiment to create logic that enables or disables replay collection based on criteria like location. For example, you can create a feature flag that targets a specific user group, and add that to your initialization logic:
 
 ```js
@@ -219,6 +231,8 @@ if (nonEUCountryFlagEnabled) {
 }
 ```
 
+
+
 ## Data retention
 
 Session replay uses existing Amplitude tools and APIs to handle privacy and deletion requests.
@@ -400,4 +414,4 @@ In general, replays should be available within minutes of ingestion. Delays or e
 - Session Replay references the wrong project.
 - Short sessions. If a users bounces within a few seconds of initialization, the SDK may not have time to upload replay data.
 - Page instrumentation. If Session Replay isn't implemented on all pages a user visits, their session may not capture properly.
-- Replays older than the set [retention period](#retention-period) (defaults to 30 days, or 90 days if you purchase extra volume).
+- Replays older than the set [retention period](#retention-period) (defaults to 30 days, or 90 days if you purchase extra volume).