From 77b387d80d6cd3ddf8c2d551e25f89a50fc711fa Mon Sep 17 00:00:00 2001 From: sanscontext Date: Mon, 12 Aug 2019 19:15:18 -0700 Subject: [PATCH 1/6] add footer to some of the todo list, move warehouse docs as I find them Signed-off-by: sanscontext --- .../destinations/catalog/aboardly/index.md | 3 + .../destinations/catalog/adtriba/index.md | 2 + .../adwords-remarketing-lists/index.md | 2 + .../destinations/catalog/adwords/index.md | 3 + .../destinations/catalog/akita/index.md | 3 + .../destinations/catalog/all-aboard/index.md | 2 + .../destinations/catalog/appcues/index.md | 2 + .../destinations/catalog/apteligent/index.md | 2 + .../destinations/catalog/batch/index.md | 2 + .../destinations/catalog/boomtrain/index.md | 2 + .../catalog/branch-metrics/index.md | 3 + .../destinations/catalog/bronto/index.md | 1 + .../destinations/catalog/bugsnag/index.md | 2 + .../destinations/catalog/callexa/index.md | 2 + .../destinations/catalog/castle/index.md | 4 +- .../destinations/catalog/chameleon/index.md | 2 + .../destinations/catalog/chartbeat/index.md | 2 + .../destinations/catalog/clevertap/index.md | 2 + .../catalog/clientsuccess/index.md | 4 +- .../destinations/catalog/comscore/index.md | 2 + .../destinations/catalog/convertro/index.md | 3 + .../destinations/catalog/cordialio/index.md | 2 + .../destinations/catalog/countly/index.md | 2 + .../destinations/catalog/criteo/index.md | 2 + .../destinations/catalog/cubitic/index.md | 2 + .../destinations/catalog/curebit/index.md | 2 + .../destinations/catalog/cxense/index.md | 2 + .../amazon-s3/images/bucket-property.png | Bin .../amazon-s3/images/customer-managed-key.png | Bin .../amazon-s3/images/disable-segment-sse.png | Bin .../catalog/amazon-s3/index.md | 0 .../{catalog.md => catalog/index.md} | 0 todo.txt | 112 +++++++++++++++++- 33 files changed, 171 insertions(+), 3 deletions(-) rename connections/{destinations => warehouses}/catalog/amazon-s3/images/bucket-property.png (100%) rename connections/{destinations => warehouses}/catalog/amazon-s3/images/customer-managed-key.png (100%) rename connections/{destinations => warehouses}/catalog/amazon-s3/images/disable-segment-sse.png (100%) rename connections/{destinations => warehouses}/catalog/amazon-s3/index.md (100%) rename connections/warehouses/{catalog.md => catalog/index.md} (100%) diff --git a/connections/destinations/catalog/aboardly/index.md b/connections/destinations/catalog/aboardly/index.md index 71b2d913b3e..38311b916f7 100644 --- a/connections/destinations/catalog/aboardly/index.md +++ b/connections/destinations/catalog/aboardly/index.md @@ -18,3 +18,6 @@ When you `identify` a user, we'll pass that user's information to Aboardly with ## Track When you `track` an event, we will send that event to Aboardly as a custom event. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/adtriba/index.md b/connections/destinations/catalog/adtriba/index.md index 42bab03b1a3..77ebb86e6eb 100644 --- a/connections/destinations/catalog/adtriba/index.md +++ b/connections/destinations/catalog/adtriba/index.md @@ -56,3 +56,5 @@ analytics.track('Conversion', { Track calls will be sent to Adtriba as a `track` event. Trigger additional events by using [Semantic Events](https://segment.com/docs/spec/semantic/) in order to enrich the Adtriba machine learning process. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/adwords-remarketing-lists/index.md b/connections/destinations/catalog/adwords-remarketing-lists/index.md index 3b53365361d..03656a5c3eb 100644 --- a/connections/destinations/catalog/adwords-remarketing-lists/index.md +++ b/connections/destinations/catalog/adwords-remarketing-lists/index.md @@ -54,3 +54,5 @@ We attempt to match users in your audience with the identifiers that Google supp ### What Adwords platforms are supported? This destination supports Search, Gmail, and Youtube ad campaigns. Adwords does not support Display campaigns through remarketing lists. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/adwords/index.md b/connections/destinations/catalog/adwords/index.md index 096c89062bc..98de902f04c 100644 --- a/connections/destinations/catalog/adwords/index.md +++ b/connections/destinations/catalog/adwords/index.md @@ -216,3 +216,6 @@ The following properties are optional, if you'd like to see more, please get in Here's Google documentation for the endpoint we hit [for iOS apps](https://developers.google.com/app-conversion-tracking/ios/conversion-tracking-server#reporting_in-app_conversions_from_an_analytics_server) and [for Android Apps](https://developers.google.com/app-conversion-tracking/android/conversion-tracking-server#in-app_conversions). It can take 24-48 hours for conversions to show up in the conversions dashboard. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/akita/index.md b/connections/destinations/catalog/akita/index.md index dfe31171354..1b8a837e525 100644 --- a/connections/destinations/catalog/akita/index.md +++ b/connections/destinations/catalog/akita/index.md @@ -50,3 +50,6 @@ When you call `page`, Segment will send that event to Akita as a `Page View`. ## Track When you call `track`, Segment will send that event to Akita as an `Event`. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/all-aboard/index.md b/connections/destinations/catalog/all-aboard/index.md index 90380392809..b3e990e89f9 100644 --- a/connections/destinations/catalog/all-aboard/index.md +++ b/connections/destinations/catalog/all-aboard/index.md @@ -40,3 +40,5 @@ Segment allows you to expose what your users do in your application. This inform For instance, using our simple example above perhaps you only want to invite customers who completed the registration process to an onboarding call. The `finished_registration: TRUE` trait allows you to quickly identify these customers. Traits are also useful in helping you have a more personal dialog with your trial customers. More personal call invitations encourage your most qualified customers to schedule a call with you. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/appcues/index.md b/connections/destinations/catalog/appcues/index.md index 30853930e33..cc6104bbf85 100644 --- a/connections/destinations/catalog/appcues/index.md +++ b/connections/destinations/catalog/appcues/index.md @@ -117,3 +117,5 @@ lifecycle events that can be tracked: To enable this feature, go to the Integrations Settings in Appcues and click “Activate” under the Segment integration. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/apteligent/index.md b/connections/destinations/catalog/apteligent/index.md index 382b4666301..339e8ca159d 100644 --- a/connections/destinations/catalog/apteligent/index.md +++ b/connections/destinations/catalog/apteligent/index.md @@ -23,3 +23,5 @@ Apteligent can show you information about the user using your app. You can recor When an error occurs, you'll want to know what user actions led to the crash. Apteligent allows you to leave "breadcrumbs" for this purpose. Whenever you call [`track`](/docs/spec/track/), we'll leave a breadcrumb in Apteligent. `Track` takes the name of the event and any optional `properties` you want to associate with the event. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/batch/index.md b/connections/destinations/catalog/batch/index.md index 8504a0f19e2..98e077c0ce4 100644 --- a/connections/destinations/catalog/batch/index.md +++ b/connections/destinations/catalog/batch/index.md @@ -97,3 +97,5 @@ All of our supported Segment integration features will work automatically, with Batch's other features are available directly by using the native SDK, which comes bundled with this integration. To leverage the native SDK through Segment, follow the instructions outlined [here for Android](https://segment.com/docs/sources/mobile/android/#how-can-i-use-an-destination-specific-feature-e-g-mixpanel-s-push-notifications-) and [here for iOS](https://segment.com/docs/sources/mobile/ios/#what-if-your-sdk-doesn-t-support-feature-x-). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/boomtrain/index.md b/connections/destinations/catalog/boomtrain/index.md index 45ca7eda41d..7f5e2ecb6da 100644 --- a/connections/destinations/catalog/boomtrain/index.md +++ b/connections/destinations/catalog/boomtrain/index.md @@ -38,3 +38,5 @@ The App ID for your app can be taken from the destination guide provided by Boom If you have any questions, or suggestions on we can improve this documentation, feel free to [contact us](http://boomtrain.com/contact/). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/branch-metrics/index.md b/connections/destinations/catalog/branch-metrics/index.md index 93a2e99a42d..b979c0f9146 100644 --- a/connections/destinations/catalog/branch-metrics/index.md +++ b/connections/destinations/catalog/branch-metrics/index.md @@ -837,3 +837,6 @@ LinkProperties linkProperties = new LinkProperties() You can also control it for individual marketing links by inserting the keys and values into the deep link data section. ![image alt text](images/image_0.png) + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/bronto/index.md b/connections/destinations/catalog/bronto/index.md index 2aa03ad69b5..6a8a11a3bd2 100644 --- a/connections/destinations/catalog/bronto/index.md +++ b/connections/destinations/catalog/bronto/index.md @@ -21,3 +21,4 @@ analytics.track('Order Completed', { orderId: '55c497bf' }); ``` +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/bugsnag/index.md b/connections/destinations/catalog/bugsnag/index.md index 0c5e595f996..614c31726d0 100644 --- a/connections/destinations/catalog/bugsnag/index.md +++ b/connections/destinations/catalog/bugsnag/index.md @@ -53,3 +53,5 @@ Bugsnag will show you the `userId` and `traits` in the Users tab of each error. ## Error Reporting In addition to sending Bugsnag user-specific information, you can send handled exceptions and diagnostic data to your Bugsnag dashboard using Bugsnag's native methods. Documentation on these methods is available [on their website](https://docs.bugsnag.com/platforms/browsers/#reporting-handled-exceptions). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/callexa/index.md b/connections/destinations/catalog/callexa/index.md index c9f250a8520..d87dfcfac1f 100644 --- a/connections/destinations/catalog/callexa/index.md +++ b/connections/destinations/catalog/callexa/index.md @@ -54,3 +54,5 @@ __If you have any questions feel free to contact Callexa at:__ [info@callexa.com --- _Net Promoter, Net Promoter Score, and NPS are trademarks of Satmetrix Systems, Inc., Bain & Company, Inc., and Fred Reichheld. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/castle/index.md b/connections/destinations/catalog/castle/index.md index 307af2ba7e0..f773acb3a8a 100644 --- a/connections/destinations/catalog/castle/index.md +++ b/connections/destinations/catalog/castle/index.md @@ -1,5 +1,5 @@ --- -title: Castle +title: Castle --- # Integrating through Segment @@ -197,3 +197,5 @@ end Castle's adaptive authentication tells you whether to allow access, initiate a second factor of authentication, or log out the user. Since all Segment calls are called asynchronously, you will need to use Castle's native SDKs to perform [adaptive authentication](https://castle.io/docs/authentication). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/chameleon/index.md b/connections/destinations/catalog/chameleon/index.md index 723603f8a07..4a7fffa46fe 100644 --- a/connections/destinations/catalog/chameleon/index.md +++ b/connections/destinations/catalog/chameleon/index.md @@ -40,3 +40,5 @@ Product tours should lead to user actions and so offer the option of tagging eac ## Help For more information, please refer to [Chameleon's docs](https://docs.trychameleon.com) or [email them](mailto:support@trychameleon.com). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/chartbeat/index.md b/connections/destinations/catalog/chartbeat/index.md index 25ea29e5400..44e068cae3c 100644 --- a/connections/destinations/catalog/chartbeat/index.md +++ b/connections/destinations/catalog/chartbeat/index.md @@ -21,3 +21,5 @@ Chartbeat is only supported on the client-side. The [`page`](/docs/spec/page/) method in Analytics.js will call Chartbeat’s `virtualPage` function with either the Url you provide or the current window’s pathname. Use the [`page`](/docs/spec/page/) method if you have a one-page app that doesn’t reload the browser page between views. You can also set a section and author for each page. For example, `analytics.page('putSectionHere', 'putNameOfPageHere', { author: 'putAuthorNameHere' }`. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/clevertap/index.md b/connections/destinations/catalog/clevertap/index.md index 36e3881608e..0dda87127ff 100644 --- a/connections/destinations/catalog/clevertap/index.md +++ b/connections/destinations/catalog/clevertap/index.md @@ -150,3 +150,5 @@ CleverTap has created a sample iOS application that integrates CleverTap via Seg If you chose not to bundle the CleverTap Mobile SDK, then you will have to implement your own Push Message processors (and you won’t have access to CleverTap’s In-App feature). If you decide to implement your own Push Message processors, then you can pass push tokens to CleverTap via the server-side destination. You can do this by sending it inside context.device.token. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/clientsuccess/index.md b/connections/destinations/catalog/clientsuccess/index.md index 1bdc61003ad..01c48b74da6 100644 --- a/connections/destinations/catalog/clientsuccess/index.md +++ b/connections/destinations/catalog/clientsuccess/index.md @@ -1,5 +1,5 @@ --- -title: ClientSuccess +title: ClientSuccess --- This destination is maintained by ClientSuccess. @@ -44,3 +44,5 @@ When you track a `page` event, Segment will send that event to ClientSuccess as ## Group When you call `group`, Segment will send that group's information to ClientSuccess with `groupId` as the id and `name` as the group name. Both `groupId` and `name` are required for ClientSuccess. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/comscore/index.md b/connections/destinations/catalog/comscore/index.md index 35ddbc572ba..c7b9db4443c 100644 --- a/connections/destinations/catalog/comscore/index.md +++ b/connections/destinations/catalog/comscore/index.md @@ -278,3 +278,5 @@ The comScore SDK will collect unique device id's under the hood, so based on thi ### How does comScore determine the application name? Used in the classification from comScore’s Audience reporting, comScore retrieves the application name from your app’s Info.plist application bundle name as returned by `CFBundleName`. If you want to override the automatically retrieved value, you can provide a string with your preferred app name. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/convertro/index.md b/connections/destinations/catalog/convertro/index.md index 9d4cb8f3be2..4399fa21128 100644 --- a/connections/destinations/catalog/convertro/index.md +++ b/connections/destinations/catalog/convertro/index.md @@ -60,3 +60,6 @@ When you call `.track()`, we will send that event to Convertro by setting the `e ## Application Installed We will send this automatically collected [`Application Installed` event](/docs/spec/mobile/) to Convertro's `Installs` endpoint. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/cordialio/index.md b/connections/destinations/catalog/cordialio/index.md index 7c2d6b0e86d..26b5046600c 100644 --- a/connections/destinations/catalog/cordialio/index.md +++ b/connections/destinations/catalog/cordialio/index.md @@ -80,3 +80,5 @@ Update your Cordial/Segment field mapping using the same JSON format as in the P ### GET https://admin.cordial.io/api/integrations Retrieve a JSON list of integrations you have set up with Cordial. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/countly/index.md b/connections/destinations/catalog/countly/index.md index 67dbc93e7ed..c19bd4f44d7 100644 --- a/connections/destinations/catalog/countly/index.md +++ b/connections/destinations/catalog/countly/index.md @@ -29,3 +29,5 @@ All you have to do is make a [`track`](/docs/spec/track/) call to send a custom ### Revenue It's easy to track revenue in Countly through Segment. All you have to do is use our [`track`](/docs/spec/track/) method with a property labeled `revenue`. The value must be a number. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/criteo/index.md b/connections/destinations/catalog/criteo/index.md index 81fd805c175..7e999e75993 100644 --- a/connections/destinations/catalog/criteo/index.md +++ b/connections/destinations/catalog/criteo/index.md @@ -299,3 +299,5 @@ Criteo can receive dates in a specific format, in order for us to pass along dat ### Is the mobile integration bundled? Even though we don't support integrating with Criteo via Segment from a server source, it's still not necessary for you to [bundle](https://segment.com/docs/guides/sources/bundled-SDK-vs-server/) the Criteo SDK into the Segment SDK! This is because while our mobile integration with them is powered from our servers, the integration requires metadata that can only be supplied by the user's mobile device (which is collected and passed along automatically by the Segment mobile SDK). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/cubitic/index.md b/connections/destinations/catalog/cubitic/index.md index d0b6266857a..a7459c114b8 100644 --- a/connections/destinations/catalog/cubitic/index.md +++ b/connections/destinations/catalog/cubitic/index.md @@ -57,3 +57,5 @@ This event must contain a revenue property that specifies the amount spent using "version": "1.1" } ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/curebit/index.md b/connections/destinations/catalog/curebit/index.md index dd4e10502ad..293c57e21db 100644 --- a/connections/destinations/catalog/curebit/index.md +++ b/connections/destinations/catalog/curebit/index.md @@ -7,3 +7,5 @@ Our Talkable destination code is open-source on GitHub if you want to [check it ## Getting Started All you need to turn on our Talkable destination is your Talkable Site ID. If you're not sure where to look see [this Help Page](https://curebit.helpjuice.com/questions/45313-Where-do-I-find-my-site-ID) from Talkable. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/cxense/index.md b/connections/destinations/catalog/cxense/index.md index c669bd30966..c95dc3bfd7b 100644 --- a/connections/destinations/catalog/cxense/index.md +++ b/connections/destinations/catalog/cxense/index.md @@ -92,3 +92,5 @@ window.cX.callQueue.push(['sendEvent', 'Shared Article', { title: 'How to View a Solar Eclipse Without Damaging Your Eyes' }]) ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/amazon-s3/images/bucket-property.png b/connections/warehouses/catalog/amazon-s3/images/bucket-property.png similarity index 100% rename from connections/destinations/catalog/amazon-s3/images/bucket-property.png rename to connections/warehouses/catalog/amazon-s3/images/bucket-property.png diff --git a/connections/destinations/catalog/amazon-s3/images/customer-managed-key.png b/connections/warehouses/catalog/amazon-s3/images/customer-managed-key.png similarity index 100% rename from connections/destinations/catalog/amazon-s3/images/customer-managed-key.png rename to connections/warehouses/catalog/amazon-s3/images/customer-managed-key.png diff --git a/connections/destinations/catalog/amazon-s3/images/disable-segment-sse.png b/connections/warehouses/catalog/amazon-s3/images/disable-segment-sse.png similarity index 100% rename from connections/destinations/catalog/amazon-s3/images/disable-segment-sse.png rename to connections/warehouses/catalog/amazon-s3/images/disable-segment-sse.png diff --git a/connections/destinations/catalog/amazon-s3/index.md b/connections/warehouses/catalog/amazon-s3/index.md similarity index 100% rename from connections/destinations/catalog/amazon-s3/index.md rename to connections/warehouses/catalog/amazon-s3/index.md diff --git a/connections/warehouses/catalog.md b/connections/warehouses/catalog/index.md similarity index 100% rename from connections/warehouses/catalog.md rename to connections/warehouses/catalog/index.md diff --git a/todo.txt b/todo.txt index f25003560df..1f63932fa8f 100644 --- a/todo.txt +++ b/todo.txt @@ -1,2 +1,112 @@ - redirects -- add integration-foot to anything that didn't have rewrite: true +- add {% include content/integration-foot.md %} to anything that didn't have rewrite: true + + +doubleclick-floodlight +drip +eloqua +errorception +extole +facebook-pixel-server-side +firebase +framed.io +freshdesk +freshsales +friendbuy +frontleaf +gauges +google-adwords-new +google-analytics +google-cloud-pubsub +google-cloud-storage +gosquared +hindsight +hittail +hull +impact-radius +infinario +insidevault +intellimize +iron.io +iterable +kahuna +keen-io +kenshoo-infinity +knowtify +leadboxer +librato +linkedin-conversion-tag +linkedin-insight-tag +livechat +localytics +lytics +madkudu +mailjet +marketo +marketo-v2 +millennial-media +moengage +monetate +moosend +nanigans +nielsen-dcr +nudgespot +olark +omniture +onesignal +optimizely-full-stack +optimizely-web +outbound +pardot +perimeterx +personas-facebook-ads +pingdom +pinterest-tag +piwik +planhat +pointillist +postgres +preact +primer +promoter.io +quantcast +ramen +relay +repeater +responsys +rollbar +route +saasquatch +sailthru +salesforce +salesforce-live-agent +salesforce-marketing-cloud +salesmachine +satismeter +seg +selligent +sendwithus +shareasale +smyte +sparkpage +stripe-radar +swrve +tableau +taplytics +tealium-audience-stream +totango +track-js +tractionboard +tray.io +treasure-data +twitter-ads +urban-airship +userengage +vero +watsi +webengage +whale-alerts +wishpond +woopra +youbora +zaius From d854e3d0e36c7f6d2be6f78ee78b1573ea5fe134 Mon Sep 17 00:00:00 2001 From: sanscontext Date: Tue, 13 Aug 2019 11:49:42 -0700 Subject: [PATCH 2/6] more footers, move warehouse docs to correct folder Signed-off-by: sanscontext --- .../catalog/doubleclick-floodlight/index.md | 4 +- .../destinations/catalog/drip/index.md | 2 + .../destinations/catalog/eloqua/index.md | 3 ++ .../catalog/errorception/index.md | 2 + .../destinations/catalog/extole/index.md | 2 + .../destinations/catalog/firebase/index.md | 2 + .../destinations/catalog/framed.io/index.md | 2 + .../destinations/catalog/freshdesk/index.md | 3 ++ .../destinations/catalog/freshsales/index.md | 2 + .../destinations/catalog/friendbuy/index.md | 4 +- .../destinations/catalog/frontleaf/index.md | 2 + .../destinations/catalog/gauges/index.md | 3 ++ .../catalog/google-adwords-new/index.md | 4 +- .../catalog/google-analytics/index.md | 2 + .../catalog/google-cloud-pubsub/index.md | 2 + .../destinations/catalog/gosquared/index.md | 4 +- .../destinations/catalog/hindsight/index.md | 2 + .../destinations/catalog/hittail/index.md | 3 ++ .../destinations/catalog/hull/index.md | 3 ++ .../catalog/impact-radius/index.md | 3 ++ .../destinations/catalog/infinario/index.md | 2 + .../destinations/catalog/insidevault/index.md | 2 + .../destinations/catalog/intellimize/index.md | 2 + .../destinations/catalog/iron.io/index.md | 2 + .../destinations/catalog/iterable/index.md | 2 + .../destinations/catalog/kahuna/index.md | 2 + .../destinations/catalog/keen-io/index.md | 2 + .../catalog/kenshoo-infinity/index.md | 3 ++ .../destinations/catalog/knowtify/index.md | 3 ++ .../destinations/catalog/leadboxer/index.md | 2 + .../destinations/catalog/librato/index.md | 3 ++ .../catalog/linkedin-conversion-tag/index.md | 3 ++ .../catalog/linkedin-insight-tag/index.md | 3 ++ .../destinations/catalog/livechat/index.md | 2 + .../destinations/catalog/localytics/index.md | 2 + .../destinations/catalog/lytics/index.md | 3 ++ .../destinations/catalog/madkudu/index.md | 2 + .../destinations/catalog/mailjet/index.md | 2 + .../destinations/catalog/marketo-v2/index.md | 2 + .../destinations/catalog/marketo/index.md | 2 + .../catalog/millennial-media/index.md | 2 + .../destinations/catalog/moengage/index.md | 2 + .../destinations/catalog/monetate/index.md | 2 + .../destinations/catalog/moosend/index.md | 2 + .../catalog/azuresqldw/index.md | 0 .../catalog/bigquery/index.md | 0 .../catalog/db2/images/add_destination.png | Bin .../catalog/db2/images/add_user.png | Bin .../catalog/db2/images/db2_menu.png | Bin .../catalog/db2/images/grant.png | Bin .../catalog/db2/images/manage_users.png | Bin .../catalog/db2/images/run_sql.png | Bin .../catalog/db2/images/search_results.png | Bin .../catalog/db2/images/settings.png | Bin .../catalog/db2/index.md | 0 .../catalog/postgres/images/compose1.png | Bin .../catalog/postgres/images/heroku1.png | Bin .../catalog/postgres/images/heroku2.png | Bin .../catalog/postgres/images/heroku3.png | Bin .../catalog/postgres/images/heroku4.png | Bin .../catalog/postgres/images/heroku5.png | Bin .../catalog/postgres/images/heroku6.png | Bin .../catalog/postgres/images/rds1.png | Bin .../catalog/postgres/images/rds10.png | Bin .../catalog/postgres/images/rds11.png | Bin .../catalog/postgres/images/rds12.png | Bin .../catalog/postgres/images/rds13.png | Bin .../catalog/postgres/images/rds2.png | Bin .../catalog/postgres/images/rds3.png | Bin .../catalog/postgres/images/rds4.png | Bin .../catalog/postgres/images/rds5.png | Bin .../catalog/postgres/images/rds6.png | Bin .../catalog/postgres/images/rds7.png | Bin .../catalog/postgres/images/rds8.png | Bin .../catalog/postgres/images/rds9.png | Bin .../catalog/postgres/images/segment1.png | Bin .../catalog/postgres/images/segment2.png | Bin .../catalog/postgres/images/segment3.png | Bin .../catalog/postgres/images/segment4.png | Bin .../catalog/postgres/images/segment5.png | Bin .../catalog/postgres/index.md | 0 .../catalog/redshift/index.md | 0 .../catalog/snowflake/images/auto_suspend.png | Bin .../snowflake/images/connect_snowflake.png | Bin .../snowflake/images/create_database.png | Bin .../snowflake/images/create_user_1.png | Bin .../snowflake/images/create_user_2.png | Bin .../snowflake/images/create_user_3.png | Bin .../images/create_virtual_warehouse.png | Bin .../catalog/snowflake/index.md | 0 todo.txt | 47 +----------------- 91 files changed, 105 insertions(+), 50 deletions(-) rename connections/{destinations => warehouses}/catalog/azuresqldw/index.md (100%) rename connections/{destinations => warehouses}/catalog/bigquery/index.md (100%) rename connections/{destinations => warehouses}/catalog/db2/images/add_destination.png (100%) rename connections/{destinations => warehouses}/catalog/db2/images/add_user.png (100%) rename connections/{destinations => warehouses}/catalog/db2/images/db2_menu.png (100%) rename connections/{destinations => warehouses}/catalog/db2/images/grant.png (100%) rename connections/{destinations => warehouses}/catalog/db2/images/manage_users.png (100%) rename connections/{destinations => warehouses}/catalog/db2/images/run_sql.png (100%) rename connections/{destinations => warehouses}/catalog/db2/images/search_results.png (100%) rename connections/{destinations => warehouses}/catalog/db2/images/settings.png (100%) rename connections/{destinations => warehouses}/catalog/db2/index.md (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/compose1.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/heroku1.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/heroku2.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/heroku3.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/heroku4.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/heroku5.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/heroku6.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds1.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds10.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds11.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds12.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds13.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds2.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds3.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds4.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds5.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds6.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds7.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds8.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/rds9.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/segment1.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/segment2.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/segment3.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/segment4.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/images/segment5.png (100%) rename connections/{destinations => warehouses}/catalog/postgres/index.md (100%) rename connections/{destinations => warehouses}/catalog/redshift/index.md (100%) rename connections/{destinations => warehouses}/catalog/snowflake/images/auto_suspend.png (100%) rename connections/{destinations => warehouses}/catalog/snowflake/images/connect_snowflake.png (100%) rename connections/{destinations => warehouses}/catalog/snowflake/images/create_database.png (100%) rename connections/{destinations => warehouses}/catalog/snowflake/images/create_user_1.png (100%) rename connections/{destinations => warehouses}/catalog/snowflake/images/create_user_2.png (100%) rename connections/{destinations => warehouses}/catalog/snowflake/images/create_user_3.png (100%) rename connections/{destinations => warehouses}/catalog/snowflake/images/create_virtual_warehouse.png (100%) rename connections/{destinations => warehouses}/catalog/snowflake/index.md (100%) diff --git a/connections/destinations/catalog/doubleclick-floodlight/index.md b/connections/destinations/catalog/doubleclick-floodlight/index.md index a9a4a3b2705..8ad6525efd4 100644 --- a/connections/destinations/catalog/doubleclick-floodlight/index.md +++ b/connections/destinations/catalog/doubleclick-floodlight/index.md @@ -1,7 +1,7 @@ --- title: DoubleClick Floodlight --- - + ## Getting Started The DoubleClick Floodlight destination allows you to make calls directly to Floodlight based on your mapped events. All you have to do is drop in your **DoubleClick Advertiser ID** into your settings and map the Segment `track` events to their corresponding Floodlight tags. @@ -114,3 +114,5 @@ Analytics.with(context).track("Free El", new Properties().putValue("show", "Stra Please refrain from mapping custom variables that are PII. Please refer to the [warning](https://support.google.com/dfa/partner/answer/2548879?hl=en) by DoubleClick: The terms of your DoubleClick contract prohibit passing any information to us that we could use or recognize as personally identifiable information (PII). If you enter certain key-values into a field in a DoubleClick product, you may see a warning that reminds you that you must not use key-values to pass data that we would recognize as PII. Key-values that trigger this warning include, for example, email and username. Note that it is okay to use these key-values if your purpose is not to collect information that DoubleClick could use or recognize as PII. (For example, email=weekly is fine, but passing a user’s email address is not.) If you do choose one of these key-values, DoubleClick may contact you in the future to confirm that you are not using them in a way that is prohibited. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/drip/index.md b/connections/destinations/catalog/drip/index.md index 717122491f9..c6bbd3bfa5d 100644 --- a/connections/destinations/catalog/drip/index.md +++ b/connections/destinations/catalog/drip/index.md @@ -26,3 +26,5 @@ When you call [`track`](/docs/spec/track/), we'll send the event to Drip with th ## Sending Data from Drip Drip supports sending [email events](/docs/spec/email/) to other tools on the Segment platform. These events will be sent as `track` calls to the other destinations you've turned on. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/eloqua/index.md b/connections/destinations/catalog/eloqua/index.md index 0f9eb392641..58974a36325 100644 --- a/connections/destinations/catalog/eloqua/index.md +++ b/connections/destinations/catalog/eloqua/index.md @@ -213,6 +213,9 @@ analytics.track({ traits: { name: "Segment.com", groupId: "1234567" + } } }) ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/errorception/index.md b/connections/destinations/catalog/errorception/index.md index eef613f05c0..9b0bb643c52 100644 --- a/connections/destinations/catalog/errorception/index.md +++ b/connections/destinations/catalog/errorception/index.md @@ -15,3 +15,5 @@ Errorception is only supported on the client-side. ## Identify This is only active if you set the `meta` setting to be true. When you call [`identify`](/docs/spec/identify/) we set Errorception's `_errs.meta` to be the `traits` you passed in. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/extole/index.md b/connections/destinations/catalog/extole/index.md index 215357959b2..a4f17ab7116 100644 --- a/connections/destinations/catalog/extole/index.md +++ b/connections/destinations/catalog/extole/index.md @@ -22,3 +22,5 @@ When you call `identify`, we keep track of the current user and will include ide Segment supports Extole events in our client-side library through the `track` method. **Note:** Remember, because Extole tracks custom user data, be sure to call [`identify`](#identify) before attempting to call [`track`](#track). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/firebase/index.md b/connections/destinations/catalog/firebase/index.md index eb988c0bc8b..d218d69f31c 100644 --- a/connections/destinations/catalog/firebase/index.md +++ b/connections/destinations/catalog/firebase/index.md @@ -234,3 +234,5 @@ As a current user of Segment-Firebase iOS, you will be able to pull in the lates For details on the new mapping, you can check out our documentation [here](https://segment.com/docs/destinations/firebase/#event-mappings). Please let us know if you have any questions. We recommend upgrading as soon as possible, and please [let us know](/contact) if you have any feedback about both the Firebase iOS and Android betas. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/framed.io/index.md b/connections/destinations/catalog/framed.io/index.md index c353abb2d52..4468c132276 100644 --- a/connections/destinations/catalog/framed.io/index.md +++ b/connections/destinations/catalog/framed.io/index.md @@ -30,3 +30,5 @@ When you `track` an event, we will send that event to Framed as a user event. Ev - `userID` (`userID`) - `event_name` (`event_name`) - Any properties of the event will be passed onto Framed as custom properties of the event itself. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/freshdesk/index.md b/connections/destinations/catalog/freshdesk/index.md index 1367530906c..d728d31d801 100644 --- a/connections/destinations/catalog/freshdesk/index.md +++ b/connections/destinations/catalog/freshdesk/index.md @@ -51,3 +51,6 @@ Here’s an example: "locale": "en-US" } }' {% endcomment %} + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/freshsales/index.md b/connections/destinations/catalog/freshsales/index.md index d35c73c200f..5e7fa157c51 100644 --- a/connections/destinations/catalog/freshsales/index.md +++ b/connections/destinations/catalog/freshsales/index.md @@ -137,3 +137,5 @@ When you call a `page` event, we send a pageview to Freshsales. You can send ext ### Custom Fields Aren’t Updating Make sure that the traits you’re passing through match the custom field’s internal name and data type. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/friendbuy/index.md b/connections/destinations/catalog/friendbuy/index.md index 8f1504f7ccc..d9c76f367a5 100644 --- a/connections/destinations/catalog/friendbuy/index.md +++ b/connections/destinations/catalog/friendbuy/index.md @@ -3,7 +3,7 @@ title: Friendbuy --- ## Getting Started - + Setting up Friendbuy is very simple! Just login to your Friendbuy account, go to **Integration Code** > and copy the **Site ID** above the snippet box. Then paste it into your Friendbuy Destiation setting back in the Segment UI as seen in the gif below: ![](https://i.gyazo.com/f02339b0c4d567e1413c6f3891062c98.gif) @@ -107,3 +107,5 @@ Then we will iterate over each item in your `properties.products` and send the f } } ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/frontleaf/index.md b/connections/destinations/catalog/frontleaf/index.md index 73045c6141f..3c2c3d7097e 100644 --- a/connections/destinations/catalog/frontleaf/index.md +++ b/connections/destinations/catalog/frontleaf/index.md @@ -29,3 +29,5 @@ analytics.page('Lesson'); ``` * A custom URL filter (configured for you by Frontleaf) that interprets part of the page path (and/or query parameters) as the interaction type. This option can work well for "object-verb" types of URL schemes, e.g. `/lesson/123/view` and `/lesson/456/view` both get labeled as a `/lesson/view` action (which you can then relabel in the UI). [Contact Frontleaf support](https://www.frontleaf.com/contact/) for assistance with this option. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/gauges/index.md b/connections/destinations/catalog/gauges/index.md index 80d62695d1f..f2185ec3f82 100644 --- a/connections/destinations/catalog/gauges/index.md +++ b/connections/destinations/catalog/gauges/index.md @@ -24,3 +24,6 @@ When you call [`page`](/docs/spec/page/), we call Gauges' `track` method with no ### My visits aren't showing up in Gauges Gauges doesn’t record data from any browser where you’ve signed into Gauges. That way your data doesn’t get polluted by your own actions. If you want your browsing to show up in Gauges - open an incognito/private window in your browser. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/google-adwords-new/index.md b/connections/destinations/catalog/google-adwords-new/index.md index 0a701833a2c..aac76961771 100644 --- a/connections/destinations/catalog/google-adwords-new/index.md +++ b/connections/destinations/catalog/google-adwords-new/index.md @@ -1,5 +1,5 @@ --- -title: Google Adwords New Experience +title: Google Adwords New Experience --- @@ -46,3 +46,5 @@ The only exception is that for `Order Completed` events, we will map Google's se ## Multiple AdWords Account If you are an enterprise that uses multiple AdWords accounts (usually managed by various third party agencies) you can override the top level default Google Conversion ID at the event level by entering it into the settings. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/google-analytics/index.md b/connections/destinations/catalog/google-analytics/index.md index 86278b0ba71..ca3b84c44be 100644 --- a/connections/destinations/catalog/google-analytics/index.md +++ b/connections/destinations/catalog/google-analytics/index.md @@ -903,3 +903,5 @@ Analytics.track( Google Analytics requires the `context.app.name` passed in each call. Since the `analytics-ios` SDK pulls it in [locally](https://developer.apple.com/library/ios/documentation/General/Reference/InfoPlistKeyReference/Articles/CoreFoundationKeys.html#//apple_ref/doc/uid/20001431-110725), you may see the error "`context.app.name` required" if you are not providing a `CFBundleDisplayName` within your **Info.plist** file. To resolve this error, ensure you [provide a localized info dictionary](https://github.com/segmentio/analytics-ios/blob/760be85a5119c2e8bd31a745ce2ec30385a0ad69/Pod/Classes/Internal/SEGSegmentIntegration.m#L110) as outlined [here](https://developer.apple.com/library/ios/qa/qa1823/_index.html). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/google-cloud-pubsub/index.md b/connections/destinations/catalog/google-cloud-pubsub/index.md index a0ace2da78a..927905da057 100644 --- a/connections/destinations/catalog/google-cloud-pubsub/index.md +++ b/connections/destinations/catalog/google-cloud-pubsub/index.md @@ -45,3 +45,5 @@ The structure of a Pub/Sub message follows this structure: [PubsubMessage](https Our integration will publish the entire Segment event payload as a Base64 encoded string and set it as the value of the `data` parameter in the Pub/Sub message payload. We will set the `publishTime` to be the `timestamp` of the Segment event. We do not currently integrate with the optional `attributes` parameter. If you use this functionality, please [contact us](https://segment.com/help/contact). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/gosquared/index.md b/connections/destinations/catalog/gosquared/index.md index 45c32eebf6d..76d2745b457 100644 --- a/connections/destinations/catalog/gosquared/index.md +++ b/connections/destinations/catalog/gosquared/index.md @@ -1,5 +1,5 @@ --- -title: GoSquared +title: GoSquared --- ## Getting Started @@ -62,3 +62,5 @@ GoSquared converts the [`group`](/docs/spec/group/) method into an identify call ## Ecommerce GoSquared supports our [Ecommerce tracking API](/docs/spec/ecommerce/v2/#order-completed), so the `Order Completed` event will be tracked as a [GoSquared Transaction](https://www.gosquared.com/docs/tracking/api/js#transactions). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/hindsight/index.md b/connections/destinations/catalog/hindsight/index.md index 1e9e04a0493..edaad2a08c1 100644 --- a/connections/destinations/catalog/hindsight/index.md +++ b/connections/destinations/catalog/hindsight/index.md @@ -14,3 +14,5 @@ When you trigger a `.page()` call, we will fire `window.RB.track('view')` and pa ## Track Rockerbox can accept any custom `.track()` events and properties. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/hittail/index.md b/connections/destinations/catalog/hittail/index.md index 9aad083fb96..7141cd38de9 100644 --- a/connections/destinations/catalog/hittail/index.md +++ b/connections/destinations/catalog/hittail/index.md @@ -10,3 +10,6 @@ When you toggle on HitTail in Segment, this is what happens: + HitTail will automatically start recording search keywords and showing them on its dashboard. HitTail does not track any other forms of data, so none of the rest of our API is supported. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/hull/index.md b/connections/destinations/catalog/hull/index.md index 1c8ac346d38..0b4e5ed32ba 100644 --- a/connections/destinations/catalog/hull/index.md +++ b/connections/destinations/catalog/hull/index.md @@ -114,3 +114,6 @@ will add the following traits on all users that belong to the group : Internally, we flatten objects and use '/' as a separator. They're really stored as `traits_group/name`. Our sources handle nesting for you when you receive data coming from Hull __Note: This feature is optional and not enabled by default. You should only enable it if your users can only belong to one group.__ + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/impact-radius/index.md b/connections/destinations/catalog/impact-radius/index.md index fc620bbc7e5..8da72e019ed 100644 --- a/connections/destinations/catalog/impact-radius/index.md +++ b/connections/destinations/catalog/impact-radius/index.md @@ -328,3 +328,6 @@ We integrate with Impact mobile attribution capabilities via our [Deep Link Open googleaid + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/infinario/index.md b/connections/destinations/catalog/infinario/index.md index ef9e5cbf88b..7ccefcffd76 100644 --- a/connections/destinations/catalog/infinario/index.md +++ b/connections/destinations/catalog/infinario/index.md @@ -45,3 +45,5 @@ This call is currently only supported partially. Whenever a user is assigned to - - - Please consult the [Infinario guides](http://guides.infinario.com/) to see what can you do with the data you tracked. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/insidevault/index.md b/connections/destinations/catalog/insidevault/index.md index 1058242bc38..f0aea1f1a5e 100644 --- a/connections/destinations/catalog/insidevault/index.md +++ b/connections/destinations/catalog/insidevault/index.md @@ -28,3 +28,5 @@ analytics.enqueue(TrackMessage.builder("Purchased Item") ) ); ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/intellimize/index.md b/connections/destinations/catalog/intellimize/index.md index a25f786505f..97ed3e6ec60 100644 --- a/connections/destinations/catalog/intellimize/index.md +++ b/connections/destinations/catalog/intellimize/index.md @@ -24,3 +24,5 @@ When you call any of these events, Segment will relay the events to Intellimize' ## Settings You will need to enter your API key in the Destination Settings page for Intellimize. To retrieve your API key, reach out to your account representative at Intellimize or to segment@intellimize.com. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/iron.io/index.md b/connections/destinations/catalog/iron.io/index.md index a9cabff2bac..3cca7546afe 100644 --- a/connections/destinations/catalog/iron.io/index.md +++ b/connections/destinations/catalog/iron.io/index.md @@ -8,3 +8,5 @@ When you toggle on Iron.io in Segment, we'll start sending data to an IronMQ ins When sending data to Iron.io, we'll auto-fill a queue called "segment". You can use Iron.io as a message queue buffer in front of your webhook server or internal data processing cluster. For example, if you want to analyze your data as part of an ETL process, Iron.io can act as an intermediary buffer. Here's a case study: [How to Build an ETL Pipeline for ElasticSearch Using Segment and Iron.io (Iron.io's blog)](http://blog.iron.io/2014/10/how-to-build-etl-pipeline-for.html?utm_source=segment&medium=docs) + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/iterable/index.md b/connections/destinations/catalog/iterable/index.md index 72386e9f324..ce4f905b3ea 100644 --- a/connections/destinations/catalog/iterable/index.md +++ b/connections/destinations/catalog/iterable/index.md @@ -100,3 +100,5 @@ Iterable supports sending push notification events to Segment. These events will They support the following events: `Push Delivered`, `Push Bounced`, `Mobile App Uninstalled`, `Push Opened` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/kahuna/index.md b/connections/destinations/catalog/kahuna/index.md index 828efdb436e..46217bd8fe1 100644 --- a/connections/destinations/catalog/kahuna/index.md +++ b/connections/destinations/catalog/kahuna/index.md @@ -139,3 +139,5 @@ For `Completed Order`, we will track the Kahuna User Attributes "Last Purchase D If you chose not to bundle the Kahuna Mobile SDK, then you will have to implement your own Push Message processors, and you won’t have access to Kahuna’s In-App feature. If you decide to implement your own Push Message processors, then make sure you pass the Push Tokens to Kahuna via Server Side. You can do this by sending it inside `context.device.token`. We will send this to Kahuna as `push_token`. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/keen-io/index.md b/connections/destinations/catalog/keen-io/index.md index 34f9676026b..13072c2e97a 100644 --- a/connections/destinations/catalog/keen-io/index.md +++ b/connections/destinations/catalog/keen-io/index.md @@ -55,3 +55,5 @@ We will forward the following to Keen: revenue: 19.99 } ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/kenshoo-infinity/index.md b/connections/destinations/catalog/kenshoo-infinity/index.md index 57ddf43ba91..3ddf6a5a391 100644 --- a/connections/destinations/catalog/kenshoo-infinity/index.md +++ b/connections/destinations/catalog/kenshoo-infinity/index.md @@ -55,3 +55,6 @@ customParamObjectSchools_gradSchool_graduationYear: '2011', ``` *Note*: All values are encoded. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/knowtify/index.md b/connections/destinations/catalog/knowtify/index.md index b703b1a2b92..9e9a21be33b 100644 --- a/connections/destinations/catalog/knowtify/index.md +++ b/connections/destinations/catalog/knowtify/index.md @@ -9,3 +9,6 @@ Knowtify supports sending [email events](/docs/spec/email/) to other tools on th To enable this feature, follow this [link](http://www.knowtify.io/integrations/segment_email_events) and enter in your Writekey. ![Send email events from Knowtify](https://cldup.com/pQTgionViG.png) + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/leadboxer/index.md b/connections/destinations/catalog/leadboxer/index.md index c6a9a118268..12153e02075 100644 --- a/connections/destinations/catalog/leadboxer/index.md +++ b/connections/destinations/catalog/leadboxer/index.md @@ -12,3 +12,5 @@ By turning on the LeadBoxer destination, you can start using the LeadBoxer app w Toggle Leadboxer on in your Segment destinations, and add your Dataset Identifier which you can find in the LeadBoxer interface under profile > datasets. LeadBoxer currently supports the `identify` method for identifying leads from your online data. Other methods will be added in the near future. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/librato/index.md b/connections/destinations/catalog/librato/index.md index 8a041aa4dac..fb49e102627 100644 --- a/connections/destinations/catalog/librato/index.md +++ b/connections/destinations/catalog/librato/index.md @@ -25,6 +25,7 @@ analytics.track({ event: 'Event Triggered' properties: { value: 2 + } }); ``` @@ -83,3 +84,5 @@ analytics.track('507f191e81', 'Event Triggered', } }) ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/linkedin-conversion-tag/index.md b/connections/destinations/catalog/linkedin-conversion-tag/index.md index 81abad4d607..ea6374addfd 100644 --- a/connections/destinations/catalog/linkedin-conversion-tag/index.md +++ b/connections/destinations/catalog/linkedin-conversion-tag/index.md @@ -10,3 +10,6 @@ When you toggle on the LinkedIn Insight Tag in Segment, this is what happens: + The LinkedIn Insight Tag will automatically start loading the pixel on sites which you load Analytics.js on. LinkedIn Insight Tag doesn't track any other forms of data through Segment, so none of the rest of our API is supported. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/linkedin-insight-tag/index.md b/connections/destinations/catalog/linkedin-insight-tag/index.md index 2dbb8b204c2..26c02bc51e3 100644 --- a/connections/destinations/catalog/linkedin-insight-tag/index.md +++ b/connections/destinations/catalog/linkedin-insight-tag/index.md @@ -52,3 +52,6 @@ From there, click **Configure LinkedIn Insight Tag** and select the source for w ![](images/Nmad4zYvWy.png) Select that option and paste in the LinkedIn Data Partner ID that you copied earlier. Click **Save**, then click **Activate Destination**. Our servers build the latest CDN for that source, and the LinkedIn Insight Tag loads on the sites that use that source's Segment snippet! + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/livechat/index.md b/connections/destinations/catalog/livechat/index.md index dd14fc85f78..d109b670657 100644 --- a/connections/destinations/catalog/livechat/index.md +++ b/connections/destinations/catalog/livechat/index.md @@ -30,3 +30,5 @@ These events will then flow out to your other tools, so you can do things like a To learn more about the live chat events you can capture with this destination, head on over to our [Live Chat spec docs](/docs/spec/live-chat/). ![Turn on LiveChat](Images/livechaton.png) + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/localytics/index.md b/connections/destinations/catalog/localytics/index.md index 875ee9a79a8..058ed54823a 100644 --- a/connections/destinations/catalog/localytics/index.md +++ b/connections/destinations/catalog/localytics/index.md @@ -79,3 +79,5 @@ Push notifications on Android require a bit of extra work to setup. }); } ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/lytics/index.md b/connections/destinations/catalog/lytics/index.md index 19c1583dc8c..fc1057050de 100644 --- a/connections/destinations/catalog/lytics/index.md +++ b/connections/destinations/catalog/lytics/index.md @@ -21,3 +21,6 @@ Paste into your Destination page: ## Features You can see what [data fields Lytics pulls in by default](https://admin.lytics.io/#/documentation/jstag). However, if you would like to pull in any custom data, you can [test it here](http://lytics.github.io/jstag/out/analyticsjs/). This is generally not necessary when using Segment. + + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/madkudu/index.md b/connections/destinations/catalog/madkudu/index.md index d9bc6188a94..db63f0e97b2 100644 --- a/connections/destinations/catalog/madkudu/index.md +++ b/connections/destinations/catalog/madkudu/index.md @@ -36,3 +36,5 @@ These events are enriched with other data, aggregated, and pushed to appropriate ## Questions? More details available on [MadKudu’s website](http://www.madkudu.com/segment) or email [hello@madkudu.com](mailto:hello@madkudu.com). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/mailjet/index.md b/connections/destinations/catalog/mailjet/index.md index 52c6652beb7..10d7d0aaf6a 100644 --- a/connections/destinations/catalog/mailjet/index.md +++ b/connections/destinations/catalog/mailjet/index.md @@ -18,3 +18,5 @@ Confirm that the contact list id is the same, click save, and then Enable Destin Mailjet supports sending [email events](/docs/spec/email/) to data warehouses and other tools on the Segment platform. These events will be sent as `track` calls to the other destinations you've turned on. You will have the option to enable this feature when you're on the App Connections page. Simply grab Segment's write-key and paste it in the box and save. You will see the Sources come in as `track` events in your debugger. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/marketo-v2/index.md b/connections/destinations/catalog/marketo-v2/index.md index 4da9c6f15c7..24ac8711e31 100644 --- a/connections/destinations/catalog/marketo-v2/index.md +++ b/connections/destinations/catalog/marketo-v2/index.md @@ -243,3 +243,5 @@ To figure out what the trigger name for that Custom Activity is, navigate to the ![](images/cg6YhDEPWXv+.png) 6. When enabling Marketo V2, because of the way Marketo’s API works, there is potential to create duplicate leads, especially when the first enabling the destination. For ways to prevent this, check out the Preventing Duplicate Leads. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/marketo/index.md b/connections/destinations/catalog/marketo/index.md index e633cabbf69..70be0db45db 100644 --- a/connections/destinations/catalog/marketo/index.md +++ b/connections/destinations/catalog/marketo/index.md @@ -122,3 +122,5 @@ For more information about syncronising your Marketo leads, please [visit their To create a custom field in Marketo, follow Marketo's [documentation for creating a custom field](http://docs.marketo.com/display/public/DOCS/Create+a+Custom+Field+in+Marketo). Be sure that the **API Name** is `PascalCase`'d, as our destination will account for Marketo's Pascal trait standards. For instance, if you configure `SomeTrait` in the **API Name** field (the **Name** value does not matter), you can pass in this field as `someTrait`, and we will convert this to `SomeTrait` when sending into Marketo. Note that if you configured **API Name** to be `someTrait`, and passed it in as `someTrait` in your call, this would fail to send. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/millennial-media/index.md b/connections/destinations/catalog/millennial-media/index.md index 312cd154e10..3fa99b63320 100644 --- a/connections/destinations/catalog/millennial-media/index.md +++ b/connections/destinations/catalog/millennial-media/index.md @@ -8,3 +8,5 @@ You'll need to map from the Segment event name to the Millennial Media Pixel ID ### Getting your Pixel ID We built this destination off [this documentation](http://docs.millennialmedia.com/conversion-tracking/S2S/mobile-web.html) please refer to that or let us know if you have any questions! + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/moengage/index.md b/connections/destinations/catalog/moengage/index.md index b9f3f7b384f..6e294371b07 100644 --- a/connections/destinations/catalog/moengage/index.md +++ b/connections/destinations/catalog/moengage/index.md @@ -446,3 +446,5 @@ There are some further optional features you can read about here: While updating the MoEngage settings on the Segment Dashboard, you can enable the logging functionality of the MoEngage SDK to see the SDK logs on the browser console. Just set `Enable Debug Logging` to `On` and the SDK will be loaded in debug mode. NOTE: When debug mode is enabled, the events and attributes of the users are sent to the `TEST` environment of your MoEngage App. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/monetate/index.md b/connections/destinations/catalog/monetate/index.md index 6ede9ab6d3f..f104ce17e72 100644 --- a/connections/destinations/catalog/monetate/index.md +++ b/connections/destinations/catalog/monetate/index.md @@ -37,3 +37,5 @@ When you call the [`page`](/docs/spec/page/) method with a name and category, we ## Track When you call the [`track`](/docs/spec/track/) method with the event names `Viewed Product`, `Added Product`, `Order Completed` from our [e-commerce API](/docs/spec/ecommerce/v2/) we will call the corresponding `addItems`, `addReviewRows`, `addConversionRows` in Monetate if the Retail option is not checked in settings, and `addProducts`, `addCartRows`, `addPurchaseRows` if it is. Other event names will not be forwarded to Monetate. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/moosend/index.md b/connections/destinations/catalog/moosend/index.md index 7ee7a18f53a..eaea3bfdad0 100644 --- a/connections/destinations/catalog/moosend/index.md +++ b/connections/destinations/catalog/moosend/index.md @@ -39,3 +39,5 @@ Please adhere to the specd property defintions outlined in the documentation lin A [Product Added](https://segment.com/docs/spec/ecommerce/v2/#product-added) event should be used to track when a user adds an item to their cart. These events can be then used to implement cart abandonment emails. Please adhere to the specd property defintions outlined in the documentation linked above. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/azuresqldw/index.md b/connections/warehouses/catalog/azuresqldw/index.md similarity index 100% rename from connections/destinations/catalog/azuresqldw/index.md rename to connections/warehouses/catalog/azuresqldw/index.md diff --git a/connections/destinations/catalog/bigquery/index.md b/connections/warehouses/catalog/bigquery/index.md similarity index 100% rename from connections/destinations/catalog/bigquery/index.md rename to connections/warehouses/catalog/bigquery/index.md diff --git a/connections/destinations/catalog/db2/images/add_destination.png b/connections/warehouses/catalog/db2/images/add_destination.png similarity index 100% rename from connections/destinations/catalog/db2/images/add_destination.png rename to connections/warehouses/catalog/db2/images/add_destination.png diff --git a/connections/destinations/catalog/db2/images/add_user.png b/connections/warehouses/catalog/db2/images/add_user.png similarity index 100% rename from connections/destinations/catalog/db2/images/add_user.png rename to connections/warehouses/catalog/db2/images/add_user.png diff --git a/connections/destinations/catalog/db2/images/db2_menu.png b/connections/warehouses/catalog/db2/images/db2_menu.png similarity index 100% rename from connections/destinations/catalog/db2/images/db2_menu.png rename to connections/warehouses/catalog/db2/images/db2_menu.png diff --git a/connections/destinations/catalog/db2/images/grant.png b/connections/warehouses/catalog/db2/images/grant.png similarity index 100% rename from connections/destinations/catalog/db2/images/grant.png rename to connections/warehouses/catalog/db2/images/grant.png diff --git a/connections/destinations/catalog/db2/images/manage_users.png b/connections/warehouses/catalog/db2/images/manage_users.png similarity index 100% rename from connections/destinations/catalog/db2/images/manage_users.png rename to connections/warehouses/catalog/db2/images/manage_users.png diff --git a/connections/destinations/catalog/db2/images/run_sql.png b/connections/warehouses/catalog/db2/images/run_sql.png similarity index 100% rename from connections/destinations/catalog/db2/images/run_sql.png rename to connections/warehouses/catalog/db2/images/run_sql.png diff --git a/connections/destinations/catalog/db2/images/search_results.png b/connections/warehouses/catalog/db2/images/search_results.png similarity index 100% rename from connections/destinations/catalog/db2/images/search_results.png rename to connections/warehouses/catalog/db2/images/search_results.png diff --git a/connections/destinations/catalog/db2/images/settings.png b/connections/warehouses/catalog/db2/images/settings.png similarity index 100% rename from connections/destinations/catalog/db2/images/settings.png rename to connections/warehouses/catalog/db2/images/settings.png diff --git a/connections/destinations/catalog/db2/index.md b/connections/warehouses/catalog/db2/index.md similarity index 100% rename from connections/destinations/catalog/db2/index.md rename to connections/warehouses/catalog/db2/index.md diff --git a/connections/destinations/catalog/postgres/images/compose1.png b/connections/warehouses/catalog/postgres/images/compose1.png similarity index 100% rename from connections/destinations/catalog/postgres/images/compose1.png rename to connections/warehouses/catalog/postgres/images/compose1.png diff --git a/connections/destinations/catalog/postgres/images/heroku1.png b/connections/warehouses/catalog/postgres/images/heroku1.png similarity index 100% rename from connections/destinations/catalog/postgres/images/heroku1.png rename to connections/warehouses/catalog/postgres/images/heroku1.png diff --git a/connections/destinations/catalog/postgres/images/heroku2.png b/connections/warehouses/catalog/postgres/images/heroku2.png similarity index 100% rename from connections/destinations/catalog/postgres/images/heroku2.png rename to connections/warehouses/catalog/postgres/images/heroku2.png diff --git a/connections/destinations/catalog/postgres/images/heroku3.png b/connections/warehouses/catalog/postgres/images/heroku3.png similarity index 100% rename from connections/destinations/catalog/postgres/images/heroku3.png rename to connections/warehouses/catalog/postgres/images/heroku3.png diff --git a/connections/destinations/catalog/postgres/images/heroku4.png b/connections/warehouses/catalog/postgres/images/heroku4.png similarity index 100% rename from connections/destinations/catalog/postgres/images/heroku4.png rename to connections/warehouses/catalog/postgres/images/heroku4.png diff --git a/connections/destinations/catalog/postgres/images/heroku5.png b/connections/warehouses/catalog/postgres/images/heroku5.png similarity index 100% rename from connections/destinations/catalog/postgres/images/heroku5.png rename to connections/warehouses/catalog/postgres/images/heroku5.png diff --git a/connections/destinations/catalog/postgres/images/heroku6.png b/connections/warehouses/catalog/postgres/images/heroku6.png similarity index 100% rename from connections/destinations/catalog/postgres/images/heroku6.png rename to connections/warehouses/catalog/postgres/images/heroku6.png diff --git a/connections/destinations/catalog/postgres/images/rds1.png b/connections/warehouses/catalog/postgres/images/rds1.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds1.png rename to connections/warehouses/catalog/postgres/images/rds1.png diff --git a/connections/destinations/catalog/postgres/images/rds10.png b/connections/warehouses/catalog/postgres/images/rds10.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds10.png rename to connections/warehouses/catalog/postgres/images/rds10.png diff --git a/connections/destinations/catalog/postgres/images/rds11.png b/connections/warehouses/catalog/postgres/images/rds11.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds11.png rename to connections/warehouses/catalog/postgres/images/rds11.png diff --git a/connections/destinations/catalog/postgres/images/rds12.png b/connections/warehouses/catalog/postgres/images/rds12.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds12.png rename to connections/warehouses/catalog/postgres/images/rds12.png diff --git a/connections/destinations/catalog/postgres/images/rds13.png b/connections/warehouses/catalog/postgres/images/rds13.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds13.png rename to connections/warehouses/catalog/postgres/images/rds13.png diff --git a/connections/destinations/catalog/postgres/images/rds2.png b/connections/warehouses/catalog/postgres/images/rds2.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds2.png rename to connections/warehouses/catalog/postgres/images/rds2.png diff --git a/connections/destinations/catalog/postgres/images/rds3.png b/connections/warehouses/catalog/postgres/images/rds3.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds3.png rename to connections/warehouses/catalog/postgres/images/rds3.png diff --git a/connections/destinations/catalog/postgres/images/rds4.png b/connections/warehouses/catalog/postgres/images/rds4.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds4.png rename to connections/warehouses/catalog/postgres/images/rds4.png diff --git a/connections/destinations/catalog/postgres/images/rds5.png b/connections/warehouses/catalog/postgres/images/rds5.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds5.png rename to connections/warehouses/catalog/postgres/images/rds5.png diff --git a/connections/destinations/catalog/postgres/images/rds6.png b/connections/warehouses/catalog/postgres/images/rds6.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds6.png rename to connections/warehouses/catalog/postgres/images/rds6.png diff --git a/connections/destinations/catalog/postgres/images/rds7.png b/connections/warehouses/catalog/postgres/images/rds7.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds7.png rename to connections/warehouses/catalog/postgres/images/rds7.png diff --git a/connections/destinations/catalog/postgres/images/rds8.png b/connections/warehouses/catalog/postgres/images/rds8.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds8.png rename to connections/warehouses/catalog/postgres/images/rds8.png diff --git a/connections/destinations/catalog/postgres/images/rds9.png b/connections/warehouses/catalog/postgres/images/rds9.png similarity index 100% rename from connections/destinations/catalog/postgres/images/rds9.png rename to connections/warehouses/catalog/postgres/images/rds9.png diff --git a/connections/destinations/catalog/postgres/images/segment1.png b/connections/warehouses/catalog/postgres/images/segment1.png similarity index 100% rename from connections/destinations/catalog/postgres/images/segment1.png rename to connections/warehouses/catalog/postgres/images/segment1.png diff --git a/connections/destinations/catalog/postgres/images/segment2.png b/connections/warehouses/catalog/postgres/images/segment2.png similarity index 100% rename from connections/destinations/catalog/postgres/images/segment2.png rename to connections/warehouses/catalog/postgres/images/segment2.png diff --git a/connections/destinations/catalog/postgres/images/segment3.png b/connections/warehouses/catalog/postgres/images/segment3.png similarity index 100% rename from connections/destinations/catalog/postgres/images/segment3.png rename to connections/warehouses/catalog/postgres/images/segment3.png diff --git a/connections/destinations/catalog/postgres/images/segment4.png b/connections/warehouses/catalog/postgres/images/segment4.png similarity index 100% rename from connections/destinations/catalog/postgres/images/segment4.png rename to connections/warehouses/catalog/postgres/images/segment4.png diff --git a/connections/destinations/catalog/postgres/images/segment5.png b/connections/warehouses/catalog/postgres/images/segment5.png similarity index 100% rename from connections/destinations/catalog/postgres/images/segment5.png rename to connections/warehouses/catalog/postgres/images/segment5.png diff --git a/connections/destinations/catalog/postgres/index.md b/connections/warehouses/catalog/postgres/index.md similarity index 100% rename from connections/destinations/catalog/postgres/index.md rename to connections/warehouses/catalog/postgres/index.md diff --git a/connections/destinations/catalog/redshift/index.md b/connections/warehouses/catalog/redshift/index.md similarity index 100% rename from connections/destinations/catalog/redshift/index.md rename to connections/warehouses/catalog/redshift/index.md diff --git a/connections/destinations/catalog/snowflake/images/auto_suspend.png b/connections/warehouses/catalog/snowflake/images/auto_suspend.png similarity index 100% rename from connections/destinations/catalog/snowflake/images/auto_suspend.png rename to connections/warehouses/catalog/snowflake/images/auto_suspend.png diff --git a/connections/destinations/catalog/snowflake/images/connect_snowflake.png b/connections/warehouses/catalog/snowflake/images/connect_snowflake.png similarity index 100% rename from connections/destinations/catalog/snowflake/images/connect_snowflake.png rename to connections/warehouses/catalog/snowflake/images/connect_snowflake.png diff --git a/connections/destinations/catalog/snowflake/images/create_database.png b/connections/warehouses/catalog/snowflake/images/create_database.png similarity index 100% rename from connections/destinations/catalog/snowflake/images/create_database.png rename to connections/warehouses/catalog/snowflake/images/create_database.png diff --git a/connections/destinations/catalog/snowflake/images/create_user_1.png b/connections/warehouses/catalog/snowflake/images/create_user_1.png similarity index 100% rename from connections/destinations/catalog/snowflake/images/create_user_1.png rename to connections/warehouses/catalog/snowflake/images/create_user_1.png diff --git a/connections/destinations/catalog/snowflake/images/create_user_2.png b/connections/warehouses/catalog/snowflake/images/create_user_2.png similarity index 100% rename from connections/destinations/catalog/snowflake/images/create_user_2.png rename to connections/warehouses/catalog/snowflake/images/create_user_2.png diff --git a/connections/destinations/catalog/snowflake/images/create_user_3.png b/connections/warehouses/catalog/snowflake/images/create_user_3.png similarity index 100% rename from connections/destinations/catalog/snowflake/images/create_user_3.png rename to connections/warehouses/catalog/snowflake/images/create_user_3.png diff --git a/connections/destinations/catalog/snowflake/images/create_virtual_warehouse.png b/connections/warehouses/catalog/snowflake/images/create_virtual_warehouse.png similarity index 100% rename from connections/destinations/catalog/snowflake/images/create_virtual_warehouse.png rename to connections/warehouses/catalog/snowflake/images/create_virtual_warehouse.png diff --git a/connections/destinations/catalog/snowflake/index.md b/connections/warehouses/catalog/snowflake/index.md similarity index 100% rename from connections/destinations/catalog/snowflake/index.md rename to connections/warehouses/catalog/snowflake/index.md diff --git a/todo.txt b/todo.txt index 1f63932fa8f..68f04bb7691 100644 --- a/todo.txt +++ b/todo.txt @@ -1,53 +1,8 @@ - redirects +- Find and import google-cloud-storage - add {% include content/integration-foot.md %} to anything that didn't have rewrite: true -doubleclick-floodlight -drip -eloqua -errorception -extole -facebook-pixel-server-side -firebase -framed.io -freshdesk -freshsales -friendbuy -frontleaf -gauges -google-adwords-new -google-analytics -google-cloud-pubsub -google-cloud-storage -gosquared -hindsight -hittail -hull -impact-radius -infinario -insidevault -intellimize -iron.io -iterable -kahuna -keen-io -kenshoo-infinity -knowtify -leadboxer -librato -linkedin-conversion-tag -linkedin-insight-tag -livechat -localytics -lytics -madkudu -mailjet -marketo -marketo-v2 -millennial-media -moengage -monetate -moosend nanigans nielsen-dcr nudgespot From 7c4b0ac50e7c40ec0b72a457c2bee80663e713f0 Mon Sep 17 00:00:00 2001 From: sanscontext Date: Tue, 13 Aug 2019 16:11:19 -0700 Subject: [PATCH 3/6] additional cleanup Signed-off-by: sanscontext --- _config.yml | 2 ++ _data/sidenav/default.yml | 62 +++++++++++++++++++-------------------- sitemap.xml | 2 +- 3 files changed, 34 insertions(+), 32 deletions(-) diff --git a/_config.yml b/_config.yml index 00501e2a7dd..c7cd1201f13 100644 --- a/_config.yml +++ b/_config.yml @@ -13,6 +13,8 @@ defaults: layout: "page" hidden: false beta: false + seo-priority: 0.5 + seo-changefreq: weekly - scope: path: "connections/destinations" values: diff --git a/_data/sidenav/default.yml b/_data/sidenav/default.yml index f327370ed17..6c9fbda3f2b 100644 --- a/_data/sidenav/default.yml +++ b/_data/sidenav/default.yml @@ -1,36 +1,5 @@ --- sections: -- section_title: Connections - section: - - path: "/connections/spec" - title: Spec - - section_title: Sources - slug: connections/Sources - section: - - path: "/connections/sources" - title: Overview - - path: "/connections/sources/visual-tagger" - title: "Visual tagger" - - path: "connections/sources/faq" - title: "FAQ" - - path: "/connections/sources/catalog" - title: Sources catalog - - section_title: Destinations - slug: connections/destinations - section: - - path: "/connections/destinations" - title: Overview - - path: "/connections/destinations/destination-filters" - title: Destinations Filters - - path: "/connections/destinations/catalog" - title: Destinations catalog - - section_title: Warehouses - slug: connections/warehouses - section: - - path: "/connections/warehouses" - title: Overview - - path: "/connections/warehouses/catalog" - title: Warehouses catalog - section_title: Guides section: - path: "/guides" @@ -158,6 +127,37 @@ sections: title: How do I find out my usage data? - path: "/guides/usage-and-billing/volume-and-pricing" title: How does my event and object volume impact my pricing? +- section_title: Connections + section: + - path: "/connections/spec" + title: Spec + - section_title: Sources + slug: connections/Sources + section: + - path: "/connections/sources" + title: Overview + - path: "/connections/sources/visual-tagger" + title: "Visual tagger" + - path: "/connections/sources/faq" + title: "FAQ" + - path: "/connections/sources/catalog" + title: Sources catalog + - section_title: Destinations + slug: connections/destinations + section: + - path: "/connections/destinations" + title: Overview + - path: "/connections/destinations/destination-filters" + title: Destinations Filters + - path: "/connections/destinations/catalog" + title: Destinations catalog + - section_title: Warehouses + slug: connections/warehouses + section: + - path: "/connections/warehouses" + title: Overview + - path: "/connections/warehouses/catalog" + title: Warehouses catalog - section_title: Personas section: - path: "/personas" diff --git a/sitemap.xml b/sitemap.xml index 8015991e701..53fd5291f8e 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -12,7 +12,7 @@ layout: null {% for doc in docs %} {% unless doc.hidden %} - {{ doc.url | replace:'/index.html','/' | absolute_url | xml_escape }}{% if doc.seo-changefreq %}{{doc.seo-changefreq}} {% else %}weekly{% endif %}{% if doc.seo-priority %}{{doc.seo-priority}}{% else %}0.5{% endif %} + {{ doc.url | replace:'/index.html','/' | absolute_url | xml_escape }}{% if doc.seo-changefreq %}{{doc.seo-changefreq}}{% else %}weekly{% endif %}{% if doc.seo-priority %}{{doc.seo-priority}}{% else %}0.5{% endif %} {% if doc.last_modified_at or doc.date %}{{ doc.last_modified_at | default: doc.date | date_to_xmlschema }} {% endif %} From ee1af05384fc180691cd928078af60a4675ab740 Mon Sep 17 00:00:00 2001 From: sanscontext Date: Tue, 13 Aug 2019 16:27:49 -0700 Subject: [PATCH 4/6] finish adding footers Signed-off-by: sanscontext --- .../destinations/catalog/nanigans/index.md | 2 + .../destinations/catalog/nielsen-dcr/index.md | 2 + .../destinations/catalog/nudgespot/index.md | 2 + .../destinations/catalog/olark/index.md | 2 + .../destinations/catalog/omniture/index.md | 3 +- .../destinations/catalog/onesignal/index.md | 2 + .../catalog/optimizely-full-stack/index.md | 4 +- .../catalog/optimizely-web/index.md | 2 + .../destinations/catalog/outbound/index.md | 2 + .../destinations/catalog/pardot/index.md | 6 +- .../destinations/catalog/perimeterx/index.md | 2 + .../catalog/personas-facebook-ads/index.md | 2 + .../destinations/catalog/pingdom/index.md | 2 + .../catalog/pinterest-tag/index.md | 2 + .../destinations/catalog/piwik/index.md | 4 +- .../destinations/catalog/planhat/index.md | 2 + .../destinations/catalog/pointillist/index.md | 2 + .../destinations/catalog/preact/index.md | 2 + .../destinations/catalog/primer/index.md | 2 + .../destinations/catalog/promoter.io/index.md | 2 + .../destinations/catalog/quantcast/index.md | 2 + .../destinations/catalog/ramen/index.md | 2 + .../destinations/catalog/relay/index.md | 2 + .../destinations/catalog/repeater/index.md | 2 + .../destinations/catalog/responsys/index.md | 2 + .../destinations/catalog/rollbar/index.md | 2 + .../destinations/catalog/route/index.md | 2 + .../destinations/catalog/saasquatch/index.md | 2 + .../destinations/catalog/sailthru/index.md | 2 + .../catalog/salesforce-live-agent/index.md | 2 + .../salesforce-marketing-cloud/index.md | 2 + .../destinations/catalog/salesforce/index.md | 2 + .../catalog/salesmachine/index.md | 2 + .../destinations/catalog/satismeter/index.md | 2 + connections/destinations/catalog/seg/index.md | 2 + .../destinations/catalog/selligent/index.md | 21 ++--- .../destinations/catalog/sendwithus/index.md | 2 + .../destinations/catalog/shareasale/index.md | 2 + .../destinations/catalog/smyte/index.md | 2 + .../destinations/catalog/sparkpage/index.md | 2 + .../catalog/stripe-radar/index.md | 2 + .../destinations/catalog/swrve/index.md | 8 +- .../destinations/catalog/tableau/index.md | 2 + .../destinations/catalog/taplytics/index.md | 2 + .../catalog/tealium-audience-stream/index.md | 2 + .../destinations/catalog/totango/index.md | 2 + .../destinations/catalog/track-js/index.md | 2 + .../catalog/tractionboard/index.md | 2 + .../destinations/catalog/tray.io/index.md | 6 +- .../catalog/treasure-data/index.md | 2 + .../destinations/catalog/twitter-ads/index.md | 2 + .../catalog/urban-airship/index.md | 76 ++++++++++--------- .../destinations/catalog/userengage/index.md | 2 + .../destinations/catalog/vero/index.md | 2 + .../destinations/catalog/watsi/index.md | 2 + .../destinations/catalog/webengage/index.md | 2 + .../catalog/whale-alerts/index.md | 2 + .../destinations/catalog/wishpond/index.md | 2 + .../destinations/catalog/woopra/index.md | 2 + .../destinations/catalog/youbora/index.md | 4 +- .../destinations/catalog/zaius/index.md | 2 + todo.txt | 65 ---------------- 62 files changed, 176 insertions(+), 125 deletions(-) diff --git a/connections/destinations/catalog/nanigans/index.md b/connections/destinations/catalog/nanigans/index.md index 950bcd4da09..2f085e556df 100644 --- a/connections/destinations/catalog/nanigans/index.md +++ b/connections/destinations/catalog/nanigans/index.md @@ -34,3 +34,5 @@ By default, if you send any data with either the iOS or Android library, we will If you'd like to send any other server side event using a server side library, you can either enable the option "Send Events to Mobile Endpoint" in your Nanigans settings. However, this means that ALL server side events sent from your server side library will be sent to the mobile endpoint. If you are unsure which endpoint to send to, please contact Nanigans support! + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/nielsen-dcr/index.md b/connections/destinations/catalog/nielsen-dcr/index.md index 95186ddab5b..011005176fd 100644 --- a/connections/destinations/catalog/nielsen-dcr/index.md +++ b/connections/destinations/catalog/nielsen-dcr/index.md @@ -335,3 +335,5 @@ The Parent Client ID and Sub-Brand (VCID) values are automatically populated thr #### Can I override the Nielsen-DCR `clientId` and `subbrand` values? In the event that your app contains multiple brands and sub-brands, Segment lets you override the `clientId` and `subbrand` values, to give credit to another brand or sub-brand. In your Segment dashboard, under "Client Id Property Name", indicate a payload property to be mapped to the Nielsen `clientId`. To override a `subbrand`, indicate a payload property to mapped to Nielsen `subbrand` under "Subbrand Property Name". + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/nudgespot/index.md b/connections/destinations/catalog/nudgespot/index.md index 81211f3caf7..2f1c821690e 100644 --- a/connections/destinations/catalog/nudgespot/index.md +++ b/connections/destinations/catalog/nudgespot/index.md @@ -42,3 +42,5 @@ Nudgespot supports sending [email events](/docs/spec/email/) to other tools on t ### When will I see data from my mobile app? If you already have an app deployed with the Segment source, and you just turned on Nudgespot, it will take up to an hour for all your mobile users to refresh their Segment settings cache, and learn about the new service that you want to send to. After the settings cache refreshes, our source will automatically start sending data to Nudgespot. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/olark/index.md b/connections/destinations/catalog/olark/index.md index 3b015c3fe49..fa4def0a848 100644 --- a/connections/destinations/catalog/olark/index.md +++ b/connections/destinations/catalog/olark/index.md @@ -70,3 +70,5 @@ These events will be sent to other tools in your stack that can accept track cal To learn more about the live chat events you can capture with this destination, head on over to our [Live Chat spec docs](/docs/spec/live-chat/). ![Turn on Olark](images/olarklivechat.png) + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/omniture/index.md b/connections/destinations/catalog/omniture/index.md index b9d8a8cb5a2..231aa98dee6 100644 --- a/connections/destinations/catalog/omniture/index.md +++ b/connections/destinations/catalog/omniture/index.md @@ -2,7 +2,6 @@ title: Omniture --- - ## Getting Started When you toggle on Omniture in Segment, our CDN is updated within 5-10 minutes. Then our javascript will start sending all mapped `track` calls to your Omniture installation. @@ -163,3 +162,5 @@ After the settings cache refreshes, our library will automatically start sending ### Custom Links In order to populate the Custom Links report when sending data server-side, you'll need to pass `context.page.url` manually. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/onesignal/index.md b/connections/destinations/catalog/onesignal/index.md index 83bdd80ea02..49aa57ee7b1 100644 --- a/connections/destinations/catalog/onesignal/index.md +++ b/connections/destinations/catalog/onesignal/index.md @@ -45,3 +45,5 @@ OneSignal will also assign the following custom tags based on user attributes or - `Website` All of the above values can be used to deliver and schedule notifications to your users from the OneSignal dashboard. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/optimizely-full-stack/index.md b/connections/destinations/catalog/optimizely-full-stack/index.md index b1f4dac8916..4c631963051 100644 --- a/connections/destinations/catalog/optimizely-full-stack/index.md +++ b/connections/destinations/catalog/optimizely-full-stack/index.md @@ -1,5 +1,5 @@ --- -title: Optimizely Full Stack +title: Optimizely Full Stack beta: true --- @@ -126,3 +126,5 @@ Invoking a Segment `identify` event sets Segment `traits` as Optimziely `attribu ### Notification Listeners Notification listeners are not available when implementing Optimizely via Segment using cloud mode. However, notification listeners are straightforward to set up, as [documented here on Optimizely's site](https://docs.developers.optimizely.com/full-stack/docs/notification-listeners). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/optimizely-web/index.md b/connections/destinations/catalog/optimizely-web/index.md index 77f266bca14..3eb215161e9 100644 --- a/connections/destinations/catalog/optimizely-web/index.md +++ b/connections/destinations/catalog/optimizely-web/index.md @@ -435,3 +435,5 @@ More importantly, to send the true referrer value with the initial `page` call i }}(); ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/outbound/index.md b/connections/destinations/catalog/outbound/index.md index 3f0a8a7e943..7ddd8cb607d 100644 --- a/connections/destinations/catalog/outbound/index.md +++ b/connections/destinations/catalog/outbound/index.md @@ -85,3 +85,5 @@ Now that everything is hooked up, you can start messaging your users! Check out 1. [Getting started with Connect](https://support.zendesk.com/hc/en-us/articles/360022370293-Introduction-Getting-started-with-Connect) 2. [Understanding events in Connect](https://support.zendesk.com/hc/en-us/articles/360022178494-Understanding-Connect-events) 3. [Create a trigger based campaign](https://support.zendesk.com/hc/en-us/articles/360022362093-Creating-a-trigger-based-campaign) + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/pardot/index.md b/connections/destinations/catalog/pardot/index.md index d5c3e992a22..2f1ae000079 100644 --- a/connections/destinations/catalog/pardot/index.md +++ b/connections/destinations/catalog/pardot/index.md @@ -30,7 +30,7 @@ Our script will use the most appropriate campaign Id. ### Pardot Version 3 and Version 4 -There are currently two active versions of the Pardot platform, version 3 and version 4. The major change in version 4 is the new ability to create multiple prospects in Pardot with the same email address. +There are currently two active versions of the Pardot platform, version 3 and version 4. The major change in version 4 is the new ability to create multiple prospects in Pardot with the same email address. Previously, this was not possible. Email was used by Pardot as a distinct identifier. In version 4 however, in order to update an *existing* prospect, you must provide either the Pardot ID for a given user OR the Salesforce FID. If one of these values is not provided in a request, Pardot will create a new prospect. More information is available on their [website](http://developer.pardot.com/kb/api-version-4/). @@ -107,7 +107,7 @@ If a user existed in your Pardot instance with a custom field called `org_id` an Alternatively, you can specify in your integration settings that we use the `userId` passed in as an argument to the `identify` event to match the user on. Keeping with the above example, if you already were using your internal `org_id` as the `userId` for Segment events, you could enable this option and avoid having to explicitly define it as a trait. -**Important**: If you have users in Pardot that do not have values for the custom field you will be using as a lookup field, you will likely see duplicate prospects being created. +**Important**: If you have users in Pardot that do not have values for the custom field you will be using as a lookup field, you will likely see duplicate prospects being created. If possible, we recommend you explore bulk updating all existing users to ensure they have a value for this custom field before enabling the integration. @@ -122,3 +122,5 @@ On the client-side browser we load Pardot's javascript snippet to enable [anonym If you are using Version 4 of the API and are using a lookup field to match existing prospects with Segment `identify` events, trying to update a prospect's email will result in a new prospect being created. This is because the Pardot API only allows read operations with email as the query (or PardotID/SaleforceFID but if you were passing those, this issue would be irrelevant to you). What ends up happening is our integration performs a read operation for a prospect matching the new email being passed in. This will not return a lookup field match and thus a new user will be generated. To update a user's email, you must pass either a PardotID or a SaleforceFID (see above for specifics on how to do this). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/perimeterx/index.md b/connections/destinations/catalog/perimeterx/index.md index a70aac1eb39..dca43df4041 100644 --- a/connections/destinations/catalog/perimeterx/index.md +++ b/connections/destinations/catalog/perimeterx/index.md @@ -50,3 +50,5 @@ You have the option to map up to 10 of your Segment `.identify()` traits to cust ![](https://cloudup.com/cmA_dv62kgp+) 3. In your Segment PerimeterX Destination settings, enter the name of the `.identify()` trait you'd like to map the the custom parameter you created and then enter the number of the custom parameter (1-10). ![](https://cloudup.com/cnKeeTBLune+) + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/personas-facebook-ads/index.md b/connections/destinations/catalog/personas-facebook-ads/index.md index a36b10a5cbb..5d72e323f97 100644 --- a/connections/destinations/catalog/personas-facebook-ads/index.md +++ b/connections/destinations/catalog/personas-facebook-ads/index.md @@ -61,3 +61,5 @@ We attempt to match users in your audience with the identifiers that Facebook su ## How do lookalikes work? You can create a seed audience in Personas and then sync that to Facebook. For example, you might want to create a group of high-value users that have spent a certain amount of money on your product. In Facebook, you can then create a lookalike based on that audience. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/pingdom/index.md b/connections/destinations/catalog/pingdom/index.md index 9f468ece858..f7c8c9f13ee 100644 --- a/connections/destinations/catalog/pingdom/index.md +++ b/connections/destinations/catalog/pingdom/index.md @@ -10,3 +10,5 @@ When you toggle on Pingdom in Segment, this is what happens: + Pingdom will automatically start recording page load times. Go to [Pingdom](https://my.pingdom.com/rum) to view your page load performance data. Since Pingdom only records data about page load performance, it does not collect any of the data represented by our API. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/pinterest-tag/index.md b/connections/destinations/catalog/pinterest-tag/index.md index 160eff01033..9ee0b353dc6 100644 --- a/connections/destinations/catalog/pinterest-tag/index.md +++ b/connections/destinations/catalog/pinterest-tag/index.md @@ -79,3 +79,5 @@ Segment automatically binds the following properties to Pinterest [Event Data](h + `nested within the e-commerce products array: brand` => product_brand In the Segment.com Pinterest Tag destination settings, one can also define their own custom properties, in addition to the mapped properties above. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/piwik/index.md b/connections/destinations/catalog/piwik/index.md index 3ff149e0b9a..cbcde61b9fd 100644 --- a/connections/destinations/catalog/piwik/index.md +++ b/connections/destinations/catalog/piwik/index.md @@ -91,7 +91,7 @@ analytics.track('event', { } } } -} +}) ``` ### Goals @@ -101,3 +101,5 @@ If you want to flag specific events as Piwik Goals you can do so by mapping thos ![piwik goals settings](images/goals.png) Fill in the event on the left and the Goal ID from Piwik on the right. Then every time the event happens we'll fire Piwik's `trackGoal` method. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/planhat/index.md b/connections/destinations/catalog/planhat/index.md index db58a49125e..d9acce2553b 100644 --- a/connections/destinations/catalog/planhat/index.md +++ b/connections/destinations/catalog/planhat/index.md @@ -25,3 +25,5 @@ When you `identify` a user, we'll pass that user's information to Planhat with ` In addition, all calls will get Segment as 'source'. If the `userId` or `traits.email` matches an existing Contact in Planhat the Identify-call will automatically be associated with that Contact. Otherwise a new Contact will be created in Planhat. New Contacts received from Segment can either be discarded or manually assigned to a Customer profile in Planhat. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/pointillist/index.md b/connections/destinations/catalog/pointillist/index.md index 7eb295303c4..73f50522304 100644 --- a/connections/destinations/catalog/pointillist/index.md +++ b/connections/destinations/catalog/pointillist/index.md @@ -37,3 +37,5 @@ Below is an example of how your track events will start appearing instantly in ## API Key To get your API key please get in touch with a Pointillist customer representative via customer-success@pointillist.com + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/preact/index.md b/connections/destinations/catalog/preact/index.md index 0493bdd9f21..5ab806cd56e 100644 --- a/connections/destinations/catalog/preact/index.md +++ b/connections/destinations/catalog/preact/index.md @@ -35,3 +35,5 @@ analytics.track('!Image upload error', { Message: 'File size too large' }); ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/primer/index.md b/connections/destinations/catalog/primer/index.md index 4cb1cb48f9b..7050cc6bd22 100644 --- a/connections/destinations/catalog/primer/index.md +++ b/connections/destinations/catalog/primer/index.md @@ -30,3 +30,5 @@ Segment's special traits are attached on to the Primer User's user properties. ## Track When you `track` an event, we will send that event to Primer as a custom event. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/promoter.io/index.md b/connections/destinations/catalog/promoter.io/index.md index 06b6c4249cc..05bcc9ac6cf 100644 --- a/connections/destinations/catalog/promoter.io/index.md +++ b/connections/destinations/catalog/promoter.io/index.md @@ -59,3 +59,5 @@ Here’s an example: ### Completed Order When you `track` an event with the name `Order Completed` using the [e-commerce tracking API](/docs/spec/ecommerce/v2/), we will send the event and data to Promoter as a custom event with the data stored with Promoter for future use. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/quantcast/index.md b/connections/destinations/catalog/quantcast/index.md index f5cfea17ec5..b9edb56c3b1 100644 --- a/connections/destinations/catalog/quantcast/index.md +++ b/connections/destinations/catalog/quantcast/index.md @@ -91,3 +91,5 @@ When you call `screen` we'll automatically log an event like `Viewed ABC Screen` ### Other Features #### Labels The destination does not currently support labels. If this is important to you, please [let us know](https://segment.com/help/contact/). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/ramen/index.md b/connections/destinations/catalog/ramen/index.md index 4111b4cf60d..b9788583aa3 100644 --- a/connections/destinations/catalog/ramen/index.md +++ b/connections/destinations/catalog/ramen/index.md @@ -144,3 +144,5 @@ If the above all look correct, and you are sending `timestamp` and `auth_hash`, + `auth_hash` is being calculated correctly ​ If you are still having trouble, you can email [Ramen support](mailto:support@ramen.is). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/relay/index.md b/connections/destinations/catalog/relay/index.md index 5c04df1df82..7193f816e01 100644 --- a/connections/destinations/catalog/relay/index.md +++ b/connections/destinations/catalog/relay/index.md @@ -21,3 +21,5 @@ All other traits will be sent to Relay as custom attributes. ## Track When you `track` an event, we will send that event to Relay as a custom event. Your '.track' events should have the properties associated with it. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/repeater/index.md b/connections/destinations/catalog/repeater/index.md index 07bd9b97902..1fe5d604cb3 100644 --- a/connections/destinations/catalog/repeater/index.md +++ b/connections/destinations/catalog/repeater/index.md @@ -24,3 +24,5 @@ You can do this for as many sources as you need. ![](images/write-key-settings.png) Repeater will replay all events it gets to the sources you specified using the write key(s) you specified. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/responsys/index.md b/connections/destinations/catalog/responsys/index.md index fef71feac63..7ee174b3f37 100644 --- a/connections/destinations/catalog/responsys/index.md +++ b/connections/destinations/catalog/responsys/index.md @@ -285,3 +285,5 @@ You should enter `address_street` as your Segment Property Name. ### I'm seeing a 'Merge cannot be done on one field' in the Segment debugger! This error occurs when you try to upsert a record to a Profile Extension Table but you did not provide any additional traits other than what we used to match the columns. For PETs, we use your `userId` or `traits.email` from your `.identify()` calls to upsert the record. You need to send at least one other trait that would map to a field in your PET. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/rollbar/index.md b/connections/destinations/catalog/rollbar/index.md index 7b663c7d2d1..69ddb692409 100644 --- a/connections/destinations/catalog/rollbar/index.md +++ b/connections/destinations/catalog/rollbar/index.md @@ -28,3 +28,5 @@ This feature makes use of JavaScript Source Maps to translate the minified code b. Upload pre-deploy: at the beginning of your deploy script, upload a source map package via Rollbar's API. For more detail on providing your source map, checkout [Rollbar's documentation here](https://rollbar.com/docs/source-maps/#step-2-provide-your-source-map). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/route/index.md b/connections/destinations/catalog/route/index.md index d5f15c1528f..37501f7e7bc 100644 --- a/connections/destinations/catalog/route/index.md +++ b/connections/destinations/catalog/route/index.md @@ -25,3 +25,5 @@ When you `identify` a contact, we'll pass that contact's information to Route wi When you `track` an event, we will send that event to Route using the following data: - `eventName` [`string`] + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/saasquatch/index.md b/connections/destinations/catalog/saasquatch/index.md index 985d8e3577d..fa02119265a 100644 --- a/connections/destinations/catalog/saasquatch/index.md +++ b/connections/destinations/catalog/saasquatch/index.md @@ -33,3 +33,5 @@ analytics.identify( 'u1234', { ``` For more information about Referral SaaSquatch check out [their docs](http://docs.referralsaasquatch.com/segment-io)! + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/sailthru/index.md b/connections/destinations/catalog/sailthru/index.md index 5f5c9eb5893..79bb8d093a0 100644 --- a/connections/destinations/catalog/sailthru/index.md +++ b/connections/destinations/catalog/sailthru/index.md @@ -275,3 +275,5 @@ Sailthru does not accept nested custom traits or properties, so by default we wi ### Replays Note that Sailthru does not support historical replay. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/salesforce-live-agent/index.md b/connections/destinations/catalog/salesforce-live-agent/index.md index ea82bd9c3fe..14747b8748a 100644 --- a/connections/destinations/catalog/salesforce-live-agent/index.md +++ b/connections/destinations/catalog/salesforce-live-agent/index.md @@ -51,3 +51,5 @@ Many of the settings required to allow Segment to integrate with your Live Agent liveagent.init('https://{LIVE_AGENT_ENDPOINT_URL}.salesforceliveagent.com/chat', {DEPLOYMENT_ID}, {ORG_ID}); ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/salesforce-marketing-cloud/index.md b/connections/destinations/catalog/salesforce-marketing-cloud/index.md index e17e28b6702..e505bb55bf3 100644 --- a/connections/destinations/catalog/salesforce-marketing-cloud/index.md +++ b/connections/destinations/catalog/salesforce-marketing-cloud/index.md @@ -213,3 +213,5 @@ In order to take advantage of this functionality, you will need to create attrib [app center - summary]: /docs/integrations/salesforce-marketing-cloud/images/new_app-4_summary.png [eventing API]: https://code.exacttarget.com/apis-sdks/rest-api/v1/hub/data-events/putDataExtensionRowByKeyAsync.html [standard identify traits]: https://segment.com/docs/spec/identify/#traits + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/salesforce/index.md b/connections/destinations/catalog/salesforce/index.md index 64ce5d0f645..892bb2af06a 100644 --- a/connections/destinations/catalog/salesforce/index.md +++ b/connections/destinations/catalog/salesforce/index.md @@ -205,3 +205,5 @@ If you want to set your passwords to never expire, you can do so in **Salesforce ### Updating Lead Status Currently Segment does not support updating the Salesforce Lead Status field due to constraints of the Salesforce API. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/salesmachine/index.md b/connections/destinations/catalog/salesmachine/index.md index 15950b10e81..459671e0db7 100644 --- a/connections/destinations/catalog/salesmachine/index.md +++ b/connections/destinations/catalog/salesmachine/index.md @@ -32,3 +32,5 @@ When you call `group`, we will send an account call to Salesmachine.io and link ## Alias When you call `alias`, we will send an alias call to Salesmachine.io. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/satismeter/index.md b/connections/destinations/catalog/satismeter/index.md index 6af73cf7451..c1042cd6736 100644 --- a/connections/destinations/catalog/satismeter/index.md +++ b/connections/destinations/catalog/satismeter/index.md @@ -74,3 +74,5 @@ Make sure you are sending an `analytics.identify()` call when the page is loaded ### The SatisMeter widget shows up right after sign-up It is important to send the `createdAt` trait to `analytics.identify()` method. Without this SatisMeter widget will be shown right after sign-up to every user that fits your other targeting settings. You can change the targeting settings in Targeting section of SatisMeter settings. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/seg/index.md b/connections/destinations/catalog/seg/index.md index 197e70d4008..6581d42f92c 100644 --- a/connections/destinations/catalog/seg/index.md +++ b/connections/destinations/catalog/seg/index.md @@ -130,3 +130,5 @@ analytics.alias('old-email@segment.com','new-email@segment.com') ``` If both parameters are not email address types, the call is ignored in Seg. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/selligent/index.md b/connections/destinations/catalog/selligent/index.md index 1e961b9d365..9a60dc102a7 100644 --- a/connections/destinations/catalog/selligent/index.md +++ b/connections/destinations/catalog/selligent/index.md @@ -8,26 +8,17 @@ This destination is built and supported by Selligent. If you run into any issues ## Getting Started Once the Segment Connector is integrated with Message Studio, -the Segment API shall support receiving Segment’s "Identify" and -"Track" event data. Message Studio translates these events as follows:

