diff --git a/src/connections/destinations/catalog/indicative/index.md b/src/connections/destinations/catalog/indicative/index.md index 37a31a7fb7..42a69af1c6 100644 --- a/src/connections/destinations/catalog/indicative/index.md +++ b/src/connections/destinations/catalog/indicative/index.md @@ -81,8 +81,6 @@ analytics.screen({ }) ``` -- - - - ## Troubleshooting ### Property values have maximum length of 255 characters diff --git a/src/connections/destinations/catalog/inflection/index.md b/src/connections/destinations/catalog/inflection/index.md index 23688482b4..c67bfa5f3d 100644 --- a/src/connections/destinations/catalog/inflection/index.md +++ b/src/connections/destinations/catalog/inflection/index.md @@ -48,11 +48,11 @@ analytics.track('Login Button Clicked') 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. ```js - analytics.group("0e8c78ea9d97a7b8185e8632", { -name: "Initech", -industry: "Technology", -employees: 329, -plan: "enterprise", -"total billed": 830 +analytics.group("0e8c78ea9d97a7b8185e8632", { + name: "Initech", + industry: "Technology", + employees: 329, + plan: "enterprise", + "total billed": 830 }); -``` \ No newline at end of file +``` diff --git a/src/connections/destinations/catalog/inkit/index.md b/src/connections/destinations/catalog/inkit/index.md index 523eb4deba..a3f04dadb6 100644 --- a/src/connections/destinations/catalog/inkit/index.md +++ b/src/connections/destinations/catalog/inkit/index.md @@ -103,5 +103,13 @@ All other fields are then added to the user's profile as custom fields within In Segment sends Identify calls to Inkit as an `identify` event. - -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') \ No newline at end of file +```sql +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') +``` diff --git a/src/connections/destinations/catalog/kable/index.md b/src/connections/destinations/catalog/kable/index.md index 378f2de825..6f14286318 100644 --- a/src/connections/destinations/catalog/kable/index.md +++ b/src/connections/destinations/catalog/kable/index.md @@ -55,7 +55,7 @@ analytics.track({ The Segment Track event above would be transformed and transmitted to Kable as: -```curl +```bash curl --request POST \ --url https://live.kable.io/api/v1/events/create \ --header 'Accept: application/json' \ diff --git a/src/connections/destinations/catalog/leanplum/index.md b/src/connections/destinations/catalog/leanplum/index.md index 9634a70c30..72cabd7a45 100644 --- a/src/connections/destinations/catalog/leanplum/index.md +++ b/src/connections/destinations/catalog/leanplum/index.md @@ -187,7 +187,7 @@ As every analytics provider deals with push notifications and in-app messaging d 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. -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. +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. 7. Configure your app to use push notifications in your app delegate's `applicationDidFinishLaunching` method (you may choose any combination of formats. diff --git a/src/connections/destinations/catalog/localytics/index.md b/src/connections/destinations/catalog/localytics/index.md index b47fd6e190..8fc041f3ca 100644 --- a/src/connections/destinations/catalog/localytics/index.md +++ b/src/connections/destinations/catalog/localytics/index.md @@ -43,8 +43,6 @@ Whenever you call [`track`](/docs/connections/spec/track/), we'll log an event w Localytics. [`track`](/docs/connections/spec/track/) takes the name of the event and any optional properties you want to associate with the event. -- - - - ## Push Notifications Push notifications on Android require a bit of extra work to setup. diff --git a/src/connections/destinations/catalog/lytics/index.md b/src/connections/destinations/catalog/lytics/index.md index acdb17d7e7..6e0a080bc3 100644 --- a/src/connections/destinations/catalog/lytics/index.md +++ b/src/connections/destinations/catalog/lytics/index.md @@ -7,7 +7,7 @@ id: 54521fd925e721e32a72eed2 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/). -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**. +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**. ![cid](https://lyticspublic.s3.amazonaws.com/images/Segment.io/segment_cid.png) diff --git a/src/connections/destinations/catalog/mailchimp/index.md b/src/connections/destinations/catalog/mailchimp/index.md index 71c51bc974..d520ec9cc6 100644 --- a/src/connections/destinations/catalog/mailchimp/index.md +++ b/src/connections/destinations/catalog/mailchimp/index.md @@ -134,7 +134,7 @@ Again, this will **NOT** work for new users. New users will always have their su Mailchimp doesn't support arrays as traits values. This can cause calls to not show up. #### Why am I seeing a `400 Bad Request` error? -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. +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. #### Why am I seeing frequent `404 Bad Request` errors from Identify events with no error message?