Skip to content

Commit 3a38a21

Browse files
authored
Merge pull request #8049 from segmentio/DOCSPLAT-2991
DOCSPLAT 2991 Changes to simplify docs
2 parents 08b6fe8 + f9146f0 commit 3a38a21

File tree

8 files changed

+21
-17
lines changed

8 files changed

+21
-17
lines changed

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

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

84-
- - -
85-
8684
## Troubleshooting
8785

8886
### 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 & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,8 +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-
- - -
47-
4846
## Push Notifications
4947

5048
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

0 commit comments

Comments
 (0)