- - ->Identify: add records to an Internal Data Source (IDS) - ->Track: add records to an Interaction Extension +the Segment API shall support receiving Segment’s "Identify" and "Track" event data. Message Studio translates these events as follows: +- Identify: add records to an Internal Data Source (IDS) +- Track: add records to an Interaction Extension These records can be used to enhance the targeting and -personalization of your email messages within the Message Studio platform.

- +personalization of your email messages within the Message Studio platform. ## Identify When you identify a user, we’ll pass that user’s information to -Message Studio as a record in the configured Internal Data Source.  Since -the Internal Data Source schema is flexible, each customer’s destination with -Segment will require unique mapping of the Internal Data Source fields.  -Customers should contact their Selligent Relationship Manager so we can work -with them to configure the mapping to best meet their needs. +Message Studio as a record in the configured Internal Data Source. Since the Internal Data Source schema is flexible, each customer’s destination with Segment will require unique mapping of the Internal Data Source fields. Customers should contact their Selligent Relationship Manager so we can work with them to configure the mapping to best meet their needs. ### Example Internal Data Source Schema @@ -108,3 +99,5 @@ style='font:7.0pt "Times New Roman"'>      acct_

If you have any questions, please contact your Selligent Relationship Manager for assistance.

+ +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/sendwithus/index.md b/connections/destinations/catalog/sendwithus/index.md index e7985e4cefe..ba54b75a47b 100644 --- a/connections/destinations/catalog/sendwithus/index.md +++ b/connections/destinations/catalog/sendwithus/index.md @@ -19,3 +19,5 @@ When you call identify from one of our libraries, this will create a customer in ## Track To see your [`track`](/docs/spec/track) events in Sendwithus, ensure that you have first created a Segment.com integration under Automation > Triggers. If you select 'Add Trigger' and select the Segment Event Name dropdown, you'll see a list of event names that you have sent through. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/shareasale/index.md b/connections/destinations/catalog/shareasale/index.md index bd030bbdc9f..6e2719cdb3b 100644 --- a/connections/destinations/catalog/shareasale/index.md +++ b/connections/destinations/catalog/shareasale/index.md @@ -21,3 +21,5 @@ ShareASale only supports the event "Order Completed", which requires the followi - `orderId` - `total` or `subtotal` - an optional `repeat` property to signify whether a customer has bought from you before. Valid values for this property are `true` or `false`. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/smyte/index.md b/connections/destinations/catalog/smyte/index.md index 2cbceb931c2..cad2fb3e27d 100644 --- a/connections/destinations/catalog/smyte/index.md +++ b/connections/destinations/catalog/smyte/index.md @@ -43,3 +43,5 @@ This event helps Smyte identify whether the user is suspicious. ## Screen This event also helps Smyte identify whether the user is suspicious. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/sparkpage/index.md b/connections/destinations/catalog/sparkpage/index.md index 7e014cc4a04..0a6267c6c7d 100644 --- a/connections/destinations/catalog/sparkpage/index.md +++ b/connections/destinations/catalog/sparkpage/index.md @@ -26,3 +26,5 @@ All other traits will be sent to SparkPage as custom attributes. ## Track When you track an event, we will send that event to SparkPage as a custom API event. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/stripe-radar/index.md b/connections/destinations/catalog/stripe-radar/index.md index 1dd63e8243d..14d787b84af 100644 --- a/connections/destinations/catalog/stripe-radar/index.md +++ b/connections/destinations/catalog/stripe-radar/index.md @@ -7,3 +7,5 @@ title: Stripe Radar In order to use Stripe Radar, all you have to do is enable it in your Segment destinations page and enter your **API Key**! Read more about Stripe Radar in their [official website](https://stripe.com/radar). After we initialize Stripe Radar, we will call `window.Stripe.setPublishableKey();`. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/swrve/index.md b/connections/destinations/catalog/swrve/index.md index 1dd2b88672c..ca3fbdc9a40 100644 --- a/connections/destinations/catalog/swrve/index.md +++ b/connections/destinations/catalog/swrve/index.md @@ -68,19 +68,19 @@ No further action is required to integrate in-app messages or Conversations, whi 1. Add this line to your `Podfile`: - ``` + ```objc pod 'Segment-Swrve' ``` 2. Register the integration. To do this, import the Swrve integration in your `AppDelegate`: - ``` + ```objc #import ``` And add the following lines: - ``` + ```objc NSString *const SEGMENT_WRITE_KEY = @"..."; SEGAnalyticsConfiguration *config = [SEGAnalyticsConfiguration configurationWithWriteKey:SEGMENT_WRITE_KEY]; @@ -125,3 +125,5 @@ All other traits will be sent to Swrve as custom user properties. Traits will be ## Track When you `track` an event, we will send that event directly to Swrve as a custom event. Event properties will be sent to Swrve as event payloads. Properties will be converted to strings before sending. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/tableau/index.md b/connections/destinations/catalog/tableau/index.md index d238f308024..e84a1309a51 100644 --- a/connections/destinations/catalog/tableau/index.md +++ b/connections/destinations/catalog/tableau/index.md @@ -21,3 +21,5 @@ You may get an error that looks like the below. If so, fear not! You just need t ![](images/tableausetup2.png) You'll have to close out of Tableau as you set up the necessary drivers. Once those are installed, restart Tableau, repeat the getting started steps. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/taplytics/index.md b/connections/destinations/catalog/taplytics/index.md index 53caf30dbfa..bc6e5a4663a 100644 --- a/connections/destinations/catalog/taplytics/index.md +++ b/connections/destinations/catalog/taplytics/index.md @@ -32,3 +32,5 @@ This will send the event to Taplytics with the associated properties. If you inc ## Reset If your app supports the ability for a user to logout and login with a new identity, then you’ll need to call reset in your mobile app. Here we will call Taplytic's resetUser implementation to ensure the user information remains consistent. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/tealium-audience-stream/index.md b/connections/destinations/catalog/tealium-audience-stream/index.md index b675ed0695c..a3af25eb113 100644 --- a/connections/destinations/catalog/tealium-audience-stream/index.md +++ b/connections/destinations/catalog/tealium-audience-stream/index.md @@ -16,3 +16,5 @@ Segment `track` events will pass through to Tealium AudienceStream as `link` eve ## Page / Screen Segment `page` and `screen` events will pass through to Tealium AudienceStream as `view` events. Any event `properties` and the `context` object will be passed as part of the payload. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/totango/index.md b/connections/destinations/catalog/totango/index.md index d5593d15c43..7aa2d5f0688 100644 --- a/connections/destinations/catalog/totango/index.md +++ b/connections/destinations/catalog/totango/index.md @@ -128,3 +128,5 @@ analytics.identify({ } }); ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/track-js/index.md b/connections/destinations/catalog/track-js/index.md index 073bc5cf66d..2685cc5973f 100644 --- a/connections/destinations/catalog/track-js/index.md +++ b/connections/destinations/catalog/track-js/index.md @@ -26,3 +26,5 @@ analytics.ready(function(){ ``` Note that the `userId` parameter is automatically determined. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/tractionboard/index.md b/connections/destinations/catalog/tractionboard/index.md index 289f426da57..e5136b0b9e5 100644 --- a/connections/destinations/catalog/tractionboard/index.md +++ b/connections/destinations/catalog/tractionboard/index.md @@ -39,3 +39,5 @@ With this method we will change the id to a certain user saving the old one as a ## Screen It's the same that the page method. Currently we don't support mobile apps, but we can get events from them. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/tray.io/index.md b/connections/destinations/catalog/tray.io/index.md index 905b684a40d..c73ab460272 100644 --- a/connections/destinations/catalog/tray.io/index.md +++ b/connections/destinations/catalog/tray.io/index.md @@ -10,7 +10,7 @@ You can target up to 10 discrete tray workflows from within Segment. ## Message Types Tray supports all message types. You can filter the message type when you configure the trigger within tray. -![](./images/tray-types.png) +![](images/tray-types.png) ### Delete @@ -24,4 +24,6 @@ The payload will consist of: In order to receive and process the message, we recommend starting with an "All Message Types" filter, and then removing all the default types and adding `"delete"` manually. We're working with tray to add a dedicated `"delete"` message type filter in the dropdown pictured above. -![](./images/tray-delete-setup.gif) +![](images/tray-delete-setup.gif) + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/treasure-data/index.md b/connections/destinations/catalog/treasure-data/index.md index 61deaa6b51f..601aa59b018 100644 --- a/connections/destinations/catalog/treasure-data/index.md +++ b/connections/destinations/catalog/treasure-data/index.md @@ -36,3 +36,5 @@ A table with all of your screen method calls. This table will include all of the ### source.event_name For track calls, each event like `Signed Up` or `Order Completed` also has it's own table, with columns for each of the event's distinct properties. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/twitter-ads/index.md b/connections/destinations/catalog/twitter-ads/index.md index 283f72bd65b..2d6a2932283 100644 --- a/connections/destinations/catalog/twitter-ads/index.md +++ b/connections/destinations/catalog/twitter-ads/index.md @@ -368,3 +368,5 @@ window.twq('track', 'AddPaymentInfo', {}); ## Troubleshooting {% include content/client-side-script-unverified.md %} + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/urban-airship/index.md b/connections/destinations/catalog/urban-airship/index.md index 9b2ca22779f..ffd85a557d1 100644 --- a/connections/destinations/catalog/urban-airship/index.md +++ b/connections/destinations/catalog/urban-airship/index.md @@ -27,56 +27,56 @@ or setting up automation rules. 1) Include the Urban Airship dependency in the project’s build.gradle file: - repositories { - ... - - maven { - url "https://urbanairship.bintray.com/android" - } - } - - - dependencies { - ... - - // Urban Airship SDK - compile 'com.urbanairship.android:segment-integration:1.0.+' - } +```java +repositories { + ... + maven { + url "https://urbanairship.bintray.com/android" + } +} +dependencies { + ... + // Urban Airship SDK + compile 'com.urbanairship.android:segment-integration:1.0.+' +} +``` 2) Verify the `applicationId` is set in the project’s build.gradle file: - +```java android { ... - defaultConfig { ... - applicationId "com.example.application" } } +``` 3) Add the Urban Airship Destination factory: +```java Analytics analytics = new Analytics.Builder(context, writeKey) .use(UrbanAirshipIntegration.FACTORY) ... .build(); - +``` ### Enabling user notifications Once the Urban Airship destination is ready, you can enable user notifications with the following: - analytics.onIntegrationReady(UrbanAirshipIntegration.URBAN_AIRSHIP_KEY, new Analytics.Callback() { - @Override - public void onReady(Object instance) { - UAirship airship = (UAirship) instance; - airship.getPushManager().setUserNotificationsEnabled(true); - } - }); +```js +analytics.onIntegrationReady(UrbanAirshipIntegration.URBAN_AIRSHIP_KEY, new Analytics.Callback() { + @Override + public void onReady(Object instance) { + UAirship airship = (UAirship) instance; + airship.getPushManager().setUserNotificationsEnabled(true); + } + }); +``` ## iOS @@ -90,23 +90,29 @@ Once the Urban Airship destination is ready, you can enable user notifications w 2) Use the Urban Airship Destination: - SEGAnalyticsConfiguration *config = [SEGAnalyticsConfiguration configurationWithWriteKey:@"YOUR_WRITE_KEY"]; - - [config use:[SEGUrbanAirshipIntegrationFactory instance]]; + ```objc + SEGAnalyticsConfiguration *config = [SEGAnalyticsConfiguration configurationWithWriteKey:@"YOUR_WRITE_KEY"]; - [SEGAnalytics setupWithConfiguration:config]; + [config use:[SEGUrbanAirshipIntegrationFactory instance]]; + [SEGAnalytics setupWithConfiguration:config]; + ``` ### Enabling user notifications Once the Urban Airship destination is ready, you can enable user notifications with the following: +```objc [UAirship push].userPushNotificationsEnabled = YES; - +``` To listen for when the Urban Airship destination is ready, listen for the `SEGAnalyticsIntegrationDidStart` event in `NSNotificationCenter`: - [[[NSNotificationCenter defaultCenter] addObserver:self - selector:@selector(airshipReady) - name:@"io.segment.analytics.integration.did.start" - object:[SEGUrbanAirshipIntegrationFactory instance].key]; +```objc +[[[NSNotificationCenter defaultCenter] addObserver:self + selector:@selector(airshipReady) + name:@"io.segment.analytics.integration.did.start" + object:[SEGUrbanAirshipIntegrationFactory instance].key]; +``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/userengage/index.md b/connections/destinations/catalog/userengage/index.md index 7ef300e8484..1629825b8eb 100644 --- a/connections/destinations/catalog/userengage/index.md +++ b/connections/destinations/catalog/userengage/index.md @@ -60,3 +60,5 @@ Any custom traits of the `.group()` call will follow same logic as `Identify` me Verify that API key your using in Segment is not revoked by going to **App settings > Advanced > Segment API keys** at [app.userengage.com](https://app.userengage.com). If problem still persist verify that domain the request from is trusted. You can edit domains you trust by going to **App settings > Advanced > Domains** at [app.userengage.com](https://app.userengage.com). + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/vero/index.md b/connections/destinations/catalog/vero/index.md index 36e901ffa2f..ac04ad66f6f 100644 --- a/connections/destinations/catalog/vero/index.md +++ b/connections/destinations/catalog/vero/index.md @@ -120,3 +120,5 @@ analytics.identify('324LKJF', { } }) ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/watsi/index.md b/connections/destinations/catalog/watsi/index.md index af73479085b..61dc5e8de21 100644 --- a/connections/destinations/catalog/watsi/index.md +++ b/connections/destinations/catalog/watsi/index.md @@ -61,3 +61,5 @@ Here's an example `track` call (omitting common fields) with all the required pr } } ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/webengage/index.md b/connections/destinations/catalog/webengage/index.md index b13718e1d06..aff9b5b42f4 100644 --- a/connections/destinations/catalog/webengage/index.md +++ b/connections/destinations/catalog/webengage/index.md @@ -117,3 +117,5 @@ Include the following rules in your ProGuard file. -keep class com.webengage.sdk.android.**{*;} -dontwarn com.webengage.sdk.android.** ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/whale-alerts/index.md b/connections/destinations/catalog/whale-alerts/index.md index f5f1bc30104..dca81fef410 100644 --- a/connections/destinations/catalog/whale-alerts/index.md +++ b/connections/destinations/catalog/whale-alerts/index.md @@ -59,3 +59,5 @@ Once Whalr has enough information to move beyond the out-of-box intelligence, ou ## Contact Whalr [Contact us](mailto:customersuccess@whalr.com) if you need additional support. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/wishpond/index.md b/connections/destinations/catalog/wishpond/index.md index 7c1dabb7fa2..f119ca01cee 100644 --- a/connections/destinations/catalog/wishpond/index.md +++ b/connections/destinations/catalog/wishpond/index.md @@ -78,3 +78,5 @@ Make sure you have copied the right keys from Wishpond’s [“API Keys” dialo [Analytics.js]: https://segment.com/docs/libraries/analytics.js/ [ci-link]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond [ci-badge]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond.svg?style=svg + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/woopra/index.md b/connections/destinations/catalog/woopra/index.md index 6e72fd7bba1..2cb39f1a2ba 100644 --- a/connections/destinations/catalog/woopra/index.md +++ b/connections/destinations/catalog/woopra/index.md @@ -94,3 +94,5 @@ If you are seeing split user profiles, the most likely culprit is that you are c Calling `.identify()` in the browser will effectively map the `userId` you passed in with the `wooTracker` cookie value. So in the event that you call `.identify()` on the server side first, you **MUST** call `.identify()` on the client side as well to tie the `wooTracker` cookie to that `userId`. Doing so will ensure that duplicate profiles are not created. + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/youbora/index.md b/connections/destinations/catalog/youbora/index.md index f469b8b8b19..7d74d217da4 100644 --- a/connections/destinations/catalog/youbora/index.md +++ b/connections/destinations/catalog/youbora/index.md @@ -303,7 +303,7 @@ See the below example for what a working implementation looks like: html5: [ { player: 'html5-player', - options: {} + options: {}} ] } } @@ -314,3 +314,5 @@ See the below example for what a working implementation looks like: ``` + +{% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/zaius/index.md b/connections/destinations/catalog/zaius/index.md index 59bbe802ce1..e2e4c84926a 100644 --- a/connections/destinations/catalog/zaius/index.md +++ b/connections/destinations/catalog/zaius/index.md @@ -36,3 +36,5 @@ Zaius will be able to process any of your track events and properties sent throu ### Page The Zaius platform processes all of the page events passed into the Segment as well. + +{% include content/integration-foot.md %} diff --git a/todo.txt b/todo.txt index 68f04bb7691..b0c0baab2f7 100644 --- a/todo.txt +++ b/todo.txt @@ -1,67 +1,2 @@ - redirects - Find and import google-cloud-storage -- add {% include content/integration-foot.md %} to anything that didn't have rewrite: true - - -nanigans -nielsen-dcr -nudgespot -olark -omniture -onesignal -optimizely-full-stack -optimizely-web -outbound -pardot -perimeterx -personas-facebook-ads -pingdom -pinterest-tag -piwik -planhat -pointillist -postgres -preact -primer -promoter.io -quantcast -ramen -relay -repeater -responsys -rollbar -route -saasquatch -sailthru -salesforce -salesforce-live-agent -salesforce-marketing-cloud -salesmachine -satismeter -seg -selligent -sendwithus -shareasale -smyte -sparkpage -stripe-radar -swrve -tableau -taplytics -tealium-audience-stream -totango -track-js -tractionboard -tray.io -treasure-data -twitter-ads -urban-airship -userengage -vero -watsi -webengage -whale-alerts -wishpond -woopra -youbora -zaius From dba019a36c4432e588e9a489b8ed84011a6009e1 Mon Sep 17 00:00:00 2001 From: sanscontext Date: Tue, 13 Aug 2019 16:45:35 -0700 Subject: [PATCH 5/6] remove smart quotes ugh Signed-off-by: sanscontext --- _includes/content/spec-field-page-name.md | 2 +- _templates/destinations.example.yml | 12 +-- .../catalog/activecampaign/index.md | 4 +- .../catalog/adobe-analytics/index.md | 2 +- .../catalog/adobe-target/index.md | 2 +- .../destinations/catalog/adroll/index.md | 4 +- .../destinations/catalog/alexa/index.md | 4 +- .../catalog/amazon-lambda/index.md | 4 +- .../catalog/amazon-personalize/index.md | 10 +-- .../destinations/catalog/appcues/index.md | 2 +- .../destinations/catalog/appsflyer/index.md | 4 +- .../destinations/catalog/apptimize/index.md | 4 +- .../destinations/catalog/auryc/index.md | 2 +- .../destinations/catalog/autopilothq/index.md | 2 +- .../destinations/catalog/bing-ads/index.md | 4 +- .../destinations/catalog/braze/index.md | 6 +- .../destinations/catalog/bugherd/index.md | 4 +- .../destinations/catalog/bugsnag/index.md | 4 +- .../catalog/clearbit-enrichment/index.md | 4 +- .../catalog/clearbit-reveal/index.md | 4 +- .../destinations/catalog/clicky/index.md | 4 +- .../destinations/catalog/delighted/index.md | 4 +- .../destinations/catalog/drift/index.md | 2 +- .../catalog/facebook-app-events/index.md | 4 +- .../facebook-offline-conversions/index.md | 4 +- .../index.md | 2 +- .../index.md | 2 +- .../index.md | 6 +- .../index.md | 4 +- .../index.md | 2 +- .../destinations/catalog/firebase/index.md | 6 +- .../destinations/catalog/flurry/index.md | 4 +- .../destinations/catalog/foxmetrics/index.md | 4 +- .../catalog/freshmarketer/index.md | 2 +- .../destinations/catalog/fullstory/index.md | 4 +- .../catalog/gainsight-px/index.md | 4 +- .../destinations/catalog/gainsight/index.md | 2 +- .../destinations/catalog/goedle/index.md | 4 +- .../catalog/google-tag-manager/index.md | 4 +- .../destinations/catalog/heap/index.md | 4 +- .../destinations/catalog/help-scout/index.md | 2 +- .../destinations/catalog/hotjar/index.md | 4 +- .../destinations/catalog/hubspot/index.md | 4 +- .../destinations/catalog/inspectlet/index.md | 4 +- .../destinations/catalog/intercom/index.md | 4 +- .../destinations/catalog/iterable/index.md | 2 +- .../destinations/catalog/kissmetrics/index.md | 4 +- .../destinations/catalog/klaviyo/index.md | 4 +- .../destinations/catalog/kochava/index.md | 2 +- .../destinations/catalog/leanplum/index.md | 4 +- .../destinations/catalog/mailchimp/index.md | 4 +- .../destinations/catalog/mailjet/index.md | 2 +- .../destinations/catalog/mammoth/index.md | 2 +- .../destinations/catalog/marketo-v2/index.md | 4 +- .../destinations/catalog/mixpanel/index.md | 2 +- .../destinations/catalog/moengage/index.md | 2 +- .../destinations/catalog/mouseflow/index.md | 4 +- .../destinations/catalog/msg91/index.md | 4 +- .../destinations/catalog/new-relic/index.md | 4 +- .../destinations/catalog/outbound/index.md | 2 +- .../destinations/catalog/pendo/index.md | 8 +- .../destinations/catalog/perimeterx/index.md | 8 +- .../destinations/catalog/personyze/index.md | 2 +- .../destinations/catalog/quanticmind/index.md | 2 +- .../catalog/quora-conversion-pixel/index.md | 4 +- .../destinations/catalog/refersion/index.md | 4 +- .../catalog/salesforce-dmp/index.md | 6 +- .../salesforce-marketing-cloud/index.md | 2 +- .../destinations/catalog/satismeter/index.md | 2 +- .../destinations/catalog/sentry/index.md | 4 +- .../destinations/catalog/simplereach/index.md | 4 +- .../destinations/catalog/singular/index.md | 2 +- .../destinations/catalog/slicingdice/index.md | 14 +-- .../destinations/catalog/snapengage/index.md | 4 +- .../destinations/catalog/sparkpage/index.md | 2 +- .../destinations/catalog/trackier/index.md | 2 +- .../destinations/catalog/tune/index.md | 4 +- .../destinations/catalog/tv-squared/index.md | 4 +- .../destinations/catalog/userlike/index.md | 4 +- .../destinations/catalog/userlist/index.md | 4 +- .../catalog/visual-website-optimizer/index.md | 10 +-- .../destinations/catalog/webhooks/index.md | 4 +- .../destinations/catalog/wishpond/index.md | 4 +- .../destinations/catalog/wootric/index.md | 4 +- .../catalog/yandex-metrica/index.md | 4 +- .../destinations/catalog/zendesk/index.md | 4 +- .../destinations/catalog/zopim/index.md | 4 +- .../cloud-apps/activecampaign/index.md | 12 +-- .../cloud-apps/amplitude-cohorts/index.md | 4 +- .../catalog/cloud-apps/autopilothq/index.md | 2 +- .../catalog/cloud-apps/blueshift/index.md | 4 +- .../sources/catalog/cloud-apps/braze/index.md | 2 +- .../catalog/cloud-apps/chatlio/index.md | 2 +- .../catalog/cloud-apps/customer.io/index.md | 2 +- .../catalog/cloud-apps/delighted/index.md | 2 +- .../sources/catalog/cloud-apps/drip/index.md | 2 +- .../cloud-apps/facebook-lead-ads/index.md | 2 +- .../cloud-apps/factual-engine/index.md | 2 +- .../catalog/cloud-apps/iterable/index.md | 2 +- .../catalog/cloud-apps/klaviyo/index.md | 2 +- .../catalog/cloud-apps/klenty/index.md | 2 +- .../catalog/cloud-apps/looker/index.md | 2 +- .../catalog/cloud-apps/mailjet/index.md | 2 +- .../catalog/cloud-apps/mandrill/index.md | 2 +- .../catalog/cloud-apps/nudgespot/index.md | 2 +- .../catalog/cloud-apps/provesource/index.md | 2 +- .../salesforce-marketing-cloud/index.md | 2 +- .../catalog/cloud-apps/selligent/index.md | 2 +- .../sources/catalog/cloud-apps/vero/index.md | 2 +- .../catalog/cloud-apps/zendesk/index.md | 4 +- .../sources/catalog/mobile/android/index.md | 4 +- connections/sources/catalog/ott/roku/index.md | 86 +++++++++---------- .../catalog/website/analytics.js/index.md | 2 +- connections/sources/cross-domain/index.md | 2 +- .../sources/faq/cloud-source-object.md | 2 +- .../sources/faq/measure-advertising-funnel.md | 2 +- connections/sources/faq/native-mobile-spec.md | 4 +- .../sources/faq/tracking-plan-example.md | 2 +- connections/sources/guides/tumblr/index.md | 2 +- connections/sources/index.md | 17 ++++ connections/sources/visual-tagger/index.md | 2 +- .../warehouses/catalog/amazon-s3/index.md | 2 +- .../warehouses/catalog/bigquery/index.md | 2 +- connections/warehouses/catalog/db2/index.md | 2 +- .../warehouses/catalog/postgres/index.md | 2 +- .../warehouses/catalog/redshift/index.md | 6 +- .../warehouses/catalog/snowflake/index.md | 8 +- connections/warehouses/choose-warehouse.md | 2 +- connections/warehouses/redshift-faq.md | 2 +- guides/account-management/add-team-member.md | 2 +- .../move-source-workspace.md | 4 +- .../collect-on-client-or-server.md | 6 +- .../collect-pageviews-serverside.md | 4 +- .../best-practices/cross-channel-tracking.md | 20 ++--- .../best-practices/ecommerce-tracking-plan.md | 4 +- guides/best-practices/forecast-with-sql.md | 12 +-- .../best-practices/measure-marketing-roi-2.md | 6 +- .../best-practices/measure-marketing-roi.md | 6 +- guides/best-practices/test-connections.md | 8 +- .../user-deletion-suppression.md | 36 ++++---- .../best-practices/whats-a-tracking-plan.md | 8 +- guides/general/segment-vs-tag-managers.md | 2 +- guides/general/what-is-segment.md | 2 +- guides/general/whats-a-warehouse.md | 2 +- .../miscellaneous/destination-data-control.md | 24 +++--- guides/setup/find-writekey.md | 2 +- .../cancelation-final-bill.md | 2 +- .../discounts-for-startups-npos.md | 2 +- guides/usage-and-billing/event-vs-object.md | 2 +- .../mtu-count-vs-other-tools.md | 2 +- guides/usage-and-billing/startup-program.md | 2 +- .../usage-and-billing/trial-for-paid-plans.md | 4 +- legal/first-access-beta-preview.md | 14 +-- legal/privacy-2017.md | 16 ++-- legal/privacy.md | 12 +-- legal/terms-2016.md | 44 +++++----- partners/checklist.md | 6 +- partners/plugins.md | 2 +- partners/subscriptions.md | 4 +- personas/computed-traits.md | 2 +- personas/sql-traits.md | 4 +- protocols/schema.md | 8 +- segment-app/audit-trail.md | 2 +- segment-app/secure-password.md | 2 +- segment-app/sso.md | 20 ++--- 165 files changed, 434 insertions(+), 417 deletions(-) diff --git a/_includes/content/spec-field-page-name.md b/_includes/content/spec-field-page-name.md index 3eddaad4a6f..2099172ea9f 100644 --- a/_includes/content/spec-field-page-name.md +++ b/_includes/content/spec-field-page-name.md @@ -2,6 +2,6 @@ `name` *optional* String Name of the page -

