Skip to content

Commit e51a257

Browse files
committed
Put some stuff back
1 parent 0160379 commit e51a257

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

src/connections/spec/mobile.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,15 @@ Segment recommends using the above event names if you're going to be integrating
4343

4444
Mobile applications live within a fairly bounded lifecycle. In order to understand and communicate effectively with your users, it's crucial to instrument the core flows associated with installing and opening your app. The following events, allow you to get a picture of top-line metrics such as DAUs, MAUs, and Screen Views per session. Automatic tracking of lifecycle events is completely optional - you can learn how to enable and disable them in Segment's [iOS](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#step-2-install-the-sdk){:target="_blank"} and [Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/quickstart/#step-3-initialize-the-client){:target="_blank"} library docs.
4545

46+
The following events will be tracked automatically when lifecycle events are enabled:
47+
48+
- [Application Installed](#application-installed)
49+
- [Application Opened](#application-opened)
50+
- [Application Updated](#application-updated)
51+
4652
### Application Installed
4753

48-
This event fires when a user **first** opens your mobile application. Note, if the user never opens your app after installing, Segment will not be able to collect this event. This event doesn't wait for attribution or campaign information to be received. Advertising providers like Facebook and Google require discrete install events to correctly attribute installs to ads served through their platform.
54+
This event fires when a user **first** opens your mobile application. Note, if the user never opens your app after installing, Segment will not be able to collect this event. This event doesn't wait for attribution or campaign information to be received, and is collected automatically by Segment's SDKs. Advertising providers like Facebook and Google require discrete install events to correctly attribute installs to ads served through their platform.
4955

5056
{% comment %} api-example '{ "userId": "019mr8mf4r", "type": "track", "event": "Application Installed", "properties": { "version": "1.2.3", "build": "1234" }}'}}} {% endcomment %}
5157

@@ -112,7 +118,7 @@ This event should be sent when a user backgrounds the application upon [`applica
112118

113119
### Application Updated
114120

115-
This event fires when a user updates the application.
121+
This event fires when a user updates the application. Segment's SDK will automatically collect this event instead of an "Application Opened" event when we determine that the Open is first since an update.
116122

117123
{% comment %} api-example '{ "userId": "019mr8mf4r", "type": "track", "event": "Application Updated", "properties": { "previous_version": "1.1.2", "previous_build": 1234, "version": "1.2.0", "build": "1456" }}'}}} {% endcomment %}
118124

0 commit comments

Comments
 (0)