Update index.md #114
Update index.md #114
Conversation
Added a note on Start/End Session events to clarify that they do count towards the event volume.
🦙 MegaLinter status: ✅ SUCCESS
See detailed report in MegaLinter reports MegaLinter is graciously provided by |
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
| @@ -575,8 +575,9 @@ You can adjust the time window for which sessions are extended. The default sess | |||
| Amplitude amplitude = new Amplitude(configuration); | |||
| ``` | |||
|
|
|||
| By default, Amplitude automatically sends the '[Amplitude] Start Session' and '[Amplitude] End Session' events. Even though these events aren't sent, sessions are still tracked by using `session_id`. | |||
| You can also disable those session events. | |||
| By default, Amplitude sends the '[Amplitude] Start Session' and '[Amplitude] End Session' events. Even though these events aren't sent, sessions are still tracked by using `session_id`. | |||
There was a problem hiding this comment.
@zheniasemenina This paragraph is unclear. First sentence says that Amplitude sends those events, but the second says otherwise. Can you confirm which is correct? Is it the same as the iOS-Swift article?
There was a problem hiding this comment.
@markzegarelli This is incorrect, but it stems from the previous version of this SDK: it used to say 'By default, '[Amplitude] Start Session' and '[Amplitude] End Session' events aren't sent. Even though these events..'
So we can get rid of this piece now.
Added a note on Start/End Session events to clarify that they do count towards the event volume.
Amplitude Developer Docs PR
Description
Describe your changes.
Deadline
When do these changes need to be live on the site?
Change type
PR checklist:
mkdocs serve.mkdocs servedidn't generate any failures.@amplitude-dev-docs