From 77b387d80d6cd3ddf8c2d551e25f89a50fc711fa Mon Sep 17 00:00:00 2001 From: sanscontext Date: Mon, 12 Aug 2019 19:15:18 -0700 Subject: [PATCH 1/4] 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 71b2d913b3..38311b916f 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 42bab03b1a..77ebb86e6e 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 3b53365361..03656a5c3e 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 096c89062b..98de902f04 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 dfe3117135..1b8a837e52 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 9038039280..b3e990e89f 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 30853930e3..cc6104bbf8 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 382b466630..339e8ca159 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 8504a0f19e..98e077c0ce 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 45ca7eda41..7f5e2ecb6d 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 93a2e99a42..b979c0f914 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 2aa03ad69b..6a8a11a3bd 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 0c5e595f99..614c31726d 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 c9f250a852..d87dfcfac1 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 307af2ba7e..f773acb3a8 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 723603f8a0..4a7fffa46f 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 25ea29e540..44e068cae3 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 36e3881608..0dda87127f 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 1bdc61003a..01c48b74da 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 35ddbc572b..c7b9db4443 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 9d4cb8f3be..4399fa2112 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 7c2d6b0e86..26b5046600 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 67dbc93e7e..c19bd4f44d 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 81fd805c17..7e999e7599 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 d0b6266857..a7459c114b 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 dd4e10502a..293c57e21d 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 c669bd3096..c95dc3bfd7 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 f25003560d..1f63932fa8 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/4] 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 a9a4a3b270..8ad6525efd 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 717122491f..c6bbd3bfa5 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 0f9eb39264..58974a3632 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 eef613f05c..9b0bb643c5 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 215357959b..a4f17ab711 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 eb988c0bc8..d218d69f31 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 c353abb2d5..4468c13227 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 1367530906..d728d31d80 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 d35c73c200..5e7fa157c5 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 8f1504f7cc..d9c76f367a 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 73045c6141..3c2c3d7097 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 80d62695d1..f2185ec3f8 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 0a701833a2..aac7696177 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 86278b0ba7..ca3b84c44b 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 a0ace2da78..927905da05 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 45c32eebf6..76d2745b45 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 1e9e04a049..edaad2a08c 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 9aad083fb9..7141cd38de 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 1c8ac346d3..0b4e5ed32b 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 fc620bbc7e..8da72e019e 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 ef9e5cbf88..7ccefcffd7 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 1058242bc3..f0aea1f1a5 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 a25f786505..97ed3e6ec6 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 a9cabff2ba..3cca7546af 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 72386e9f32..ce4f905b3e 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 828efdb436..46217bd8fe 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 34f9676026..13072c2e97 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 57ddf43ba9..3ddf6a5a39 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 b703b1a2b9..9e9a21be33 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 c6a9a11826..12153e0207 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 8a041aa4da..fb49e10262 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 81abad4d60..ea6374addf 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 2dbb8b204c..26c02bc51e 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 dd14fc85f7..d109b67065 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 875ee9a79a..058ed54823 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 19c1583dc8..fc1057050d 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 d9bc6188a9..db63f0e97b 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 52c6652beb..10d7d0aaf6 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 4da9c6f15c..24ac8711e3 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 e633cabbf6..70be0db45d 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 312cd154e1..3fa99b6332 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 b9f3f7b384..6e294371b0 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 6ede9ab6d3..f104ce17e7 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 7ee7a18f53..eaea3bfdad 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 1f63932fa8..68f04bb769 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/4] 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 00501e2a7d..c7cd1201f1 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 f327370ed1..6c9fbda3f2 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 8015991e70..53fd5291f8 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/4] 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 950bcd4da0..2f085e556d 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 95186ddab5..011005176f 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 81211f3caf..2f1c821690 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 3b015c3fe4..fa4def0a84 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 b9d8a8cb5a..231aa98dee 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 83bdd80ea0..49aa57ee7b 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 b1f4dac891..4c63196305 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 77f266bca1..3eb215161e 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 3f0a8a7e94..7ddd8cb607 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 d5c3e992a2..2f1ae00007 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 a70aac1eb3..dca43df404 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 a36b10a5cb..5d72e323f9 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 9f468ece85..f7c8c9f13e 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 160eff0103..9ee0b353dc 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 3ff149e0b9..cbcde61b9f 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 db58a49125..d9acce2553 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 7eb295303c..73f5052230 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 0493bdd9f2..5ab806cd56 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 4cb1cb48f9..7050cc6bd2 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 06b6c4249c..05bcc9ac6c 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 f5cfea17ec..b9edb56c3b 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 4111b4cf60..b9788583aa 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 5c04df1df8..7193f816e0 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 07bd9b9790..1fe5d604cb 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 fef71feac6..7ee174b3f3 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 7b663c7d2d..69ddb69240 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 d5f15c1528..37501f7e7b 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 985d8e3577..fa02119265 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 5f5c9eb589..79bb8d093a 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 ea82bd9c3f..14747b8748 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 e17e28b670..e505bb55bf 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 64ce5d0f64..892bb2af06 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 15950b10e8..459671e0db 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 6af73cf745..c1042cd673 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 197e70d400..6581d42f92 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 1e961b9d36..9a60dc102a 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 e7985e4cef..ba54b75a47 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 bd030bbdc9..6e2719cdb3 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 2cbceb931c..cad2fb3e27 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 7e014cc4a0..0a6267c6c7 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 1dd63e8243..14d787b84a 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 1dd2b88672..ca3fbdc9a4 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 d238f30802..e84a1309a5 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 53caf30dbf..bc6e5a4663 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 b675ed0695..a3af25eb11 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 d5593d15c4..7aa2d5f068 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 073bc5cf66..2685cc5973 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 289f426da5..e5136b0b9e 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 905b684a40..c73ab46027 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 61deaa6b51..601aa59b01 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 283f72bd65..2d6a293228 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 9b2ca22779..ffd85a557d 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 7ef300e848..1629825b8e 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 36e901ffa2..ac04ad66f6 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 af73479085..61dc5e8de2 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 b13718e1d0..aff9b5b42f 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 f5f1bc3010..dca81fef41 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 7c1dabb7fa..f119ca01ce 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 6e72fd7bba..2cb39f1a2b 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 f469b8b8b1..7d74d217da 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 59bbe802ce..e2e4c84926 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 68f04bb769..b0c0baab2f 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