Skip to content

Commit 6f9923d

Browse files
rchinn1rchinn1
authored
Merge pull request #7897 from segmentio/Predictions-edits-
Predictions and Mobile batch edits [DOC-1250][DOC-1251]
2 parents ab6c256 + d215832 commit 6f9923d

File tree

2 files changed

+16
-16
lines changed

2 files changed

+16
-16
lines changed

‎src/connections/spec/mobile.md

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -9,12 +9,12 @@ One of the core components of the Segment [Spec](/docs/connections/spec/) is the
99
By standardizing the events that comprise the core **mobile application lifecycle** and associated **mobile campaign and referral events**, Segment and its partners can, wherever possible, forward these events on your behalf and build downstream destinations that take full advantage of the semantic meaning associated with these events and their properties.
1010

1111
> info ""
12-
> If you're already collecting similar events, Segment recommends migrating to these event names so that you can take advantage of available features in Segment destinations that depend on the spec as they become available.
12+
> If you're already collecting similar events, Segment recommends migrating to these event names so that you can take advantage of available features in Segment destinations that depend on the spec as they become available.
1313
14-
These events pair nicely with Segment's [ecommerce spec](/docs/connections/spec/ecommerce/v2/) for mobile marketplaces to take full advantage of features like dynamic ads in Facebook and the ability to take full advantage of server-side destinations with Mobile Attribution Platforms like [Tune](https://www.tune.com/){:target="_blank"} and [Kochava](https://www.kochava.com/){:target="_blank"}.
14+
These events also work with Segment's [ecommerce spec](/docs/connections/spec/ecommerce/v2/) for mobile marketplaces to take full advantage of features like dynamic ads in Facebook and the ability to take full advantage of server-side destinations with Mobile Attribution Platforms like [Tune](https://www.tune.com/){:target="_blank"} and [Kochava](https://www.kochava.com/){:target="_blank"}.
1515

