You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/spec/mobile.md
+24-24Lines changed: 24 additions & 24 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,13 +51,13 @@ The following events will be tracked automatically when lifecycle events are ena
51
51
52
52
This event fires when a user **first** opens your mobile application. Note, if the user never opens your app after installing, we will not be able to collect this event. This event does not wait for attribution or campaign information to be received, and is collected automatically by our SDKs. Advertising providers like Facebook and Google require discrete install events to correctly attribute installs to ads served through their platform.
@@ -75,12 +75,12 @@ This event fires when a user **first** opens your mobile application. Note, if t
75
75
76
76
This event fires when a user launches or foregrounds your mobile application after the first open. It will fire after the `Application Installed` event and again after the app is re-opened after being closed. This event does not wait for attribution information to be received but may include information about referring applications or deep link URLs if available to the application upon open.
@@ -103,12 +103,12 @@ This event fires when a user launches or foregrounds your mobile application aft
103
103
104
104
This event should be sent when a user backgrounds the application upon [`applicationDidEnterBackground`](https://developer.apple.com/reference/uikit/uiapplicationdelegate/1622997-applicationdidenterbackground)
@@ -118,12 +118,12 @@ This event should be sent when a user backgrounds the application upon [`applica
118
118
119
119
This event fires when a user updates the application. Our SDK will automatically collect this event in lieu of an "Application Opened" event when we determine that the Open is first since an update.
@@ -145,12 +145,12 @@ This event fires when a user updates the application. Our SDK will automatically
145
145
146
146
Fire this event when a user uninstalls the application. Several destination partners will detect this for you using Silent Push Notifications and send this event to Segment on your behalf.
@@ -160,12 +160,12 @@ Fire this event when a user uninstalls the application. Several destination part
160
160
161
161
You can send this event when you receive a crash notification from your app, but is not meant to supplant traditional crash reporting tools. By tracking crashes as an analytics event with device and user information, you can analyze the which types of users are impacted by crashes and how those crashes, in turn, affect their engagement. You may also want to target those customers with tailored communications in other channels if they've encountered several crashes.
@@ -179,12 +179,12 @@ As the walls between apps become increasingly lowered, capturing information abo
179
179
180
180
When Segment or an integrated partner can discern the source of an install, we'll collect an `Install Attributed` event. This event may be sent to Segment using server-to-server connection from your attribution provider, or directly on the device using packaged destinations. In either case, this will happen **after** install, and does not apply to all installs, which is why it is a discrete event.
@@ -214,12 +214,12 @@ When Segment or an integrated partner can discern the source of an install, we'l
214
214
215
215
This event can be sent when a push notification is received in the app. It can be automatically enabled on [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#automatic-push-notification-tracking).
216
216
217
-
{% comment %} api-example '{ "userId": "019mr8mf4r", "action": "track", "event": "Push Notification Received", "properties": { "campaign": { "medium": "Push", "source": "Vendor Name", "name": "Referral Flow", "content": "Your friend invited you to play a match."}}}'}}} {% endcomment %}
217
+
{% comment %} api-example '{ "userId": "019mr8mf4r", "type": "track", "event": "Push Notification Received", "properties": { "campaign": { "medium": "Push", "source": "Vendor Name", "name": "Referral Flow", "content": "Your friend invited you to play a match."}}}'}}} {% endcomment %}
218
218
219
219
```json
220
220
{
221
221
"userId": "019mr8mf4r",
222
-
"action": "track",
222
+
"type": "track",
223
223
"event": "Push Notification Received",
224
224
"properties": {
225
225
"campaign": {
@@ -244,12 +244,12 @@ This event can be sent when a push notification is received in the app. It can b
244
244
245
245
This event can be sent when a user taps on a push notification associated with your app. It can be automatically enabled on [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#automatic-push-notification-tracking).
246
246
247
-
{% comment %} api-example '{ "userId": "019mr8mf4r", "action": "track", "event": "Push Notification Tapped", "properties": {"action": "Accept", "campaign": { "medium": "Push", "source": "Vendor Name", "name": "Referral Flow", "content": "Your friend invited you to play a match." }}}'}}} {% endcomment %}
247
+
{% comment %} api-example '{ "userId": "019mr8mf4r", "type": "track", "event": "Push Notification Tapped", "properties": {"action": "Accept", "campaign": { "medium": "Push", "source": "Vendor Name", "name": "Referral Flow", "content": "Your friend invited you to play a match." }}}'}}} {% endcomment %}
248
248
249
249
```json
250
250
{
251
251
"userId": "019mr8mf4r",
252
-
"action": "track",
252
+
"type": "track",
253
253
"event": "Push Notification Tapped",
254
254
"properties": {
255
255
"action": "Accept",
@@ -277,12 +277,12 @@ This event can be sent when a user taps on a push notification associated with y
277
277
278
278
This event fires when a push notification from a provider bounces. If your push notification provider forwards push lifecycle events to Segment, they should include this event in their suite.
279
279
280
-
{% comment %} api-example '{ "userId": "019mr8mf4r", "action": "track", "event":"Push Notification Bounced", "properties": { "action": "Accept", "campaign": { "medium": "Push", "source": "Vendor Name", "name": "Referral Flow", "content": "Your friend invited you to play a match." }}}'}}} {% endcomment %}
280
+
{% comment %} api-example '{ "userId": "019mr8mf4r", "type": "track", "event":"Push Notification Bounced", "properties": { "action": "Accept", "campaign": { "medium": "Push", "source": "Vendor Name", "name": "Referral Flow", "content": "Your friend invited you to play a match." }}}'}}} {% endcomment %}
281
281
282
282
```json
283
283
{
284
284
"userId": "019mr8mf4r",
285
-
"action": "track",
285
+
"type": "track",
286
286
"event":"Push Notification Bounced",
287
287
"properties": {
288
288
"action": "Accept",
@@ -313,12 +313,12 @@ This event is fired *in addition* to the associated `Application Opened` event.
313
313
314
314
Our [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#automatic-deep-link-tracking) SDK can collect this event automatically if configured to do so.
This event may be provided by deep link providers postback mechanisms or an internal redirect service if you use one in order to provide a waypoint funnel step between your content or advertisement and the resulting app open.
0 commit comments