Skip to content

Commit 5510371

Browse files
lopenchilopenchi
authored
Merge branch 'develop' into DOCSPLAT-2993
2 parents 6c624e0 + 3a38a21 commit 5510371

File tree

9 files changed

+74
-88
lines changed

9 files changed

+74
-88
lines changed

‎src/connections/destinations/catalog/indicative/index.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -81,7 +81,6 @@ analytics.screen({
8181
})
8282
```
8383

84-
8584
## Troubleshooting
8685

8786
### Property values have maximum length of 255 characters

‎src/connections/destinations/catalog/inflection/index.md‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -48,11 +48,11 @@ analytics.track('Login Button Clicked')
4848
Send [Group](/docs/connections/spec/group) calls to tie a user to an org. There are two IDs that are relevant in a group call: the userId, which belongs and refers to the user, and the groupId, which belongs and refers to the specific group. A user can belong to multiple groups, each associated with a different groupId, but the user will have only one userId linked to each of these different groups.
4949

5050
```js
51-
analytics.group("0e8c78ea9d97a7b8185e8632", {
52-
name: "Initech",
53-
industry: "Technology",
54-
employees: 329,
55-
plan: "enterprise",
56-
"total billed": 830
51+
analytics.group("0e8c78ea9d97a7b8185e8632", {
52+
name: "Initech",
53+
industry: "Technology",
54+
employees: 329,
55+
plan: "enterprise",
56+
"total billed": 830
5757
});
58-
```
58+
```

‎src/connections/destinations/catalog/inkit/index.md‎

Lines changed: 10 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -103,5 +103,13 @@ All other fields are then added to the user's profile as custom fields within In
103103

104104
Segment sends Identify calls to Inkit as an `identify` event.
105105

106-
107-
SELECT COUNT(*) FROM destination_config WHERE destination_id = '54521fd525e721e32a72ee8f' AND enabled = 1 AND id IN (SELECT config_id FROM destination_config_options_2 WHERE option_name = 'canOmitAppsFlyerId' AND value = 'false')
106+
```sql
107+
SELECT COUNT(*)
108+
FROM destination_config
109+
WHERE destination_id = '54521fd525e721e32a72ee8f'
110+
AND enabled = 1
111+
AND id IN (SELECT config_id
112+
FROM destination_config_options_2
113+
WHERE option_name = 'canOmitAppsFlyerId'
114+
AND value = 'false')
115+
```

‎src/connections/destinations/catalog/kable/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -55,7 +55,7 @@ analytics.track({
5555

5656
The Segment Track event above would be transformed and transmitted to Kable as:
5757

58-
```curl
58+
```bash
5959
curl --request POST \
6060
--url https://live.kable.io/api/v1/events/create \
6161
--header 'Accept: application/json' \

‎src/connections/destinations/catalog/leanplum/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -187,7 +187,7 @@ As every analytics provider deals with push notifications and in-app messaging d
187187

188188
5. In Keychain, select the new certificates, expand them to view the private key, and then right click to export them as .p12 files. You must enter a password.
189189

190-
6. In Leanplum, go to your app's Keys & Settings (App Settings > {Your app} > Keys & Settings). Under Push Notifications, upload your .p12 files to Leanplum and enter your passphrase from step 5 above.
190+
6. In Leanplum, go to your app's Keys & Settings (App Settings > \{Your app} > Keys & Settings). Under Push Notifications, upload your .p12 files to Leanplum and enter your passphrase from step 5 above.
191191

192192
7. Configure your app to use push notifications in your app delegate's `applicationDidFinishLaunching` method (you may choose any combination of formats.
193193

‎src/connections/destinations/catalog/localytics/index.md‎

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,6 @@ Whenever you call [`track`](/docs/connections/spec/track/), we'll log an event w
4343
Localytics. [`track`](/docs/connections/spec/track/) takes the name of the event and any
4444
optional properties you want to associate with the event.
4545

46-
4746
## Push Notifications
4847

4948
Push notifications on Android require a bit of extra work to setup.

‎src/connections/destinations/catalog/lytics/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ id: 54521fd925e721e32a72eed2
77

88
1. Lytics uses Segment's JavaScript library so make sure to [go through our quickstart guide to get set up on that first](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/).
99

10-
2) Once you're recording data enable Lytics on your destination page using your Customer ID number, which can be found in the admin section of your Lytics account: **Account** -> **Manage Accounts**.
10+
2. Once you're recording data enable Lytics on your destination page using your Customer ID number, which can be found in the admin section of your Lytics account: **Account** -> **Manage Accounts**.
1111

1212
![cid](https://lyticspublic.s3.amazonaws.com/images/Segment.io/segment_cid.png)
1313

‎src/connections/destinations/catalog/mailchimp/index.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -134,7 +134,7 @@ Again, this will **NOT** work for new users. New users will always have their su
134134
Mailchimp doesn't support arrays as traits values. This can cause calls to not show up.
135135

136136
#### Why am I seeing a `400 Bad Request` error?
137-
A **400 Bad Request** error can occur if the email address contains a misspelled domain name. For example, Mailchimp might reject`"joe@gmil.com"` because "gmail" is misspelled.
137+
A **400 Bad Request** error can occur if the email address contains a misspelled domain name. For example, Mailchimp might reject `"joe@gmil.com"` because "gmail" is misspelled.
138138

139139
#### Why am I seeing frequent `404 Bad Request` errors from Identify events with no error message?
140140

‎src/connections/storage/warehouses/schema.md‎

Lines changed: 53 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -22,99 +22,79 @@ Segment's libraries pass nested objects and arrays into tracking calls as **prop
2222
- The warehouse connector optionally stringifies **arrays** when they follow the [Ecommerce spec](/docs/connections/spec/ecommerce/v2/)
2323
- The warehouse connector "flattens" all **context fields** that contain a nested **object** (for example, context.field.nestedA.nestedB becomes a column called context_field_nestedA_nestedB)
2424

25-
<table>
26-
<thead>
27-
<tr>
28-
<th> Field </th>
29-
<th> Code (Example) </th>
30-
<th> Schema (Example) </th>
31-
</tr>
32-
</thead>
33-
34-
<tr>
35-
<td><b>Object (Context):</b> Flatten </td>
36-
<td markdown="1">
37-
38-
``` json
39-
context: {
40-
app: {
41-
version: "1.0.0"
25+
### Schema objects
26+
27+
The following examples show how Segment transforms nested objects and arrays into warehouse columns.
28+
29+
#### Context
30+
31+
**Type:** Object
32+
33+
```json
34+
{
35+
"context": {
36+
"app": {
37+
"version": "1.0.0"
38+
}
4239
}
4340
}
4441
```
45-
</td>
46-
<td>
47-
<b>Column Name:</b><br/>
48-
context_app_version
49-
<br/><br/>
50-
<b>Value:</b><br/>
51-
"1.0.0"
52-
</td>
53-
</tr>
54-
55-
<tr>
56-
<td> <b>Object (Traits):</b> Flatten </td>
57-
<td markdown= "1">
42+
43+
Segment flattens nested objects in context fields.
44+
45+
**Result:** Column `context_app_version` with value `"1.0.0"`
46+
47+
#### Traits
48+
49+
**Type:** Object
5850

5951
```json
60-
traits: {
61-
address: {
62-
street: "6th Street"
52+
{
53+
"traits": {
54+
"address": {
55+
"street": "6th Street"
56+
}
6357
}
6458
}
6559
```
6660

67-
</td>
68-
<td>
69-
<b>Column Name:</b><br/>
70-
address_street<br/>
71-
<br/>
72-
<b>Value:</b><br/>
73-
"6th Street"
74-
</td>
75-
</tr>
61+
Segment flattens nested objects in traits.
7662

77-
<tr>
78-
<td><b>Object (Properties):</b> Flatten</td>
79-
<td markdown="1">
63+
**Result:** Column `address_street` with value `"6th Street"`
64+
65+
#### Properties
66+
67+
**Type:** Object
8068

8169
```json
82-
properties: {
83-
product_id: {
84-
sku: "G-32"
70+
{
71+
"properties": {
72+
"product_id": {
73+
"sku": "G-32"
74+
}
8575
}
8676
}
8777
```
88-
</td>
89-
<td>
90-
<b>Column Name:</b><br/>
91-
product_id_sku<br/><br/>
92-
<b>Value:</b><br/>
93-
"G-32"
94-
</td>
95-
</tr>
96-
97-
<tr>
98-
<td><b>Array (Any):</b> Stringify</td>
99-
<td markdown="1">
78+
79+
Segment flattens nested objects in properties.
80+
81+
**Result:** Column `product_id_sku` with value `"G-32"`
82+
83+
#### Array (String)
84+
85+
**Type**: String array
10086

10187
```json
102-
products: {
103-
product_id: [
104-
"507f1", "505bd"
105-
]
88+
{
89+
"products": {
90+
"product_id": ["507f1", "505bd"]
91+
}
10692
}
10793
```
10894

109-
</td>
110-
<td>
111-
<b>Column Name:</b> <br/>
112-
product_id <br/><br/>
113-
<b>Value:</b>
114-
"[507f1, 505bd]"
115-
</td>
116-
</tr>
117-
</table>
95+
Segment stringifes arrays.
96+
97+
**Result:** Column `product_id` with value `"[507f1, 505bd]"`
11898

11999
## Warehouse tables
120100

0 commit comments

Comments
 (0)