1616
> info ""
17-
> Per the [Privacy Policy](https://segment.com/legal/privacy/#sensitive-personal-information){:target="_blank"} and applicable terms, don't send Segment sensitive personal information about your users. Certain features from Segment and its partners allow you to opt-in to automatically track data (for example: Application Installed or Deep Link Clicked). When working with these features and Segment in general, be cognizant of the data that is being tracked to ensure its matching both your obligations under your agreement with Segment and the privacy expectations of your users.
17+
> Per the [Privacy Policy](https://segment.com/legal/privacy/#sensitive-personal-information){:target="_blank"} and applicable terms, don't send Segment sensitive personal information about your users. Certain features from Segment and its partners allow you to opt-in to automatically track data (for example, **Application Installed** or **Deep Link Clicked**). When working with these features and Segment in general, be cognizant of the data that is being tracked to ensure its matching both your obligations under your agreement with Segment and the privacy expectations of your users.
1818
1919
## Overview of events
2020

@@ -37,7 +37,7 @@ The Segment Native Mobile Spec includes the following semantic events:
3737
- [Deep Link Opened](#deep-link-opened)
3838
- [Deep Link Clicked](#deep-link-clicked)
3939

40-
Segment recommends using the above event names if you're going to be integrating the events yourself. This will ensure that they can be mapped effectively in downstream tools.
40+
We recommend using the above event names if you're going to be integrating the events yourself. This will ensure that they can be mapped effectively in downstream tools.
4141

4242
## Lifecycle events
4343

@@ -80,7 +80,7 @@ This event fires when a user **first** opens your mobile application. Note, if t
8080
}
8181
```
8282

83-
| **Property** | **Type** | **Description** |
83+
| Property | Type | Description |
8484
| ------------ | -------- | -------------------------------------- |
8585
| `version` | String | The version installed. |
8686
| `build` | String | The build number of the installed app. |
@@ -105,7 +105,7 @@ This event fires when a user launches or foregrounds your mobile application aft
105105
}
106106
```
107107

108-
| **Property** | **Type** | **Description** |
108+
| Property | Type | Description |
109109
| ----------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
110110
| `from_background` | Boolean | If application [transitioned](https://developer.apple.com/library/ios/documentation/UIKit/Reference/UIApplicationDelegate_Protocol/#//apple_ref/doc/uid/TP40006786-CH3-SW52){:target="_blank"} from "Background" to "Inactive" state prior to foregrounding (as opposed to from "Not Running" state). |
111111
| `url` | String | The value of `UIApplicationLaunchOptionsURLKey` from `launchOptions`. **Collected on iOS only**. |
@@ -164,7 +164,7 @@ This event fires when a user updates the application. Segment's SDK will automat
164164
}
165165
```
166166

167-
| **Property** | **Type** | **Description** |
167+
| Property | Type | Description |
168168
| ------------------ | -------- | -------------------------------- |
169169
| `previous_version` | String | The previously recorded version. |
170170
| `previous_build` | String | The previously recorded build. |
@@ -231,7 +231,7 @@ When Segment or an integrated partner can discern the source of an install, we'l
231231
}
232232
```
233233

234-
| **Property** | **Type** | **Description** |
234+
| Property | Type | Description |
235235
| ----------------------- | -------- | --------------------------------------- |
236236
| `provider` | String | The attribution provider. |
237237
| `campaign[source]` | String | Campaign source — attributed ad network.|
@@ -264,7 +264,7 @@ This event can be sent when a push notification is received in the app. It can b
264264
}
265265
```
266266

267-
| **Property** | **Type** | **Description** |
267+
| Property | Type | Description |
268268
| ------------------- | -------- | ---------------------------------------------------------- |
269269
| `campaign[name]` | String | Campaign name. |
270270
| `campaign[medium]` | String | Identifies what type of link was used (Push Notification). |
@@ -296,7 +296,7 @@ This event can be sent when a user taps on a push notification associated with y
296296
```
297297

298298

299-
| **Property** | **Type** | **Description** |
299+
| Property | Type | Description |
300300
| ------------------- | -------- | ----------------------------------------------------------------------------------- |
301301
| `action` | String | If this notification is "actionable", the custom action tapped. **Default:** "Open" |
302302
| `campaign[name]` | String | Campaign name. |
@@ -328,7 +328,7 @@ This event fires when a push notification from a provider bounces. If your push
328328
}
329329
```
330330

331-
| **Property** | **Type** | **Description** |
331+
| Property | Type | Description |
332332
| ------------------- | -------- | ----------------------------------------------------------------------------------- |
333333
| `action` | String | If this notification is "actionable", the custom action tapped. **Default:** "Open" |
334334
| `campaign[name]` | String | Campaign name. |
@@ -357,7 +357,7 @@ This event is fired *in addition* to the associated `Application Opened` event.
357357
}
358358
```
359359

360-
| **Property** | **Type** | **Description** |
360+
| Property | Type | Description |
361361
| ------------ | -------- | ----------------------- |
362362
| `provider` | String | The deep link provider. |
363363
| `url` | String | The App URL opened. |
@@ -381,7 +381,7 @@ This event may be provided by deep link providers postback mechanisms or an inte
381381
}
382382
```
383383

384-
| **Property** | **Type** | **Description** |
384+
| Property | Type | Description |
385385
| ------------ | -------- | -------------------------- |
386386
| `provider` | String | The deep link provider. |
387387
| `url` | String | The deep link URL clicked. |

‎src/unify/Traits/predictions/index.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ For example, to predict a customer's propensity to purchase over the next 30 day
7272

7373
To access Predictions, you must:
7474

75-
- Track more than 1 event type, but fewer than 2,000 event types. An event type refers to the total number of distinct events seen across all users in an Engage Space within the past 15 days.
75+
- Track more than one event type, but fewer than 2,000 event types. An event type refers to the total number of distinct events seen across all users in an Engage Space within the past 15 days.
7676
- If you currently track more than 2,000 distinct events, reduce the number of tracked events below this limit and wait around 15 days before creating your first prediction.
7777
- Events become inactive if they've not been sent to an Engage Space within the past 15 days.
7878
- To prevent events from reaching your Engage Space, modify your event payloads to set `integrations.Personas` to `false`.
@@ -113,7 +113,7 @@ If you don’t track `Order Completed`, choose a target event that represents a
113113

114114
### Predicted Lifetime Value
115115

116-
Predicted Lifetime Value predicts a customer's future spend over the next 120 days. To create this prediction, select a purchase event, revenue property, and the currency (which defaults to USD). LTV is only calculated for customers that have performed the selected purchase events 2 or more times. The following table contains details for each property:
116+
Predicted Lifetime Value predicts a customer's future spend over the next 120 days. To create this prediction, select a purchase event, revenue property, and the currency (which defaults to USD). LTV is only calculated for customers that have performed the selected purchase events two or more times. The following table contains details for each property:
117117

118118
| Property | Description |
119119
| --------------- | -------------------------------------------------------------------------------------------------------------------------- |
@@ -150,7 +150,7 @@ Once a trait successfully computes, you can send them downstream to some destina
150150
BRAZE = "braze_id"
151151
SEGMENT = "segment_id"
152152

153-
Other destinations may drop events published by Predictive Traits
153+
Other destinations may drop events published by Predictive Traits.
154154

155155
For use additional cases and information on how Segment builds prediction, read [Using Predictions](/docs/unify/traits/predictions/using-predictions/).
156156

0 commit comments

Comments
 (0)