For example, most sites have a “Signup” page that can be useful to tag, so you can see users as they move through your funnel.

+

For example, most sites have a "Signup" page that can be useful to tag, so you can see users as they move through your funnel.

\ No newline at end of file diff --git a/_templates/destinations.example.yml b/_templates/destinations.example.yml index f7c2d77efcd..bd053183238 100644 --- a/_templates/destinations.example.yml +++ b/_templates/destinations.example.yml @@ -11873,7 +11873,7 @@ destinations: required: false string_validators: regexp: '' - description: To find your API key, log into Pendo and navigate to “your user name” + description: To find your API key, log into Pendo and navigate to "your user name" > Site settings > Basic Information > API key. If your account has not fully been set up yet, you can see the API key inside of the code snippet on the Pendo setup page. @@ -14653,11 +14653,11 @@ destinations: required: true string_validators: regexp: "^.{8,}$" - description: To find your key, log into Split and navigate to “Admin Settings” - > “Integrations” > select your desired workspace > “Segment”. There you can + description: To find your key, log into Split and navigate to "Admin Settings" + > "Integrations" > select your desired workspace > "Segment". There you can find the key for each configured integration. If you don’t have an integration - configured, be sure to configure your integration in the section “Configure - as a destination in Segment” and click save to generate a key. For more information, + configured, be sure to configure your integration in the section "Configure + as a destination in Segment" and click save to generate a key. For more information, learn more in Split’s [integration documentation](https://segment.com/docs/destinations/split/). settings: [] - name: catalog/destinations/stitch-data @@ -15562,7 +15562,7 @@ destinations: required: true string_validators: regexp: "^[a-zA-Z0-9]*$" - description: Drop in the “Integration Key” into your Segment Settings UI which + description: Drop in the "Integration Key" into your Segment Settings UI which you can find on https://businessapp.b2b.trustpilot.com/#/ecommerce/segment settings: [] - name: catalog/destinations/tune diff --git a/connections/destinations/catalog/activecampaign/index.md b/connections/destinations/catalog/activecampaign/index.md index ef22ce04c84..5548c63e328 100644 --- a/connections/destinations/catalog/activecampaign/index.md +++ b/connections/destinations/catalog/activecampaign/index.md @@ -13,8 +13,8 @@ This document was last updated on March 27, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Active Campaign” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Active Campaign" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your API URL and API Key which can be found in your ActiveCampaign UI Settings page under the Developer tab. 4. Since the Segment ActiveCampaign destination integration is 100% handled through Segment, you don't need to install ActiveCampaign site tracking or event tracking Javascript code. diff --git a/connections/destinations/catalog/adobe-analytics/index.md b/connections/destinations/catalog/adobe-analytics/index.md index 1d823182540..3926d841228 100644 --- a/connections/destinations/catalog/adobe-analytics/index.md +++ b/connections/destinations/catalog/adobe-analytics/index.md @@ -451,7 +451,7 @@ You can either send the property value as a string (ie. `'brady'`) or as an arra ### Merchandising Events -The Merchandising Events settings allow you to set eVars and events on a per-product basis within the “products” string, and support increment and currency events. This provides robust product string support, which you can read more about [here](https://marketing.adobe.com/resources/help/en_US/sc/implement/products.html). +The Merchandising Events settings allow you to set eVars and events on a per-product basis within the "products" string, and support increment and currency events. This provides robust product string support, which you can read more about [here](https://marketing.adobe.com/resources/help/en_US/sc/implement/products.html). The setting operates as follows: diff --git a/connections/destinations/catalog/adobe-target/index.md b/connections/destinations/catalog/adobe-target/index.md index de600956848..934eb30c300 100644 --- a/connections/destinations/catalog/adobe-target/index.md +++ b/connections/destinations/catalog/adobe-target/index.md @@ -121,7 +121,7 @@ document.addEventListener(adobe.target.event.REQUEST_SUCCEEDED, function() { ### Preventing Page Flicker Page flicker may occur when default content momentarily displays to a visitor -prior to the A/B “activity” content replacing it. One approach to preventing +prior to the A/B "activity" content replacing it. One approach to preventing page flicker in conjunction with Segment would be to create a global mbox. Adobe will automatically set the HTML body style opacity to 0, which keeps the page content hidden while allowing the browser to still execute page load. After a diff --git a/connections/destinations/catalog/adroll/index.md b/connections/destinations/catalog/adroll/index.md index f7b0f0347dd..8a009cd5df2 100644 --- a/connections/destinations/catalog/adroll/index.md +++ b/connections/destinations/catalog/adroll/index.md @@ -17,8 +17,8 @@ This document was last updated on January 26, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Adroll" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Locate both your AdRoll Advertiser ID and Pixel ID in AdRoll's "Audience" tab, "AdRoll Pixel" section. Click on "View Pixel". Your Advertiser ID will be listed beside `adroll_adv_id` and your AdRoll Pixel will be listed beside `adroll_pix_id`. ![](images/adroll-pixel.png) diff --git a/connections/destinations/catalog/alexa/index.md b/connections/destinations/catalog/alexa/index.md index 5edfcf55142..4b92458ade9 100644 --- a/connections/destinations/catalog/alexa/index.md +++ b/connections/destinations/catalog/alexa/index.md @@ -10,8 +10,8 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Alexa” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Alexa" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Fill in your "Account ID" which you can find in the Alexa Javascript snippet. It appears as atrk_acct: 'XXXXXXX'. 4. Fill in your "Domain" which you can find in the Alexa Javascript snippet. It appears as domain: 'example.com'. 5. In about 5-10 minutes the CDN will be updated and the Alexa Javascript snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/amazon-lambda/index.md b/connections/destinations/catalog/amazon-lambda/index.md index c8a754e8055..8c2a6abfaa2 100644 --- a/connections/destinations/catalog/amazon-lambda/index.md +++ b/connections/destinations/catalog/amazon-lambda/index.md @@ -133,7 +133,7 @@ While setting up the new role, add the policy you created in the previous step. Finish with any other setup items you may want (like `tags`). Once that’s complete, search for and click on your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home). -Select the “Trust Relationships” tab, then click the “Edit trust relationship” button. +Select the "Trust Relationships" tab, then click the "Edit trust relationship" button. ![](images/LambdaTrustRelationship.png) @@ -170,7 +170,7 @@ If you have multiple Source’s using this Role, replace the `sts:ExternalId` se ## Configure Segment Lambda Destination -Search for “Lambda" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the AWS Lambda settings. +Search for "Lambda" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the AWS Lambda settings. ## FAQ diff --git a/connections/destinations/catalog/amazon-personalize/index.md b/connections/destinations/catalog/amazon-personalize/index.md index 1ca70ba1502..e8eca2f5fa2 100644 --- a/connections/destinations/catalog/amazon-personalize/index.md +++ b/connections/destinations/catalog/amazon-personalize/index.md @@ -590,7 +590,7 @@ The "Import user-item interaction data" step is displayed next. To complete this For the "IAM service role", select "Create a new role" from the dropdown. In the next pop-up, we recommend listing your bucket name in the "Specific S3 buckets" option, but you're free to choose the option that best suits your needs. -Next you will need the location of the CSV file you generated in the earlier steps. This needs to be configured in the “Data Location” field on this screen. +Next you will need the location of the CSV file you generated in the earlier steps. This needs to be configured in the "Data Location" field on this screen. ![](images/PersonalizeImportJob.png) @@ -692,7 +692,7 @@ While setting up the new role, add the policy you created in the previous step. Finish with any other setup items you may want (like `tags`). Once that’s complete, search for and click on your new roles from the [IAM home](https://console.aws.amazon.com/iam/home#/home). -Select the “Trust Relationships” tab, then click the “Edit trust relationship” button. +Select the "Trust Relationships" tab, then click the "Edit trust relationship" button. ![](images/LambdaTrustRelationship.png) @@ -868,7 +868,7 @@ Enter a name for your Event Tracker. You will need to configure a role for Personalize to that allows it to execute the tracker. This is the same as the execution role you defined earlier for Personalize: -Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess” +Often this is automatically included as a policy labelled "AmazonPersonalizeFullAccess" ``` { @@ -917,7 +917,7 @@ Often this is automatically included as a policy labelled "AmazonPersonalizeFull } ``` -This may be automatically included as policy “AmazonPersonalize-ExecutionPolicy-” +This may be automatically included as policy "AmazonPersonalize-ExecutionPolicy-" ``` { @@ -998,7 +998,7 @@ Your lambda is now ready to receive events from Segment. Next, you will need to Once your Lambda function is enabled, you can send it events from Segment using the Personalize Destination. -Search for “Amazon Personalize” in our catalog. Connect the destination to the source you created previously. Now you will be presented with the Amazon Personalize Settings. +Search for "Amazon Personalize" in our catalog. Connect the destination to the source you created previously. Now you will be presented with the Amazon Personalize Settings. We allow you to send each call type to a different Lambda. If you leave the Lambda field blank for a given call type, we won’t attempt to send any of those calls. diff --git a/connections/destinations/catalog/appcues/index.md b/connections/destinations/catalog/appcues/index.md index cc6104bbf85..796c593f829 100644 --- a/connections/destinations/catalog/appcues/index.md +++ b/connections/destinations/catalog/appcues/index.md @@ -116,6 +116,6 @@ lifecycle events that can be tracked: * `coachmarks_completed` To enable this feature, go to the Integrations Settings in Appcues and -click “Activate” under the Segment integration. +click "Activate" under the Segment integration. {% include content/integration-foot.md %} diff --git a/connections/destinations/catalog/appsflyer/index.md b/connections/destinations/catalog/appsflyer/index.md index 4ea4942a3d3..e873e43aa68 100644 --- a/connections/destinations/catalog/appsflyer/index.md +++ b/connections/destinations/catalog/appsflyer/index.md @@ -11,8 +11,8 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “AppsFlyer“ within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "AppsFlyer" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `AppsFlyer Dev Key`, which can be retrieved from the App Settings section of your AppsFlyer account. 4. Follow the instructions in the Github repos: [iOS SDK](https://github.com/AppsFlyerSDK/segment-appsflyer-ios) and [Android SDK](https://github.com/AppsFlyerSDK/AppsFlyer-Segment-Integration). 5. After you build and release to the app store, we start translating and sending your data to AppsFlyer automatically. diff --git a/connections/destinations/catalog/apptimize/index.md b/connections/destinations/catalog/apptimize/index.md index 332f30ea94e..33bafe114e0 100644 --- a/connections/destinations/catalog/apptimize/index.md +++ b/connections/destinations/catalog/apptimize/index.md @@ -10,8 +10,8 @@ This document was last updated on April 27, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “Apptimize“ within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "Apptimize" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Apptimize application key, the 31 character key which you can find in your [Apptimize app settings](https://apptimize.com/admin/settings/apps). 4. Depending on the mobile library you've selected, follow the below instructions to complete your setup. diff --git a/connections/destinations/catalog/auryc/index.md b/connections/destinations/catalog/auryc/index.md index 501bef91393..91816a9532e 100644 --- a/connections/destinations/catalog/auryc/index.md +++ b/connections/destinations/catalog/auryc/index.md @@ -11,7 +11,7 @@ _**NOTE:** The Auryc Destination is currently in beta, which means that they are {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for Auryc within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. 3. Add your Auryc site id in the destination settings. You can find this in Auryc by navigating to Project Settings > Web > and copying the value found on the line //cdn.auryc.com/auryc_siteid_here/container.js; 4. In about 5-10 minutes the CDN will be updated and Auryc snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/autopilothq/index.md b/connections/destinations/catalog/autopilothq/index.md index 0f07bf0aefa..d2c09b0788a 100644 --- a/connections/destinations/catalog/autopilothq/index.md +++ b/connections/destinations/catalog/autopilothq/index.md @@ -13,7 +13,7 @@ This document was last updated on October 12, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. + 1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "Autopilot" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your "API Key" from [here](https://login.autopilothq.com/login#settings/app-connections/segment-sync) or go to Autopilot: Settings -> App Connections -> Segment and copy/paste the API key which is listed there. 4. Once enabled 'identify' and 'track' calls will be sent to Autopilot. diff --git a/connections/destinations/catalog/bing-ads/index.md b/connections/destinations/catalog/bing-ads/index.md index a99e81a30dd..c3f307710ec 100644 --- a/connections/destinations/catalog/bing-ads/index.md +++ b/connections/destinations/catalog/bing-ads/index.md @@ -14,8 +14,8 @@ Before you can track conversions or target audiences, you need to create a UET t Once you have created the Tag ID, you can follow the steps below: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Bing Ads” within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Bing Ads" within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. 3. Drop in your Tag Id 4. In about 5-10 minutes the CDN will be updated and Bing Ads' snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/braze/index.md b/connections/destinations/catalog/braze/index.md index fe809d0e58c..e733265f24a 100644 --- a/connections/destinations/catalog/braze/index.md +++ b/connections/destinations/catalog/braze/index.md @@ -23,8 +23,8 @@ This document was last updated on June 13, 2018. If you notice any gaps, outdate {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Braze” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Braze" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, add the "API Key" which can be found in your Braze Dashboard under App Settings > Manage App Group. 4. You will also need to setup a new App Group REST API Key in the Braze Dashboard under App Settings > Developer Console > API Settings. Instructions can be found [here](https://www.braze.com/documentation/REST_API/#creating-and-managing-rest-api-keys). **Note:** For this App Group REST API Key, you will only need to select users.track endpoint under "User Data" 5. If you are implementing via Analytics.js, Segment will automatically load the [Braze Web SDK](https://www.braze.com/documentation/Web/). Otherwise, depending on the source you’ve selected, include Braze’s library by adding the following lines to your dependency configuration. @@ -326,7 +326,7 @@ The `inAppMessages` parameter will be an array of [`appboy.ab.InAppMessage`](htt ### Soft Push Prompts -1. Follow [step one](https://www.Braze.com/documentation/Web/#soft-push-prompts) to create a “Prime for Push” in-app messaging Campaign on the Braze dashboard. +1. Follow [step one](https://www.Braze.com/documentation/Web/#soft-push-prompts) to create a "Prime for Push" in-app messaging Campaign on the Braze dashboard. 2. Disable your [Automatically Send In-App Messages Destination setting](https://segment.com/docs/integrations/Braze/#settings). By default, it is enabled when you enable the Braze destination. diff --git a/connections/destinations/catalog/bugherd/index.md b/connections/destinations/catalog/bugherd/index.md index 93047e9aaba..e8973632177 100644 --- a/connections/destinations/catalog/bugherd/index.md +++ b/connections/destinations/catalog/bugherd/index.md @@ -9,8 +9,8 @@ This document was last updated on November 26, 2018. If you notice any gaps, out {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “BugHerd” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "BugHerd" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `API Key` as retrieved from the Install BugHerd tab on your BugHerd Project page. 4. Our CDN is updated within 5-10 minutes. Then our snippet will start asynchronously loading BugHerd onto your page. This means you should remove BugHerd's snippet from your page. 5. The BugHerd Destination doesn’t utilize any Segment API calls (e.g. identify, track, etc) so, once it's loaded, it’s good to go! Your BugHerd sidebar will begin appearing for your team. diff --git a/connections/destinations/catalog/bugsnag/index.md b/connections/destinations/catalog/bugsnag/index.md index 614c31726d0..c3d8ba6086e 100644 --- a/connections/destinations/catalog/bugsnag/index.md +++ b/connections/destinations/catalog/bugsnag/index.md @@ -19,8 +19,8 @@ This document was last updated on July 11th, 2018. If you notice any gaps, outda ### Web -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Bugsnag” within the Destinations Catalog and confirm the project you’d like to connect to +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Bugsnag" within the Destinations Catalog and confirm the project you’d like to connect to 3. Add your API key to your connection settings. You can find your API key in your Bugsnag dashboard under "Settings", which is located in the upper left-hand corner 4. We’ll automatically initialize Bugsnag's javascript script with your API key upon loading analytics.js diff --git a/connections/destinations/catalog/clearbit-enrichment/index.md b/connections/destinations/catalog/clearbit-enrichment/index.md index 73832ec2a41..003aca84f87 100644 --- a/connections/destinations/catalog/clearbit-enrichment/index.md +++ b/connections/destinations/catalog/clearbit-enrichment/index.md @@ -16,8 +16,8 @@ This document was last updated on April 20th, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Clearbit Enrichment” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Clearbit Enrichment" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment UI's destination settings, enter your Clearbit **secret** API key (note: it should start with "sk_"). You can find this in the API section of your [Clearbit dashboard](https://dashboard.clearbit.com/api). To verify that the destination has been set up correctly, check the Debugger section of your Segment Source. Assuming everything is as it should be, you should start seeing Clearbit Enrichment data populate in the `identify` events – click on the specific event you're interested in to see Clearbit Enrichment traits. These traits will now be available to other Segment destinations in your account. Notice that all Clearbit Enrichment traits are prefixed with `clearbit_` to ensure they don't conflict with existing traits. diff --git a/connections/destinations/catalog/clearbit-reveal/index.md b/connections/destinations/catalog/clearbit-reveal/index.md index 86fab218606..c2a647f71f8 100644 --- a/connections/destinations/catalog/clearbit-reveal/index.md +++ b/connections/destinations/catalog/clearbit-reveal/index.md @@ -17,8 +17,8 @@ This document was last updated on August 29, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} Setup within Segment: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Clearbit Reveal” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Clearbit Reveal" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, enter your Clearbit **secret** API key (note: it should start with "sk_"). You can find this in the API section of your [Clearbit dashboard](https://dashboard.clearbit.com/api). Setup within Clearbit: diff --git a/connections/destinations/catalog/clicky/index.md b/connections/destinations/catalog/clicky/index.md index cf61de2c63f..3a8f6180b66 100644 --- a/connections/destinations/catalog/clicky/index.md +++ b/connections/destinations/catalog/clicky/index.md @@ -14,8 +14,8 @@ This document was last updated on July 30th, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Clicky” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Clicky" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Site ID in the settings. You can find your Site ID under the Preferences of your account: ![Clicky Preferences](images/clicky-settings.png) 4. We’ll automatically initialize Clicky's script with your Site ID upon loading analytics.js. diff --git a/connections/destinations/catalog/delighted/index.md b/connections/destinations/catalog/delighted/index.md index db11e8dccec..d3faf5b4056 100644 --- a/connections/destinations/catalog/delighted/index.md +++ b/connections/destinations/catalog/delighted/index.md @@ -15,8 +15,8 @@ This document was last updated on January 29, 2019. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your {{integration.name}} "API Key" in Segment's Settings UI. You can retrieve this from your {{integration.name}} Settings > API > Your API Key. It should look like "T8jtGnuYaNerDedVMYrcgn1dRdywfGOl". 4. If you're using Segment's client-side `analytics.js` library, we asynchronously load {{integration.name}}'s Javascript library onto the page and the CDN will be updated in 5-10 minutes. diff --git a/connections/destinations/catalog/drift/index.md b/connections/destinations/catalog/drift/index.md index c5a8153c8fa..7ecb5222416 100644 --- a/connections/destinations/catalog/drift/index.md +++ b/connections/destinations/catalog/drift/index.md @@ -20,7 +20,7 @@ This document was last updated on January 25, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. + 1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "Drift" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `API Key` and `Embed ID` as obtained from your Drift account (if Drift account not accessible yet, please [email the team](mailto:team@drift.com) to get a link for the Drift account creation). 4. If you're using analytics.js and 'identify' users by default, Drift will work automatically. If you don’t have analytics.js setup, after enabling the Drift destination in Segment, you must 'identify' users in order for Drift to display in your product. diff --git a/connections/destinations/catalog/facebook-app-events/index.md b/connections/destinations/catalog/facebook-app-events/index.md index 1cb9b6ee618..56f1556b07a 100644 --- a/connections/destinations/catalog/facebook-app-events/index.md +++ b/connections/destinations/catalog/facebook-app-events/index.md @@ -14,8 +14,8 @@ This document was last updated on October 04, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Facebook App Events” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Facebook App Events" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Facebook App ID which can be retrieved from your [Facebook Apps dashboard](https://developers.facebook.com/apps/). 4. Once you turn on the Facebook App Events integration in your app's Segment project, we'll start sending `track` data to Facebook's App Events endpoints. diff --git a/connections/destinations/catalog/facebook-offline-conversions/index.md b/connections/destinations/catalog/facebook-offline-conversions/index.md index 618b69d8990..07f7c85b169 100644 --- a/connections/destinations/catalog/facebook-offline-conversions/index.md +++ b/connections/destinations/catalog/facebook-offline-conversions/index.md @@ -13,9 +13,9 @@ This document was last updated on April 24, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “Facebook Offline Conversions” within the Destinations Catalog and confirm the Source you’d like to connect to. +2. Search for "Facebook Offline Conversions" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Authorize Segment to send data on your behalf by connecting through OAuth: diff --git a/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md b/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md index 103f86e24fa..9b123e555a7 100644 --- a/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md +++ b/connections/destinations/catalog/faq/how-do-i-automate-multi-channel-re-engagement-campaigns/index.md @@ -29,7 +29,7 @@ Before we proceed, it’s important to register for these tools and enable them When you send tracking data from your app or website to Segment, Segment will send the same data to all of your tools. Segment also collects key messaging events like Push Notification Opened and Email Opened from AppBoy and Customer.io, respectively, and sends that to other tools. By defining cohorts based on these events, you can create dynamic campaign audiences, to which customers can add and remove themselves. -In each of your destinations—Appboy, Facebook, Customer.io, AdRoll—you can create custom campaigns to show display ads or send emails to a specific segment of users who have performed (or not performed) a given action, or “event.” In this cross-channel re-engagement example, we’ll start with push notifications. +In each of your destinations—Appboy, Facebook, Customer.io, AdRoll—you can create custom campaigns to show display ads or send emails to a specific segment of users who have performed (or not performed) a given action, or "event." In this cross-channel re-engagement example, we’ll start with push notifications. ## 1st Line of Defense: The Push Notification diff --git a/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md b/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md index 96cf79d83c9..0da91f0d007 100644 --- a/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md +++ b/connections/destinations/catalog/faq/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/index.md @@ -34,7 +34,7 @@ Scenarios when this tool will be useful:  ## Where to find it?  -Event Delivery can be accessed within any supported destination in the App. It’s located on the tab under “Settings” for each destination.  +Event Delivery can be accessed within any supported destination in the App. It’s located on the tab under "Settings" for each destination.  ![](../images/asset_rzYZESor.png) diff --git a/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md b/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md index ac1b47dd9f2..bcdab6a8a1b 100644 --- a/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md +++ b/connections/destinations/catalog/faq/how-do-i-setup-a-dynamic-coupon-program-to-reward-loyal-customers/index.md @@ -40,7 +40,7 @@ We’ll conduct a split test (half of the cohort will represent the control grou ## Set it up -First, register for an account with Customer.io and Amplitude. Then, enable Customer.io and enable Amplitude on your Segment project. Finally, go into your Customer.io account and enable “sending data to Segment”: +First, register for an account with Customer.io and Amplitude. Then, enable Customer.io and enable Amplitude on your Segment project. Finally, go into your Customer.io account and enable "sending data to Segment": ![](../images/asset_tps7HAgP.png) @@ -52,13 +52,13 @@ When everything is enabled, customer event data such as `Order Completed` and `P ## Define the cohort in Customer.io -Now we define the specific cohort in Customer.io as per our conditions listed earlier: someone who spends over $20 per order and shops over twice a month. In Customer.io, go to “Segments” and “Create Segment”: +Now we define the specific cohort in Customer.io as per our conditions listed earlier: someone who spends over $20 per order and shops over twice a month. In Customer.io, go to "Segments" and "Create Segment": ![](../images/asset_kTaK5L7l.png) After this cohort is created, then when a customer makes the third purchase in a month and it’s over $20, then she will be added to this segment. -Next, we’ll create a “segment trigger campaign”, where Customer.io will send a message the first time someone enters a segment. The segment in this case will be the one we just created: Coupon Loyalty Experiment. +Next, we’ll create a "segment trigger campaign", where Customer.io will send a message the first time someone enters a segment. The segment in this case will be the one we just created: Coupon Loyalty Experiment. ![](../images/asset_lE6v8cXN.png) diff --git a/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md b/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md index 02a184a93b4..825fcf9511f 100644 --- a/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md +++ b/connections/destinations/catalog/faq/how-do-we-craft-a-push-notification/index.md @@ -17,7 +17,7 @@ Every Push messaging focuses around three key features: ### Choose an destination -It’s best practice to self evaluate when trying to choose the “one” that suits your needs. +It’s best practice to self evaluate when trying to choose the "one" that suits your needs. 1. What’s your user base size? Is it more than 10k? If not, you can try demo versions of mobile marketing automation libraries. 2. Are you looking for a tool only to support push notification or provide an entire marketing suite ? @@ -58,7 +58,7 @@ Test different action words, phrases, message lengths, etc. * Marketing automation -To “auto-enroll” new users into existing campaigns +To "auto-enroll" new users into existing campaigns * Measure the right metrics diff --git a/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md b/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md index f525ce59c0e..69aa421e8b4 100644 --- a/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md +++ b/connections/destinations/catalog/faq/what-role-does-segment-play-in-attribution/index.md @@ -51,7 +51,7 @@ Destination receives the **Application Installed** event and attributes the inst Device-Mode Connection -For tools that support this, if you have enabled “Track Attribution Data” in your Segment dashboard, our integration listens to the attribution tool’s SDK for a change in attribution state. **Note**: Not all device-mode attribution tools offer “Track Attribution Data” functionality.  See the settings section for a particular tool in your Segment dashboard for confirmation.  +For tools that support this, if you have enabled "Track Attribution Data" in your Segment dashboard, our integration listens to the attribution tool’s SDK for a change in attribution state. **Note**: Not all device-mode attribution tools offer "Track Attribution Data" functionality.  See the settings section for a particular tool in your Segment dashboard for confirmation.  When there is a change in attribution state, the integration code triggers an **Install Attributed** call to be sent back to your Segment source (and on to all other enabled destinations - in device and cloud mode).   diff --git a/connections/destinations/catalog/firebase/index.md b/connections/destinations/catalog/firebase/index.md index d218d69f31c..f07737af13a 100644 --- a/connections/destinations/catalog/firebase/index.md +++ b/connections/destinations/catalog/firebase/index.md @@ -10,7 +10,7 @@ To start sending data to Firebase Analytics from your Android project, you’ll - Register your mobile app with Firebase at `https://console.firebase.google.com` -- Once your app is registered, you’ll be prompted to download a `google-services.json` file. Place this in your Application’s “app” folder. This file contains all necessary configurations and cannot be used across multiple apps. If you’re configuring Firebase for other apps, you should create a new view in your Firebase console and download a unique `google-services.json` file for each. +- Once your app is registered, you’ll be prompted to download a `google-services.json` file. Place this in your Application’s "app" folder. This file contains all necessary configurations and cannot be used across multiple apps. If you’re configuring Firebase for other apps, you should create a new view in your Firebase console and download a unique `google-services.json` file for each. ***Module-level build.gradle**: Add the Segment-Firebase SDK and apply the Google Services plugin at the end of the file: @@ -96,7 +96,7 @@ When you call `identify` Segment will map to the corresponding Firebase Analytic You can use these traits to create audiences and views to analyze your users’ behavior. -**Note**: Google prohibits sending PII to Firebase unless [“robust notice” is given to your app users](https://firebase.google.com/policies/analytics/). For iOS apps, you must include the iAD Framework to automatically collect the Age, Gender, and Interests Firebase properties. +**Note**: Google prohibits sending PII to Firebase unless ["robust notice" is given to your app users](https://firebase.google.com/policies/analytics/). For iOS apps, you must include the iAD Framework to automatically collect the Age, Gender, and Interests Firebase properties. Learn more about [Firebase's reporting dashboard here](https://support.google.com/firebase/answer/6317517?hl=en&ref_topic=6317489). @@ -174,7 +174,7 @@ Segment maps the followed Segment specced properties (left) to the corresponding ### Passing Revenue and Currency -Ecommerce events containing “revenue” or “total” must also include the appropriate ISO 4217 “currency” string for revenue data to populate to the Firebase dashboard. If a “currency” value is not included, Segment default to "USD". +Ecommerce events containing "revenue" or "total" must also include the appropriate ISO 4217 "currency" string for revenue data to populate to the Firebase dashboard. If a "currency" value is not included, Segment default to "USD". ```js Properties properties = new Properties() diff --git a/connections/destinations/catalog/flurry/index.md b/connections/destinations/catalog/flurry/index.md index c4cbc8574d3..3cd40e6c89d 100644 --- a/connections/destinations/catalog/flurry/index.md +++ b/connections/destinations/catalog/flurry/index.md @@ -12,8 +12,8 @@ This document was last updated on January 10, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Flurry” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Flurry" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Flurry "API Key" in Segment's Settings UI. You can retrieve this from your Flurry Admin > Apps > API Key. It should look like "4KKKGS3BAK4WW8WJ93DN". 4. Follow the instructions in the Github repos: [iOS SDK](https://github.com/segment-integrations/analytics-ios-integration-flurry) and [Android SDK](https://github.com/segment-integrations/analytics-android-integration-flurry). 5. Once the Segment library is integrated with your app, toggle Flurry on in your Segment UI. diff --git a/connections/destinations/catalog/foxmetrics/index.md b/connections/destinations/catalog/foxmetrics/index.md index 759de1c28f3..81002e7ee91 100644 --- a/connections/destinations/catalog/foxmetrics/index.md +++ b/connections/destinations/catalog/foxmetrics/index.md @@ -10,8 +10,8 @@ This document was last updated on October 15, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “FoxMetrics” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "FoxMetrics" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your FoxMetrics `App ID` 4. When FoxMetrics in enabled in Segment, our CDN will update within 5-10 minutes, and FoxMetrics's javascript will be loaded asynchronously onto your page. Please remember to remove FoxMetrics's snippet from your page. diff --git a/connections/destinations/catalog/freshmarketer/index.md b/connections/destinations/catalog/freshmarketer/index.md index 8519bfdbf22..27e0acdbbce 100644 --- a/connections/destinations/catalog/freshmarketer/index.md +++ b/connections/destinations/catalog/freshmarketer/index.md @@ -14,7 +14,7 @@ _**NOTE:** The Freshmarketer Destination is currently in beta, which means that {% include content/connection-modes.md %} 1. From your Segment UI’s Destinations page click **Add Destination**. -2. Search for “Freshmarketer” in the Destinations Catalog and confirm the Source you’d like to connect to. +2. Search for "Freshmarketer" in the Destinations Catalog and confirm the Source you’d like to connect to. 3. Go to your Freshmarketer dashboard (Admin Settings > API Settings) and copy your API Key. 4. In the Freshmarketer settings in the Segment UI, paste your API Key. diff --git a/connections/destinations/catalog/fullstory/index.md b/connections/destinations/catalog/fullstory/index.md index aca10866ef7..c49f76f7789 100644 --- a/connections/destinations/catalog/fullstory/index.md +++ b/connections/destinations/catalog/fullstory/index.md @@ -9,8 +9,8 @@ This document was last updated on January 25, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “FullStory” within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "FullStory" within the Destinations Catalog and confirm the Source you’d like to connect to. Please note the source must be sending events via our Javascript library Analytics.js. 3. Add your `FS Org` in the destination settings. You can find this in FullStory by navigating to `Settings` > `General` > and copying the value found on the line `window['_fs_org'] = 'fullstory_org_here';` 4. In about 5-10 minutes the CDN will be updated and FullStory's recording snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/gainsight-px/index.md b/connections/destinations/catalog/gainsight-px/index.md index 191d9659c22..2839da63905 100644 --- a/connections/destinations/catalog/gainsight-px/index.md +++ b/connections/destinations/catalog/gainsight-px/index.md @@ -14,8 +14,8 @@ This document was last updated on June 14, 2018. If you notice any gaps, outdate {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “Gainsight PX” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "Gainsight PX" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. To find your Gainsight PX key, log into Gainsight PX and navigate to Settings > Products > Web App. If you have not already entered the URL for your web application, do that and click the Generate button. The Tag Key is the value to the right of the URL value. Use the "Copy" button to copy the value to your clipboard. ![](images/TagKey.png) diff --git a/connections/destinations/catalog/gainsight/index.md b/connections/destinations/catalog/gainsight/index.md index 310ddbf0dab..30b0d83dd59 100644 --- a/connections/destinations/catalog/gainsight/index.md +++ b/connections/destinations/catalog/gainsight/index.md @@ -13,7 +13,7 @@ This document was last updated on October 18, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for Gainsight within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Copy your Gainsight Access Key and paste it into to the Access Key field in your Segment settings for Gainsight. This key can be generated from the integrations page under the `admin` area in Gainsight. It should be 36 characters long, for reference. If you need more information, please visit the [relevant documentation provided by Gainsight](https://support.gainsight.com/Connectors/API_Integration/Generate_API_Access_Key). 4. Start sending events! diff --git a/connections/destinations/catalog/goedle/index.md b/connections/destinations/catalog/goedle/index.md index 34bdde93e5b..72d4cdb213e 100644 --- a/connections/destinations/catalog/goedle/index.md +++ b/connections/destinations/catalog/goedle/index.md @@ -11,8 +11,8 @@ This document was last updated on May 16, 2018. If you notice any gaps, outdated {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Goedle” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Goedle" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, enter your goedle.io app key which you received upon [sign up](https://go.goedle.io/signup "Sign up at goedle.io"). 4. After activating, goedle.io will start automatically collecting data from your website, mobile app, or game. However, it will take up to 24 hours for goedle.io to process this data and predict future user behavior - you will receive an email from goedle.io when your data is available. diff --git a/connections/destinations/catalog/google-tag-manager/index.md b/connections/destinations/catalog/google-tag-manager/index.md index 7f380ae0776..773d6dab3af 100644 --- a/connections/destinations/catalog/google-tag-manager/index.md +++ b/connections/destinations/catalog/google-tag-manager/index.md @@ -11,8 +11,8 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Google Tag Manager” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Google Tag Manager" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment UI's destination settings, enter your Container ID (note: it should start with "GTM-"). You can find this in the Admin section of your [GTM dashboard](https://tagmanager.google.com/#/admin/). 4. GTM will be loaded on any pages where your Segment snippet is initialized and `analytics.page` gets called in client-side Javascript. Once you've turned on GTM through Segment, you can use Segment `track` events to populate the GTM `dataLayer`. diff --git a/connections/destinations/catalog/heap/index.md b/connections/destinations/catalog/heap/index.md index 8350b1ccfa7..0a1d90e1e0f 100644 --- a/connections/destinations/catalog/heap/index.md +++ b/connections/destinations/catalog/heap/index.md @@ -10,8 +10,8 @@ This document was last updated on January 29, 2018. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Heap” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Heap" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Heap "App ID" into the connection settings. 4. If you are using Heap via Segment's client-side `analytics.js` library, we asynchronously load Heap's Javascript library onto the page. As such, all native functionality of Heap, including auto-capturing of all events. diff --git a/connections/destinations/catalog/help-scout/index.md b/connections/destinations/catalog/help-scout/index.md index 37d1c1ce087..5699c123c10 100644 --- a/connections/destinations/catalog/help-scout/index.md +++ b/connections/destinations/catalog/help-scout/index.md @@ -10,7 +10,7 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for Help Scout within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Copy your Help Scout API key and paste it into to the API Key field in your Segment settings for Help Scout. You can find your API Key on the Help Scout API keys page by navigating from the [Help Scout Dashboard](https://secure.helpscout.net/). diff --git a/connections/destinations/catalog/hotjar/index.md b/connections/destinations/catalog/hotjar/index.md index 5ce30da06d7..dbce3efb423 100644 --- a/connections/destinations/catalog/hotjar/index.md +++ b/connections/destinations/catalog/hotjar/index.md @@ -11,9 +11,9 @@ This document was last updated on April 28, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “Hotjar” within the Destinations Catalog and confirm the Javascript source you’d like to connect to. +2. Search for "Hotjar" within the Destinations Catalog and confirm the Javascript source you’d like to connect to. 3. Add your Hotjar Site ID - which you can find under Settings and Sites & Organizations in our Hotjar dashboard - to your Destination settings. It should be a whole number (e.g. 123456). diff --git a/connections/destinations/catalog/hubspot/index.md b/connections/destinations/catalog/hubspot/index.md index 8ce9acc04d6..fb450213d9d 100644 --- a/connections/destinations/catalog/hubspot/index.md +++ b/connections/destinations/catalog/hubspot/index.md @@ -11,8 +11,8 @@ This document was last updated on March 30, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “HubSpot” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "HubSpot" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. If you haven't already done so, add your API Key from [HubSpot](https://knowledge.hubspot.com/articles/kcs_article/integrations/how-do-i-get-my-hubspot-api-key) and drop into the "API Key" field within the Segment UI. 4. Navigate to the "Settings" page within the HubSpot UI to find your Hub ID and drop into the "Hub ID" field within the Segment UI. 5. When you activate the destination, our CDN will be updated in about 5-10 minutes and the HubSpot snippet will be initilized and begin recording data. diff --git a/connections/destinations/catalog/inspectlet/index.md b/connections/destinations/catalog/inspectlet/index.md index eb4157d57f9..fd37a20c7ba 100644 --- a/connections/destinations/catalog/inspectlet/index.md +++ b/connections/destinations/catalog/inspectlet/index.md @@ -10,8 +10,8 @@ This document was last updated on 20th June, 2018. If you notice any gaps, out-d {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “Inspectlet” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "Inspectlet" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Take your Inspectlet WID (website’s ID), you can find it after clicking the Get Install Code button for your site in your Inspectlet dashboard. It will appear near the beginning of your embed code snippet. It should be a series of numbers, like 9492461759. 4. Add the WID in the "Connection Settings" section in Segment. 5. Our CDN is updated within 5-10 minutes. Then our snippet will start asynchronously loading Inspectlet's tracker.js onto your page. This means you should remove Inspectlet's snippet from your page. diff --git a/connections/destinations/catalog/intercom/index.md b/connections/destinations/catalog/intercom/index.md index 72566cc22c8..253f8bfa156 100644 --- a/connections/destinations/catalog/intercom/index.md +++ b/connections/destinations/catalog/intercom/index.md @@ -17,8 +17,8 @@ This document was last updated on January 18, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Intercom” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Intercom" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Authorize your Intercom account in Segment and select the Intercom Account you want to sync with Segment. You can choose which account to sync in the drop down menu in the top right. If you have opted to utilize our [server-side sources](https://segment.com/docs/sources/#server), we will begin passing data through our servers once you activate the Destination. For other libraries please continue reading below. 4. Find your "App ID" within the Intercom UI following [the instructions here](https://docs.intercom.com/faqs-and-troubleshooting/getting-set-up/where-can-i-find-my-app-id) or by navigating to the Gear Menu and clicking on "App Settings" followed by "API Keys". It should look something like this: `9iefb489`. diff --git a/connections/destinations/catalog/iterable/index.md b/connections/destinations/catalog/iterable/index.md index ce4f905b3ea..0d06ac69679 100644 --- a/connections/destinations/catalog/iterable/index.md +++ b/connections/destinations/catalog/iterable/index.md @@ -77,7 +77,7 @@ analytics.track("Order Completed", { ## Page -Calling `page` to track pageviews will register as a custom event within Iterable. If you have a page called “shoppingCart” the custom event will be called “shoppingCart page” within Iterable. +Calling `page` to track pageviews will register as a custom event within Iterable. If you have a page called "shoppingCart" the custom event will be called "shoppingCart page" within Iterable. If a user does not already exist in Iterable, calling `page` for a user event will add that user into the system. Be sure to pass in the `email` the first time you call page for a user, since Iterable keys users by `email`. After the first time, you can call page with `userId`. diff --git a/connections/destinations/catalog/kissmetrics/index.md b/connections/destinations/catalog/kissmetrics/index.md index e4cae63a615..e48066f1a3f 100644 --- a/connections/destinations/catalog/kissmetrics/index.md +++ b/connections/destinations/catalog/kissmetrics/index.md @@ -11,9 +11,9 @@ This document was last updated on July 3, 2018. If you notice any gaps, out-date When you toggle on KISSmetrics in Segment, this is what happens: -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "KISSmetrics" within the Destinations Catalog and confirm the Source you’d like to connect to. -3. Drop in your KISSmetrics "API Key” into the connection settings. +3. Drop in your KISSmetrics "API Key" into the connection settings. 4. If you are using KISSmetrics via Segment’s client-side analytics.js library, we asynchronously load KISSmetrics Javascript library onto the page. This means you should remove KISSmetrics's snippet from your page. Your KISSmetrics source will start automatically collecting "Visited Site" events and [other automatically tracked events](http://support.kissmetrics.com/article/show/javascript-settings). ## Page diff --git a/connections/destinations/catalog/klaviyo/index.md b/connections/destinations/catalog/klaviyo/index.md index 9b8a4108ea9..08a04b0a7c1 100644 --- a/connections/destinations/catalog/klaviyo/index.md +++ b/connections/destinations/catalog/klaviyo/index.md @@ -16,8 +16,8 @@ This document was last updated on September 6, 2018. If you notice any gaps, out {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Navigate to your [Account > Settings > API Keys](https://www.klaviyo.com/account#api-keys-tab) in the Klaviyo's UI and copy your "API Key" into the Segment Settings UI. 5. **Note:** Private API Key is required to use the List API. You can find this by going to Klaviyo’s UI and clicking [Account > Settings > API Keys > Create API Key](https://www.klaviyo.com/account#api-keys-tab) in order to generate a Private API Key and copy it into the Segment Settings UI. diff --git a/connections/destinations/catalog/kochava/index.md b/connections/destinations/catalog/kochava/index.md index cbb13fcfb1a..bd4cd6b8c50 100644 --- a/connections/destinations/catalog/kochava/index.md +++ b/connections/destinations/catalog/kochava/index.md @@ -15,7 +15,7 @@ This document was last updated on October 8, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} 1. If you have not already, create your app within the Kochava dashboard. Check out Kochava's documentation for information on [creating your app](http://support.kochava.com/create-manage-apps/create-edit-apps). -2. From your Segment UI’s Destinations page click on “Add Destination”. +2. From your Segment UI’s Destinations page click on "Add Destination". 3. Search for "Kochava" within the Destinations Catalog and confirm the Source you’d like to connect to. 4. In the Kochava app, grab your Kochava App GUID (Globally Unique Identifier) 5. Copy the Kochava GUID into the Segment Destinations Settings UI under "API key". diff --git a/connections/destinations/catalog/leanplum/index.md b/connections/destinations/catalog/leanplum/index.md index 8ab59e5e5b9..2de9e7f20e0 100644 --- a/connections/destinations/catalog/leanplum/index.md +++ b/connections/destinations/catalog/leanplum/index.md @@ -10,8 +10,8 @@ This document was last updated on January 29, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Leanplum” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Leanplum" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Navigate to your "App Settings" within the Leanplum UI and open up your "Keys & Settings" 4. Copy the "App ID" into the Segment Settings UI under "Leanplum Application ID" 5. We recommend creating 2 Leanplum Destinations, 1 for production and 1 for development. diff --git a/connections/destinations/catalog/mailchimp/index.md b/connections/destinations/catalog/mailchimp/index.md index f7a04aea4b7..c6a1f0a59c6 100644 --- a/connections/destinations/catalog/mailchimp/index.md +++ b/connections/destinations/catalog/mailchimp/index.md @@ -13,8 +13,8 @@ This document was last updated on May 08, 2018. If you notice any gaps, out-date {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “MailChimp” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "MailChimp" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your MailChimp "API key" into the connection settings. It is recommended that you create a brand new API key for the Segment destination. MailChimp restricts each API key to a maximum of 10 concurrent requests, so creating a dedicated one for Segment will ensure maximum throughput for outgoing calls. You can read more about API keys on [MailChimp's docs](http://kb.mailchimp.com/integrations/api-integrations/about-api-keys). 4. Drop in your MailChimp "Audience ID" into your connection settings. diff --git a/connections/destinations/catalog/mailjet/index.md b/connections/destinations/catalog/mailjet/index.md index 10d7d0aaf6a..89a50aececd 100644 --- a/connections/destinations/catalog/mailjet/index.md +++ b/connections/destinations/catalog/mailjet/index.md @@ -5,7 +5,7 @@ This destination is maintained by Mailjet. For any issues with the destination, ## Getting Started -Navigate to the “App Connections” page* (Account -> App Connections) and click on the “Segment” destination block to find your Segment Authentication key. * If you do not see the App Connections page for any reason, please contact us at plugins@mailjet.com. Select a Contact list from the drop down menu that you wish to have Segment send contact property data to. +Navigate to the "App Connections" page* (Account -> App Connections) and click on the "Segment" destination block to find your Segment Authentication key. * If you do not see the App Connections page for any reason, please contact us at plugins@mailjet.com. Select a Contact list from the drop down menu that you wish to have Segment send contact property data to. Be sure and note the contact list id inside the field below the chosen list because you will need to paste it into your Segment account so Segment knows where to send the data to. diff --git a/connections/destinations/catalog/mammoth/index.md b/connections/destinations/catalog/mammoth/index.md index 6542786d3b1..d28e8b5de25 100644 --- a/connections/destinations/catalog/mammoth/index.md +++ b/connections/destinations/catalog/mammoth/index.md @@ -100,7 +100,7 @@ Page calls will be sent to the webhook dataset you created earlier. You can filt If you haven’t had a chance to review our spec, please take a look to understand what the [Screen method](https://segment.com/docs/spec/screen/) does. An example call would look like: ``` -[[SEGAnalytics sharedAnalytics] screen:@ “Home”]; +[[SEGAnalytics sharedAnalytics] screen:@ "Home"]; ``` Screen calls will be sent to the webhook dataset you created earlier. You can filter this data into a different view after you have set up JSON extract pipelines. diff --git a/connections/destinations/catalog/marketo-v2/index.md b/connections/destinations/catalog/marketo-v2/index.md index 24ac8711e31..c8c0564e8ab 100644 --- a/connections/destinations/catalog/marketo-v2/index.md +++ b/connections/destinations/catalog/marketo-v2/index.md @@ -215,7 +215,7 @@ You can do one of the following to prevent duplicate leads: | alex@email.com | ABC1234 | | natasha@email.com | XYZ9876 | -To upload a list to Marketo, when you are in Lead Database, click All Leads. Then click “New”, then “Import List” from the drop down. Select your CSV, then click “Next”. Make sure “Email Address” and “userId” are the Marketo Fields selected then click “Next”. Name your list or select a pre-existing list. Select “None” for Acquisition Program. Then Click “Import”. +To upload a list to Marketo, when you are in Lead Database, click All Leads. Then click "New", then "Import List" from the drop down. Select your CSV, then click "Next". Make sure "Email Address" and "userId" are the Marketo Fields selected then click "Next". Name your list or select a pre-existing list. Select "None" for Acquisition Program. Then Click "Import". ![](images/jBhuNezWWP.gif) @@ -234,7 +234,7 @@ There are a few necessary steps that have to be taken to Migrate from Marketo to 2. Two custom fields must be created in Marketo: userId and anonymousId. Check out [Getting Started](https://segment.com/docs/integrations/marketo-v2/#-2-you-must-create-a-user-id-and-an-anonymous-id-field-in-marketo-) for exact details on how to create these custom fields in Marketo. 3. `Track` calls must be mapped in your Destination settings. Our Marketo Destination sent `track` calls as a Munchkin Visit WebPage event in Marketo. In Marketo V2, we'll send your track calls to your Marketo Custom Activities. Detailed instructions [here](https://segment.com/docs/integrations/marketo-v2/#track). 4. If there are any custom Lead fields that you’d like sent to Marketo in your `Identify` calls, you must add them in your Destination settings. Detailed instructions [here](https://segment.com/docs/integrations/marketo-v2/#identify). -5. Update anything in Marketo that rely on the way V1 sends `.track()` events to be triggered by your custom activities. For example, our V1 Marketo destination sent track events as a “Visit Web Page” event with `/event/`. So if you a workflow that is triggered by a “Visit Web Page” event where the web page contains `/event/`, you'll have to swap out the "Visit Web Page" event trigger you have with your Custom Attribute Trigger. In the right side bar, click the "Custom" folder under "Triggers" and select the trigger that you set for your custom activity: +5. Update anything in Marketo that rely on the way V1 sends `.track()` events to be triggered by your custom activities. For example, our V1 Marketo destination sent track events as a "Visit Web Page" event with `/event/`. So if you a workflow that is triggered by a "Visit Web Page" event where the web page contains `/event/`, you'll have to swap out the "Visit Web Page" event trigger you have with your Custom Attribute Trigger. In the right side bar, click the "Custom" folder under "Triggers" and select the trigger that you set for your custom activity: ![](images/cPD4kP65buG+.png) diff --git a/connections/destinations/catalog/mixpanel/index.md b/connections/destinations/catalog/mixpanel/index.md index 4b9ee58450f..b5883fe8ae0 100644 --- a/connections/destinations/catalog/mixpanel/index.md +++ b/connections/destinations/catalog/mixpanel/index.md @@ -11,7 +11,7 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat 1. From your Segment UI’s Destinations page click on **Add Destination**. 2. Search for Mixpanel within the Destinations Catalog and confirm the Source you’d like to connect to. -3. Copy your Mixpanel “API Secret” and "Token", and paste them into the Connection Settings in Segment. +3. Copy your Mixpanel "API Secret" and "Token", and paste them into the Connection Settings in Segment. 4. Enable the destination to start sending your data to Mixpanel. ## Page diff --git a/connections/destinations/catalog/moengage/index.md b/connections/destinations/catalog/moengage/index.md index 6e294371b07..e48369d055e 100644 --- a/connections/destinations/catalog/moengage/index.md +++ b/connections/destinations/catalog/moengage/index.md @@ -75,7 +75,7 @@ For more info refer to this [link](https://segment.com/docs/sources/mobile/ios/# ### Tracking Events -Event tracking is used to track user behaviour in an app. **track** lets you record the actions your users perform. Every action triggers i.e,“event”, which can also have associated attributes. +Event tracking is used to track user behaviour in an app. **track** lets you record the actions your users perform. Every action triggers i.e,"event", which can also have associated attributes. ```[[SEGAnalytics sharedAnalytics] track:@"Item Purchased" properties:@{ @"item": @"Sword of Heracles"}];``` diff --git a/connections/destinations/catalog/mouseflow/index.md b/connections/destinations/catalog/mouseflow/index.md index 4674f93ce1b..3bd4275625c 100644 --- a/connections/destinations/catalog/mouseflow/index.md +++ b/connections/destinations/catalog/mouseflow/index.md @@ -10,8 +10,8 @@ This document was last updated on April 28, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Mouseflow” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Mouseflow" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Site ID within the Segment Settings UI. You can find this in [your Mouseflow UI](http://help.mouseflow.com/knowledge_base/topics/how-do-i-find-my-mouseflow-site-id). 4. In about 5-10 minutes the CDN will be updated and Mouseflow snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/msg91/index.md b/connections/destinations/catalog/msg91/index.md index 7ceb0337823..215172034e0 100644 --- a/connections/destinations/catalog/msg91/index.md +++ b/connections/destinations/catalog/msg91/index.md @@ -16,9 +16,9 @@ _**NOTE:** The MSG91 Destination is currently in beta, which means that they are {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “MSG91” within the Destinations Catalog and confirm the Source you’d like to connect to. +2. Search for "MSG91" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in the "API Key" into your Segment Settings UI which you can find from your [MSG91 dashboard](https://control.msg91.com/signin/) in the API page using the ['API' option in the sidebar](https://help.msg91.com/article/177-where-can-i-find-my-authentication-key). It is recommended that you create a brand new API key for the Segment destination. diff --git a/connections/destinations/catalog/new-relic/index.md b/connections/destinations/catalog/new-relic/index.md index 2443d644844..90860e5aba3 100644 --- a/connections/destinations/catalog/new-relic/index.md +++ b/connections/destinations/catalog/new-relic/index.md @@ -9,8 +9,8 @@ This document was last updated on August 29, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. - 2. Search for “New Relic” within the Destinations Catalog and confirm the Source you’d like to connect to. + 1. From your Segment UI’s Destinations page click on "Add Destination". + 2. Search for "New Relic" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Insights [Account ID](https://docs.newrelic.com/docs/accounts/install-new-relic/account-setup/account-id) and your [Insert Key](https://docs.newrelic.com/docs/insights/insights-data-sources/custom-data/insert-custom-events-insights-api#register). 4. Once destination enabled we'll start forwarding your calls to New Relic. diff --git a/connections/destinations/catalog/outbound/index.md b/connections/destinations/catalog/outbound/index.md index 7ddd8cb607d..3e672e7e71d 100644 --- a/connections/destinations/catalog/outbound/index.md +++ b/connections/destinations/catalog/outbound/index.md @@ -16,7 +16,7 @@ Connect is supported on the client-side, server-side and on mobile. ## Identify -Connect needs to identify users and their data to track who we should message. Segment will pass your UserID and any traits that you store on that user to Connect. (Note: Segment refers to user data as “traits”; Connect refers to user data as “attributes”.) +Connect needs to identify users and their data to track who we should message. Segment will pass your UserID and any traits that you store on that user to Connect. (Note: Segment refers to user data as "traits"; Connect refers to user data as "attributes".) analytics.identify({ userId: '019mr8mf4r', diff --git a/connections/destinations/catalog/pendo/index.md b/connections/destinations/catalog/pendo/index.md index 6741129c72d..e13606572ec 100644 --- a/connections/destinations/catalog/pendo/index.md +++ b/connections/destinations/catalog/pendo/index.md @@ -12,8 +12,8 @@ This document was last updated on September 26, 2018. If you notice any gaps, ou {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin) > Basic Information > API Key. 4. In about 5-10 minutes the CDN will be updated and Pendo’s snippet will be initialized onto your page. This pulls in all page and click events without needing to make additional method calls. @@ -21,8 +21,8 @@ This document was last updated on September 26, 2018. If you notice any gaps, ou If you are implementing server-side, please follow the steps above to add Pendo continue with steps below to add a Webhook destination: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Webhooks” within the Destinations Catalog and confirm the Javascript Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Webhooks" within the Destinations Catalog and confirm the Javascript Source you’d like to connect to. 3. Add the following as your Webhook URL: `https://pendo-io.appspot.com/data/segmentio/YOUR_PENDO_API_KEY` and replace `YOUR_PENDO_API_KEY` with your actual Pendo API Key which you can find in the Pendo UI under [Site Settings](https://app.pendo.io/admin) > Basic Information > API Key. 4. Headers are not required in Webhook configuration. Once you’re done adding in your URL, save changes. 5. Using Track method also requires a setting enabled on your Pendo subscription. Please reach out to Pendo to enable this feature flag for your account. diff --git a/connections/destinations/catalog/perimeterx/index.md b/connections/destinations/catalog/perimeterx/index.md index dca43df4041..429187b4fa9 100644 --- a/connections/destinations/catalog/perimeterx/index.md +++ b/connections/destinations/catalog/perimeterx/index.md @@ -19,15 +19,15 @@ Here's how you can get started using PerimeterX! + Click the "Admin" tab inside the console. + Click "New Policy". -+ Rename your new policy by clicking the words “Policy name” in the new policy and then -click “Apply Changes”. ++ Rename your new policy by clicking the words "Policy name" in the new policy and then +click "Apply Changes". ![](https://cloudup.com/cg69lTztbJx+) ### 3. Configure your Application -+ Click the “Admin” tab inside the console. -+ Define your first application by clicking the button “Create a New Application” and filling ++ Click the "Admin" tab inside the console. ++ Define your first application by clicking the button "Create a New Application" and filling in the modal. + Select the policy that you would like to use (default is pxDefault_Policy and you should use the policy that you just created) diff --git a/connections/destinations/catalog/personyze/index.md b/connections/destinations/catalog/personyze/index.md index 880fcb6307c..4a89dda8a63 100644 --- a/connections/destinations/catalog/personyze/index.md +++ b/connections/destinations/catalog/personyze/index.md @@ -14,7 +14,7 @@ _**NOTE:** Personyze is currently in beta, which means that they are still activ 1. From your Segment UI's Destinations page click on "Add Destination". 2. Search for "Personyze" within the Destinations Catalog and confirm the Source you'd like to connect to. 3. Drop in the "API Key" into your Segment Settings UI which you can find from your [Personyze dashboard](https://personyze.com/site/tracker/condition/index#cat=Account%20settings%2FMain%20settings%2FIntegrations/conditions) under Account Settings > Integrations > Segment > Get Keys -4. Once you’ve updated the API key in Segment, data from the source you selected will be shown right away in Personyze under “Manage Visitor Profiles”. +4. Once you’ve updated the API key in Segment, data from the source you selected will be shown right away in Personyze under "Manage Visitor Profiles". ## Identify diff --git a/connections/destinations/catalog/quanticmind/index.md b/connections/destinations/catalog/quanticmind/index.md index 9059fd57d84..f309b0d67bd 100644 --- a/connections/destinations/catalog/quanticmind/index.md +++ b/connections/destinations/catalog/quanticmind/index.md @@ -9,7 +9,7 @@ This document was last updated on January 09, 2019. If you notice any gaps, outd {% include content/connection-modes.md %} - 1. From your Segment UI’s Destinations page click on “Add Destination”. + 1. From your Segment UI’s Destinations page click on "Add Destination". 2. Search for "QuanticMind" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your `ClientID`, and `Domain` if provided, from QuanticMind account manager. 4. Under `Events` you can then map any necessary 'track' event/s to QuanticMind numbered event/s. Please note that unless mapped in the settings, no 'track' calls will be sent to QuanticMind. diff --git a/connections/destinations/catalog/quora-conversion-pixel/index.md b/connections/destinations/catalog/quora-conversion-pixel/index.md index c5ad1e404f4..499da2edfc5 100644 --- a/connections/destinations/catalog/quora-conversion-pixel/index.md +++ b/connections/destinations/catalog/quora-conversion-pixel/index.md @@ -10,8 +10,8 @@ This document was last updated on June 15th, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Quora” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Quora" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your Quora Conversion Pixel Key to your Destination settings. To get this you will need to do the following: i. Log into your [Quora Ads Manager Account](https://www.quora.com/ads/account). diff --git a/connections/destinations/catalog/refersion/index.md b/connections/destinations/catalog/refersion/index.md index f76c469cf4a..eea0882c65a 100644 --- a/connections/destinations/catalog/refersion/index.md +++ b/connections/destinations/catalog/refersion/index.md @@ -20,8 +20,8 @@ You have two options to connect - either automatically within your Refersion das ### Option 2 - Segment UI -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Refersion” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Refersion" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Once connected, you will be asked to input an API key - which can be found in your [Refersion dashboard](https://www.refersion.com/base/settings/integrations/api) - which is formatted as `publickey.secretkey`. You will need to click "Show" to obtain the "Secret Key" portion. ## Identify diff --git a/connections/destinations/catalog/salesforce-dmp/index.md b/connections/destinations/catalog/salesforce-dmp/index.md index 46ae14c59bb..af8383974fd 100644 --- a/connections/destinations/catalog/salesforce-dmp/index.md +++ b/connections/destinations/catalog/salesforce-dmp/index.md @@ -146,9 +146,9 @@ To collect a Segment property as an SFDMP `user attribute` instead, contact your SFDMP can split an attribute value into many individual values based on a delimiter. For example, say you have a property `colors` with a value `red,green,blue,yellow`. You can adjust your SFDMP settings so that it recognizes a comma as a delimiter for this attribute. That way, you can -create audience Segments based on individual attribute values such as “red”, -“green”, “blue” and “yellow” rather than on complete strings like -“red,green,blue,yellow”. +create audience Segments based on individual attribute values such as "red", +"green", "blue" and "yellow" rather than on complete strings like +"red,green,blue,yellow". To set up a custom delimiter, contact your Salesforce representative. diff --git a/connections/destinations/catalog/salesforce-marketing-cloud/index.md b/connections/destinations/catalog/salesforce-marketing-cloud/index.md index e505bb55bf3..80d94d8fb03 100644 --- a/connections/destinations/catalog/salesforce-marketing-cloud/index.md +++ b/connections/destinations/catalog/salesforce-marketing-cloud/index.md @@ -30,7 +30,7 @@ You should now see a Summary page with a Components section. This section lists Segment will pass any traits you specify in an `identify` call through to the *Identify Data Extension* you specify in the Segment UI. You'll need to create this Data Extension manually in SMC's Contact Builder UI. When creating a Data Extension in SMC, you can set up as many or as few traits as you would like, but a good starting point for your schema is to include Segment's [standard identify traits][]. ### Set up your subdomain -Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters “mc” in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. +Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters "mc" in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. **If you do not set your subdomain, Segment will use the legacy V1 endpoint and your events can result in authentication errors.** diff --git a/connections/destinations/catalog/satismeter/index.md b/connections/destinations/catalog/satismeter/index.md index c1042cd6736..cb5918758f6 100644 --- a/connections/destinations/catalog/satismeter/index.md +++ b/connections/destinations/catalog/satismeter/index.md @@ -20,7 +20,7 @@ With SatisMeter you can: ## Get Started -To get started you need to sign up to SatisMeter, and click the green button “Enable with Segment”. This will link your SatisMeter project with your Segment project and enable the destination. +To get started you need to sign up to SatisMeter, and click the green button "Enable with Segment". This will link your SatisMeter project with your Segment project and enable the destination. !["Enable with segment" button](https://cloud.githubusercontent.com/assets/12846380/9251740/edd579ca-41d4-11e5-9ebe-732156cbdb2f.png) diff --git a/connections/destinations/catalog/sentry/index.md b/connections/destinations/catalog/sentry/index.md index 1104c64f267..c493d044cf7 100644 --- a/connections/destinations/catalog/sentry/index.md +++ b/connections/destinations/catalog/sentry/index.md @@ -10,8 +10,8 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Sentry” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Sentry" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your "Public DSN" into the Sentry destination settings. 4. We’ll automatically initialize Sentry with your "Public DSN" upon loading analytics.js. 5. Sentry will automatically start tracking errors in your app's javascript. diff --git a/connections/destinations/catalog/simplereach/index.md b/connections/destinations/catalog/simplereach/index.md index 058ab55ad39..686e452fc2b 100644 --- a/connections/destinations/catalog/simplereach/index.md +++ b/connections/destinations/catalog/simplereach/index.md @@ -10,7 +10,7 @@ This document was last updated on April 16, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “SimpleReach” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "SimpleReach" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. In your Segment Settings UI, enter your SimpleReach PID which was given to you by the SimpleReach client services team. 4. In about 5-10 minutes the CDN will be updated and the SimpleReach snippet will be initialized onto your page and data will flow through to your SimpleReach Dashboard. diff --git a/connections/destinations/catalog/singular/index.md b/connections/destinations/catalog/singular/index.md index 11a3b414b9d..8eba7f4dc08 100644 --- a/connections/destinations/catalog/singular/index.md +++ b/connections/destinations/catalog/singular/index.md @@ -24,7 +24,7 @@ This destination is maintained by Singular. For any issues with the destination, ## Install Attribution -Enable automatic tracking of lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) via initialization config parameters ([iOS](https://segment.com/docs/sources/mobile/ios/#application-lifecycle-tracking), [Android](https://segment.com/docs/sources/mobile/android/#step-2-initialize-the-client)) to track installs and sessions in Singular. The Singular “**session**” will be sent automatically by the integration as long as you are including the events above. +Enable automatic tracking of lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) via initialization config parameters ([iOS](https://segment.com/docs/sources/mobile/ios/#application-lifecycle-tracking), [Android](https://segment.com/docs/sources/mobile/android/#step-2-initialize-the-client)) to track installs and sessions in Singular. The Singular "**session**" will be sent automatically by the integration as long as you are including the events above. ## Apple Search Ads Attribution diff --git a/connections/destinations/catalog/slicingdice/index.md b/connections/destinations/catalog/slicingdice/index.md index 3a98a1dec27..9fd1faa9bea 100644 --- a/connections/destinations/catalog/slicingdice/index.md +++ b/connections/destinations/catalog/slicingdice/index.md @@ -54,9 +54,9 @@ analytics.identify('userId123', { ``` Identify calls will be sent to SlicingDice using the following columns: -* `{source_name}-identifies-user-id`: contains the “userId” attribute of an Identify call -* `{source_name}-identifies-{attribute_name}`: contains the “traits” attributes of an Identify call, saving each one as an individual column -* `{source_name}-identifies-context-{attribute_name}`: contains the “context” attributes of an Identify call, saving each one as an individual column +* `{source_name}-identifies-user-id`: contains the "userId" attribute of an Identify call +* `{source_name}-identifies-{attribute_name}`: contains the "traits" attributes of an Identify call, saving each one as an individual column +* `{source_name}-identifies-context-{attribute_name}`: contains the "context" attributes of an Identify call, saving each one as an individual column ## Track @@ -69,9 +69,9 @@ analytics.track('Clicked Login Button') Track calls will be sent to SlicingDice using the following columns: -* `{source_name}-track-event`: contains the “event” attribute of a Track call -* `{source_name}-track-{attribute_name}`: contains the “properties” attributes of a Track call, saving each one as an individual column -* `{source_name}-track-context-{attribute_name}`: contains the “context” attributes of a Track call, saving each one as an individual column +* `{source_name}-track-event`: contains the "event" attribute of a Track call +* `{source_name}-track-{attribute_name}`: contains the "properties" attributes of a Track call, saving each one as an individual column +* `{source_name}-track-context-{attribute_name}`: contains the "context" attributes of a Track call, saving each one as an individual column *Observation: if your* `context` *attribute has nested attributes, your column names will follow this pattern:* `{source_name}-track-context-{attribute_name}{nested_attribute_name}` @@ -92,7 +92,7 @@ Group calls will be sent to SlicingDice using the following columns: * `{source_name}-groups-group-id`: contains the `groupID` attribute of a Group call * `{source_name}-groups-{attribute_name}`: contains the `traits` attributes of a Group call, saving each one as an individual column -* `{source_name}-groups-context-{attribute_name}`: contains the “context” attributes of a Group call, saving each one as an individual column +* `{source_name}-groups-context-{attribute_name}`: contains the "context" attributes of a Group call, saving each one as an individual column *Observation: Group calls will also be sent to SlicingDice using the following [Account](https://segment.com/docs/destinations/#warehouse-schemas) columns that holds the latest state of a group.* * `{source_name}-accounts-group-id`: contains the `groupId` attribute of a Group call diff --git a/connections/destinations/catalog/snapengage/index.md b/connections/destinations/catalog/snapengage/index.md index 5bd173b0a5b..819d36ee22f 100644 --- a/connections/destinations/catalog/snapengage/index.md +++ b/connections/destinations/catalog/snapengage/index.md @@ -10,9 +10,9 @@ This document was last updated on October 22, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “SnapEngage” within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind that our "SnapEngage" destination is only compatible with our client-side [analytics.js](https://segment.com/docs/sources/website/analytics.js/) library. +2. Search for "SnapEngage" within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind that our "SnapEngage" destination is only compatible with our client-side [analytics.js](https://segment.com/docs/sources/website/analytics.js/) library. 3. Add your SnapEngage `Widget ID` to your destination settings in Segment. You can find the `Widget ID` in your SnapEngage Javascript snippet. It will look something like this: 0c739ebb-2016-44a0-b1da-a5b5eb272474. Alternatively, the `Widget ID` can also be found under the _Advanced Widget ID_ section of the _Get the Code_ tab in the Admin Dashboard when logged in to SnapEngage. diff --git a/connections/destinations/catalog/sparkpage/index.md b/connections/destinations/catalog/sparkpage/index.md index 0a6267c6c7d..781ef19a1f7 100644 --- a/connections/destinations/catalog/sparkpage/index.md +++ b/connections/destinations/catalog/sparkpage/index.md @@ -5,7 +5,7 @@ This destination is maintained by SparkPage. ## Getting Started -Once the Segment library is integrated with your server, toggle SparkPage on in your Segment destinations, and add your API key which you can find in the SparkPage Dashboard under “Settings” +Once the Segment library is integrated with your server, toggle SparkPage on in your Segment destinations, and add your API key which you can find in the SparkPage Dashboard under "Settings" The Segment SparkPage destination is 100% handled through our servers, so you don't need to bundle their iOS or Android SDKs. Your Segment SDK will be enough. diff --git a/connections/destinations/catalog/trackier/index.md b/connections/destinations/catalog/trackier/index.md index a433087e1f6..32c680f064f 100644 --- a/connections/destinations/catalog/trackier/index.md +++ b/connections/destinations/catalog/trackier/index.md @@ -20,7 +20,7 @@ _**NOTE:** The Trackier Destination is currently in beta, which means that they If you haven't had a chance to review our spec, please take a look to understand what the [Track method](https://segment.com/docs/spec/track/) does. An example call would look like: ``` - analytics.track(“Item Sold”, { + analytics.track("Item Sold", { click_id: '1233443', sale_amount: $12.54, txn_id: 'random', diff --git a/connections/destinations/catalog/tune/index.md b/connections/destinations/catalog/tune/index.md index bb2b6e0257b..be0c396c7e9 100644 --- a/connections/destinations/catalog/tune/index.md +++ b/connections/destinations/catalog/tune/index.md @@ -14,8 +14,8 @@ This document was last updated on May 8, 2018. If you notice any gaps, outdated {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “TUNE” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "TUNE" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your TUNE Advertiser ID in the Segment Settings UI from [your TUNE Dashboard](https://developers.tune.com/sdk/finding-your-advertiser-id-and-conversion-key/). 4. In your TUNE account, ensure that you have created a new app by navigating to Applications > Apps > Add A New App. 5. Depending on library you've installed, please follow the additional steps below to finish setting up! diff --git a/connections/destinations/catalog/tv-squared/index.md b/connections/destinations/catalog/tv-squared/index.md index e8a7558487d..fe4d2ee8c2a 100644 --- a/connections/destinations/catalog/tv-squared/index.md +++ b/connections/destinations/catalog/tv-squared/index.md @@ -10,9 +10,9 @@ This document was last updated on April 20th, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. +1. From your Segment UI’s Destinations page click on "Add Destination". -2. Search for “TV Squared” within the Destinations Catalog and confirm the Javascript source you’d like to connect to. +2. Search for "TV Squared" within the Destinations Catalog and confirm the Javascript source you’d like to connect to. 3. Add your TV Squared Brand ID and Client ID to your Segment Settings UI. You can find this within your TV Squared dashboard. diff --git a/connections/destinations/catalog/userlike/index.md b/connections/destinations/catalog/userlike/index.md index ef52cc4bad2..ec6e3db2818 100644 --- a/connections/destinations/catalog/userlike/index.md +++ b/connections/destinations/catalog/userlike/index.md @@ -10,8 +10,8 @@ This document was last updated on October 22, 2018. If you notice any gaps, outd {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Userlike” within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind, that the Userlike destination is only compatible with our Javascript source. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Userlike" within the Destinations Catalog and confirm the Source you’d like to connect to - keep in mind, that the Userlike destination is only compatible with our Javascript source. 3. Add your Secret Key to your destination settings in Segment - your Secret Key can be found under Config > Install > Secret in your Userlike dashboard. It should look something like this: 8a3707ab96df8354253c158a25f908b84dc655c27d5828a1a97d99f08bfba6f4. 4. Once you enable the destination, our CDN is updated within 5-10 minutes. Analytics.js will start asynchronously loading Userlike's javascript onto your page. Please remember to remove Userlike's snippet from your page. diff --git a/connections/destinations/catalog/userlist/index.md b/connections/destinations/catalog/userlist/index.md index 3c7e68fff0f..2fd7f0ce729 100644 --- a/connections/destinations/catalog/userlist/index.md +++ b/connections/destinations/catalog/userlist/index.md @@ -13,8 +13,8 @@ _**NOTE:** The Userlist.io Destination is currently in beta, which means that th {% include content/connection-modes.md %} 1. From your Segment UI's Destinations page click on "Add Destination". -2. Search for “Userlist” within the Destinations Catalog and confirm the Source you'd like to connect to. -3. Drop in the “Push API Key" into your Segment Settings UI which you can find from your [Userlist.io Push API settings](https://app.userlist.io/settings/push). +2. Search for "Userlist" within the Destinations Catalog and confirm the Source you'd like to connect to. +3. Drop in the "Push API Key" into your Segment Settings UI which you can find from your [Userlist.io Push API settings](https://app.userlist.io/settings/push). _**NOTE:** The Userlist.io Destination does not support tracking of anonymous users, so please make sure to call `identify` before calling `track`. If you do call `track` on unidentified users, you will receive a 400 error which you can disregard if it was intentional._ diff --git a/connections/destinations/catalog/visual-website-optimizer/index.md b/connections/destinations/catalog/visual-website-optimizer/index.md index c372ae73d85..81ded4d9947 100644 --- a/connections/destinations/catalog/visual-website-optimizer/index.md +++ b/connections/destinations/catalog/visual-website-optimizer/index.md @@ -19,8 +19,8 @@ Because the VWO destination needs to be on the page right away, there are two wa Additionaly, to enable the destination please follow these instructions: -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Visual Web Optimizer” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Visual Web Optimizer" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Toggle the destination on! @@ -75,10 +75,10 @@ analytics.track('Order Completed', { If you are using VWO together with Google Analytics, you can enable this setting to add the `nonInteraction` flag to your `Experiment Viewed` track events. This can help with low bounce rates. ### Library Tolerance -The maximum amount of time (in milliseconds) to wait for VWO’s full library to be downloaded before simply displaying your original page. This setting is only effective if “Use Async Smart Code” is set to “true”. +The maximum amount of time (in milliseconds) to wait for VWO’s full library to be downloaded before simply displaying your original page. This setting is only effective if "Use Async Smart Code" is set to "true". ### Settings Tolerance -The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page. This setting is only effective if “Use Async Smart Code” is set to “true”. +The maximum amount of time (in milliseconds) to wait for test settings before VWO will simply display your original page. This setting is only effective if "Use Async Smart Code" is set to "true". ## Use Existing JQuery -If your page already includes JQuery, you can set this to “true”. Otherwise, VWO will include JQuery onto the page for you. VWO needs JQuery on the page to function correctly. This setting is only effective if “Use Async Smart Code” is enabled. +If your page already includes JQuery, you can set this to "true". Otherwise, VWO will include JQuery onto the page for you. VWO needs JQuery on the page to function correctly. This setting is only effective if "Use Async Smart Code" is enabled. diff --git a/connections/destinations/catalog/webhooks/index.md b/connections/destinations/catalog/webhooks/index.md index 84e791352dd..1d043c7428d 100644 --- a/connections/destinations/catalog/webhooks/index.md +++ b/connections/destinations/catalog/webhooks/index.md @@ -9,8 +9,8 @@ This document was last updated on January 28, 2018. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Webhooks” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Webhooks" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Specify up to five different Webhook URLs, you would like to forward data to. 4. Add in any header values you would like to add to the HTTP requests 5. If you require authentication, add in a [shared secret](https://segment.com/docs/destinations/webhooks/#authentication). diff --git a/connections/destinations/catalog/wishpond/index.md b/connections/destinations/catalog/wishpond/index.md index f119ca01cee..144c66d7b70 100644 --- a/connections/destinations/catalog/wishpond/index.md +++ b/connections/destinations/catalog/wishpond/index.md @@ -11,7 +11,7 @@ Our Wishpond destination code is open sourced on Github. Feel free to check it o Wishpond works with our client-side javascript library: Analytics.js. -From your Segment Destinations page click on Wishpond. Drop in your Merchant ID and Trackey Key from Wishpond’s [“API Keys” dialog](https://www.wishpond.com/central/welcome?api_keys=true). These are also found in your Wishpond Account in the "API Keys" dropdown under your account name in the top right corner. +From your Segment Destinations page click on Wishpond. Drop in your Merchant ID and Trackey Key from Wishpond’s ["API Keys" dialog](https://www.wishpond.com/central/welcome?api_keys=true). These are also found in your Wishpond Account in the "API Keys" dropdown under your account name in the top right corner. We’ll automatically initialize Wishpond’s Tracking Code with your Tracking Key and Merchant ID upon loading Analytics.js. @@ -73,7 +73,7 @@ To more details how Wishpond's identify works please visit [Wishpond API Docs: # ### Destination is not working properly -Make sure you have copied the right keys from Wishpond’s [“API Keys” dialog](https://www.wishpond.com/central/welcome?api_keys=true), this destination will need `Merchant ID` and `Tracking Key`. +Make sure you have copied the right keys from Wishpond’s ["API Keys" dialog](https://www.wishpond.com/central/welcome?api_keys=true), this destination will need `Merchant ID` and `Tracking Key`. [Analytics.js]: https://segment.com/docs/libraries/analytics.js/ [ci-link]: https://circleci.com/gh/segment-integrations/analytics.js-integration-wishpond diff --git a/connections/destinations/catalog/wootric/index.md b/connections/destinations/catalog/wootric/index.md index dbe50cb00ac..dbbc60a5bfa 100644 --- a/connections/destinations/catalog/wootric/index.md +++ b/connections/destinations/catalog/wootric/index.md @@ -11,8 +11,8 @@ This document was last updated on October 15, 2018. If you notice any gaps, out- {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “{{integration.name}}” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "{{integration.name}}" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Drop in your {{integration.name}} "Account Token" in Segment's Settings UI. You can retrieve this from your {{integration.name}} Settings > Your unique Account Token is. It should look like "NPS-XXXXXXXX". 4. If you're using Segment's client-side `analytics.js` library, we asynchronously load {{integration.name}}'s Javascript library onto the page and the CDN will be updated in 5-10 minutes. diff --git a/connections/destinations/catalog/yandex-metrica/index.md b/connections/destinations/catalog/yandex-metrica/index.md index 4afc78b3bfe..6d91d914f2a 100644 --- a/connections/destinations/catalog/yandex-metrica/index.md +++ b/connections/destinations/catalog/yandex-metrica/index.md @@ -9,8 +9,8 @@ This document was last updated on January 18, 2019. If you notice any gaps, outd ## Getting Started -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Yandex.Metrica” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Yandex.Metrica" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Enter your Counter ID that you can find in your Yandex.Metrica UI navigating to Settings > Tag. 4. In about 5-10 minutes the CDN will be updated and Yandex.Metrica’s snippet will be initialized onto your page. diff --git a/connections/destinations/catalog/zendesk/index.md b/connections/destinations/catalog/zendesk/index.md index 01676f232b6..9b866a960ec 100644 --- a/connections/destinations/catalog/zendesk/index.md +++ b/connections/destinations/catalog/zendesk/index.md @@ -12,8 +12,8 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Zendesk” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Zendesk" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. There are two ways to authenticate your Zendesk account with Segment: * Use the standard email and password you use to Sign In to your Zendesk account. In the Zendesk settings, add your email in the **Email** setting and your password in the **Password** setting. * Use Zendesk OAuth with a unique token. Get the corresponding token from your Zendesk account: **Settings > Channels > API** and under the Settings Tab choose the corresponding token from the "Active API Tokens" list. In the Zendesk settings, add your `email/token` in the **Email** setting (i.e. `peter@intech.com/token` - use the actual word token in your email address) and add the actual token in the **Password** setting. diff --git a/connections/destinations/catalog/zopim/index.md b/connections/destinations/catalog/zopim/index.md index b067c6e1a28..8e4e110407f 100644 --- a/connections/destinations/catalog/zopim/index.md +++ b/connections/destinations/catalog/zopim/index.md @@ -13,8 +13,8 @@ This document was last updated on June 11th, 2018. If you notice any gaps, outda {% include content/connection-modes.md %} -1. From your Segment UI’s Destinations page click on “Add Destination”. -2. Search for “Zopim” within the Destinations Catalog and confirm the Source you’d like to connect to. +1. From your Segment UI’s Destinations page click on "Add Destination". +2. Search for "Zopim" within the Destinations Catalog and confirm the Source you’d like to connect to. 3. Add your Zopim ID to your Destination Settings. If you are using the `Chat Widget`, you can find your Zopim ID in the widget script itself. See example below: ``` diff --git a/connections/sources/catalog/cloud-apps/activecampaign/index.md b/connections/sources/catalog/cloud-apps/activecampaign/index.md index dad3cf975a2..79495a56ae9 100644 --- a/connections/sources/catalog/cloud-apps/activecampaign/index.md +++ b/connections/sources/catalog/cloud-apps/activecampaign/index.md @@ -17,24 +17,24 @@ If you have previously enabled sending email events via the ActiveCampaign desti 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `ActiveCampaign` for nickname and `activecampaign` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for ActiveCampaign.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for ActiveCampaign.** Copy this write key.  5. In your ActiveCampaign account, navigate to http://YOURACCOUNT.activehosted.com/apps/#/segment -6. Scroll to the bottom of the page to where it says “Send email events data from ActiveCampaign to Segment.” +6. Scroll to the bottom of the page to where it says "Send email events data from ActiveCampaign to Segment." -7. Click the “OFF” toggle. +7. Click the "OFF" toggle. ![off](https://cldup.com/QLv153k6CU.png) -8. This will open a modal for you to enter your Segment.com write key. Enter your write key and click “Connect”. +8. This will open a modal for you to enter your Segment.com write key. Enter your write key and click "Connect". -9. The toggle will now say “ON”. +9. The toggle will now say "ON". ![on](https://cldup.com/cv4rU1Ivg5.png) 10. Once the first event occurs, you’ll always see the last event that occurred in this box. ![last event](https://cldup.com/5OZGDQD3wB.png) -11. If you ever need to re-enter your Segment write key, just click “Re-enter your Segment write key.” +11. If you ever need to re-enter your Segment write key, just click "Re-enter your Segment write key." 12. In Segment, click into your ActiveCampaign Source in `segment.com//sources`. From there you’ll be able to add Destinations where you want to see email events. diff --git a/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md b/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md index b2d532064bd..0a62fbf5dfb 100644 --- a/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md +++ b/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md @@ -31,8 +31,8 @@ Segment `identify` events. ![Add your Segment writeKey](./images/amplitude-segment-writekey.png) 7. If you would like to set up automated export on an hourly or daily basis, - you can use Amplitude's Cohort Sync feature. Click “Advanced Preferences” - and select “Segment” as the integration. + you can use Amplitude's Cohort Sync feature. Click "Advanced Preferences" + and select "Segment" as the integration. 8. From your Segment account, click into your Amplitude Cohorts Source, and you’ll be able to add other downstream destinations where you want to see your Behavioral Cohort data. diff --git a/connections/sources/catalog/cloud-apps/autopilothq/index.md b/connections/sources/catalog/cloud-apps/autopilothq/index.md index 816084385fa..d47ddb8936d 100644 --- a/connections/sources/catalog/cloud-apps/autopilothq/index.md +++ b/connections/sources/catalog/cloud-apps/autopilothq/index.md @@ -13,7 +13,7 @@ This document was last updated on October 19, 2018. If you notice any gaps, outd ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for AutopilotHQ within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup flow to "Add Source". The nickname is a label used in the Segment interface, and Segment creates a related schema name, which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Sign in to your Autopilot account and visit the [Segment destination](https://app.autopilothq.com/#settings/app-connections/segment-sync) to connect. diff --git a/connections/sources/catalog/cloud-apps/blueshift/index.md b/connections/sources/catalog/cloud-apps/blueshift/index.md index b88c8b84f6c..df0a3ff88be 100644 --- a/connections/sources/catalog/cloud-apps/blueshift/index.md +++ b/connections/sources/catalog/cloud-apps/blueshift/index.md @@ -13,7 +13,7 @@ In your favorite BI or analytics tool, you’ll be able to analyze your email ca 1. From your workspace’s segment.com//sources page, click Add source. 2. Choose Blueshift. 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like Blueshift for nickname and Blueshift for the schema name. -4. The next page (“Overview”) will surface your Segment write key for Blueshift. Copy this write key. +4. The next page ("Overview") will surface your Segment write key for Blueshift. Copy this write key. 5. To finish the setup, you’ll have to go into your Blueshift account and enter this Segment write key in their destinations settings. Find the right place in Blueshift by clicking Account > Webhooks: ![](https://i.gyazo.com/39c3955d4ea74e0a8ff07ef6651d4b30.png) @@ -136,7 +136,7 @@ Below is a table of properties that are sent for the events above: ## UserId -Blueshift sends their `customer_id` associated with the message recipient as the top level `userId` field. Additionally, we will also send “email” and “blueshift_user_uuid” under `context.traits`. +Blueshift sends their `customer_id` associated with the message recipient as the top level `userId` field. Additionally, we will also send "email" and "blueshift_user_uuid" under `context.traits`. ## Send Data to Blueshift diff --git a/connections/sources/catalog/cloud-apps/braze/index.md b/connections/sources/catalog/cloud-apps/braze/index.md index 8f6aabb99ec..77fc4b65919 100644 --- a/connections/sources/catalog/cloud-apps/braze/index.md +++ b/connections/sources/catalog/cloud-apps/braze/index.md @@ -13,7 +13,7 @@ In your favorite BI or analytics tool, you’ll be able to analyze your mobile, 1. From your workspace Overview page, click Add Source. 2. Choose Braze 3. Give the Source a name. The name will be used to identify this source within your workspace. You can name it however you’d like, but we recommend sticking to something that reflects the Source itself, like Braze. -4. The next page “Overview” will surface your Segment write key for Braze. Copy this write key. +4. The next page "Overview" will surface your Segment write key for Braze. Copy this write key. 5. To finish the setup, you need to activate "Currents" in Braze which requires reaching out to Braze Support or your Customer Support Manager. Braze Currents is only available in select Braze packages and cannot be configured within Braze without assistance from your Braze Customer Success representative. diff --git a/connections/sources/catalog/cloud-apps/chatlio/index.md b/connections/sources/catalog/cloud-apps/chatlio/index.md index 579bdfc57d3..a01decc0079 100644 --- a/connections/sources/catalog/cloud-apps/chatlio/index.md +++ b/connections/sources/catalog/cloud-apps/chatlio/index.md @@ -10,7 +10,7 @@ Chatlio is a live chat tool that allows you to talk to your customers through yo 1. From your workspace’s `segment.com//sources` page, click Add source. 2. Choose Chatlio. 3. Give the Source a name. The name will be used to identify this source within your workspace. You can name it however you’d like, but we recommend sticking to something that reflects the Source itself, like Chatlio. -4. The next page “Overview” will surface your Segment write key for Chatlio. Copy this write key. +4. The next page "Overview" will surface your Segment write key for Chatlio. Copy this write key. 5. To finish the setup, you’ll have to go into your [Chatlio dashboard](https://chatlio.com/app/#/login) and enter the Segment write key in the settings towards the bottom of the page. 6. Now when you go back to Segment, click into your Chatlio Source and you’ll be able to add other downstream Destinations where you want to see live chat events. diff --git a/connections/sources/catalog/cloud-apps/customer.io/index.md b/connections/sources/catalog/cloud-apps/customer.io/index.md index ba83e06daad..3b37bae96d9 100644 --- a/connections/sources/catalog/cloud-apps/customer.io/index.md +++ b/connections/sources/catalog/cloud-apps/customer.io/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Customer.io destinat 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Customerio` for nickname and `customerio` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Customer.io.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Customer.io.** Copy this write key.  5. To finish the setup, you’ll have to go into your Customer.io account and enter this Segment write key in their integrations settings. Find the right place in Customer.io by clicking Settings > Integrations > Segment. diff --git a/connections/sources/catalog/cloud-apps/delighted/index.md b/connections/sources/catalog/cloud-apps/delighted/index.md index 5242ec55659..b937e79529f 100644 --- a/connections/sources/catalog/cloud-apps/delighted/index.md +++ b/connections/sources/catalog/cloud-apps/delighted/index.md @@ -12,7 +12,7 @@ This document was last updated on October 19, 2018. If you notice any gaps, outd ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for Delighted within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup steps to "Add Source". The nickname is used as a label for the source in your Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be anything, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Sign in to your Delighted account and visit the [Segment destination](https://delighted.com/integrations/segment) to connect. diff --git a/connections/sources/catalog/cloud-apps/drip/index.md b/connections/sources/catalog/cloud-apps/drip/index.md index 83ed21118c3..5a0e08f5e9c 100644 --- a/connections/sources/catalog/cloud-apps/drip/index.md +++ b/connections/sources/catalog/cloud-apps/drip/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Drip destination dur 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Drip` for nickname and `drip` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Drip.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Drip.** Copy this write key.  5. To finish the setup, you’ll have to go into your Drip account and enter this Segment write key in their integrations settings. Find the right place in Drip by clicking Settings > Integrations > Segment. diff --git a/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md b/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md index 69c259c6faf..2202cb4cb50 100644 --- a/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md +++ b/connections/sources/catalog/cloud-apps/facebook-lead-ads/index.md @@ -15,7 +15,7 @@ _**NOTE:** Facebook Lead Ads is currently in beta and this doc was last updated ## Getting Started 1. Set up a Facebook Lead Ad campaign if you haven’t already. Instructions on how to do so are [here](https://www.facebook.com/business/help/1462876307360828). -2. Search for "Facebook Lead Ads” within the Sources Catalog and confirm by clicking "Connect" +2. Search for "Facebook Lead Ads" within the Sources Catalog and confirm by clicking "Connect" 3. Give the source a name. The name is a label used in the Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself, like Facebook Lead Ads or Facebook Lead Ads Prod.  4. Click Create And Continue then Connect to OAuth into Facebook. 5. Select which accounts you would like to sync (you may change this selection later). diff --git a/connections/sources/catalog/cloud-apps/factual-engine/index.md b/connections/sources/catalog/cloud-apps/factual-engine/index.md index 5d139183bbd..63cfa09531b 100644 --- a/connections/sources/catalog/cloud-apps/factual-engine/index.md +++ b/connections/sources/catalog/cloud-apps/factual-engine/index.md @@ -4,7 +4,7 @@ beta: true --- ## How Engine Works -Installing the Engine SDK in your app enables you to gather and analyze information about your users’ location. Engine caches the relevant portion of Factual’s Global Places data on the device to determine where the user is, beyond raw location. Engine needs device location data in order to work and will use whatever location permissions your app has authorized. You can also set custom rules to trigger “actions” like push notifications or emails. +Installing the Engine SDK in your app enables you to gather and analyze information about your users’ location. Engine caches the relevant portion of Factual’s Global Places data on the device to determine where the user is, beyond raw location. Engine needs device location data in order to work and will use whatever location permissions your app has authorized. You can also set custom rules to trigger "actions" like push notifications or emails. The Factual Engine Source is a cloud-based event source. You simply include, configure, and initialize the Engine SDK as you normally would, and then add only a few lines of code to trigger correctly formatted events to Segment in response to your dynamic triggers and actions. This event data then flows seamlessly to your downstream Segment Destinations. Once the Factual Engine Source is enabled, any Segment Destination that can accept server-to-server data can accept data from Factual Engine. The data is also automatically streamed into your next warehouse sync. The data generated from the Factual Engine can also be easily combined with other Source data collected via Segment without any additional development work on your end. diff --git a/connections/sources/catalog/cloud-apps/iterable/index.md b/connections/sources/catalog/cloud-apps/iterable/index.md index 5d6cda8734d..cc9160d982b 100644 --- a/connections/sources/catalog/cloud-apps/iterable/index.md +++ b/connections/sources/catalog/cloud-apps/iterable/index.md @@ -22,7 +22,7 @@ If you have previously enabled sending email events via the Iterable destination ![](images/Iterable2.png) -4. The next page (“Overview”) will surface your **Segment write key for Iterable.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Iterable.** Copy this write key.  ![](images/Iterable3.png) diff --git a/connections/sources/catalog/cloud-apps/klaviyo/index.md b/connections/sources/catalog/cloud-apps/klaviyo/index.md index da20fdd1ccd..4f6df62e281 100644 --- a/connections/sources/catalog/cloud-apps/klaviyo/index.md +++ b/connections/sources/catalog/cloud-apps/klaviyo/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Klaviyo destination 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Klaviyo` for nickname and `klaviyo` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Klaviyo.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Klaviyo.** Copy this write key.  5. To finish the setup, you’ll have to go into your Klaviyo account and enter this Segment write key in their integrations settings. Find the right place in Klaviyo by clicking [Integrations > Segment](https://www.klaviyo.com/integration/segment_io). diff --git a/connections/sources/catalog/cloud-apps/klenty/index.md b/connections/sources/catalog/cloud-apps/klenty/index.md index 22ef2f398de..dab2c3936d1 100644 --- a/connections/sources/catalog/cloud-apps/klenty/index.md +++ b/connections/sources/catalog/cloud-apps/klenty/index.md @@ -11,7 +11,7 @@ _**NOTE:** The Klenty Source is currently in beta, which means that they are sti ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for "Klenty" within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup flow to "Add Source". The nickname is a label used in the Segment interface, and Segment creates a related schema name which you query against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (Eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Copy the Write key from the Segment UI and log in to your Klenty account - navigate to Settings > Integrations > Segment Integration and paste the key to connect. diff --git a/connections/sources/catalog/cloud-apps/looker/index.md b/connections/sources/catalog/cloud-apps/looker/index.md index 5a777e8195a..6145519c047 100644 --- a/connections/sources/catalog/cloud-apps/looker/index.md +++ b/connections/sources/catalog/cloud-apps/looker/index.md @@ -11,7 +11,7 @@ From Segment's end, you will need to create a Looker source, and copy your write Using this Source, Looker will send Look (query) results into Segment as `identify` calls. This is the only API method that Looker sends to Segment. Any user trait that you include as a column in your Look will be included as a user trait on these identify call. -Note: When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. “churn risk”) and that trait already exists in your tools, syncing the user profile to the downstream tool will override the existing trait value with the new one. +Note: When you set up your Look and generate new user traits (column names), avoid using trait names that may already exist in your marketing tools. If you create a new user trait in Looker (e.g. "churn risk") and that trait already exists in your tools, syncing the user profile to the downstream tool will override the existing trait value with the new one. Below is an example of a cohort of users in Looker who have been active on toastmates.com (example website) at least once in the last 30 days. diff --git a/connections/sources/catalog/cloud-apps/mailjet/index.md b/connections/sources/catalog/cloud-apps/mailjet/index.md index 18954578e09..02c5cf3702a 100644 --- a/connections/sources/catalog/cloud-apps/mailjet/index.md +++ b/connections/sources/catalog/cloud-apps/mailjet/index.md @@ -17,7 +17,7 @@ If you have previously enabled sending email events via the Mailjet destination 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Mailjet` for nickname and `Mailjet` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Mailjet.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Mailjet.** Copy this write key.  5. To finish the setup, you’ll have to go into your Mailjet account and enter this Segment write key in their integrations settings. Find the right place in Mailjet by clicking App Connections > Segment. diff --git a/connections/sources/catalog/cloud-apps/mandrill/index.md b/connections/sources/catalog/cloud-apps/mandrill/index.md index 0ca99dad95d..0e31cb11d1b 100644 --- a/connections/sources/catalog/cloud-apps/mandrill/index.md +++ b/connections/sources/catalog/cloud-apps/mandrill/index.md @@ -32,7 +32,7 @@ Take your company’s email analysis to the next level by **adding Mandrill as a ### Streaming -The Mandrill source is comprised only of a streaming component which listens in real time for inbound webhooks from [Mandrill’s Webhooks](https://mandrill.zendesk.com/hc/en-us/articles/205583217-Introduction-to-Webhooks) and batches the events to be uploaded on your next warehouse flush. These events are only ever appended to your warehouse. Since Mandrill is strictly used for transactional emails triggered directly by API calls, there are no “dimensional” concepts in their data model that would require any additional components. +The Mandrill source is comprised only of a streaming component which listens in real time for inbound webhooks from [Mandrill’s Webhooks](https://mandrill.zendesk.com/hc/en-us/articles/205583217-Introduction-to-Webhooks) and batches the events to be uploaded on your next warehouse flush. These events are only ever appended to your warehouse. Since Mandrill is strictly used for transactional emails triggered directly by API calls, there are no "dimensional" concepts in their data model that would require any additional components. ## Collections diff --git a/connections/sources/catalog/cloud-apps/nudgespot/index.md b/connections/sources/catalog/cloud-apps/nudgespot/index.md index 6db8fb3539e..184dc606727 100644 --- a/connections/sources/catalog/cloud-apps/nudgespot/index.md +++ b/connections/sources/catalog/cloud-apps/nudgespot/index.md @@ -17,7 +17,7 @@ If you have previously enabled sending email events via the Nudgespot destinatio 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Nudgespot` for nickname and `nudgespot` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Nudgespot.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Nudgespot.** Copy this write key.  5. To finish the setup, you’ll have to go into your Nudgespot account and enter this Segment write key in their integrations settings. Find the right place in Nudgespot in Setup > Send Email Events to Segment.com. diff --git a/connections/sources/catalog/cloud-apps/provesource/index.md b/connections/sources/catalog/cloud-apps/provesource/index.md index e142af0c9a1..9adab9fa11c 100644 --- a/connections/sources/catalog/cloud-apps/provesource/index.md +++ b/connections/sources/catalog/cloud-apps/provesource/index.md @@ -9,7 +9,7 @@ _**NOTE:** The ProveSource Source is currently in beta, which means that they ar ## Getting Started -1. From your Segment UI’s Sources page click on “Add Source”. +1. From your Segment UI’s Sources page click on "Add Source". 2. Search for "ProveSource" within the Sources Catalog and confirm by clicking "Connect". 3. Give the Source a nickname and follow the setup flow to "Add Source". The nickname will be used to designate the source in the Segment interface, and Segment will create a related schema name. The schema name is the namespace you'll be querying against in your warehouse. The nickname can be whatever you like, but we recommend sticking to something that reflects the source itself and distinguishes amongst your environments (eg. SourceName_Prod, SourceName_Staging, SourceName_Dev). 4. Copy the Write key from the Segment UI and log in to your ProveSource account - navigate to [Settings](https://console.provesrc.com/#/settings) > Integrations > Click Edit next to Segment Integration and paste the key to connect. diff --git a/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md b/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md index 63bb2518487..4a4dd76e771 100644 --- a/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md +++ b/connections/sources/catalog/cloud-apps/salesforce-marketing-cloud/index.md @@ -56,7 +56,7 @@ and client secret: You should now see a Summary page with a Components section. This section lists your _Client ID_ and _Client Secret_ settings. ### Set up your subdomain -Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters “mc” in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. +Segment will use your unique Salesforce subdomain to make API calls to SFMC. Your subdomain is represented by a 28-character string starting with the letters "mc" in any of your base URIs. For example, in the base URI `mc563885gzs27c5t9-63k636ttgm.rest.marketingcloudapis.com`, the subdomain is `mc563885gzs27c5t9-63k636ttgm`. ### Enable the Salesforce Marketing Cloud Source diff --git a/connections/sources/catalog/cloud-apps/selligent/index.md b/connections/sources/catalog/cloud-apps/selligent/index.md index 9220d1fe10e..0945a260900 100644 --- a/connections/sources/catalog/cloud-apps/selligent/index.md +++ b/connections/sources/catalog/cloud-apps/selligent/index.md @@ -18,7 +18,7 @@ If you have previously enabled sending email events via the Selligent destinatio 3. Give the Source a nickname and a schema name. The nickname is a label used in the Segment interface, and the schema name is the namespace you query against in your warehouse. You can name them however you’d like, but we recommend sticking to something that reflects the Source itself, like `Selligent` for nickname and `selligent` for the schema name. -4. The next page (“Overview”) will surface your **Segment write key for Selligent.** Copy this write key. +4. The next page ("Overview") will surface your **Segment write key for Selligent.** Copy this write key. 5. To finish the setup, send your write key to your Selligent Account Manager. He/she will enable the Source for you on Selligent's end. diff --git a/connections/sources/catalog/cloud-apps/vero/index.md b/connections/sources/catalog/cloud-apps/vero/index.md index c7b90a1f453..4b96ad71f21 100644 --- a/connections/sources/catalog/cloud-apps/vero/index.md +++ b/connections/sources/catalog/cloud-apps/vero/index.md @@ -21,7 +21,7 @@ If you have previously enabled sending email events via the Vero destination dur ![](images/vero2.png) -4. The next page (“Overview”) will surface your **Segment write key for Vero.** Copy this write key.  +4. The next page ("Overview") will surface your **Segment write key for Vero.** Copy this write key.  5. To finish the setup, you’ll have to go into your Vero account and enter this Segment write key in their integrations settings. Find the right place in Vero by clicking [Integrations](https://app.getvero.com/settings/integrations?integrations=all) > Segment. diff --git a/connections/sources/catalog/cloud-apps/zendesk/index.md b/connections/sources/catalog/cloud-apps/zendesk/index.md index d8da001d4cf..5a09159f8cc 100644 --- a/connections/sources/catalog/cloud-apps/zendesk/index.md +++ b/connections/sources/catalog/cloud-apps/zendesk/index.md @@ -242,7 +242,7 @@ In your warehouse, each collection gets its own table. Find below a list of the type - The type of this ticket. Possible values: "problem", "incident", "question" or "task”. + The type of this ticket. Possible values: "problem", "incident", "question" or "task". subject @@ -262,7 +262,7 @@ In your warehouse, each collection gets its own table. Find below a list of the status - The state of the ticket. Possible values: "new", "open", "pending", "hold", "solved", "closed”. + The state of the ticket. Possible values: "new", "open", "pending", "hold", "solved", "closed". recipient diff --git a/connections/sources/catalog/mobile/android/index.md b/connections/sources/catalog/mobile/android/index.md index 597034e245a..d8d2f80720f 100644 --- a/connections/sources/catalog/mobile/android/index.md +++ b/connections/sources/catalog/mobile/android/index.md @@ -196,7 +196,7 @@ import com.segment.analytics.Properties.Product; Properties properties = new Properties(); // add orderId and revenue to the properties object -properties.putValue(“orderId”, String orderId).putValue(“revenue”, double revenue); +properties.putValue("orderId", String orderId).putValue("revenue", double revenue); // initialize a new product Product product1 = new Product(String id, String sku, double price); @@ -208,7 +208,7 @@ Product product2 = new Product(String id, String sku, double price); properties.putProducts(product1, product2); // pass the properties object into your Order Completed event -Analytics.with(context).track(“Order Completed”, properties); +Analytics.with(context).track("Order Completed", properties); ``` Find details on **best practices in event naming** as well as the **`track` method payload** in our [Spec](/docs/spec/track/). diff --git a/connections/sources/catalog/ott/roku/index.md b/connections/sources/catalog/ott/roku/index.md index 2b8166e9e27..4ce92b71848 100644 --- a/connections/sources/catalog/ott/roku/index.md +++ b/connections/sources/catalog/ott/roku/index.md @@ -33,7 +33,7 @@ The library consists of three parts: 2. **source/SegmentAnalytics.brs** - Implementation responsible for making HTTP requests to Segment REST API for identify, track, screen, group or alias. Includes handling for batching, error handling. Must be used within context of SceneGraph Task node. Cannot be used directly within context of SceneGraph UI components. 3. **components/SegmentAnalyticsTask.brs/xml** - SceneGraph Task node that will be running for the entire lifecycle of the app. Responsible for delegating calls to SegmentAnalytics.brs to make requests to Segment REST API. -The “components” folder contains SceneGraph components and the “source” folder contains BrightScript files. The content of each folder must be included in the respective folder of the application. Depending on the application folder structure and where the library files are included, SegmentAnalyticsTask.xml might need to be updated to reflect the file paths. +The "components" folder contains SceneGraph components and the "source" folder contains BrightScript files. The content of each folder must be included in the respective folder of the application. Depending on the application folder structure and where the library files are included, SegmentAnalyticsTask.xml might need to be updated to reflect the file paths. ### Initializing the library @@ -43,32 +43,32 @@ To instantiate the library, you first need to update the application scene .xml 1. Include SegmentAnalyticsConnector.brs BrightScript file ``` -