From 6f70071555157cdb23936b2393bcc42372535529 Mon Sep 17 00:00:00 2001 From: markzegarelli Date: Wed, 10 Nov 2021 16:06:03 -0800 Subject: [PATCH] round 3 --- lychee.toml | 2 +- .../catalog/activecampaign/index.md | 6 +-- .../destinations/catalog/adquick/index.md | 8 ++-- .../destinations/catalog/adroll/index.md | 10 ++--- .../destinations/catalog/adtriba/index.md | 10 ++--- .../catalog/algolia-insights/index.md | 4 +- .../catalog/amazon-eventbridge/index.md | 6 +-- .../catalog/amazon-kinesis-firehose/index.md | 8 ++-- .../catalog/amazon-kinesis/index.md | 8 ++-- .../catalog/amazon-lambda/index.md | 2 +- .../destinations/catalog/ambassador/index.md | 4 +- .../destinations/catalog/amplitude/index.md | 14 +++--- .../destinations/catalog/anodot/index.md | 8 ++-- .../destinations/catalog/appsflyer/index.md | 10 ++--- .../destinations/catalog/apptimize/index.md | 6 +-- .../destinations/catalog/asayer/index.md | 4 +- .../destinations/catalog/attribution/index.md | 8 ++-- .../destinations/catalog/auryc/index.md | 4 +- .../destinations/catalog/autopilothq/index.md | 6 +-- .../destinations/catalog/batch/index.md | 2 +- .../destinations/catalog/beamer/index.md | 2 +- .../destinations/catalog/bing-ads/index.md | 4 +- .../destinations/catalog/blendo/index.md | 8 ++-- .../catalog/branch-metrics/index.md | 6 +-- .../destinations/catalog/bucket/index.md | 6 +-- .../destinations/catalog/bugsnag/index.md | 2 +- .../destinations/catalog/button/index.md | 10 ++--- .../destinations/catalog/buzzboard/index.md | 2 +- .../destinations/catalog/bytegain/index.md | 8 ++-- .../destinations/catalog/calixa/index.md | 18 ++++---- .../destinations/catalog/callingly/index.md | 2 +- .../destinations/catalog/candu/index.md | 8 ++-- .../destinations/catalog/castle/index.md | 2 +- .../destinations/catalog/churnzero/index.md | 4 +- .../catalog/clearbit-enrichment/index.md | 2 +- .../catalog/clearbit-reveal/index.md | 2 +- .../destinations/catalog/clevertap/index.md | 4 +- .../destinations/catalog/clicky/index.md | 6 +-- .../destinations/catalog/cliff/index.md | 10 ++--- .../destinations/catalog/comscore/index.md | 2 +- .../destinations/catalog/convertflow/index.md | 2 +- .../destinations/catalog/courier/index.md | 4 +- .../destinations/catalog/crazy-egg/index.md | 2 +- .../catalog/criteo-app-web-events/index.md | 4 +- .../criteo-offline-conversions/index.md | 4 +- .../destinations/catalog/crowdpower/index.md | 4 +- .../destinations/catalog/custify/index.md | 6 +-- .../catalog/customersuccessbox/index.md | 8 ++-- .../catalog/customfit-ai/index.md | 8 ++-- .../destinations/catalog/cxense/index.md | 2 +- .../destinations/catalog/databrain/index.md | 12 ++--- .../destinations/catalog/delighted/index.md | 6 +-- .../destinations/catalog/digioh/index.md | 4 +- .../catalog/dreamdata-io/index.md | 10 ++--- .../destinations/catalog/drift/index.md | 8 ++-- .../destinations/catalog/elevio/index.md | 2 +- .../destinations/catalog/eloqua/index.md | 4 +- .../destinations/catalog/emma/index.md | 2 +- .../destinations/catalog/enjoyhq/index.md | 2 +- .../destinations/catalog/epica/index.md | 8 ++-- .../destinations/catalog/evergage/index.md | 4 +- .../experiments-by-growthhackers/index.md | 2 +- .../destinations/catalog/exponea/index.md | 14 +++--- .../catalog/extole-platform/index.md | 4 +- .../facebook-offline-conversions/index.md | 4 +- .../destinations/catalog/factorsai/index.md | 8 ++-- .../destinations/catalog/firebase/index.md | 4 +- .../destinations/catalog/flurry/index.md | 6 +-- .../destinations/catalog/foxmetrics/index.md | 6 +-- .../catalog/freshmarketer/index.md | 2 +- .../destinations/catalog/fullstory/index.md | 4 +- .../destinations/catalog/funnelenvy/index.md | 4 +- .../destinations/catalog/funnelfox/index.md | 8 ++-- .../catalog/gainsight-px/index.md | 6 +-- .../destinations/catalog/gainsight/index.md | 6 +-- .../destinations/catalog/gameball/index.md | 4 +- .../destinations/catalog/gist/index.md | 4 +- .../destinations/catalog/goedle-io/index.md | 30 ++++++------- .../catalog/google-ads-gtag/index.md | 4 +- .../catalog/google-analytics/migrating.md | 4 +- .../catalog/google-tag-manager/index.md | 4 +- .../destinations/catalog/hawkei/index.md | 8 ++-- .../destinations/catalog/headsup-ai/index.md | 8 ++-- .../destinations/catalog/heap/index.md | 4 +- .../destinations/catalog/help-scout/index.md | 4 +- .../destinations/catalog/hotjar/index.md | 2 +- .../destinations/catalog/hydra/index.md | 4 +- .../destinations/catalog/ibm-ubx/index.md | 2 +- .../catalog/impact-partnership-cloud/index.md | 8 ++-- .../destinations/catalog/impact/index.md | 8 ++-- .../destinations/catalog/indicative/index.md | 8 ++-- .../destinations/catalog/insider/index.md | 6 +-- .../destinations/catalog/journy-io/index.md | 8 ++-- .../destinations/catalog/june/index.md | 8 ++-- .../destinations/catalog/kahuna/index.md | 6 +-- .../destinations/catalog/kevel/index.md | 2 +- .../destinations/catalog/kissmetrics/index.md | 20 ++++----- .../destinations/catalog/kitemetrics/index.md | 6 +-- .../destinations/catalog/klaviyo/index.md | 2 +- .../destinations/catalog/kochava/index.md | 2 +- .../destinations/catalog/kubit/index.md | 4 +- .../destinations/catalog/kubric/index.md | 8 ++-- .../destinations/catalog/kustomer/index.md | 12 ++--- .../catalog/launchdarkly-events/index.md | 2 +- .../destinations/catalog/leanplum/index.md | 14 +++--- .../destinations/catalog/learndot/index.md | 8 ++-- .../destinations/catalog/lou/index.md | 4 +- .../catalog/lucky-orange/index.md | 2 +- .../destinations/catalog/mabl/index.md | 4 +- .../destinations/catalog/mailchimp/index.md | 2 +- .../destinations/catalog/mammoth/index.md | 8 ++-- .../destinations/catalog/marketo-v2/index.md | 6 +-- .../destinations/catalog/matomo/index.md | 6 +-- .../destinations/catalog/metacx/index.md | 8 ++-- .../catalog/modern-pricing/index.md | 2 +- .../catalog/moesif-api-analytics/index.md | 8 ++-- .../destinations/catalog/mouseflow/index.md | 4 +- .../destinations/catalog/movable-ink/index.md | 6 +-- .../destinations/catalog/msg91/index.md | 8 ++-- .../destinations/catalog/mutiny/index.md | 6 +-- .../destinations/catalog/nat/index.md | 2 +- .../destinations/catalog/new-relic/index.md | 2 +- .../destinations/catalog/noora/index.md | 2 +- .../catalog/optimizely-web/index.md | 10 ++--- .../catalog/owneriq-pixel/index.md | 6 +-- .../destinations/catalog/parsely/index.md | 12 ++--- .../destinations/catalog/persistiq/index.md | 2 +- .../destinations/catalog/personyze/index.md | 2 +- .../destinations/catalog/pixelme/index.md | 8 ++-- .../destinations/catalog/podsights/index.md | 18 ++++---- .../destinations/catalog/posthog/index.md | 10 ++--- .../destinations/catalog/productbird/index.md | 2 +- .../destinations/catalog/profitwell/index.md | 2 +- .../catalog/proof-experiences/index.md | 6 +-- .../destinations/catalog/qualaroo/index.md | 4 +- .../destinations/catalog/quanticmind/index.md | 6 +-- .../catalog/quora-conversion-pixel/index.md | 2 +- .../destinations/catalog/recombee-ai/index.md | 44 +++++++++---------- .../destinations/catalog/refersion/index.md | 2 +- .../destinations/catalog/refiner/index.md | 8 ++-- .../destinations/catalog/responsys/index.md | 2 +- .../destinations/catalog/retently/index.md | 2 +- .../destinations/catalog/sailthru/index.md | 2 +- .../catalog/salescamp-crm/index.md | 2 +- .../salesforce-marketing-cloud/index.md | 6 +-- .../destinations/catalog/savio/index.md | 4 +- .../destinations/catalog/screeb/index.md | 6 +-- .../catalog/scuba-analytics/index.md | 8 ++-- .../destinations/catalog/segmetrics/index.md | 6 +-- .../destinations/catalog/sentry/index.md | 2 +- .../destinations/catalog/serenytics/index.md | 8 ++-- .../catalog/signl4-alerting/index.md | 12 ++--- .../destinations/catalog/singular/index.md | 6 +-- .../destinations/catalog/slack/index.md | 16 +++---- .../destinations/catalog/slicingdice/index.md | 10 ++--- .../destinations/catalog/smartlook/index.md | 4 +- .../destinations/catalog/snapboard/index.md | 10 ++--- .../destinations/catalog/snapengage/index.md | 6 +-- .../destinations/catalog/split/index.md | 18 ++++---- .../destinations/catalog/stonly/index.md | 6 +-- .../destinations/catalog/stormly/index.md | 8 ++-- .../destinations/catalog/survicate/index.md | 4 +- .../destinations/catalog/talonone/index.md | 4 +- .../destinations/catalog/tamber/index.md | 6 +-- .../destinations/catalog/trackier/index.md | 2 +- .../catalog/trafficguard/index.md | 6 +-- .../destinations/catalog/trustpilot/index.md | 2 +- .../destinations/catalog/tune/index.md | 10 ++--- .../destinations/catalog/twitter-ads/index.md | 2 +- .../destinations/catalog/unwaffle/index.md | 6 +-- .../destinations/catalog/upcall/index.md | 4 +- .../destinations/catalog/useriq/index.md | 8 ++-- .../destinations/catalog/userleap/index.md | 8 ++-- .../destinations/catalog/userlike/index.md | 2 +- .../destinations/catalog/userlist/index.md | 6 +-- .../destinations/catalog/userpilot/index.md | 6 +-- .../destinations/catalog/uservoice/index.md | 6 +-- .../destinations/catalog/variance/index.md | 8 ++-- .../destinations/catalog/vero/index.md | 2 +- .../destinations/catalog/vespucci/index.md | 8 ++-- .../destinations/catalog/vidora/index.md | 10 ++--- .../destinations/catalog/vitally/index.md | 4 +- .../destinations/catalog/voucherify/index.md | 4 +- .../destinations/catalog/walkme/index.md | 6 +-- .../destinations/catalog/watchtower/index.md | 8 ++-- .../catalog/whale-alerts/index.md | 2 +- .../destinations/catalog/wigzo/index.md | 8 ++-- .../destinations/catalog/windsor/index.md | 22 +++++----- .../catalog/wootric-by-inmoment/index.md | 6 +-- .../destinations/catalog/xtremepush/index.md | 4 +- .../destinations/catalog/youbora/index.md | 4 +- .../destinations/catalog/zendesk/index.md | 6 +-- .../destinations/catalog/zopim/index.md | 2 +- .../cloud-apps/amplitude-cohorts/index.md | 2 +- .../catalog/cloud-apps/zendesk/index.md | 2 +- .../catalog/libraries/server/net/index.md | 2 +- .../catalog/libraries/server/php/index.md | 2 +- .../storage/catalog/postgres/index.md | 2 +- 198 files changed, 600 insertions(+), 600 deletions(-) diff --git a/lychee.toml b/lychee.toml index f32ef4ac01..7bf8b7716c 100644 --- a/lychee.toml +++ b/lychee.toml @@ -50,7 +50,7 @@ headers = [] ### Exclusions ### # Exclude URLs from checking (supports regex) -exclude = ['https://segment.zendesk.com','(example-service)','(redacted)','(foo)','http://dl.bintray.com/swrve-inc/android','https://ajs.cd.segment.com/analytics.js/v1/','http://0.0.0.0:4000','https://api.segment.io/v1/', 'https://segment.com/docs/assets/docs.bundle.js','https://www.linkedin.com', 'https://segment.com/jobs/', 'https://segment.com/press/', 'https://github.com/segmentio', 'https://unpkg.com/@segment/consent-manager@4.2.2/standalone/consent-manager.js', '(segment.com)', '(segmentapis.com)', '(example.com)', '(schema.org)','(maxcdn)', '(your-org-name)', '(mywebsite)'] +exclude = ['(acme.com)','(webhooks.company.com)','(your-webhook-url)','https://segment.zendesk.com','(example-service)','(redacted)','(foo)','http://dl.bintray.com/swrve-inc/android','https://ajs.cd.segment.com/analytics.js/v1/','http://0.0.0.0:4000','https://api.segment.io/v1/', 'https://segment.com/docs/assets/docs.bundle.js','https://www.linkedin.com', 'https://segment.com/jobs/', 'https://segment.com/press/', 'https://github.com/segmentio', 'https://unpkg.com/@segment/consent-manager@4.2.2/standalone/consent-manager.js', '(segment.com)', '(segmentapis.com)', '(example.com)', '(schema.org)','(maxcdn)', '(your-org-name)', '(mywebsite)'] # Exclude URLs contained in a file from checking exclude_file = [] diff --git a/src/connections/destinations/catalog/activecampaign/index.md b/src/connections/destinations/catalog/activecampaign/index.md index 34d1267f5a..863c968b92 100644 --- a/src/connections/destinations/catalog/activecampaign/index.md +++ b/src/connections/destinations/catalog/activecampaign/index.md @@ -19,7 +19,7 @@ This destination is maintained by ActiveCampaign. For any issues with the destin ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page(); @@ -32,7 +32,7 @@ When you call `page`, we will send that event to ActiveCampaign as a `site track ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('ze8rt1u89', { @@ -119,7 +119,7 @@ analytics.identify('ze8rt1u89', { ``` ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Clicked a button', { diff --git a/src/connections/destinations/catalog/adquick/index.md b/src/connections/destinations/catalog/adquick/index.md index 9955d400a9..aaee26b3fc 100644 --- a/src/connections/destinations/catalog/adquick/index.md +++ b/src/connections/destinations/catalog/adquick/index.md @@ -21,7 +21,7 @@ This destination is maintained by AdQuick. For any issues with the destination, ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -32,7 +32,7 @@ Page calls will be sent to AdQuick as a `pageview`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -43,7 +43,7 @@ Screen calls will be sent to AdQuick as a `screenview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -56,7 +56,7 @@ Identify calls will be sent to AdQuick as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/adroll/index.md b/src/connections/destinations/catalog/adroll/index.md index dcf4477212..131076ed51 100644 --- a/src/connections/destinations/catalog/adroll/index.md +++ b/src/connections/destinations/catalog/adroll/index.md @@ -19,7 +19,7 @@ title: AdRoll Destination ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page() ``` @@ -27,18 +27,18 @@ _**NOTE:** The `page` call **must** be made on a page for any `identify` or `tra ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('123', { email: 'testing@segment.com' }); ``` -Set a `userId` using the `identify` call which will then be passed it to AdRoll each time a [`track`](https://segment.com/docs/connections/destinations/catalog/adroll/#track) call is made. If you pass an `email` trait, we'll send that to AdRoll by setting `window.adroll_email` to that value. +Set a `userId` using the `identify` call which will then be passed it to AdRoll each time a [`track`](/docs/connections/destinations/catalog/adroll/#track) call is made. If you pass an `email` trait, we'll send that to AdRoll by setting `window.adroll_email` to that value. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track('Sign-up Form Completed'); ``` @@ -88,7 +88,7 @@ analytics.track('Vewed Product', { ### **Legacy:** Named Segments -Prior to rolling out Segment ID's, AdRoll allowed "named segments". If your account was created prior to 2015, then the track events you send from the browser using our [`analytics.track`](https://segment.com/docs/connections/destinations/catalog/adroll/#track) method will be passed on to AdRoll as `adroll_segments` with the segment being the snake-cased event name. +Prior to rolling out Segment ID's, AdRoll allowed "named segments". If your account was created prior to 2015, then the track events you send from the browser using our [`analytics.track`](/docs/connections/destinations/catalog/adroll/#track) method will be passed on to AdRoll as `adroll_segments` with the segment being the snake-cased event name. ## Troubleshooting diff --git a/src/connections/destinations/catalog/adtriba/index.md b/src/connections/destinations/catalog/adtriba/index.md index 56fb8d7201..7ea65d916e 100644 --- a/src/connections/destinations/catalog/adtriba/index.md +++ b/src/connections/destinations/catalog/adtriba/index.md @@ -17,12 +17,12 @@ This destination is maintained by Adtriba. For any issues with the destination, 1. From the Segment web app, click **Catalog**. 2. Search for "Adtriba" in the Catalog, select it, and choose which of your sources to connect the destination to. -3. Enter the "Project Tracker ID / API Key" into your Segment Settings UI which you can find from your [Adtriba dashboard](https://console.adtriba.com). +3. Enter the "Project Tracker ID / API Key" into your Segment Settings UI which you can find from the Adtriba dashboard. 4. Validate the forwarded events by checking the Tracking Report under the "Tracking" tab. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -33,7 +33,7 @@ Page calls will be sent to Adtriba as a `pageview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -46,7 +46,7 @@ Identify calls will be sent to Adtriba as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Conversion', { @@ -58,4 +58,4 @@ 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/connections/spec/semantic/) in order to enrich the Adtriba machine learning process. +Trigger additional events by using [Semantic Events](/docs/connections/spec/semantic/) in order to enrich the Adtriba machine learning process. diff --git a/src/connections/destinations/catalog/algolia-insights/index.md b/src/connections/destinations/catalog/algolia-insights/index.md index d582b28404..c96feb3508 100644 --- a/src/connections/destinations/catalog/algolia-insights/index.md +++ b/src/connections/destinations/catalog/algolia-insights/index.md @@ -32,9 +32,9 @@ You can read more about how to send Algolia-related data to Segment from [the do ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. -Algolia supports the following six events from Segment's [Ecommerce Spec](https://segment.com/docs/connections/spec/ecommerce/v2/). +Algolia supports the following six events from Segment's [Ecommerce Spec](/docs/connections/spec/ecommerce/v2/). diff --git a/src/connections/destinations/catalog/amazon-eventbridge/index.md b/src/connections/destinations/catalog/amazon-eventbridge/index.md index 1ebe41159e..0b85e24d02 100644 --- a/src/connections/destinations/catalog/amazon-eventbridge/index.md +++ b/src/connections/destinations/catalog/amazon-eventbridge/index.md @@ -20,13 +20,13 @@ The Event Source will be denoted by your Segment Source ID, which you can find i We'll forward all the messages in the source (pending any Destination Filters you've enabled) to the Segment Partner Event Source we create for you in EventBridge. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page(); ``` ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example identify call is shown below: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example identify call is shown below: ```javascript analytics.identify('97980cfea0085', { email: 'gibbons@example.com', @@ -35,7 +35,7 @@ analytics.identify('97980cfea0085', { ``` ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example identify call is shown below: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example identify call is shown below: ```javascript analytics.track("User Registered", { diff --git a/src/connections/destinations/catalog/amazon-kinesis-firehose/index.md b/src/connections/destinations/catalog/amazon-kinesis-firehose/index.md index 89cc2c5ba7..284e1a2994 100644 --- a/src/connections/destinations/catalog/amazon-kinesis-firehose/index.md +++ b/src/connections/destinations/catalog/amazon-kinesis-firehose/index.md @@ -49,13 +49,13 @@ To get started: 2. Search and select the **Amazon Kinesis Firehose** destination and enter details for [these settings options](#settings). ## Page -Take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +Take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page(); ``` ## Identify -Take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example identify call is shown below: +Take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example identify call is shown below: ```javascript analytics.identify('97980cfea0085', { email: 'gibbons@example.com', @@ -64,7 +64,7 @@ analytics.identify('97980cfea0085', { ``` ## Track -Take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example identify call is shown below: +Take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example identify call is shown below: ```js analytics.track("User Registered", { @@ -116,7 +116,7 @@ firehose.putRecord({ Segment appends a newline character to each record to allow for easy downstream parsing. ## Group -Take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example group call is shown below: +Take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example group call is shown below: ```js analytics.group("0e8c78ea9d9dsasahjg", { diff --git a/src/connections/destinations/catalog/amazon-kinesis/index.md b/src/connections/destinations/catalog/amazon-kinesis/index.md index a808e206ce..03a6f0a412 100644 --- a/src/connections/destinations/catalog/amazon-kinesis/index.md +++ b/src/connections/destinations/catalog/amazon-kinesis/index.md @@ -51,14 +51,14 @@ To get started: * **NOTE:** For security purposes, Segment sets your Workspace ID as your Secret ID. If you’re using a Secret ID different from your Workspace ID, reach out to our support team so they can change it to make your account more secure. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page(); ``` ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('97980cfea0085', { @@ -68,7 +68,7 @@ analytics.identify('97980cfea0085', { ``` ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track("User Registered", { @@ -105,7 +105,7 @@ Segment uses the the `userId || anonymousId` as the `PartitionKey`. The partitio > **NOTE:** The JSON payload is base64 stringified. ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example group call is shown below: ```js diff --git a/src/connections/destinations/catalog/amazon-lambda/index.md b/src/connections/destinations/catalog/amazon-lambda/index.md index 2377eaacbd..ce864beeac 100644 --- a/src/connections/destinations/catalog/amazon-lambda/index.md +++ b/src/connections/destinations/catalog/amazon-lambda/index.md @@ -193,7 +193,7 @@ This setting controls the [Log Type](https://docs.aws.amazon.com/lambda/latest/d Due to how our event delivery system, [Centrifuge](https://segment.com/blog/introducing-centrifuge/), works, your Lambda can't take more than 5 seconds to run per message. If you're consistently running into timeout issues, you should consult the [AWS Lambda docs](https://docs.aws.amazon.com/lambda/index.html#lang/en_us), as well as docs for your language of choice, for tips on optimizing performance. **Handling Common Errors** -You can find delivery logs in Destination > [Event Delivery](https://segment.com/docs/guides/destinations/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/). +You can find delivery logs in Destination > [Event Delivery](/docs/guides/destinations/how-do-i-check-if-data-is-successfully-being-delivered-to-my-destination/). Here are some common errors you may come across and how to resolve: diff --git a/src/connections/destinations/catalog/ambassador/index.md b/src/connections/destinations/catalog/ambassador/index.md index c5d71a5290..020f7fdf64 100644 --- a/src/connections/destinations/catalog/ambassador/index.md +++ b/src/connections/destinations/catalog/ambassador/index.md @@ -22,7 +22,7 @@ Since Ambassador only records specific events and user data, events and users ma ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. For Ambassador it takes the unique `userId` of a user and a specific set of traits. All supported `traits` are listed in the example below: @@ -47,7 +47,7 @@ _**NOTE:** You can optionally use the URL campaign map to enroll the user as an ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. For Ambassador `track` events will be recorded as a conversion if the Segment event name is mapped to a campaign in your Ambassador destination settings in the Segment UI. All supported `properties` are listed in the example below: diff --git a/src/connections/destinations/catalog/amplitude/index.md b/src/connections/destinations/catalog/amplitude/index.md index fc29e6ec8c..ce643b9f8a 100644 --- a/src/connections/destinations/catalog/amplitude/index.md +++ b/src/connections/destinations/catalog/amplitude/index.md @@ -54,7 +54,7 @@ If you included Segment's Javascript snippet on your page, then Amplitude's SDK ## Page and Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Page](https://segment.com/docs/connections/spec/page/) and [Screen](https://segment.com/docs/connections/spec/screen/) methods do. By default, Segment does not send these standard calls to Amplitude. However, you can enable them with the destination settings below, which you can find under the "Optional Settings" tab. +If you're not familiar with the Segment Specs, take a look to understand what the [Page](/docs/connections/spec/page/) and [Screen](/docs/connections/spec/screen/) methods do. By default, Segment does not send these standard calls to Amplitude. However, you can enable them with the destination settings below, which you can find under the "Optional Settings" tab. The example below shows a Page call from a server library. @@ -129,7 +129,7 @@ and Screen calls from our [Screen spec](/docs/connections/spec/screen/). ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js // On server-side @@ -214,7 +214,7 @@ same user, you must pass the same `deviceID` to Amplitude. Otherwise, Amplitude creates two users - one for each of the `deviceID`'s set per the functionality outlined in the tables above. You can get the `deviceID` from Amplitude in device-mode so you can return it on cloud-mode calls. The example method below shows how you could log the `deviceId` in the -[`ready`](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#ready) +[`ready`](/docs/connections/sources/catalog/libraries/website/javascript/#ready) function on the device, so you could send it to the server. ```js @@ -231,7 +231,7 @@ When a user logs in, be sure to send the same Amplitude `deviceID` in your Ident ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. Amplitude supports several special properties, all of which are included in the example below: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. Amplitude supports several special properties, all of which are included in the example below: ```js // On server-side @@ -326,7 +326,7 @@ For Segment's Analytics.js (device-mode), iOS, and Android sources, if you do no Segment recommends that you use the [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) event to track revenue with Amplitude. This event allows you to define a list of products that a user purchased in a single transaction, which is the best way to track purchases for sites that have a shopping cart system. -You can currently use this event only for data coming from a server or web [source](https://segment.com/docs/connections/sources/). An `Order Completed` event from mobile using our bundled Amplitude integration +You can currently use this event only for data coming from a server or web [source](/docs/connections/sources/). An `Order Completed` event from mobile using our bundled Amplitude integration will work the same as our standard `track` event documented above. Here's an example of how you'd create an "Order Completed" event: @@ -382,7 +382,7 @@ Make sure you are using formatting your events using the [Track method spec](/do ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. > warning "" > Groups are an enterprise-only feature in Amplitude, and are only available if you've purchased the Accounts add-on. @@ -460,7 +460,7 @@ or are sending Alias events from a Segment server-side library (such as Node). > note "" > To use Alias, you must have the Amplitude Portfolio add-on enabled. -For more information, see the [Segment Spec page for the Alias method](https://segment.com/docs/connections/spec/alias/) and [the Amplitude `usermap` documentation](https://amplitude.zendesk.com/hc/en-us/articles/360002750712-Portfolio-Cross-Project-Analysis#user-mapping-aliasing). +For more information, see the [Segment Spec page for the Alias method](/docs/connections/spec/alias/) and [the Amplitude `usermap` documentation](https://amplitude.zendesk.com/hc/en-us/articles/360002750712-Portfolio-Cross-Project-Analysis#user-mapping-aliasing). | Segment identifier name | Equivalent Amplitude identifier name | |--|--| diff --git a/src/connections/destinations/catalog/anodot/index.md b/src/connections/destinations/catalog/anodot/index.md index d5d78de5f2..209a3a057c 100644 --- a/src/connections/destinations/catalog/anodot/index.md +++ b/src/connections/destinations/catalog/anodot/index.md @@ -19,7 +19,7 @@ This destination is maintained by Anodot. For any issues with the destination, [ ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -29,7 +29,7 @@ Segment sends Page calls to Anodot as a `pageview`. ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ``` obj-c [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -39,7 +39,7 @@ Segment sends Screen calls to Anodot as a `screenview`. ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -51,7 +51,7 @@ Segment sends Identify calls to Anodot as an `identify` event. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/appsflyer/index.md b/src/connections/destinations/catalog/appsflyer/index.md index 0708177726..dcfc858070 100644 --- a/src/connections/destinations/catalog/appsflyer/index.md +++ b/src/connections/destinations/catalog/appsflyer/index.md @@ -44,7 +44,7 @@ To use the latest AppsFlyer SDK to collect IDFAs, do the following: } } ``` -5. Follow [Segment's guide for collecting IDFA](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#idfa-collection-in-40-beta-and-later) +5. Follow [Segment's guide for collecting IDFA](/docs/connections/sources/catalog/libraries/mobile/ios/#idfa-collection-in-40-beta-and-later) #### Additional iOS Cloud Mode Set up for iOS 14 @@ -68,7 +68,7 @@ If you want to use AppsFlyer server-side only, contact your AppsFlyer representa ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example iOS call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example iOS call would look like: ```swift [[SEGAnalytics sharedAnalytics] identify:@"12091906-01011992" @@ -81,7 +81,7 @@ When you call `.identify()`, we will use AppsFlyer's `setCustomerUserID` to send ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example iOS call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example iOS call would look like: ```swift [[SEGAnalytics sharedAnalytics] track:@"Article Completed" @@ -92,7 +92,7 @@ When you call `track`, Segment translates it automatically and sends the event We include all the event properties as callback parameters on the AppsFlyer event, and automatically translate `properties.revenue` to the appropriate AppsFlyer purchase event properties based on our spec'd properties. -Finally, we automatically use AppsFlyer's `transactionId` deduplication when you send an an `orderId` (see the [e-commerce spec](https://segment.com/docs/connections/spec/ecommerce/v2/)). +Finally, we automatically use AppsFlyer's `transactionId` deduplication when you send an an `orderId` (see the [e-commerce spec](/docs/connections/spec/ecommerce/v2/)). ### Server @@ -131,7 +131,7 @@ analytics.track({ } }); ``` -> Check your specific [serverside library docs](https://segment.com/docs/connections/sources/#server) for specifics on how to format the method properly. +> Check your specific [serverside library docs](/docs/connections/sources/#server) for specifics on how to format the method properly. Finally, the serverside component will look for the following `properties` and handle them specially: diff --git a/src/connections/destinations/catalog/apptimize/index.md b/src/connections/destinations/catalog/apptimize/index.md index e4bc12648a..8643e4cab8 100644 --- a/src/connections/destinations/catalog/apptimize/index.md +++ b/src/connections/destinations/catalog/apptimize/index.md @@ -67,7 +67,7 @@ It is important to note that if the app keys in the plist/code and the Segment d ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example iOS call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example iOS call would look like: ```swift [[SEGAnalytics sharedAnalytics] screen:@"Photo Feed" @@ -78,7 +78,7 @@ When you record a `screen`, Apptimize will track an event of the form `Viewed [S ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example iOS call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example iOS call would look like: ```swift [[SEGAnalytics sharedAnalytics] identify:@"12091906-01011992" @@ -89,7 +89,7 @@ When you `identify` a user, Segment will pass that user's information to Apptimi ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example iOS call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example iOS call would look like: ```swift [[SEGAnalytics sharedAnalytics] track:@"Article Completed" diff --git a/src/connections/destinations/catalog/asayer/index.md b/src/connections/destinations/catalog/asayer/index.md index 29f40a75fd..63511577df 100644 --- a/src/connections/destinations/catalog/asayer/index.md +++ b/src/connections/destinations/catalog/asayer/index.md @@ -23,7 +23,7 @@ In the meantime, remove Asayer's native snippet from your site. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to Asayer's `asayer.vars` method. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to Asayer's `asayer.vars` method. An example call which does not include a `userId` will transmit Asayer the value of the `anonymousId` and would look like: ```js @@ -48,7 +48,7 @@ analytics.identify("userId123", { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('New Order', { diff --git a/src/connections/destinations/catalog/attribution/index.md b/src/connections/destinations/catalog/attribution/index.md index 4bb5772085..24cbd140da 100644 --- a/src/connections/destinations/catalog/attribution/index.md +++ b/src/connections/destinations/catalog/attribution/index.md @@ -20,7 +20,7 @@ This destination is maintained by Attribution. For any issues with the destinati ## Page -If you haven’t had a chance to review our spec, take a look tounderstand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you haven’t had a chance to review our spec, take a look tounderstand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page("pageLoaded"); @@ -32,7 +32,7 @@ Page calls are sent to Attribution to record visits on your dashboard. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify("userId123", { @@ -46,7 +46,7 @@ Identify calls are sent to Attribution as an `identify` event and are used to as ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track("Clicked Login Button") @@ -57,7 +57,7 @@ Track calls are sent to Attribution as a `conversion event`. You should add a `c ![page](images/att5.png) ## Alias -If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](https://segment.com/docs/connections/spec/alias/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](/docs/connections/spec/alias/) does. An example call would look like: ```js analytics.alias('507f191e81'); diff --git a/src/connections/destinations/catalog/auryc/index.md b/src/connections/destinations/catalog/auryc/index.md index 1c4b58a6ba..16f61692f2 100644 --- a/src/connections/destinations/catalog/auryc/index.md +++ b/src/connections/destinations/catalog/auryc/index.md @@ -22,7 +22,7 @@ And you’re done! Once you click "Allow", Auryc shows an installation confirmat ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. Identify calls will be sent to Auryc as an `identify` event and `addUserProperties` event. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. Identify calls will be sent to Auryc as an `identify` event and `addUserProperties` event. If the call only contains the user id and does not have the traits, the user id will be sent to Auryc as identity. @@ -45,7 +45,7 @@ analytics.identify("userId123", { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Order Submitted', {price: 234.12}) diff --git a/src/connections/destinations/catalog/autopilothq/index.md b/src/connections/destinations/catalog/autopilothq/index.md index 42491fc875..e51348229e 100644 --- a/src/connections/destinations/catalog/autopilothq/index.md +++ b/src/connections/destinations/catalog/autopilothq/index.md @@ -6,7 +6,7 @@ title: Autopilot Destination This destination is maintained by Autopilot. See [Autopilot's documentation](https://support.autopilothq.com/hc/en-us/categories/200396835-Segment) for more information. For any issues with the destination, [contact our friends at Autopilot](https://support.autopilothq.com/hc/en-us/requests/new). -Are you instead trying to set up Autopilot as a Source to get data from Autopilot into your data warehouse or other downstream tools? See our documentation on our [Autopilot source](https://segment.com/docs/connections/sources/catalog/cloud-apps/autopilothq/) instead. +Are you instead trying to set up Autopilot as a Source to get data from Autopilot into your data warehouse or other downstream tools? See our documentation on our [Autopilot source](/docs/connections/sources/catalog/cloud-apps/autopilothq/) instead. This document was last updated on October 12, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)! @@ -21,7 +21,7 @@ This document was last updated on October 12, 2018. If you notice any gaps, outd ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('12091906-01011992', { @@ -32,7 +32,7 @@ analytics.identify('12091906-01011992', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track("Step Activated", { diff --git a/src/connections/destinations/catalog/batch/index.md b/src/connections/destinations/catalog/batch/index.md index e6adb1c0da..6049da9ca5 100644 --- a/src/connections/destinations/catalog/batch/index.md +++ b/src/connections/destinations/catalog/batch/index.md @@ -95,4 +95,4 @@ 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 use the Batch native SDK through Segment, follow the [instructions for Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/#how-can-i-use-a-destination-specific-feature) and [instructions for iOS](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#what-if-your-sdk-doesnt-support-feature-x). +To use the Batch native SDK through Segment, follow the [instructions for Android](/docs/connections/sources/catalog/libraries/mobile/android/#how-can-i-use-a-destination-specific-feature) and [instructions for iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#what-if-your-sdk-doesnt-support-feature-x). diff --git a/src/connections/destinations/catalog/beamer/index.md b/src/connections/destinations/catalog/beamer/index.md index bf0a001c22..58b0327346 100644 --- a/src/connections/destinations/catalog/beamer/index.md +++ b/src/connections/destinations/catalog/beamer/index.md @@ -26,7 +26,7 @@ You can select any of the existing API keys in [your list](https://app.getbeamer ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify({ diff --git a/src/connections/destinations/catalog/bing-ads/index.md b/src/connections/destinations/catalog/bing-ads/index.md index 58c83ee2d9..c4c93c7106 100644 --- a/src/connections/destinations/catalog/bing-ads/index.md +++ b/src/connections/destinations/catalog/bing-ads/index.md @@ -25,7 +25,7 @@ _**Note:** You'll only be able to include one Tag ID per source so make sure to ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript // name and properties are optional @@ -36,7 +36,7 @@ Page events will be sent to Bing Ads as a `Page Load` event where name and prope ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. In order for us to map your track events to a Conversion Goal, you'll first need to create the goal on your Bing Ads account: diff --git a/src/connections/destinations/catalog/blendo/index.md b/src/connections/destinations/catalog/blendo/index.md index 52ecbca97c..2ec78d32f1 100644 --- a/src/connections/destinations/catalog/blendo/index.md +++ b/src/connections/destinations/catalog/blendo/index.md @@ -21,7 +21,7 @@ This destination is maintained by Blendo. For any issues with the destination, [ ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -32,7 +32,7 @@ Page calls will be sent to Blendo as a `pageview`, which will be copied to your ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -43,7 +43,7 @@ Screen calls will be sent to Blendo as a `screenview`, which will be copied to y ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -56,7 +56,7 @@ Identify calls will be sent to Blendo as an `identify` event, which will be copi ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/branch-metrics/index.md b/src/connections/destinations/catalog/branch-metrics/index.md index 96900d485e..c0d363e42e 100644 --- a/src/connections/destinations/catalog/branch-metrics/index.md +++ b/src/connections/destinations/catalog/branch-metrics/index.md @@ -12,7 +12,7 @@ hide-personas-partial: true Existing users of the Branch SDKs are unaffected, however new installations must implement the Branch native SDK separately. They can then enable Branch's [data export integration](https://docs.branch.io/integrations/segment-export/) to push additional data to Segment, and [data import integration](https://docs.branch.io/integrations/segment-import/) to pull additional Segment data into the Branch dashboard. -The legacy instructions for implementing the Branch mobile SDKs for Segment have been removed from this documentation. If you need access to the removed sections, you can view them [here](https://web.archive.org/web/20191113225102/https://segment.com/docs/connections/destinations/catalog/branch-metrics/). +The legacy instructions for implementing the Branch mobile SDKs for Segment have been removed from this documentation. If you need access to the removed sections, you can view them [here](https://web.archive.org/web/20191113225102//docs/connections/destinations/catalog/branch-metrics/). --- @@ -55,7 +55,7 @@ To add the Branch device-mode SDK to a [React Native](/docs/connections/sources/ ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example iOS call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example iOS call would look like: ```swift [[SEGAnalytics sharedAnalytics] identify:@"12091906-01011992" traits:@{ @"email": @"john.doe@example.com" }]; @@ -63,7 +63,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example iOS call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example iOS call would look like: ```swift [[SEGAnalytics sharedAnalytics] track:@"Article Completed" diff --git a/src/connections/destinations/catalog/bucket/index.md b/src/connections/destinations/catalog/bucket/index.md index d3142e819d..ad5bf4b1ed 100644 --- a/src/connections/destinations/catalog/bucket/index.md +++ b/src/connections/destinations/catalog/bucket/index.md @@ -18,7 +18,7 @@ This destination is maintained by Bucket. For any issues with the destination, [ ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -31,7 +31,7 @@ Segment sends Identify calls to Bucket as an `identify` event which updates User ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.identify('groupId123', { @@ -43,7 +43,7 @@ Segment sends Group calls to Bucket as a `group` event which updates Company pro ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked', { diff --git a/src/connections/destinations/catalog/bugsnag/index.md b/src/connections/destinations/catalog/bugsnag/index.md index 31402cfe3b..5ead595919 100644 --- a/src/connections/destinations/catalog/bugsnag/index.md +++ b/src/connections/destinations/catalog/bugsnag/index.md @@ -44,7 +44,7 @@ If you'd like to integrate with Bugsnag's iOS and/or Android SDKs, in addition t Once you've correctly set up your Bugsnag integration, you should [`identify`](/docs/connections/spec/identify/) each of your users as soon as you know their identity (this typically happens after log in or sign up), so that Bugsnag can provide you with more visibility into which user is encountering which error. -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('ze8rt1u89', { diff --git a/src/connections/destinations/catalog/button/index.md b/src/connections/destinations/catalog/button/index.md index 715e5445b8..e07ff149f1 100644 --- a/src/connections/destinations/catalog/button/index.md +++ b/src/connections/destinations/catalog/button/index.md @@ -19,7 +19,7 @@ This destination is maintained by Button. For any issues with the destination, [ 4. Enter the "API Key" in the Button destination settings in Segment. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Deep Link Opened') @@ -28,7 +28,7 @@ analytics.track('Deep Link Opened') Segment sends Track calls to Button as a `track` event. ### Deep links -To track deep links from your app or website, use Segment's [Deep Link Opened](https://segment.com/docs/connections/spec/mobile/#deep-link-opened) and [Application Opened](https://segment.com/docs/connections/spec/mobile/#application-opened) events. +To track deep links from your app or website, use Segment's [Deep Link Opened](/docs/connections/spec/mobile/#deep-link-opened) and [Application Opened](/docs/connections/spec/mobile/#application-opened) events. Make sure you pass the referring URL. An example would look like: @@ -46,7 +46,7 @@ analytics.track('Application Opened' { someProperty: true }, { > **Tip!** Make sure you record any different names for `Deep Link Opened` Track events across your sources so you know which are sent where. ### Installs -To track mobile app installs, use Segment's [Application Installed](https://segment.com/docs/connections/spec/mobile/#application-installed) event. +To track mobile app installs, use Segment's [Application Installed](/docs/connections/spec/mobile/#application-installed) event. Capture the referring URL when possible. An example would look like: @@ -76,7 +76,7 @@ analytics.track('Application Installed' { someProperty: true }, { > **Tip!** Make sure you record any different names for `Application Installed` Track events across your sources so you know which are sent where. ### Orders -To track `order` events from your app or website, use Segment's [Order Completed](https://segment.com/docs/connections/spec/ecommerce/v2/#order-completed) event. +To track `order` events from your app or website, use Segment's [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) event. An example call would look like: @@ -111,7 +111,7 @@ analytics.track('Order Completed' { someProperty: true }, { ## Setting up a Destination Filter -If you are a Business Tier customer, you can set up a [Destination Filter](https://segment.com/docs/connections/destinations/destination-filters/) to only send your `Deep link` and `Order` events to Button. +If you are a Business Tier customer, you can set up a [Destination Filter](/docs/connections/destinations/destination-filters/) to only send your `Deep link` and `Order` events to Button. Read [Button's Destination Filter documentation](https://developer.usebutton.com/docs/segment-integration-guide) to learn more. diff --git a/src/connections/destinations/catalog/buzzboard/index.md b/src/connections/destinations/catalog/buzzboard/index.md index 2d4a212c84..6af4324d43 100644 --- a/src/connections/destinations/catalog/buzzboard/index.md +++ b/src/connections/destinations/catalog/buzzboard/index.md @@ -22,7 +22,7 @@ This destination is maintained by BuzzBoard. For any issues with the destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('John123', { diff --git a/src/connections/destinations/catalog/bytegain/index.md b/src/connections/destinations/catalog/bytegain/index.md index 38158881ad..3b12e13eeb 100644 --- a/src/connections/destinations/catalog/bytegain/index.md +++ b/src/connections/destinations/catalog/bytegain/index.md @@ -20,7 +20,7 @@ This destination is maintained by ByteGain. For any issues with the destination, ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -31,7 +31,7 @@ Page calls will be sent to ByteGain as a `page` event. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -42,7 +42,7 @@ Screen calls will be sent to ByteGain as a `screen` event. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -55,7 +55,7 @@ Identify calls will be sent to ByteGain as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/calixa/index.md b/src/connections/destinations/catalog/calixa/index.md index 279feec92f..a74c5fdd00 100644 --- a/src/connections/destinations/catalog/calixa/index.md +++ b/src/connections/destinations/catalog/calixa/index.md @@ -16,7 +16,7 @@ This destination is maintained by Calixa. For any issues with the destination, [ 3. Select the Segment Integration and sign in to your Segment account to grant Calixa access. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```json { @@ -32,16 +32,16 @@ If you aren't familiar with the Segment Spec, take a look at the [Track method d } ``` -Calixa supports the following Track calls from Segment's [B2B Spec](https://segment.com/docs/connections/spec/b2b-saas/): +Calixa supports the following Track calls from Segment's [B2B Spec](/docs/connections/spec/b2b-saas/): -* [Signed Up](https://segment.com/docs/connections/spec/b2b-saas/#signed-up) - Creates a user in Calixa -* [Account Created](https://segment.com/docs/connections/spec/b2b-saas/#account-created) - Creates an account in Calixa -* [Account Deleted](https://segment.com/docs/connections/spec/b2b-saas/#account-deleted) - Deletes an account in Calixa -* [Account Added User](https://segment.com/docs/connections/spec/b2b-saas/#account-added-user) - Adds a user to an account -* [Account Removed User](https://segment.com/docs/connections/spec/b2b-saas/#account-removed-user) - Removes a user from an account +* [Signed Up](/docs/connections/spec/b2b-saas/#signed-up) - Creates a user in Calixa +* [Account Created](/docs/connections/spec/b2b-saas/#account-created) - Creates an account in Calixa +* [Account Deleted](/docs/connections/spec/b2b-saas/#account-deleted) - Deletes an account in Calixa +* [Account Added User](/docs/connections/spec/b2b-saas/#account-added-user) - Adds a user to an account +* [Account Removed User](/docs/connections/spec/b2b-saas/#account-removed-user) - Removes a user from an account ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -51,7 +51,7 @@ analytics.identify('userId123', { Segment sends Identify calls to Calixa as an `identify` event. When you identify a new user, Calixa creates a new User record. If the User already exists, Calixa updates the User's properties. ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```json { 'type': 'group', diff --git a/src/connections/destinations/catalog/callingly/index.md b/src/connections/destinations/catalog/callingly/index.md index e4dd5b7b72..1427d128dd 100644 --- a/src/connections/destinations/catalog/callingly/index.md +++ b/src/connections/destinations/catalog/callingly/index.md @@ -21,7 +21,7 @@ This destination is maintained by Callingly. For any issues with the destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/candu/index.md b/src/connections/destinations/catalog/candu/index.md index af24dd2791..c435d5b6fb 100644 --- a/src/connections/destinations/catalog/candu/index.md +++ b/src/connections/destinations/catalog/candu/index.md @@ -20,7 +20,7 @@ This destination is maintained by Candu Labs. For any issues with the destinatio ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js @@ -31,7 +31,7 @@ Page calls will be sent to Candu as a `page` event. You will be able to use `pag ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: @@ -42,7 +42,7 @@ Screen calls will be sent to Candu as a `screen` event. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: @@ -55,7 +55,7 @@ analytics.identify('userId123', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: diff --git a/src/connections/destinations/catalog/castle/index.md b/src/connections/destinations/catalog/castle/index.md index a350309e5a..7ef965d9c6 100644 --- a/src/connections/destinations/catalog/castle/index.md +++ b/src/connections/destinations/catalog/castle/index.md @@ -134,7 +134,7 @@ For privacy reasons, **you do not want to send the "Cookie" header to Castle**, There are example implementations on how to extract request headers in [PHP](https://github.com/castle/castle-php/blob/e93de1532ef28af17b8bf2bef350e6995a580085/lib/Castle/Request.php#L31), [Ruby](https://github.com/castle/castle-ruby/blob/master/lib/castle-rb/client.rb#L54), and [Java](https://github.com/castle/castle-java/blob/96cdc7469aa0995a836100c3dfd370b10f299e8c/src/main/java/io/castle/client/objects/UserInfoHeader.java#L148). ## Identify -When you call [`identify`](https://segment.com/docs/connections/spec/identify), a user will be created in Castle. The Segment special traits `email`, `username`, `name`, `createdAt`, `phone`, and `address` are mapped to Castle's reserved [user traits](https://castle.io/docs/castlejs#attributes). +When you call [`identify`](/docs/connections/spec/identify), a user will be created in Castle. The Segment special traits `email`, `username`, `name`, `createdAt`, `phone`, and `address` are mapped to Castle's reserved [user traits](https://castle.io/docs/castlejs#attributes). Any additional traits will be stored on the Castle user model as _custom traits_. diff --git a/src/connections/destinations/catalog/churnzero/index.md b/src/connections/destinations/catalog/churnzero/index.md index 4a860627be..592b3de450 100644 --- a/src/connections/destinations/catalog/churnzero/index.md +++ b/src/connections/destinations/catalog/churnzero/index.md @@ -19,7 +19,7 @@ This destination is maintained by ChurnZero. For any issues with the destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -32,7 +32,7 @@ Identify calls will match to Accounts and Contacts in ChurnZero when you pass th ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/clearbit-enrichment/index.md b/src/connections/destinations/catalog/clearbit-enrichment/index.md index ba55c1a481..ef73167b58 100644 --- a/src/connections/destinations/catalog/clearbit-enrichment/index.md +++ b/src/connections/destinations/catalog/clearbit-enrichment/index.md @@ -19,7 +19,7 @@ To verify that the destination has been set up correctly, check the Debugger sec ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('pixar123', { diff --git a/src/connections/destinations/catalog/clearbit-reveal/index.md b/src/connections/destinations/catalog/clearbit-reveal/index.md index 3f393e8238..d7d51a235f 100644 --- a/src/connections/destinations/catalog/clearbit-reveal/index.md +++ b/src/connections/destinations/catalog/clearbit-reveal/index.md @@ -27,7 +27,7 @@ To verify that the destination has been set up correctly, send a page event **th ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page('Home', { diff --git a/src/connections/destinations/catalog/clevertap/index.md b/src/connections/destinations/catalog/clevertap/index.md index 070277b42e..d58313b381 100644 --- a/src/connections/destinations/catalog/clevertap/index.md +++ b/src/connections/destinations/catalog/clevertap/index.md @@ -34,7 +34,7 @@ Please also note that the default logic for our cloud mode connection to CleverT ### Order Completed -When you `track` an event using the server-side destination with the name `Order Completed` using the [e-commerce tracking API](https://segment.com/docs/connections/spec/ecommerce/v2/), we will map that event to CleverTap's [Charged](https://support.clevertap.com/docs/working-with-events.html#recording-customer-purchases) event. +When you `track` an event using the server-side destination with the name `Order Completed` using the [e-commerce tracking API](/docs/connections/spec/ecommerce/v2/), we will map that event to CleverTap's [Charged](https://support.clevertap.com/docs/working-with-events.html#recording-customer-purchases) event. ## Page @@ -125,7 +125,7 @@ CleverTap has created a sample Android application that integrates CleverTap usi ### Integrating Push -1. Follow the directions to register for push at: [https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#how-do-i-use-push-notifications](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#how-do-i-use-push-notifications). +1. Follow the directions to register for push at: [/docs/connections/sources/catalog/libraries/mobile/ios/#how-do-i-use-push-notifications](/docs/connections/sources/catalog/libraries/mobile/ios/#how-do-i-use-push-notifications). 2. In your application's application:didReceiveRemoteNotification: method, add the following: diff --git a/src/connections/destinations/catalog/clicky/index.md b/src/connections/destinations/catalog/clicky/index.md index 58703be7fd..aab10cdf1f 100644 --- a/src/connections/destinations/catalog/clicky/index.md +++ b/src/connections/destinations/catalog/clicky/index.md @@ -24,7 +24,7 @@ This document was last updated on July 30th, 2018. If you notice any gaps, outda ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like this: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like this: ```javascript analytics.page("Home",{ @@ -37,7 +37,7 @@ When you call [`page`](/docs/connections/spec/page/), we call Clicky's `log` fun ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like this: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like this: ```javascript analytics.identify('ze8rt1u89', { @@ -57,7 +57,7 @@ When you make an Identify call with Segment, we will create a Clicky custom sess ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track("My Custom Event", { diff --git a/src/connections/destinations/catalog/cliff/index.md b/src/connections/destinations/catalog/cliff/index.md index 8c274eaa70..f410d3cdb8 100644 --- a/src/connections/destinations/catalog/cliff/index.md +++ b/src/connections/destinations/catalog/cliff/index.md @@ -23,7 +23,7 @@ This destination is maintained by Cliff.ai. For any issues with the destination, ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -33,7 +33,7 @@ Segment sends Track calls to Cliff as a `track` event. ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -43,7 +43,7 @@ Segment sends Page calls to Cliff as a `pageview`. ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```objc [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -53,7 +53,7 @@ Segment sends Screen calls to Cliff as a `screenview`. ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -65,7 +65,7 @@ Segment sends Identify calls to Cliff as an `identify` event. ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.group("0e8c78ea9d97a7b8185e8632", { diff --git a/src/connections/destinations/catalog/comscore/index.md b/src/connections/destinations/catalog/comscore/index.md index 74017a5776..1a456f7fd2 100644 --- a/src/connections/destinations/catalog/comscore/index.md +++ b/src/connections/destinations/catalog/comscore/index.md @@ -77,7 +77,7 @@ Segment will map values to comScore's `cs_ucfr` label as outlined below: **Note**: The video tracking functionality is in beta for **mobile only**, and requires version 3.0.0 of the `Segment-comScore` SDK. If you have feedback on or questions about this beta feature, [contact us](https://segment.com/help/contact)! -To get started tracking video content through Segment, make sure you are using a media player that has an API which allows you to detect the player state. Refer to our [Video Spec](https://segment.com/docs/connections/spec/video/) and implement video tracking as outlined there. We will map the semantic events to comScore's relevant methods. +To get started tracking video content through Segment, make sure you are using a media player that has an API which allows you to detect the player state. Refer to our [Video Spec](/docs/connections/spec/video/) and implement video tracking as outlined there. We will map the semantic events to comScore's relevant methods. ### Playback Events diff --git a/src/connections/destinations/catalog/convertflow/index.md b/src/connections/destinations/catalog/convertflow/index.md index d614db0af0..be7aae7277 100644 --- a/src/connections/destinations/catalog/convertflow/index.md +++ b/src/connections/destinations/catalog/convertflow/index.md @@ -19,7 +19,7 @@ This destination is maintained by ConvertFlow. For any issues with the destinati ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/courier/index.md b/src/connections/destinations/catalog/courier/index.md index 0ca2b18440..c43bf653c1 100644 --- a/src/connections/destinations/catalog/courier/index.md +++ b/src/connections/destinations/catalog/courier/index.md @@ -21,7 +21,7 @@ This destination is maintained by Courier. For any issues with the destination, ## Identify -If you aren’t familiar with the Segment Spec, read through the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren’t familiar with the Segment Spec, read through the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -54,7 +54,7 @@ For more information on how Courier handles profiles, see the [Courier Profile d ## Track -If you aren't familiar with the Segment Spec, read through the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, read through the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/crazy-egg/index.md b/src/connections/destinations/catalog/crazy-egg/index.md index 4c0a5ef7f4..9ad60cfaf4 100644 --- a/src/connections/destinations/catalog/crazy-egg/index.md +++ b/src/connections/destinations/catalog/crazy-egg/index.md @@ -28,7 +28,7 @@ You can navigate to the [Crazy Egg Dashboard](https://app.crazyegg.com/v2/dashbo ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page(); ``` diff --git a/src/connections/destinations/catalog/criteo-app-web-events/index.md b/src/connections/destinations/catalog/criteo-app-web-events/index.md index 6f7f53d8ea..dd7e5858dc 100644 --- a/src/connections/destinations/catalog/criteo-app-web-events/index.md +++ b/src/connections/destinations/catalog/criteo-app-web-events/index.md @@ -15,7 +15,7 @@ Currently this destination supports events originating from Mobile or Web source To get started with Criteo Events and Segment, you'll need: 1. An existing account with [Criteo](http://www.criteo.com/). -2. A data source integrated with either one of our mobile SDK's ([iOS](/docs/connections/sources/catalog/libraries/mobile/ios/) or [Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/)) or Javascript library ([Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/)) +2. A data source integrated with either one of our mobile SDK's ([iOS](/docs/connections/sources/catalog/libraries/mobile/ios/) or [Android](/docs/connections/sources/catalog/libraries/mobile/android/)) or Javascript library ([Analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/)) Assuming both of these criteria are met, you can add Criteo Events as a destination for your desired source in your Segment account. @@ -29,7 +29,7 @@ Assuming both of these criteria are met, you can add Criteo Events as a destinat Criteo Events is built to help you track key purchase funnel events and details. To accomplish that, you'll want to [`track`](/docs/connections/spec/track/) your user's actions using the following spec'd events to ensure you're following Criteo's best practices. -We use the context fields that we capture with our SDKs automatically to populate Criteo Events' tag with the app's name, user's language, locale, userId, deviceType and deviceId so you just need to make sure that the event names and properties match up! Refer to our [common fields guide](https://segment.com/docs/connections/spec/common/#context-fields-automatically-collected) to identify which context fields we collect automatically for each of our client-side libraries (analytics.js, analytics-ios or analytics-android). +We use the context fields that we capture with our SDKs automatically to populate Criteo Events' tag with the app's name, user's language, locale, userId, deviceType and deviceId so you just need to make sure that the event names and properties match up! Refer to our [common fields guide](/docs/connections/spec/common/#context-fields-automatically-collected) to identify which context fields we collect automatically for each of our client-side libraries (analytics.js, analytics-ios or analytics-android). ### Product Viewed diff --git a/src/connections/destinations/catalog/criteo-offline-conversions/index.md b/src/connections/destinations/catalog/criteo-offline-conversions/index.md index 5506e33d31..c6f35e3969 100644 --- a/src/connections/destinations/catalog/criteo-offline-conversions/index.md +++ b/src/connections/destinations/catalog/criteo-offline-conversions/index.md @@ -22,10 +22,10 @@ This document was last updated on January 8, 2020. If you notice any gaps, out-d ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Order Completed') ``` -Track calls will be sent to the Criteo Offline Conversions as a `track` event. The Criteo Offline Conversions Destination is capable of ingesting Track events for offlines sales originating from any source that conforms to [Segment's V2 Ecommerce Events](https://segment.com/docs/connections/spec/ecommerce/v2/). Offline sales originating from a CRM or other source that map to the Order Completed event may be sent to Criteo using the Criteo Offline Conversions Destination. Each 'track' event for an Order Completed must include the products purchased in the offline transaction. A transaction ID, contained in the event.order.id attribute is also required. In addition, a shopper ID, usually a hashed email address, is needed to identify the individual making the purchse. Each product should contain a product ID, price and quantity. The absence of any of this information will trigger an error, casuing the offline sale to be rejected. Note that offline sales events sent to Criteo are not visible in Criteo's dashboard. These events are used to optimize your campaign and are not made available for analytics or reporting purposes. +Track calls will be sent to the Criteo Offline Conversions as a `track` event. The Criteo Offline Conversions Destination is capable of ingesting Track events for offlines sales originating from any source that conforms to [Segment's V2 Ecommerce Events](/docs/connections/spec/ecommerce/v2/). Offline sales originating from a CRM or other source that map to the Order Completed event may be sent to Criteo using the Criteo Offline Conversions Destination. Each 'track' event for an Order Completed must include the products purchased in the offline transaction. A transaction ID, contained in the event.order.id attribute is also required. In addition, a shopper ID, usually a hashed email address, is needed to identify the individual making the purchse. Each product should contain a product ID, price and quantity. The absence of any of this information will trigger an error, casuing the offline sale to be rejected. Note that offline sales events sent to Criteo are not visible in Criteo's dashboard. These events are used to optimize your campaign and are not made available for analytics or reporting purposes. diff --git a/src/connections/destinations/catalog/crowdpower/index.md b/src/connections/destinations/catalog/crowdpower/index.md index fce3d24b4c..8223cbd6f0 100644 --- a/src/connections/destinations/catalog/crowdpower/index.md +++ b/src/connections/destinations/catalog/crowdpower/index.md @@ -22,7 +22,7 @@ This destination is maintained by CrowdPower. For any issues with the destinatio ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -39,7 +39,7 @@ Identify calls in Segment create or update customers and their attributes in Cro ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Purchased Item', { diff --git a/src/connections/destinations/catalog/custify/index.md b/src/connections/destinations/catalog/custify/index.md index aaec590627..1f0f105abd 100644 --- a/src/connections/destinations/catalog/custify/index.md +++ b/src/connections/destinations/catalog/custify/index.md @@ -19,7 +19,7 @@ This destination is maintained by Custify. For any issues with the destination, ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -32,7 +32,7 @@ Identify calls will be sent to Custify as `customers`, with the `userId` being s ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') @@ -46,7 +46,7 @@ To view the events, go to their linked Customer and they are displayed in the ac ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ``` analytics.group("0e8c78ea9d97a7b8185e8632", { diff --git a/src/connections/destinations/catalog/customersuccessbox/index.md b/src/connections/destinations/catalog/customersuccessbox/index.md index 277b100016..8647a7bc14 100644 --- a/src/connections/destinations/catalog/customersuccessbox/index.md +++ b/src/connections/destinations/catalog/customersuccessbox/index.md @@ -28,7 +28,7 @@ Send **account_id** and **user_id** in **traits** of an identify call to set and To learn more about user traits that are supported (including custom traits), check **User traits** section from [here](https://support.customersuccessbox.com/article/77-customersuccessbox-destination-on-segment-com) -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userID123', { @@ -46,7 +46,7 @@ Send **account_id** and **user_id** in properties of a track call to attribute t You can also pass **product_id** and **module_id** in properties of a track call to define a module and product for the event. To learn more, check **Understanding Product Usage** section [here](https://support.customersuccessbox.com/article/70-getting-started-with-customersuccessbox) -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Order Received', { @@ -65,7 +65,7 @@ Send **account_id** in traits of a group call to set and update the traits of a To learn more about account traits that are supported (including custom traits), check **Account traits** section from [here](https://support.customersuccessbox.com/article/77-customersuccessbox-destination-on-segment-com) -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ``` analytics.group('accountId123', { @@ -80,7 +80,7 @@ Group calls will be sent to CustomerSuccessBox as an `account`event. Send **account_id** and **user_id** in properties of a page call to attribute the pageview to a unique user belonging to a unique Account. . -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page('orders', { diff --git a/src/connections/destinations/catalog/customfit-ai/index.md b/src/connections/destinations/catalog/customfit-ai/index.md index cb96d5a31d..6b40c71870 100644 --- a/src/connections/destinations/catalog/customfit-ai/index.md +++ b/src/connections/destinations/catalog/customfit-ai/index.md @@ -18,7 +18,7 @@ This destination is maintained by CustomFit.ai. For any issues with the destinat ## Identify -`Identify` lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them like their email, name, etc., Read more about the [Identify method](https://segment.com/docs/connections/spec/identify/) to understand what it does. An example call would look like: +`Identify` lets you tie a user to their actions and record traits about them. It includes a unique User ID and any optional traits you know about them like their email, name, etc., Read more about the [Identify method](/docs/connections/spec/identify/) to understand what it does. An example call would look like: ```js analytics.identify("user_id", { @@ -36,7 +36,7 @@ Identify calls will be sent to CustomFit.ai as an `identify` event. You can find ## Track -The `track` API call is used to record any actions your users perform, along with any properties that describe the action. Each action is known as an event. Read more about the [Track method](https://segment.com/docs/connections/spec/track/) to understand what it does. An example call would look like: +The `track` API call is used to record any actions your users perform, along with any properties that describe the action. Each action is known as an event. Read more about the [Track method](/docs/connections/spec/track/) to understand what it does. An example call would look like: ```js analytics.track("Registered", { @@ -57,7 +57,7 @@ Track calls will be sent to CustomFit.ai as an `track` event. You can find the u ## Page -The `page` call lets you record whenever a user sees a page of your website, along with any optional properties about the page. Read more about the [Page method](https://segment.com/docs/connections/spec/page/) to understand what it does. An example call would look like: +The `page` call lets you record whenever a user sees a page of your website, along with any optional properties about the page. Read more about the [Page method](/docs/connections/spec/page/) to understand what it does. An example call would look like: ```js analytics.page("Home", { @@ -72,7 +72,7 @@ Page calls will be sent to CustomFit.ai as a `pageview` event. ## Screen -The `screen` call lets you record whenever a user sees a screen, the mobile equivalent of page, in your mobile app, along with any properties about the screen. Read more about the [Screen method](https://segment.com/docs/connections/spec/screen/) to understand what it does. An example call would look like: +The `screen` call lets you record whenever a user sees a screen, the mobile equivalent of page, in your mobile app, along with any properties about the screen. Read more about the [Screen method](/docs/connections/spec/screen/) to understand what it does. An example call would look like: ```objc [[SEGAnalytics sharedAnalytics] screen:@"Home" diff --git a/src/connections/destinations/catalog/cxense/index.md b/src/connections/destinations/catalog/cxense/index.md index 0ae9777510..6b0aecc785 100644 --- a/src/connections/destinations/catalog/cxense/index.md +++ b/src/connections/destinations/catalog/cxense/index.md @@ -21,7 +21,7 @@ Assuming these criteria are met, you can add Cxense as a destination for your de ## Page -Tracking pageviews is a key component of Cxense's offering. We integrate with this capability using our `.page()` method. When you trigger a `.page()` event the integration will invoke Cxense's corresponding `sendPageView` functionality. We will also pass along any [custom properties](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#page) you define. Here is an example: +Tracking pageviews is a key component of Cxense's offering. We integrate with this capability using our `.page()` method. When you trigger a `.page()` event the integration will invoke Cxense's corresponding `sendPageView` functionality. We will also pass along any [custom properties](/docs/connections/sources/catalog/libraries/website/javascript/#page) you define. Here is an example: ```js analytics.page('My Page Name', { author: 'Chris Nixon' }); diff --git a/src/connections/destinations/catalog/databrain/index.md b/src/connections/destinations/catalog/databrain/index.md index 432e52b13d..3952611085 100644 --- a/src/connections/destinations/catalog/databrain/index.md +++ b/src/connections/destinations/catalog/databrain/index.md @@ -20,11 +20,11 @@ This destination is maintained by DataBrain. For any issues with the destination > info "" > You should see data in DataBrain within 48 hours. DataBrain notifies you by email when your model is generated. -*Optional:* You can use Segment [Replays](https://segment.com/docs/guides/what-is-replay/) to sync your past events which were sent through Segment into your DataBrain instance. +*Optional:* You can use Segment [Replays](/docs/guides/what-is-replay/) to sync your past events which were sent through Segment into your DataBrain instance. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() @@ -34,7 +34,7 @@ Segment sends Page calls to DataBrain as a `pageview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -46,7 +46,7 @@ Segment sends Identify calls to DataBrain as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -56,7 +56,7 @@ Segment sends Track calls to DataBrain as a `track` event. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. Below are two example calls: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. Below are two example calls: ```objc [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -75,7 +75,7 @@ Segment sends Screen calls to DataBrain as a `screenview`. ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```js { diff --git a/src/connections/destinations/catalog/delighted/index.md b/src/connections/destinations/catalog/delighted/index.md index 4a058aca7b..0927d01bd4 100644 --- a/src/connections/destinations/catalog/delighted/index.md +++ b/src/connections/destinations/catalog/delighted/index.md @@ -22,7 +22,7 @@ _**NOTE:** The Delighted Destination is currently only compatible with email sur ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -36,7 +36,7 @@ Identify calls will add to your list of People in Delighted. The only trait that ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Purchased Product'); @@ -54,6 +54,6 @@ This also enables you to define the "Sample Rate" and an optional "Delay" for th You can optionally configure Delighted to send feedback from Delighted _email surveys_ to Segment. This can be useful for data warehousing, forwarding to other services (such as email marketing automation tools), or performing further analysis with the BI tools you have connected to Segment. -Simply copy the `Write Key` of the Segment Source where you want to send data and paste into the [Delighted Segment Destination page](https://delighted.com/destinations/segment). +Copy the `Write Key` of the Segment Source where you want to send data and paste into the Delighted Segment Destination page. Delighted will then send all _email survey_ feedback triggered using the Segment integration into back into Segment. Refer to our [Delighted Source](/docs/connections/sources/catalog/cloud-apps/delighted/) documentation for more information. diff --git a/src/connections/destinations/catalog/digioh/index.md b/src/connections/destinations/catalog/digioh/index.md index 22a061a662..276e81da67 100644 --- a/src/connections/destinations/catalog/digioh/index.md +++ b/src/connections/destinations/catalog/digioh/index.md @@ -16,7 +16,7 @@ This destination is maintained by Digioh. For any issues with the destination, [ ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -31,7 +31,7 @@ Segment sends Identify calls to Digioh as an `identify` event. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/dreamdata-io/index.md b/src/connections/destinations/catalog/dreamdata-io/index.md index 5154885a1d..b888ac7103 100644 --- a/src/connections/destinations/catalog/dreamdata-io/index.md +++ b/src/connections/destinations/catalog/dreamdata-io/index.md @@ -20,7 +20,7 @@ This destination is maintained by Dreamdata IO. For any issues with the destinat ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -31,7 +31,7 @@ Page calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segme ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -42,7 +42,7 @@ Screen calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=seg ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -55,7 +55,7 @@ Identify calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=s ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') @@ -66,7 +66,7 @@ Track calls will be sent to [Dreamdata IO](https://dreamdata.io/?utm_source=segm ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ``` analytics.group("userId123", { diff --git a/src/connections/destinations/catalog/drift/index.md b/src/connections/destinations/catalog/drift/index.md index c4c7f6d676..bb9f4c0303 100644 --- a/src/connections/destinations/catalog/drift/index.md +++ b/src/connections/destinations/catalog/drift/index.md @@ -24,7 +24,7 @@ The cloud-mode destination is maintained by Drift. For any issues with the desti ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page(); @@ -34,7 +34,7 @@ When you send a `page` or `screen` event, we will send that event to Drift as a ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('ksc2303', { @@ -72,7 +72,7 @@ analytics.identify('ksc2303', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track('Product Purchased', { @@ -86,7 +86,7 @@ When you `track` an event, we will send that event to Drift as a custom event. ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```javascript analytics.group('companyId123', { diff --git a/src/connections/destinations/catalog/elevio/index.md b/src/connections/destinations/catalog/elevio/index.md index dd0bc4cbe4..bc2eef6406 100644 --- a/src/connections/destinations/catalog/elevio/index.md +++ b/src/connections/destinations/catalog/elevio/index.md @@ -22,7 +22,7 @@ Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.j ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify({ diff --git a/src/connections/destinations/catalog/eloqua/index.md b/src/connections/destinations/catalog/eloqua/index.md index f35af96773..234369d62b 100644 --- a/src/connections/destinations/catalog/eloqua/index.md +++ b/src/connections/destinations/catalog/eloqua/index.md @@ -32,7 +32,7 @@ Segment `identify` trait on the left to the Eloqua field on the right: | title | Title | Follow the Segment spec to ensure proper mapping of these fields from Segment -`identify` traits: https://segment.com/docs/connections/spec/identify/#traits. +`identify` traits: /docs/connections/spec/identify/#traits. In addition, Segment supports mapping custom `identify` traits to Eloqua custom object fields. To do so, you can set up mappings in the settings for your @@ -64,7 +64,7 @@ the Segment `group` event needs to include the Account's name and groupId. If you set up a custom Account field called Company in Eloqua, Segment will automatically map the name of the Account to that field. -Follow [Segment's group spec](https://segment.com/docs/connections/spec/group/#traits) to ensure proper mapping of these fields from Segment +Follow [Segment's group spec](/docs/connections/spec/group/#traits) to ensure proper mapping of these fields from Segment `group` traits. In addition, Segment supports mapping custom `group` traits to Eloqua custom diff --git a/src/connections/destinations/catalog/emma/index.md b/src/connections/destinations/catalog/emma/index.md index 285c40603f..463cd5f0b7 100644 --- a/src/connections/destinations/catalog/emma/index.md +++ b/src/connections/destinations/catalog/emma/index.md @@ -20,7 +20,7 @@ This destination is maintained by EMMA. For any issues with the destination, [co ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/enjoyhq/index.md b/src/connections/destinations/catalog/enjoyhq/index.md index 5204bfe67f..f684fef02b 100644 --- a/src/connections/destinations/catalog/enjoyhq/index.md +++ b/src/connections/destinations/catalog/enjoyhq/index.md @@ -26,7 +26,7 @@ This destination is maintained by EnjoyHQ. For any issues with the destination, ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/epica/index.md b/src/connections/destinations/catalog/epica/index.md index d278ea6e9d..28f4fd27fa 100644 --- a/src/connections/destinations/catalog/epica/index.md +++ b/src/connections/destinations/catalog/epica/index.md @@ -21,7 +21,7 @@ This destination is maintained by EPICA. For any issues with the destination, [c ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -32,7 +32,7 @@ Page calls will be sent to EPICA as a `page`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -43,7 +43,7 @@ Screen calls will be sent to EPICA as a `screen`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -59,7 +59,7 @@ Identify calls will be sent to EPICA as an `identify` event. Traits are optional ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button', { diff --git a/src/connections/destinations/catalog/evergage/index.md b/src/connections/destinations/catalog/evergage/index.md index 87669be39e..69aa2ec6cd 100644 --- a/src/connections/destinations/catalog/evergage/index.md +++ b/src/connections/destinations/catalog/evergage/index.md @@ -11,7 +11,7 @@ This document was last updated on January 8, 2021. > The Evergage Destination was deprecated on January 8, 2021 and is no longer supported or maintained. It is no longer available in the Segment catalog, but remains available to existing users. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123', { @@ -23,7 +23,7 @@ analytics.identify('userId123', { A `userId` is required on all `identify` calls sent to {{ integration.name}}. When you call `identify` Segment will call both `setUser` and `setUserField` in the [Evergage library](https://doc.evergage.com/display/EKB/Send+Data+to+Evergage) to insert both the `userId` and corresponding user traits into {{ integration.name}}. ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```javascript analytics.group('companyId123', { diff --git a/src/connections/destinations/catalog/experiments-by-growthhackers/index.md b/src/connections/destinations/catalog/experiments-by-growthhackers/index.md index 2a11736fc9..b221138766 100644 --- a/src/connections/destinations/catalog/experiments-by-growthhackers/index.md +++ b/src/connections/destinations/catalog/experiments-by-growthhackers/index.md @@ -19,7 +19,7 @@ This destination is maintained by Experiments by Growthhackers. For any issues w ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/exponea/index.md b/src/connections/destinations/catalog/exponea/index.md index 0b961672eb..b98d4d796d 100644 --- a/src/connections/destinations/catalog/exponea/index.md +++ b/src/connections/destinations/catalog/exponea/index.md @@ -26,7 +26,7 @@ This destination is maintained by Exponea. For any issues with the destination, ## Common fields -If you have not had a chance to review our spec, take a look tounderstand what the [Common fields](https://segment.com/docs/connections/spec/common/) are. +If you have not had a chance to review our spec, take a look tounderstand what the [Common fields](/docs/connections/spec/common/) are. The `userId` and `anonymousId` common fields are used for all types of calls to identify the user in Exponea. Mapping of the IDs is based on the destination settings: @@ -48,7 +48,7 @@ Other common fields are used only for `track`, `page` and `screen` calls which a ## Page -If you have not had a chance to review our spec, take a look tounderstand what the [Page method](https://segment.com/docs/connections/spec/page/) does. +If you have not had a chance to review our spec, take a look tounderstand what the [Page method](/docs/connections/spec/page/) does. Page calls will be sent to Exponea as a `page_visit` event with the `properties` field mapped into event properties and the `name` field mapped into the `page_name` property. @@ -74,7 +74,7 @@ An optional event `session_ping` can be tracked along with `page_visit` for [aut ## Screen -If you have not had a chance to review our spec, take a look tounderstand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. +If you have not had a chance to review our spec, take a look tounderstand what the [Screen method](/docs/connections/spec/screen/) does. Screen calls will be sent to Exponea as a `screen_visit` event with the `properties` field mapped into event properties and the`name` field mapped into the `screen_name` property. @@ -96,7 +96,7 @@ An optional event `session_ping` can be tracked along with `screen_visit` for [a ## Track -If you have not had a chance to review our spec, take a look tounderstand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you have not had a chance to review our spec, take a look tounderstand what the [Track method](/docs/connections/spec/track/) does. Track calls will be sent to Exponea as events under name provided in the event field. The `properties` field will be mapped into event properties (objects will be flattened using underscore). @@ -118,7 +118,7 @@ This track call is translated into a `Registered` event with the following prope ## Identify -If you have not had a chance to review our spec, take a look tounderstand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you have not had a chance to review our spec, take a look tounderstand what the [Identify method](/docs/connections/spec/identify/) does. Identify calls will be sent to Exponea as customer updates with traits set as customer properties. @@ -146,7 +146,7 @@ This identify call is translated into a customer update for user with Exponea ha ## Alias -If you have not had a chance to review our spec, take a look tounderstand what the [Alias method](https://segment.com/docs/connections/spec/alias/) does. +If you have not had a chance to review our spec, take a look tounderstand what the [Alias method](/docs/connections/spec/alias/) does. The alias call can be used to merge two user identities and their data to one. The `previousId` field should always contain a previously used `anonymousId`, as merging users by specifying two `userIds` is not supported. Sending an alias event with `previousId` and no `userId` will cause the event to be ignored. Note that users are also merged when any call specifies both a userId and an anonymousId, which previously belonged to two separate users. @@ -157,7 +157,7 @@ analytics.alias("507f191e81"); ``` ## Group -If you have not had a chance to review our spec, take a look tounderstand what the [Group method](https://segment.com/docs/connections/spec/group/) does. +If you have not had a chance to review our spec, take a look tounderstand what the [Group method](/docs/connections/spec/group/) does. Group calls will be sent to Exponea as customer updates with group traits as customer properties prefixed with `group_` and `groupId` into `group_id`. For example: diff --git a/src/connections/destinations/catalog/extole-platform/index.md b/src/connections/destinations/catalog/extole-platform/index.md index 892853b780..9e7aebb1f5 100644 --- a/src/connections/destinations/catalog/extole-platform/index.md +++ b/src/connections/destinations/catalog/extole-platform/index.md @@ -27,7 +27,7 @@ This destination is maintained by Extole. For any issues with the destination, [ ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. Identify calls are sent to Extole as an `identify` event. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. Identify calls are sent to Extole as an `identify` event. Segment sends Identify calls to Extole as an `identify` event. Extole creates a new profile or updates an existing one. The table below lists how the basic traits are mapped: | Segment Traits | Extole Properties | @@ -55,7 +55,7 @@ analytics.identify('userId123', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/facebook-offline-conversions/index.md b/src/connections/destinations/catalog/facebook-offline-conversions/index.md index 709d34dc9c..6845a45a69 100644 --- a/src/connections/destinations/catalog/facebook-offline-conversions/index.md +++ b/src/connections/destinations/catalog/facebook-offline-conversions/index.md @@ -51,7 +51,7 @@ You can find Facebook Offline Event Set ID by going to your **Offline Events** p ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track({ @@ -78,7 +78,7 @@ There are 3 places you can map your Segment `track` events: ![](images/86f8c50165a726e8168d652c8052c2a0.png) -The following table shows how we map Segment's [semantic ecommerce](https://segment.com/docs/connections/spec/ecommerce/v2) or custom event names to Facebook's semantic conversion event names: +The following table shows how we map Segment's [semantic ecommerce](/docs/connections/spec/ecommerce/v2) or custom event names to Facebook's semantic conversion event names:
diff --git a/src/connections/destinations/catalog/factorsai/index.md b/src/connections/destinations/catalog/factorsai/index.md index 68c627844c..c84c997e03 100644 --- a/src/connections/destinations/catalog/factorsai/index.md +++ b/src/connections/destinations/catalog/factorsai/index.md @@ -18,7 +18,7 @@ This destination is maintained by FactorsAI. For any issues with the destination ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -29,7 +29,7 @@ Page calls will be sent to FactorsAI as an auto tracked `pageview`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -40,7 +40,7 @@ Screen calls will be sent to FactorsAI as a track event with name `screenname`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -53,7 +53,7 @@ Identify calls will be sent to FactorsAI as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Product Viewed') diff --git a/src/connections/destinations/catalog/firebase/index.md b/src/connections/destinations/catalog/firebase/index.md index 53ae8adc74..8d3de76dea 100644 --- a/src/connections/destinations/catalog/firebase/index.md +++ b/src/connections/destinations/catalog/firebase/index.md @@ -277,7 +277,7 @@ Firebase is now Google's recommended method for reporting conversions to Adwords ### Troubleshooting -Firebase has great logging. If you are having any issues, you can enable debug mode as outlined [here](https://support.google.com/firebase/answer/7201382/?hl=en&authuser=0). +Firebase has great logging. If you are having any issues, you can enable debug mode as outlined [here](https://firebase.google.com/docs/analytics/debugview). ### Changes from iOS v1 to v2 Beta @@ -294,6 +294,6 @@ Even more exciting is that this new iOS SDK will have parity with the new Segmen As a current user of Segment-Firebase iOS, you will be able to pull in the latest version by pinning `pod 'Segment-Firebase', '~>2.0`. While we don't suggest this, if you are not ready to upgrade you can pin the old beta version at `pod 'Segment-Firebase', '~>1.0.0``'` -For details on the new mapping, you can check out our documentation [here](https://segment.com/docs/connections/destinations/catalog/firebase/#event-mappings). +For details on the new mapping, you can check out our documentation [here](/docs/connections/destinations/catalog/firebase/#event-mappings). Let us know if you have any questions. We recommend upgrading as soon as possible, and [let us know](https://segment.com/help/contact/) if you have any feedback about both the Firebase iOS and Android betas. diff --git a/src/connections/destinations/catalog/flurry/index.md b/src/connections/destinations/catalog/flurry/index.md index 23f29e6550..915b53cd3b 100644 --- a/src/connections/destinations/catalog/flurry/index.md +++ b/src/connections/destinations/catalog/flurry/index.md @@ -27,7 +27,7 @@ _Note: Flurry does not always display data in real time. We've seen that it can ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example iOS call would look like: @@ -45,7 +45,7 @@ _Note: When you toggle the Screen Tracks As Events option on in your Flurry Segm ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example iOS call would look like: @@ -67,7 +67,7 @@ When you call [`identify`](/docs/connections/spec/identify/), we'll set the user ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example iOS call would look like: diff --git a/src/connections/destinations/catalog/foxmetrics/index.md b/src/connections/destinations/catalog/foxmetrics/index.md index a90abf9b98..1f3f904106 100644 --- a/src/connections/destinations/catalog/foxmetrics/index.md +++ b/src/connections/destinations/catalog/foxmetrics/index.md @@ -21,7 +21,7 @@ Remember to remove FoxMetrics's native snippet from your page. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page(); @@ -32,7 +32,7 @@ When you call [`page`](/docs/connections/spec/page/), we call FoxMetrics' `recor ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify("97980cfea0067", { @@ -47,7 +47,7 @@ When you call `identify` on `analytics.js`, we call FoxMetrics' `_fxm.visitor.Pr ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track("Registered", { diff --git a/src/connections/destinations/catalog/freshmarketer/index.md b/src/connections/destinations/catalog/freshmarketer/index.md index 15cc664d0a..879869b363 100644 --- a/src/connections/destinations/catalog/freshmarketer/index.md +++ b/src/connections/destinations/catalog/freshmarketer/index.md @@ -21,7 +21,7 @@ This destination is maintained by Freshmarketer. For any issues with the destina ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js // On server-side diff --git a/src/connections/destinations/catalog/fullstory/index.md b/src/connections/destinations/catalog/fullstory/index.md index c6b6c8eca3..b7f64aebfc 100644 --- a/src/connections/destinations/catalog/fullstory/index.md +++ b/src/connections/destinations/catalog/fullstory/index.md @@ -16,7 +16,7 @@ Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.j ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [identify method](https://segment.com/docs/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to [FullStory's](https://help.fullstory.com/develop-js/identify) `FS.identify` method. +If you're not familiar with the Segment Specs, take a look to understand what the [identify method](/docs/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to [FullStory's](https://help.fullstory.com/develop-js/identify) `FS.identify` method. An example call which does not include a `userId` will send FullStory the value of the `anonymousId` and would look like: @@ -52,7 +52,7 @@ analytics.identify("userId123", { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [track method](https://segment.com/docs/connections/spec/track/) does. Track calls sent to Segment will be automatically passed directly to FullStory using [FullStory's](https://help.fullstory.com/develop-js/363565-fs-event-api-sending-custom-event-data-into-fullstory) `FS.event` method, including all the properties passed in the event. +If you're not familiar with the Segment Specs, take a look to understand what the [track method](/docs/connections/spec/track/) does. Track calls sent to Segment will be automatically passed directly to FullStory using [FullStory's](https://help.fullstory.com/develop-js/363565-fs-event-api-sending-custom-event-data-into-fullstory) `FS.event` method, including all the properties passed in the event. An example call would look like: diff --git a/src/connections/destinations/catalog/funnelenvy/index.md b/src/connections/destinations/catalog/funnelenvy/index.md index 0e37154cce..33f6c73485 100644 --- a/src/connections/destinations/catalog/funnelenvy/index.md +++ b/src/connections/destinations/catalog/funnelenvy/index.md @@ -28,7 +28,7 @@ The FunnelEnvy snippet can be found in your settings within FunnelEnvy which is ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -42,7 +42,7 @@ FunnelEnvy will use the id sent in the identify call to associate individuals to ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/funnelfox/index.md b/src/connections/destinations/catalog/funnelfox/index.md index bcf645365e..4f9a458de8 100644 --- a/src/connections/destinations/catalog/funnelfox/index.md +++ b/src/connections/destinations/catalog/funnelfox/index.md @@ -20,7 +20,7 @@ This destination is maintained by FunnelFox. For any issues with the destination ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -31,7 +31,7 @@ Page calls will be sent to FunnelFox as a `Customer Action: pageview`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -42,7 +42,7 @@ Screen calls will be sent to FunnelFox as a `Customer Action`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -55,7 +55,7 @@ Identify calls will be sent to FunnelFox as an `New or Updated Customer` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/gainsight-px/index.md b/src/connections/destinations/catalog/gainsight-px/index.md index ccc12ac3f0..3dc9a1eb61 100644 --- a/src/connections/destinations/catalog/gainsight-px/index.md +++ b/src/connections/destinations/catalog/gainsight-px/index.md @@ -31,7 +31,7 @@ Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.j Don't miss out the [The Configuration Checklist - Segment.com](https://www.gainsight.com/product-experience/) in Gainsight PX! ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example identify call is shown below: @@ -51,7 +51,7 @@ Segment must be running on all pages of the web application or site that you wan Your Segment integration must include use of the identify call (identifies the user & group/account). ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example track call is shown below: @@ -65,7 +65,7 @@ analytics.track("Form submitted", { When you track an event, we will send the event name together with the properties included in the track call. In Gainsight PX you will be able to create new funnels based on the custom events and properties received from Segment. You can also add "custom events" in the features created in the "Product Mapper" view. ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example group call is shown below: diff --git a/src/connections/destinations/catalog/gainsight/index.md b/src/connections/destinations/catalog/gainsight/index.md index d7f8a231ea..fb53840d68 100644 --- a/src/connections/destinations/catalog/gainsight/index.md +++ b/src/connections/destinations/catalog/gainsight/index.md @@ -20,7 +20,7 @@ This document was last updated on October 18, 2018. If you notice any gaps, outd ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like this ([analytics.js](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/)): +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like this ([analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/)): ```js analytics.identify('123', { @@ -36,7 +36,7 @@ You can map `identify` calls to Salesforce by including the Salesforce Account I **Important**: You should only send the `track` events you need to Gainsight. You can whitelist the names of the events you need in your Segment UI settings for Gainsight. Once you pre-map your events, we will only send those events to Gainsight for you. However, if you do *not* map any events, we will by default send all your track events to Gainsight. -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like this ([analytics.js](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/)): +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like this ([analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/)): ```js analytics.track('Account Created', { @@ -52,7 +52,7 @@ If they haven't been identified, pass the Salesforce Account ID as a property li ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like this ([analytics.js](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/)): +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like this ([analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/)): ```js analytics.group('555', { diff --git a/src/connections/destinations/catalog/gameball/index.md b/src/connections/destinations/catalog/gameball/index.md index 0eaae4787b..86a0356261 100644 --- a/src/connections/destinations/catalog/gameball/index.md +++ b/src/connections/destinations/catalog/gameball/index.md @@ -27,7 +27,7 @@ Segment's `track` and `identify` events can only update the following properties ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [`identify` method does](https://segment.com/docs/connections/spec/identify/). An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [`identify` method does](/docs/connections/spec/identify/). An example call would look like: ```js analytics.identify('userId123', { @@ -44,7 +44,7 @@ Segment `identify` events create or update user/player object records in Gamebal ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [track method does](https://segment.com/docs/connections/spec/track/). An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [track method does](/docs/connections/spec/track/). An example call would look like: ```js analytics.track('View Product') diff --git a/src/connections/destinations/catalog/gist/index.md b/src/connections/destinations/catalog/gist/index.md index 920ac44753..d544b79f2b 100644 --- a/src/connections/destinations/catalog/gist/index.md +++ b/src/connections/destinations/catalog/gist/index.md @@ -16,7 +16,7 @@ This destination is maintained by Gist. For any issues with the destination, [co 5. Enter the "API Key" in the Gist destination settings in Segment. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -33,7 +33,7 @@ Only `identify` events can *update* existing Contacts. See [Gist’s Contact Properties](https://docs.getgist.com/article/241-contact-properties-glossary) for more details. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/goedle-io/index.md b/src/connections/destinations/catalog/goedle-io/index.md index 22f8f4125b..6140477b6f 100644 --- a/src/connections/destinations/catalog/goedle-io/index.md +++ b/src/connections/destinations/catalog/goedle-io/index.md @@ -20,28 +20,28 @@ This destination is maintained by Goedle. For any issues with the destination, [ ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page(); ``` -goedle.io will track a pageview and log the `path` [property](https://segment.com/docs/connections/spec/page/#properties "Spec: Page - Properties") to distinguish different user behaviors. +goedle.io will track a pageview and log the `path` [property](/docs/connections/spec/page/#properties "Spec: Page - Properties") to distinguish different user behaviors. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.screen(); ``` -goedle.io will track a screenview on your mobile app and log the `name` [property](https://segment.com/docs/connections/spec/page/#properties "Spec: Page - Properties") to distinguish different user behaviors. +goedle.io will track a screenview on your mobile app and log the `name` [property](/docs/connections/spec/page/#properties "Spec: Page - Properties") to distinguish different user behaviors. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('ze8rt1u89', { @@ -55,7 +55,7 @@ goedle.io will set the `userId`, as well as specific user traits that are provid ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Reached Level', { @@ -71,7 +71,7 @@ goedle.io will log the corresponding event using the `event` along with any addi ### Ecommerce -goedle.io supports some Ecommerce events as part of the Segment [V1](https://segment.com/docs/connections/spec/ecommerce/ "Spec: V1 Ecommerce") and [V2](https://segment.com/docs/connections/spec/ecommerce/v2/ "Spec: V2 Ecommerce") Ecommerce specs and they will be automatically merged if required. An example Ecommerce call would look like: +goedle.io supports some Ecommerce events as part of the Segment [V1](/docs/connections/spec/ecommerce/ "Spec: V1 Ecommerce") and [V2](/docs/connections/spec/ecommerce/v2/ "Spec: V2 Ecommerce") Ecommerce specs and they will be automatically merged if required. An example Ecommerce call would look like: ``` analytics.track('Product List Viewed', { properties: { @@ -84,11 +84,11 @@ analytics.track('Product List Viewed', { The supported events are as follows: -* [Product List Viewed](https://segment.com/docs/connections/spec/ecommerce/v2/#product-list-viewed "Spec: V2 Ecommerce - Product List Viewed") -* [Product Added](https://segment.com/docs/connections/spec/ecommerce/v2/#product-added "Spec: V2 Ecommerce - Product Added") -* [Product Removed](https://segment.com/docs/connections/spec/ecommerce/v2/#product-removed "Spec: V2 Ecommerce - Product Removed") -* [Product Viewed](https://segment.com/docs/connections/spec/ecommerce/v2/#product-viewed "Spec: V2 Ecommerce - Product Viewed") -* [Order Completed](https://segment.com/docs/connections/spec/ecommerce/v2/#order-completed "Spec: V2 Ecommerce - Order Completed") +* [Product List Viewed](/docs/connections/spec/ecommerce/v2/#product-list-viewed "Spec: V2 Ecommerce - Product List Viewed") +* [Product Added](/docs/connections/spec/ecommerce/v2/#product-added "Spec: V2 Ecommerce - Product Added") +* [Product Removed](/docs/connections/spec/ecommerce/v2/#product-removed "Spec: V2 Ecommerce - Product Removed") +* [Product Viewed](/docs/connections/spec/ecommerce/v2/#product-viewed "Spec: V2 Ecommerce - Product Viewed") +* [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed "Spec: V2 Ecommerce - Order Completed") The following properties are supported as part of the above events: * `product_id` @@ -97,9 +97,9 @@ The following properties are supported as part of the above events: * `currency` ### A/B Testing -goedle.io supports the Segment [A/B Testing](https://segment.com/docs/connections/spec/ab-testing/ "Spec: A/B Testing") specs and builds an internal hierarchy used to enhance the prediction of the user behavior during an experiment. +goedle.io supports the Segment [A/B Testing](/docs/connections/spec/ab-testing/ "Spec: A/B Testing") specs and builds an internal hierarchy used to enhance the prediction of the user behavior during an experiment. -These experiments can be sent as follows with a required `experiment_id` and an optional `variation_id`. If `experiment_id` is not included, [Experiment Viewed](https://segment.com/docs/connections/spec/ab-testing/#experiment-viewed "Spec: A/B Testing - Experiment Viewed") will be treated as a regular event. +These experiments can be sent as follows with a required `experiment_id` and an optional `variation_id`. If `experiment_id` is not included, [Experiment Viewed](/docs/connections/spec/ab-testing/#experiment-viewed "Spec: A/B Testing - Experiment Viewed") will be treated as a regular event. ``` analytics.track('Experiment Viewed', { @@ -111,4 +111,4 @@ analytics.track('Experiment Viewed', { ## Group -When you trigger a [group](https://segment.com/docs/connections/spec/group/ "Spec: Group") event, we will log the [group_id](https://segment.com/docs/connections/spec/group/#group-id "Spec: Group - Group ID") for an individual user. +When you trigger a [group](/docs/connections/spec/group/ "Spec: Group") event, we will log the [group_id](/docs/connections/spec/group/#group-id "Spec: Group - Group ID") for an individual user. diff --git a/src/connections/destinations/catalog/google-ads-gtag/index.md b/src/connections/destinations/catalog/google-ads-gtag/index.md index 3b938a3f5b..e65d555ba2 100644 --- a/src/connections/destinations/catalog/google-ads-gtag/index.md +++ b/src/connections/destinations/catalog/google-ads-gtag/index.md @@ -11,7 +11,7 @@ name-override: true If you're using the [new Google Ads (Gtag) experience](https://support.google.com/adwords/answer/6095821?hl=en&ref_topic=3165803), you can enable the **Google Ads (Gtag)** Destination (previously called "Google Adwords New") in the Segment catalog. The new Google Ads uses a Global Site Tag (Gtag) and event snippets. > info "Info message." -> **IMPORTANT**: Only use this destination if your Google Ads account is using the _New_ (Gtag) Experience. If you're using Google Tag Manager (a separate product) as well, don't add the global site tag again in your GTM containers. You should also disable any [Google Ads (Classic)](https://segment.com/docs/connections/destinations/catalog/adwords/) destinations within the same source, since **Google Ads (Classic)** can't load at the same times as **Google Ads (Gtag)**. +> **IMPORTANT**: Only use this destination if your Google Ads account is using the _New_ (Gtag) Experience. If you're using Google Tag Manager (a separate product) as well, don't add the global site tag again in your GTM containers. You should also disable any [Google Ads (Classic)](/docs/connections/destinations/catalog/adwords/) destinations within the same source, since **Google Ads (Classic)** can't load at the same times as **Google Ads (Gtag)**. ## Getting Started @@ -38,7 +38,7 @@ analytics.page({}, { ``` > note "" -> **NOTE:** The `'Google Ads (Gtag)'` is case sensitive. Segment prefers you to use `order_id` rather than `transaction_id` to stay more consistent with the [ecommerce spec](https://segment.com/docs/connections/spec/ecommerce/v2). However, Segment will send it as `transaction_id` in the request itself to satisfy Google's specifications. +> **NOTE:** The `'Google Ads (Gtag)'` is case sensitive. Segment prefers you to use `order_id` rather than `transaction_id` to stay more consistent with the [ecommerce spec](/docs/connections/spec/ecommerce/v2). However, Segment will send it as `transaction_id` in the request itself to satisfy Google's specifications. ## Track diff --git a/src/connections/destinations/catalog/google-analytics/migrating.md b/src/connections/destinations/catalog/google-analytics/migrating.md index 160670f827..5ae6dd869c 100644 --- a/src/connections/destinations/catalog/google-analytics/migrating.md +++ b/src/connections/destinations/catalog/google-analytics/migrating.md @@ -25,10 +25,10 @@ If you received this deprecation notice, your property has already been flagged For more detailed information for each of the classes and methods in the Firebase SDK by platform visit the [Firebase Analytics SDK documentation](https://firebase.google.com/docs/reference). #### Installing the iOS SDK -For information on how to add the Segment-Firebase SDK and register the dependency with the Segment SDK visit [Segment's Firebase for iOS](https://segment.com/docs/connections/destinations/catalog/firebase/#ios) documentation. +For information on how to add the Segment-Firebase SDK and register the dependency with the Segment SDK visit [Segment's Firebase for iOS](/docs/connections/destinations/catalog/firebase/#ios) documentation. #### Installing the Android SDK -For information on how to add the Segment-Firebase SDK and apply the Google Services plugin visit [Segment's Firebase for Android](https://segment.com/docs/connections/destinations/catalog/firebase/#android) documentation. +For information on how to add the Segment-Firebase SDK and apply the Google Services plugin visit [Segment's Firebase for Android](/docs/connections/destinations/catalog/firebase/#android) documentation. ## Comparing Google Analytics and Firebase Functionality diff --git a/src/connections/destinations/catalog/google-tag-manager/index.md b/src/connections/destinations/catalog/google-tag-manager/index.md index 45990c697f..49eb2965ef 100644 --- a/src/connections/destinations/catalog/google-tag-manager/index.md +++ b/src/connections/destinations/catalog/google-tag-manager/index.md @@ -24,7 +24,7 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page('Home', { @@ -47,7 +47,7 @@ If you include a `category` parameter in your `page` calls and turn on the setti ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Article Completed', { diff --git a/src/connections/destinations/catalog/hawkei/index.md b/src/connections/destinations/catalog/hawkei/index.md index 41745ba1a5..b47c8bc5a5 100644 --- a/src/connections/destinations/catalog/hawkei/index.md +++ b/src/connections/destinations/catalog/hawkei/index.md @@ -25,7 +25,7 @@ This destination is maintained by Hawkei. For any issues with the destination, [ ## Page -If you aren't familiar with the Segment Spec, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() @@ -36,7 +36,7 @@ When you call `page`, we store it as a `page` event inside Hawkei. You can use t ## Identify -If you aren't familiar with the Segment Spec, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -48,7 +48,7 @@ Identify calls will be sent to hawkei as an `identify` event. The associated use ## Group -If you aren't familiar with the Segment Spec, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```js analytics.group('groupId123', { @@ -61,7 +61,7 @@ Group calls will be sent to hawkei as an `group` event. The associated group dat ## Track -If you aren't familiar with the Segment Spec, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/headsup-ai/index.md b/src/connections/destinations/catalog/headsup-ai/index.md index a4ab9f53fa..c7418a6c51 100644 --- a/src/connections/destinations/catalog/headsup-ai/index.md +++ b/src/connections/destinations/catalog/headsup-ai/index.md @@ -19,7 +19,7 @@ This destination is maintained by HeadsUp. For any issues with the destination, ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -30,7 +30,7 @@ Segment sends Identify calls to HeadsUp as an `identify` event. The `email` fiel ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -39,7 +39,7 @@ Segment sends Track calls to HeadsUp as a `track` event. Use Track events to per ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -47,7 +47,7 @@ analytics.page() Segment sends Page calls to HeadsUp as a `pageview`. ## Group -If you aren’t familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren’t familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.group("0e8c78ea9d97a7b8185e8632", { diff --git a/src/connections/destinations/catalog/heap/index.md b/src/connections/destinations/catalog/heap/index.md index e6c3acae12..27cf3fb4cc 100644 --- a/src/connections/destinations/catalog/heap/index.md +++ b/src/connections/destinations/catalog/heap/index.md @@ -18,7 +18,7 @@ This document was last updated on January 29, 2018. If you notice any gaps, out- ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123'); @@ -30,7 +30,7 @@ If one of your `traits` is of the date property type, we will convert it into an ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track('Clicked Button'); diff --git a/src/connections/destinations/catalog/help-scout/index.md b/src/connections/destinations/catalog/help-scout/index.md index 6f4a124861..d392f17e27 100644 --- a/src/connections/destinations/catalog/help-scout/index.md +++ b/src/connections/destinations/catalog/help-scout/index.md @@ -18,7 +18,7 @@ hide-boilerplate: true ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like this: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like this: analytics.identify({ userId: '019mr8mf4r', @@ -30,4 +30,4 @@ If you're not familiar with the Segment Specs, take a look to understand what th You can use the Identify call to create or update customers in your Help Scout account. -A `name` and an `email` are required by Help Scout to complete the request. You can set the userId as the `email`, although this is [not recommended](https://segment.com/docs/connections/spec/identify/#user-id). You can also specify `firstName` and `lastName` traits instead of a single `name` trait. You can learn more about which properties Help Scout will accept [here](https://developer.helpscout.com/mailbox-api/endpoints/customers/create/). +A `name` and an `email` are required by Help Scout to complete the request. You can set the userId as the `email`, although this is [not recommended](/docs/connections/spec/identify/#user-id). You can also specify `firstName` and `lastName` traits instead of a single `name` trait. You can learn more about which properties Help Scout will accept [here](https://developer.helpscout.com/mailbox-api/endpoints/customers/create/). diff --git a/src/connections/destinations/catalog/hotjar/index.md b/src/connections/destinations/catalog/hotjar/index.md index 1e2aeebb04..4d9f67a2d4 100644 --- a/src/connections/destinations/catalog/hotjar/index.md +++ b/src/connections/destinations/catalog/hotjar/index.md @@ -31,7 +31,7 @@ Hotjar automatically starts tracking visitors based on the tools you have enable ## Identify -The Hotjar destination will automatically ingest a User ID, as well as values sent over your Identify spec as [traits](https://segment.com/docs/connections/spec/identify/#traits), as long as [User Attributes are enabled in Hotjar](https://help.hotjar.com/hc/en-us/articles/360038394053-How-to-Setup-User-Attributes-in-4-Steps#step-2-review-your-privacy-requirements-and-enable-user-attributes). +The Hotjar destination will automatically ingest a User ID, as well as values sent over your Identify spec as [traits](/docs/connections/spec/identify/#traits), as long as [User Attributes are enabled in Hotjar](https://help.hotjar.com/hc/en-us/articles/360038394053-How-to-Setup-User-Attributes-in-4-Steps#step-2-review-your-privacy-requirements-and-enable-user-attributes). ### Nested values or lists diff --git a/src/connections/destinations/catalog/hydra/index.md b/src/connections/destinations/catalog/hydra/index.md index 8cfe02c2ae..a97ac8ee9b 100644 --- a/src/connections/destinations/catalog/hydra/index.md +++ b/src/connections/destinations/catalog/hydra/index.md @@ -22,7 +22,7 @@ If you would like to use `track` event data, create a `Segment Product Usage Sca ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -44,7 +44,7 @@ Identify calls will be sent to Hydra as an `identify` event. Upon receiving an I ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Device deploy started', diff --git a/src/connections/destinations/catalog/ibm-ubx/index.md b/src/connections/destinations/catalog/ibm-ubx/index.md index 0a9d7bb009..8c4f7cf951 100644 --- a/src/connections/destinations/catalog/ibm-ubx/index.md +++ b/src/connections/destinations/catalog/ibm-ubx/index.md @@ -476,7 +476,7 @@ options: Segment does not auto-generate events other than an initial `page` call when using our Analytics.js library and mobile lifecycle events when mobile lifecycle tracking is enabled using Segment's Android or iOS library. -This means some events supported and in some cases expected by downstream UBX destinations - including *abandonment events* - must be derived by the customer. One approach would be to integrate with a marketing tool such as [Braze](https://segment.com/docs/connections/destinations/catalog/braze/) or [Bronto](https://segment.com/docs/connections/destinations/catalog/bronto/), in which you can [set up rules that generate abandonment events](https://segment.com/docs/guides/destinations/how-do-i-automate-multi-channel-re-engagement-campaigns/#1st-line-of-defense-the-push-notification), which are then be sent back through Segment and downstream to UBX. +This means some events supported and in some cases expected by downstream UBX destinations - including *abandonment events* - must be derived by the customer. One approach would be to integrate with a marketing tool such as [Braze](/docs/connections/destinations/catalog/braze/) or [Bronto](/docs/connections/destinations/catalog/bronto/), in which you can [set up rules that generate abandonment events](/docs/guides/destinations/how-do-i-automate-multi-channel-re-engagement-campaigns/#1st-line-of-defense-the-push-notification), which are then be sent back through Segment and downstream to UBX. Another approach may be to schedule a cron job in your database that checks for users who have triggered a `Product Added` event, but who never went on to trigger an `Order Completed` event. In this case, one can logically deduce that the user abandoned his cart, hence you should trigger a server-side Segment event based on this rule, which Segment will process and pass downstream to UBX. diff --git a/src/connections/destinations/catalog/impact-partnership-cloud/index.md b/src/connections/destinations/catalog/impact-partnership-cloud/index.md index c5d33d550e..6906cef46b 100644 --- a/src/connections/destinations/catalog/impact-partnership-cloud/index.md +++ b/src/connections/destinations/catalog/impact-partnership-cloud/index.md @@ -19,7 +19,7 @@ This destination is maintained by Impact. For any issues with the destination, c ## Page -If you aren’t familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren’t familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page("Home") @@ -34,7 +34,7 @@ Read [Impact Partnership Cloud's documentation](https://impact-helpdesk.freshdes ## Screen -If you aren’t familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren’t familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```objc [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -44,7 +44,7 @@ Segment sends Screen calls to Impact Partnership Cloud as a `Clicks` event if th ## Identify -If you aren’t familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn more about what it does. An example call would look like: +If you aren’t familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn more about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -55,7 +55,7 @@ Segment sends Identify calls to Impact Partnership Cloud as a `Page Load` event ## Track -If you aren’t familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn more about what it does. An example call would look like: +If you aren’t familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn more about what it does. An example call would look like: ```js analytics.track('Order Completed', { diff --git a/src/connections/destinations/catalog/impact/index.md b/src/connections/destinations/catalog/impact/index.md index 2e7a9eddf6..61daffdcfb 100644 --- a/src/connections/destinations/catalog/impact/index.md +++ b/src/connections/destinations/catalog/impact/index.md @@ -36,7 +36,7 @@ To track events from web / server locations, you will need to choose the Action #### Click Id -Impact passes a query parameter named `CLICKID` as a part of their tracking urls. The value associated with this parameter is used to perform attribution analysis on their end. By default, if you are using our [Javascript source](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/), we will automatically look for this parameter and if it exists, pass it as a contextual property of any events that happen **on the same pageview**. However, we do not cache this id anywhere so any subsequent events the user takes outside of that initial pageview will not have the ClickId as part of the event. +Impact passes a query parameter named `CLICKID` as a part of their tracking urls. The value associated with this parameter is used to perform attribution analysis on their end. By default, if you are using our [Javascript source](/docs/connections/sources/catalog/libraries/website/javascript/), we will automatically look for this parameter and if it exists, pass it as a contextual property of any events that happen **on the same pageview**. However, we do not cache this id anywhere so any subsequent events the user takes outside of that initial pageview will not have the ClickId as part of the event. Impact recommends you cache this value in the users browser (using a cookie or local storage) if you want to attribute any subsequent user interactions to the initial ad source. We ask that you continue doing this if you are using this integration to track web conversions and pass the cached id as part of the `context.referrer` object. It should look like this: @@ -58,9 +58,9 @@ To track events from mobile, you will need to map your mobile event codes in Imp ### Property Mappings -Once you have established Action Tracker / Mobile Event code mappings, we will perform the following data translations laid out in the tables below. Review these carefully as you may need to add some properties to your Segment events to conform to Impact's API requirements. You can learn more about our spec'd event properties [here](https://segment.com/docs/connections/spec/common/). +Once you have established Action Tracker / Mobile Event code mappings, we will perform the following data translations laid out in the tables below. Review these carefully as you may need to add some properties to your Segment events to conform to Impact's API requirements. You can learn more about our spec'd event properties [here](/docs/connections/spec/common/). -**Note:** Some of the properties listed below are documented as properties of our [Order Completed](https://segment.com/docs/connections/spec/ecommerce/v2/#order-completed) event specification. You do not need to use our Order Completed event to use this integration but you may need to add some of the properties that are traditionally included in that event "type" to the events that you would like to integrate with Impact. +**Note:** Some of the properties listed below are documented as properties of our [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) event specification. You do not need to use our Order Completed event to use this integration but you may need to add some of the properties that are traditionally included in that event "type" to the events that you would like to integrate with Impact. #### Mobile Sources @@ -268,7 +268,7 @@ These mappings will occur for events originating from any data source (Web, Mobi ## Deep Link Opened -We integrate with Impact mobile attribution capabilities using our [Deep Link Opened](https://segment.com/docs/connections/spec/mobile/#deep-link-opened) event. When a Deep Link Opened event is fired we will first check to see if the referrer url (sent as the `url` property of the `properties` object) matches your Impact tracking domain. If so, we will look for the following contextual properties and pass them as metadata to Impact. +We integrate with Impact mobile attribution capabilities using our [Deep Link Opened](/docs/connections/spec/mobile/#deep-link-opened) event. When a Deep Link Opened event is fired we will first check to see if the referrer url (sent as the `url` property of the `properties` object) matches your Impact tracking domain. If so, we will look for the following contextual properties and pass them as metadata to Impact.
diff --git a/src/connections/destinations/catalog/indicative/index.md b/src/connections/destinations/catalog/indicative/index.md index a1c7ee7730..6de6743329 100644 --- a/src/connections/destinations/catalog/indicative/index.md +++ b/src/connections/destinations/catalog/indicative/index.md @@ -29,7 +29,7 @@ For additional information, contact `support@indicative.com`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. When you call [`identify`](/docs/connections/spec/identify/), we send the entire call as is to Indicative's server. @@ -50,7 +50,7 @@ analytics.identify('ze8rt1u89', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. When you call [`track`](/docs/connections/spec/track/), we send the entire call as is to Indicative's server. @@ -64,7 +64,7 @@ analytics.track("Calculation Completed", { ## Page and Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) and [Screen method](https://segment.com/docs/connections/spec/page/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) and [Screen method](/docs/connections/spec/page/) does. Both [`page`](/docs/connections/spec/page/) and [`screen`](/docs/connections/spec/screen/) calls will be sent to Indicative as events. @@ -89,4 +89,4 @@ analytics.screen({ ### Property values have maximum length of 255 characters -Indicative's [documentation](https://support.indicative.com/hc/en-us/articles/360004149152-REST-API-Track-Events?utm_source=partners&utm_medium=segment&utm_campaign=integration) states that the values in the properties must not exceed 255 characters. Segment will still accept the call, but any values that exceed 255 characters will be trimmed (meaning only the first 255 characters will be sent to Indicative). +Indicative's [documentation](https://support.indicative.com/hc/en-us/articles/360004147512-REST-API-Guide) states that the values in the properties must not exceed 255 characters. Segment will still accept the call, but any values that exceed 255 characters will be trimmed (meaning only the first 255 characters will be sent to Indicative). diff --git a/src/connections/destinations/catalog/insider/index.md b/src/connections/destinations/catalog/insider/index.md index 64338d630d..31c1c7cd94 100644 --- a/src/connections/destinations/catalog/insider/index.md +++ b/src/connections/destinations/catalog/insider/index.md @@ -19,7 +19,7 @@ This destination is maintained by Insider. For any issues with the destination, ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page("Home", { @@ -38,7 +38,7 @@ Segment sends Page calls to Insider as a `page view` event with the following ev ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify("userId123", { @@ -65,7 +65,7 @@ Insider uses `userId`, `anonymousId`, `email` and `phone number` as identifiers. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Product Viewed', { diff --git a/src/connections/destinations/catalog/journy-io/index.md b/src/connections/destinations/catalog/journy-io/index.md index 37b92fd357..49a2c459d6 100644 --- a/src/connections/destinations/catalog/journy-io/index.md +++ b/src/connections/destinations/catalog/journy-io/index.md @@ -24,7 +24,7 @@ This destination is maintained by journy.io. For any issues with the destination ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -34,7 +34,7 @@ Segment sends Page calls to journy.io as a `pageview`. Only page calls with `ano ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -46,7 +46,7 @@ Segment sends Identify calls to journy.io where they create a new, or update an ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -58,7 +58,7 @@ Set `context.groupId` to record the event and attribute it to a specific account ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.group('groupId123', { diff --git a/src/connections/destinations/catalog/june/index.md b/src/connections/destinations/catalog/june/index.md index c37ec66b5a..6ba6e3a198 100644 --- a/src/connections/destinations/catalog/june/index.md +++ b/src/connections/destinations/catalog/june/index.md @@ -18,7 +18,7 @@ This destination is maintained by June. For any issues with the destination, [co ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -29,7 +29,7 @@ Segment sends Identify calls to June as an `identify` event. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -38,7 +38,7 @@ Segment sends Track calls to June as a `track` event. ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.group("0e8c78ea9d97a7b8185e8632", { @@ -53,7 +53,7 @@ Group calls from Segment update `Companies` in June. Each `Company` is associate ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page('Home') diff --git a/src/connections/destinations/catalog/kahuna/index.md b/src/connections/destinations/catalog/kahuna/index.md index 6c96041e5b..4a9d0343b3 100644 --- a/src/connections/destinations/catalog/kahuna/index.md +++ b/src/connections/destinations/catalog/kahuna/index.md @@ -6,7 +6,7 @@ title: Kahuna Destination Segment makes it easy to send your data to Kahuna. When you tracking your data using Segment's [open-source libraries](/docs/connections/sources/catalog/), Segment translates and routes your data to Kahuna in a format it can process. -If you have mobile apps, then Kahuna recommends that you use the Segment [iOS](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios) and or [Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android) library and bundling Kahuna (see [Mobile](#mobile) section below). +If you have mobile apps, then Kahuna recommends that you use the Segment [iOS](/docs/connections/sources/catalog/libraries/mobile/ios) and or [Android](/docs/connections/sources/catalog/libraries/mobile/android) library and bundling Kahuna (see [Mobile](#mobile) section below). If you are sending data from a server side library, read the [Server side](#server-side) section. @@ -38,7 +38,7 @@ compile ('com.kahuna.integration.android.segment:kahuna:+') { } ``` -Then, bundle Kahuna during your Segment Analytics initialization, with more details [here](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/#bundling-integrations): +Then, bundle Kahuna during your Segment Analytics initialization, with more details [here](/docs/connections/sources/catalog/libraries/mobile/android/#bundling-integrations): ```java Analytics analytics = new Analytics.Builder(this, "SEGMENT_KEY") @@ -54,7 +54,7 @@ Add the Kahuna pod dependency: pod "Segment-Kahuna ``` -Then, bundle Kahuna during your Segment Analytics initialization, with more details [here](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#bundling-integrations): +Then, bundle Kahuna during your Segment Analytics initialization, with more details [here](/docs/connections/sources/catalog/libraries/mobile/ios/#bundling-integrations): ```objc #import diff --git a/src/connections/destinations/catalog/kevel/index.md b/src/connections/destinations/catalog/kevel/index.md index 3b477b0127..d85a83e0c2 100644 --- a/src/connections/destinations/catalog/kevel/index.md +++ b/src/connections/destinations/catalog/kevel/index.md @@ -21,7 +21,7 @@ This destination is maintained by Kevel. For any issues with the destination, [c ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/kissmetrics/index.md b/src/connections/destinations/catalog/kissmetrics/index.md index 602a34e877..03ab6ac669 100644 --- a/src/connections/destinations/catalog/kissmetrics/index.md +++ b/src/connections/destinations/catalog/kissmetrics/index.md @@ -2,7 +2,7 @@ title: Kissmetrics Destination rewrite: true --- -[Kissmetrics](https://www.kissmetricshq.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a behavioral email and analytics platofrm. It pulls cross-platform behavior reports so marketers can analyze key audience growth segments. It also provides an overview of custom populations, population change and growth, so marketers can analyze populations from customers who have completed actions or events. +[Kissmetrics](https://www.kissmetricshq.com/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) is a behavioral email and analytics platform. It pulls cross-platform behavior reports so marketers can analyze key audience growth segments. It also provides an overview of custom populations, population change and growth, so marketers can analyze populations from customers who have completed actions or events. This document was last updated on July 3, 2018. If you notice any gaps, out-dated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact/)! @@ -17,17 +17,17 @@ To enable Kissmetrics in Segment: 3. In the destination settings, enter your Kissmetrics "API Key". 4. If you are using Kissmetrics using Segment's client-side analytics.js library, Segment asynchronously loads Kissmetrics Javascript library onto the page. (This means you should remove Kissmetrics's snippet from your page.) -Your Kissmetrics source starts automatically collecting "Visited Site" events and [other automatically tracked events](http://support.kissmetrics.com/article/show/javascript-settings). +Your Kissmetrics source starts automatically collecting "Visited Site" events and [other automatically tracked events](https://support.kissmetrics.io/docs/javascript-settings). ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page('Docs'); ``` -By default page calls with `name` and `category` properties will automatically be sent to Kissmetrics in your [`page`](/docs/connections/spec/page/) calls. You can adjust this behavior in your Kissmetric destination settings by toggling on and off the 'Track Categorized Pages' and 'Track Named Pages' settings. +By default page calls with `name` and `category` properties will automatically be sent to Kissmetrics in your [`page`](/docs/connections/spec/page/) calls. You can adjust this behavior in your Kissmetrics destination settings by toggling on and off the 'Track Categorized Pages' and 'Track Named Pages' settings. Here's an example call on docs pages: @@ -46,7 +46,7 @@ __Note:__ Kissmetrics requires an initial pageview to load the library. By defau ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123'); @@ -56,7 +56,7 @@ When you call [`identify`](/docs/connections/spec/identify/), we first call Kiss ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track('Clicked Button'); @@ -70,7 +70,7 @@ The Kissmetrics javascript library automatically tracks a bunch of events (Visit ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```javascript analytics.group('123'); @@ -95,7 +95,7 @@ will add the following traits to the user: ## Alias -If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](https://segment.com/docs/connections/spec/alias/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](/docs/connections/spec/alias/) does. An example call would look like: ```javascript analytics.alias(); @@ -107,7 +107,7 @@ Kissmetrics automatically aliases anonymous visitors the first time you call [`i We will automatically call [`alias`](/docs/connections/spec/alias/) for you the first time you [`identify`](/docs/connections/spec/identify/) users from our iOS SDK. That way it works exactly like web browser tracking - you don't have to manually [`alias`](/docs/connections/spec/alias/) new users. -You can read more about how Kissmetrics recommends using [`alias`](/docs/connections/spec/alias/) [in their docs](http://support.kissmetrics.com/article/show/understanding-identities). +You can read more about how Kissmetrics recommends using [`alias`](/docs/connections/spec/alias/) [in their docs](https://support.kissmetrics.io/docs/understanding-identities). @@ -207,4 +207,4 @@ In order to enable this feature, ### E-Commerce -If you are using our ecommerce api, we will forward that data along to Kissmetrics following the [Kissmetrics Ecommerce Essentials Guide](http://support.kissmetrics.com/article/show/ecommerce-essentials). +If you are using our ecommerce api, we will forward that data along to Kissmetrics following the [Kissmetrics Ecommerce Essentials Guide](https://support.kissmetrics.io/docs/e-commerce-javascript-code-examples). diff --git a/src/connections/destinations/catalog/kitemetrics/index.md b/src/connections/destinations/catalog/kitemetrics/index.md index e460e4b723..734488c09a 100644 --- a/src/connections/destinations/catalog/kitemetrics/index.md +++ b/src/connections/destinations/catalog/kitemetrics/index.md @@ -22,7 +22,7 @@ This destination is maintained by Kitemetrics. For any issues with the destinati ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. In order to track Apple Search Ads attribution events you will need to include the [Analytics-iAds-Attribution](https://github.com/segmentio/analytics-ios-iads-attribution) middleware library in your iOS source application. @@ -33,7 +33,7 @@ pod "Analytics" pod "Analytics-iAds-Attribution" ``` -Segment and Kitemetrics can automatically record the following events: "Application Installed", "Application Opened", "Application Updated" and “In-App Purchases”. In order to capture those events you need to enable automatic tracking. Ensure you set up [SEGAnalyticsConfiguration](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/) as shown below: +Segment and Kitemetrics can automatically record the following events: "Application Installed", "Application Opened", "Application Updated" and “In-App Purchases”. In order to capture those events you need to enable automatic tracking. Ensure you set up [SEGAnalyticsConfiguration](/docs/connections/sources/catalog/libraries/mobile/ios/) as shown below: Swift ```swift @@ -58,7 +58,7 @@ Kitemetrics will show the device installs, sessions and purchases on the Analyti ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. You can turn on automatic screen tracking and/or call it manually. An example manual call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. You can turn on automatic screen tracking and/or call it manually. An example manual call would look like: Swift ```swift diff --git a/src/connections/destinations/catalog/klaviyo/index.md b/src/connections/destinations/catalog/klaviyo/index.md index 45d97a478a..2828fe2663 100644 --- a/src/connections/destinations/catalog/klaviyo/index.md +++ b/src/connections/destinations/catalog/klaviyo/index.md @@ -120,7 +120,7 @@ You can also choose whether you want to force users to confirm the optin to your ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track({ diff --git a/src/connections/destinations/catalog/kochava/index.md b/src/connections/destinations/catalog/kochava/index.md index 1277fdc7c5..7f98d22f2d 100644 --- a/src/connections/destinations/catalog/kochava/index.md +++ b/src/connections/destinations/catalog/kochava/index.md @@ -23,7 +23,7 @@ Additional information from Kochava on [setting up your first campaign within Ko ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] track:@"Item Purchased" diff --git a/src/connections/destinations/catalog/kubit/index.md b/src/connections/destinations/catalog/kubit/index.md index aa449509f5..4aaae0f1dd 100644 --- a/src/connections/destinations/catalog/kubit/index.md +++ b/src/connections/destinations/catalog/kubit/index.md @@ -17,7 +17,7 @@ This destination is maintained by Kubit. For any issues with the destination, [c ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -26,7 +26,7 @@ Segment sends Page calls to Kubit as a `pageview`. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/kubric/index.md b/src/connections/destinations/catalog/kubric/index.md index b494f4f4f9..833f4de598 100644 --- a/src/connections/destinations/catalog/kubric/index.md +++ b/src/connections/destinations/catalog/kubric/index.md @@ -20,7 +20,7 @@ This destination is maintained by Kubric. For any issues with the destination, [ ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -31,7 +31,7 @@ Page calls will be sent to Kubric as a `page`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -42,7 +42,7 @@ Screen calls will be sent to Kubric as a `screen`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -55,7 +55,7 @@ Identify calls will be sent to Kubric as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/kustomer/index.md b/src/connections/destinations/catalog/kustomer/index.md index 16d1e44d4f..668c774d31 100644 --- a/src/connections/destinations/catalog/kustomer/index.md +++ b/src/connections/destinations/catalog/kustomer/index.md @@ -18,11 +18,11 @@ This destination is maintained by Kustomer. For any issues with the destination, 4. In your Kustomer account, go to **Settings** > **Apps Directory** and install the **Segment** App. 5. After installing the Segment App, you need to go to the **Segment App Settings Page** listed directly underneath the Apps Directory page. From this page you will need to click the large green "Enable with Segment" button. -**NOTE:** Kustomer stores anonymous activity for 30 days but you will not see this activity in their UI unless the customer is identified using the [Identify](https://segment.com/docs/connections/destinations/catalog/kustomer/#identify) call. +**NOTE:** Kustomer stores anonymous activity for 30 days but you will not see this activity in their UI unless the customer is identified using the [Identify](/docs/connections/destinations/catalog/kustomer/#identify) call. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page('Pricing', { @@ -37,7 +37,7 @@ Page calls will sent as a `tracking event` to Kustomer on the timeline of the cu ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home" @@ -48,7 +48,7 @@ Screen calls will sent as a `tracking event` to Kustomer on the timeline of the ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -58,7 +58,7 @@ analytics.identify('userId123', { Identify calls will be sent to Kustomer which will create or update a standard customer object record. If a record with a corresponding `userId` exists, that record will be updated. If a customer record doesn't already exist, a new customer record will be created. -All of the overlapping attributes in the Segment [traits](https://segment.com/docs/connections/spec/identify/#traits) documentation are mapped to standard Kustomer attributes by default. In addition to the Segment traits, the following attributes are automatically mapped from Segment to Kustomer: +All of the overlapping attributes in the Segment [traits](/docs/connections/spec/identify/#traits) documentation are mapped to standard Kustomer attributes by default. In addition to the Segment traits, the following attributes are automatically mapped from Segment to Kustomer: | Segment | Kustomer | | ------------ | -------- | @@ -68,7 +68,7 @@ All of the overlapping attributes in the Segment [traits](https://segment.com/do ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track("Registered", { diff --git a/src/connections/destinations/catalog/launchdarkly-events/index.md b/src/connections/destinations/catalog/launchdarkly-events/index.md index de524091dc..02e06363f1 100644 --- a/src/connections/destinations/catalog/launchdarkly-events/index.md +++ b/src/connections/destinations/catalog/launchdarkly-events/index.md @@ -21,7 +21,7 @@ This destination is maintained by LaunchDarkly. For any issues with the destinat 5. Enter this ID as the **API Key** in the “LaunchDarkly” destination settings in Segment. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```json { diff --git a/src/connections/destinations/catalog/leanplum/index.md b/src/connections/destinations/catalog/leanplum/index.md index a70e541bb0..656dac6242 100644 --- a/src/connections/destinations/catalog/leanplum/index.md +++ b/src/connections/destinations/catalog/leanplum/index.md @@ -8,7 +8,7 @@ rewrite: true This document was last updated on January 29, 2018. If you notice any gaps, outdated information or simply want to leave some feedback to help us improve our documentation, [let us know](https://segment.com/help/contact)! > success "" -> **Good to know**: This page is about the Leanplum Segment destination, which receives data from Segment. There's also a page about the [Leanplum Segment source](https://segment.com/docs/connections/sources/catalog/cloud-apps/leanplum/), which sends data _to_ Segment! +> **Good to know**: This page is about the Leanplum Segment destination, which receives data from Segment. There's also a page about the [Leanplum Segment source](/docs/connections/sources/catalog/cloud-apps/leanplum/), which sends data _to_ Segment! ## Getting Started @@ -22,9 +22,9 @@ This document was last updated on January 29, 2018. If you notice any gaps, outd 5. We recommend creating 2 Leanplum Destinations, 1 for production and 1 for development. 6. Copy the "Production" or "Development" value into the corresponding Leanplum destination and add it to the Segment Settings UI under "Leanplum Client Key" depending on your chosen environment. -If you have opted to use our [server-side sources](https://segment.com/docs/connections/sources/#server), we will begin passing data through our servers or from your users' devices to Leanplum within minutes after you enable it on your source destinations page. +If you have opted to use our [server-side sources](/docs/connections/sources/#server), we will begin passing data through our servers or from your users' devices to Leanplum within minutes after you enable it on your source destinations page. -In order to use Leanplum's Push Notifications, Messaging channels or A/B testing in your mobile app, you will need to use our [iOS](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/) or [Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/) SDKs. Read on to find out how to set this up. +In order to use Leanplum's Push Notifications, Messaging channels or A/B testing in your mobile app, you will need to use our [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/) or [Android](/docs/connections/sources/catalog/libraries/mobile/android/) SDKs. Read on to find out how to set this up. ### iOS @@ -132,7 +132,7 @@ That's it! Now you can use the Segment SDK and also the [advanced features](http ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page() @@ -143,7 +143,7 @@ When you call `page` as a user moves to a new area, you can advance your user's ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify({ userId: 'user123', @@ -158,7 +158,7 @@ As soon as a user logs-in or signs-up, you'll want to make an `identify` call wh ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track({ userId: 'user123', @@ -172,7 +172,7 @@ analytics.track({ Calling a `track` event will log a user event with Leanplum so that you can figure out how to increase engagement, virality, or whatever key action is critical to your business. ## Additional Features -The features listed below are only supported if you have installed our [iOS](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/) or [Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/) SDKs. +The features listed below are only supported if you have installed our [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/) or [Android](/docs/connections/sources/catalog/libraries/mobile/android/) SDKs. ### Push Notifications diff --git a/src/connections/destinations/catalog/learndot/index.md b/src/connections/destinations/catalog/learndot/index.md index 40c18dd066..f76f65cc94 100644 --- a/src/connections/destinations/catalog/learndot/index.md +++ b/src/connections/destinations/catalog/learndot/index.md @@ -21,7 +21,7 @@ This destination is maintained by Learndot. For any issues with the destination, ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -36,7 +36,7 @@ Learndot uses the `identify` event in order to map events in Segment back to lea ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') @@ -48,7 +48,7 @@ The `track` and `identify` are tightly coupled in Learndot. We use the `identify ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -58,7 +58,7 @@ Page calls will be sent to Learndot as a `pageview`and will be used to help furt ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; diff --git a/src/connections/destinations/catalog/lou/index.md b/src/connections/destinations/catalog/lou/index.md index 93c9dad667..8749f7a81c 100644 --- a/src/connections/destinations/catalog/lou/index.md +++ b/src/connections/destinations/catalog/lou/index.md @@ -18,7 +18,7 @@ This destination is maintained by Lou. For any issues with the destination, [con ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -33,7 +33,7 @@ Lou does not accept any personally identifiable information (PII) fields from Id ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/lucky-orange/index.md b/src/connections/destinations/catalog/lucky-orange/index.md index f0805f2f1d..fa06a50462 100644 --- a/src/connections/destinations/catalog/lucky-orange/index.md +++ b/src/connections/destinations/catalog/lucky-orange/index.md @@ -18,7 +18,7 @@ This document was last updated on October 16, 2018. If you notice any gaps, outd ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify("97980cfea0067", { diff --git a/src/connections/destinations/catalog/mabl/index.md b/src/connections/destinations/catalog/mabl/index.md index 97a3fed610..9855deb737 100644 --- a/src/connections/destinations/catalog/mabl/index.md +++ b/src/connections/destinations/catalog/mabl/index.md @@ -25,7 +25,7 @@ mabl processes the usage data into rolling 24 hour summaries, every hour. It ca ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -35,7 +35,7 @@ Page calls are used by mabl to build a model of the pages in your app and determ ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/mailchimp/index.md b/src/connections/destinations/catalog/mailchimp/index.md index 9d1dfc0c60..811ac0a416 100644 --- a/src/connections/destinations/catalog/mailchimp/index.md +++ b/src/connections/destinations/catalog/mailchimp/index.md @@ -20,7 +20,7 @@ This document was last updated on May 08, 2018. If you notice any gaps, out-date ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId12345', { diff --git a/src/connections/destinations/catalog/mammoth/index.md b/src/connections/destinations/catalog/mammoth/index.md index 280eec4cd3..ae0db7b536 100644 --- a/src/connections/destinations/catalog/mammoth/index.md +++ b/src/connections/destinations/catalog/mammoth/index.md @@ -83,7 +83,7 @@ Mammoth recommends that you use the *Save as Dataset* task in the *ADD TASK* men ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -94,7 +94,7 @@ Page calls will be sent to the webhook dataset you created earlier. You can filt ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@ "Home"]; @@ -105,7 +105,7 @@ Screen calls will be sent to the webhook dataset you created earlier. You can fi ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -118,7 +118,7 @@ Identify calls will be sent to the webhook dataset you created earlier. You can ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/marketo-v2/index.md b/src/connections/destinations/catalog/marketo-v2/index.md index 88441b38f4..1495989cc9 100644 --- a/src/connections/destinations/catalog/marketo-v2/index.md +++ b/src/connections/destinations/catalog/marketo-v2/index.md @@ -130,7 +130,7 @@ When you call [`Track`](/docs/connections/spec/track/), Segment maps the event t - Enable [Cloud-mode](/docs/connections/destinations/catalog/marketo-v2/#supported-sources-and-connection-modes) - Enable [Device-mode](/docs/connections/destinations/catalog/marketo-v2/#supported-sources-and-connection-modes) and enable the [Send Track Events Server Side](/docs/connections/destinations/catalog/marketo-v2/#send-track-events-server-side) setting -- Send track events from one of our [server side libraries](https://segment.com/docs/connections/sources/#server) +- Send track events from one of our [server side libraries](/docs/connections/sources/#server) Here is a sample Ruby `.track()` event: @@ -173,7 +173,7 @@ Here is a sample Node `.page()` event: category: 'Docs', name: 'Node.js Library', properties: { - url: 'https://segment.com/docs/connections/sources/catalog/libraries/server/node', + url: '/docs/connections/sources/catalog/libraries/server/node', path: '/docs/connections/sources/catalog/libraries/server/node/', title: 'Node.js Library - Segment', referrer: 'https://github.com/segmentio/analytics-node' @@ -235,7 +235,7 @@ You can do one of the following to prevent duplicate leads: To upload a list to Marketo, when you are in Lead Database, click All Leads. Then click "New", then "Import List" from the drop down. Select your CSV, then click "Next". Make sure "Email Address" and "userId" are the Marketo Fields selected then click "Next". Name your list or select a pre-existing list. Select "None" for Acquisition Program. Then Click "Import". 2. Manually merge leads in Marketo. Follow [these instructions to merge](http://docs.marketo.com/display/public/DOCS/Find+and+Merge+Duplicate+People) any duplicate leads found in Marketo after enabling the destination. -3. Make sure to call identify first. This is already a recommended best practice as [part of our spec](https://segment.com/docs/connections/spec/identify/). +3. Make sure to call identify first. This is already a recommended best practice as [part of our spec](/docs/connections/spec/identify/). 4. Pass an email in your `.track()` and `.page()` calls. ## Migrating from Marketo to Marketo V2 diff --git a/src/connections/destinations/catalog/matomo/index.md b/src/connections/destinations/catalog/matomo/index.md index 053d4f9ad1..b9a0ca81c4 100644 --- a/src/connections/destinations/catalog/matomo/index.md +++ b/src/connections/destinations/catalog/matomo/index.md @@ -19,7 +19,7 @@ This document was last updated on July 18th, 2018. If you notice any gaps, outda 5. When you enable Matomo in your Segment settings, Segment's CDN is updated within 45 minutes. Once that happens, Segment asynchronously loads `matomo.js` on your page whenever it is loaded. This means you should remove Matomo's snippet from your page. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page(); @@ -28,7 +28,7 @@ analytics.page(); Our Page method triggers a call to Matomo's `trackPageView` method. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('97980cfea0068'); @@ -36,7 +36,7 @@ analytics.identify('97980cfea0068'); Our Identify method triggers a call to Matomo's `setUserId` method and will send the `userId` to Matomo. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Logged In'); diff --git a/src/connections/destinations/catalog/metacx/index.md b/src/connections/destinations/catalog/metacx/index.md index 412f9161f6..6406dc7d75 100644 --- a/src/connections/destinations/catalog/metacx/index.md +++ b/src/connections/destinations/catalog/metacx/index.md @@ -21,7 +21,7 @@ This destination is maintained by MetaCX. For any issues with the destination, c ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -32,7 +32,7 @@ Page calls will be sent to the SegmentIO connection with event key `page`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -43,7 +43,7 @@ Screen calls will be sent to the SegmentIO connection with event key `screenview ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -56,7 +56,7 @@ Identify calls will be sent to the SegmentIO connection with eventKey `identify` ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/modern-pricing/index.md b/src/connections/destinations/catalog/modern-pricing/index.md index 2bac2af2a4..985f554588 100644 --- a/src/connections/destinations/catalog/modern-pricing/index.md +++ b/src/connections/destinations/catalog/modern-pricing/index.md @@ -47,7 +47,7 @@ analytics.page( ); ``` -Page calls will be sent to Modern Pricing as a `pageview`. If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. +Page calls will be sent to Modern Pricing as a `pageview`. If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. **Optional Best Practices** diff --git a/src/connections/destinations/catalog/moesif-api-analytics/index.md b/src/connections/destinations/catalog/moesif-api-analytics/index.md index d68bf5d51b..e98cf870b7 100644 --- a/src/connections/destinations/catalog/moesif-api-analytics/index.md +++ b/src/connections/destinations/catalog/moesif-api-analytics/index.md @@ -20,11 +20,11 @@ This destination is maintained by Moesif. For any issues with the destination, [ 4. Once integrated, Segment data shows up in Moesif in a few seconds. > tip "" -> **Tip**: You can use Segment's [Replay feature](https://segment.com/docs/guides/what-is-replay/) to sync historical events sent through Segment into your Moesif app. +> **Tip**: You can use Segment's [Replay feature](/docs/guides/what-is-replay/) to sync historical events sent through Segment into your Moesif app. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -46,10 +46,10 @@ Segment sends `identify()` calls to Moesif as [user updates](https://www.moesif. |`traits`|`metadata`| |`traits.company.id`|`company_id`| -The integration handles Segment [reserved traits](https://segment.com/docs/connections/spec/identify/#traits) like `email` and `firstName`. It maps [automatically-collected fields](/docs/connections/spec/common/#context-fields-automatically-collected) like campaign information and IP address. +The integration handles Segment [reserved traits](/docs/connections/spec/identify/#traits) like `email` and `firstName`. It maps [automatically-collected fields](/docs/connections/spec/common/#context-fields-automatically-collected) like campaign information and IP address. ## Track -If you haven’t had a chance to review our spec, take a look tounderstand what the [Track](https://segment.com/docs/connections/spec/track/) method does. An example call would look like: +If you haven’t had a chance to review our spec, take a look tounderstand what the [Track](/docs/connections/spec/track/) method does. An example call would look like: ``` analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/mouseflow/index.md b/src/connections/destinations/catalog/mouseflow/index.md index 237c33f48f..8247737b41 100644 --- a/src/connections/destinations/catalog/mouseflow/index.md +++ b/src/connections/destinations/catalog/mouseflow/index.md @@ -19,7 +19,7 @@ Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.j ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() ``` @@ -27,7 +27,7 @@ An initial `page` call is required for data to be sent to Mouseflow using Analyt ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('user1234', { email: 'petergibbon@email.com', diff --git a/src/connections/destinations/catalog/movable-ink/index.md b/src/connections/destinations/catalog/movable-ink/index.md index 17c0b7e271..650be6de1e 100644 --- a/src/connections/destinations/catalog/movable-ink/index.md +++ b/src/connections/destinations/catalog/movable-ink/index.md @@ -22,14 +22,14 @@ Perform the following steps to get started with Segment's Movable Ink destinatio ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. When you send an `identify` event with one of Segments sources, this is passed to the Movable Ink API and includes the user `traits` you provide along with the previously used `anonymousId` as well as the `userId` that was given. Once the Movable Ink API receives this `identify` event, it will associate the events made by the previous `anonymousId` to the provided `userId` or `traits.email` if one is provided. From that point on, the events will now appear in the user profile. This enables **Signals** features such as behavioral targeting, as well as content integrations like **Behavioral Apps**. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. When you send a `track` event with one of Segment's sources, Movable Ink will normalize them into the same events that Movable Ink's API would normally receive. They will then be available to target against in behavioral marketing campaign content as well as being available in **Custom Apps** and **Behavioral Apps**. @@ -40,7 +40,7 @@ If no `identify` call has been made, then the events will be attributed to an an Events coming from Segment have a few required properties for them to work with **Signals**. ### Ecommerce Supported Events -Movable Ink currently supports the [Segment Ecommerce](https://segment.com/docs/connections/spec/ecommerce/v2/) event specification, and in the future Movable Ink may expand the supported events to work with additional client use cases. +Movable Ink currently supports the [Segment Ecommerce](/docs/connections/spec/ecommerce/v2/) event specification, and in the future Movable Ink may expand the supported events to work with additional client use cases. #### Product Events The `Product Viewed` and `Product Added` `track` events must include the following properties in order for them to be used in **Signals**: diff --git a/src/connections/destinations/catalog/msg91/index.md b/src/connections/destinations/catalog/msg91/index.md index 8108d91e2b..250fe8fa0d 100644 --- a/src/connections/destinations/catalog/msg91/index.md +++ b/src/connections/destinations/catalog/msg91/index.md @@ -22,7 +22,7 @@ This destination is maintained by MSG91. For any issues with the destination, [c ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` { @@ -46,7 +46,7 @@ Identify calls will be sent to MSG91 as an `Send SMS` event. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. Make sure you send the following Properties with `page` method to send SMS. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. Make sure you send the following Properties with `page` method to send SMS. An example call would look like: ``` { @@ -65,7 +65,7 @@ Page calls will be sent to MSG91 as a `Send SMS`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. Make sure you send the following Properties with `Screen` method to send SMS. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. Make sure you send the following Properties with `Screen` method to send SMS. An example call would look like: ``` { @@ -83,7 +83,7 @@ Screen calls will be sent to MSG91 as a `Send SMS`. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. Make sure you send the following Properties with `track` method to send SMS. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. Make sure you send the following Properties with `track` method to send SMS. An example call would look like: ``` { diff --git a/src/connections/destinations/catalog/mutiny/index.md b/src/connections/destinations/catalog/mutiny/index.md index 39cb84d1f9..455f7874bf 100644 --- a/src/connections/destinations/catalog/mutiny/index.md +++ b/src/connections/destinations/catalog/mutiny/index.md @@ -18,7 +18,7 @@ To set up Mutiny to receive Segment data: ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -29,7 +29,7 @@ Page calls will be sent to Mutiny as an `impression`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -42,7 +42,7 @@ Identify calls will be sent to Mutiny as an `identify` event. We use this in ord ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/nat/index.md b/src/connections/destinations/catalog/nat/index.md index 56af816436..583960cb04 100644 --- a/src/connections/destinations/catalog/nat/index.md +++ b/src/connections/destinations/catalog/nat/index.md @@ -21,7 +21,7 @@ This destination is maintained by Nat.app. For any issues with the destination, ## Identify -If you aren't familiar with the Segment Spec, read the documentation to learn what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you aren't familiar with the Segment Spec, read the documentation to learn what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/new-relic/index.md b/src/connections/destinations/catalog/new-relic/index.md index f10f2da6c0..8c25b0f721 100644 --- a/src/connections/destinations/catalog/new-relic/index.md +++ b/src/connections/destinations/catalog/new-relic/index.md @@ -17,7 +17,7 @@ This document was last updated on August 29, 2018. If you notice any gaps, outda ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Article Completed', { title: 'How to Create a Tracking Plan', diff --git a/src/connections/destinations/catalog/noora/index.md b/src/connections/destinations/catalog/noora/index.md index 0025caf93d..3c94592799 100644 --- a/src/connections/destinations/catalog/noora/index.md +++ b/src/connections/destinations/catalog/noora/index.md @@ -18,7 +18,7 @@ This destination is maintained by Noora. For any issues with the destination, [c ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/optimizely-web/index.md b/src/connections/destinations/catalog/optimizely-web/index.md index 242a1bc141..60301d9d8c 100644 --- a/src/connections/destinations/catalog/optimizely-web/index.md +++ b/src/connections/destinations/catalog/optimizely-web/index.md @@ -11,11 +11,11 @@ Segment's **Optimizely Web (previously Optimizely)** destination supports the fo * [Optimizely X Web](#optimizely-x-web) * [Optimizely Full Stack (JavaScript)](#optimizely-full-stack-javascript-sdk) -If you're interested in implementing Optimizely Full Stack server-side or on mobile, see Segment's [**Optimizely Full Stack** destination](https://segment.com/docs/connections/destinations/catalog/optimizelyx/), which supports: +If you're interested in implementing Optimizely Full Stack server-side or on mobile, see Segment's [**Optimizely Full Stack** destination](/docs/connections/destinations/catalog/optimizelyx/), which supports: -* [Optimizely Full Stack (server)](https://segment.com/docs/connections/destinations/catalog/optimizelyx/#server-side) -* [Optimizely Full Stack Android (cloud-mode)](https://segment.com/docs/connections/destinations/catalog/optimizelyx/#android-cloud-mode-implementation) -* [Optimizely Full Stack iOS (cloud-mode)](https://segment.com/docs/connections/destinations/catalog/optimizelyx/#ios-cloud-mode-implementation) +* [Optimizely Full Stack (server)](/docs/connections/destinations/catalog/optimizelyx/#server-side) +* [Optimizely Full Stack Android (cloud-mode)](/docs/connections/destinations/catalog/optimizelyx/#android-cloud-mode-implementation) +* [Optimizely Full Stack iOS (cloud-mode)](/docs/connections/destinations/catalog/optimizelyx/#ios-cloud-mode-implementation) **Use Cases** @@ -219,7 +219,7 @@ analytics.track('Category Clicked', { If you were to send this Segment `track` event to Optimizely using any of the Segment integrations, you would only be able to use the `eventName` ‘Click’ as a `metric` in Optimizely since custom event tags in Optimizely are not available on the [Results page](https://help.optimizely.com/Analyze_Results/The_Experiment_Results_page_for_Optimizely_X). -To send a `track` event from Segment with the context about that event from the `properties` to Optimizely, create a [custom Segment Destination Function](https://segment.com/docs/connections/destinations/destination-functions/) that maps the Segment `eventName` to a more specific Optimizely `eventName` and send an Optimizely `event` payload with the transformed `eventName` to the Optimizely [Event API](https://docs.developers.optimizely.com/web/docs/event-api). Using the example above, the Segment `track` event ‘Click’ can be transformed to an Optimizely `event` with the `eventName` ‘Clicked Shirt’. +To send a `track` event from Segment with the context about that event from the `properties` to Optimizely, create a [custom Segment Destination Function](/docs/connections/destinations/destination-functions/) that maps the Segment `eventName` to a more specific Optimizely `eventName` and send an Optimizely `event` payload with the transformed `eventName` to the Optimizely [Event API](https://docs.developers.optimizely.com/web/docs/event-api). Using the example above, the Segment `track` event ‘Click’ can be transformed to an Optimizely `event` with the `eventName` ‘Clicked Shirt’. ### Sending effective referrer in your automatic page calls diff --git a/src/connections/destinations/catalog/owneriq-pixel/index.md b/src/connections/destinations/catalog/owneriq-pixel/index.md index fa32014eeb..c4601e17c3 100644 --- a/src/connections/destinations/catalog/owneriq-pixel/index.md +++ b/src/connections/destinations/catalog/owneriq-pixel/index.md @@ -19,7 +19,7 @@ This destination is maintained by OwnerIQ. For any issues with the destination, ## Page -If you aren't familiar with the Segment Spec, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() @@ -29,9 +29,9 @@ OwnerIQ have mapped `analytics.page()` to OwnerIQ's Website Analytics Tag method ## Track -If you aren't familiar with the Segment Spec, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you aren't familiar with the Segment Spec, take a look to understand what the [Track method](/docs/connections/spec/track/) does. -The following table shows how OwnerIQ map Segment's [semantic ecommerce](https://segment.com/docs/connections/spec/ecommerce/v2/) or custom event names to OwnerIQ's tag event: +The following table shows how OwnerIQ map Segment's [semantic ecommerce](/docs/connections/spec/ecommerce/v2/) or custom event names to OwnerIQ's tag event: | Segment Event Name | ownerIQ tag event | | -------- | -------- | diff --git a/src/connections/destinations/catalog/parsely/index.md b/src/connections/destinations/catalog/parsely/index.md index 6531a84447..bfd0e2fa83 100644 --- a/src/connections/destinations/catalog/parsely/index.md +++ b/src/connections/destinations/catalog/parsely/index.md @@ -34,7 +34,7 @@ If you are using dynamic tracking, you must explicitly let us know in your [inte ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('ze8rt1u89', { @@ -60,7 +60,7 @@ Video tracking is possible with either web or server sources. ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```js analytics.group("0e8c78ea9d97a7b8185e8632", { @@ -75,7 +75,7 @@ analytics.group("0e8c78ea9d97a7b8185e8632", { ## Alias -If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](https://segment.com/docs/connections/spec/alias/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](/docs/connections/spec/alias/) does. An example call would look like: ```js analytics.alias("507f191e81"); @@ -84,7 +84,7 @@ analytics.alias("507f191e81"); ### Mapping custom properties to semantic Parsely properties -If you'd like to map certain semantic Parse.ly properties to your own custom properties (ones that do not abide by our [page spec](https://segment.com/docs/connections/spec/page), you can define your mappings in your Segment destination settings! You can put the name of your Segment property on the left and the Parse.ly property on the right hand side. +If you'd like to map certain semantic Parse.ly properties to your own custom properties (ones that do not abide by our [page spec](/docs/connections/spec/page), you can define your mappings in your Segment destination settings! You can put the name of your Segment property on the left and the Parse.ly property on the right hand side. We currently support mapping the following Parse.ly properties (make sure you spell these correctly on the right hand side of this setting!): @@ -209,7 +209,7 @@ analytics.track('Video Playback Paused', { (Note: this event is only required for server side tracking) -When using Parse.ly on the web using our Javascript SDK, video heartbeats are captured by their SDK automatically. However, if you are using this destination with a Server side source, you must pass heartbeat events manually using our [Video Content Playing](https://segment.com/docs/connections/spec/video/#content-events) event. +When using Parse.ly on the web using our Javascript SDK, video heartbeats are captured by their SDK automatically. However, if you are using this destination with a Server side source, you must pass heartbeat events manually using our [Video Content Playing](/docs/connections/spec/video/#content-events) event. **Important:** These events must be sent in 10 second increments. @@ -247,7 +247,7 @@ analytics.track({ This event is only required for server side tracking. -To track the completion of a video, use our [Video Content Completed](https://segment.com/docs/connections/spec/video/#content-events) event. +To track the completion of a video, use our [Video Content Completed](/docs/connections/spec/video/#content-events) event. Make sure you are sending at minimum, `assetId`, `totalLength`, and `position` as properties. diff --git a/src/connections/destinations/catalog/persistiq/index.md b/src/connections/destinations/catalog/persistiq/index.md index 0b27faed65..fdd14b6c01 100644 --- a/src/connections/destinations/catalog/persistiq/index.md +++ b/src/connections/destinations/catalog/persistiq/index.md @@ -21,7 +21,7 @@ This destination is maintained by PersistIQ. For any issues with the destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { email: 'john.doe@example.com' diff --git a/src/connections/destinations/catalog/personyze/index.md b/src/connections/destinations/catalog/personyze/index.md index 6005210714..1240cf0bb3 100644 --- a/src/connections/destinations/catalog/personyze/index.md +++ b/src/connections/destinations/catalog/personyze/index.md @@ -21,7 +21,7 @@ This destination is maintained by Personyze. For any issues with the destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/pixelme/index.md b/src/connections/destinations/catalog/pixelme/index.md index 173242ddd6..b83a76fd9a 100644 --- a/src/connections/destinations/catalog/pixelme/index.md +++ b/src/connections/destinations/catalog/pixelme/index.md @@ -22,7 +22,7 @@ This destination is maintained by PixelMe. For any issues with the destination, ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -33,7 +33,7 @@ Unique page calls will be sent to PixelMe as a `Visitor`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -45,7 +45,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -58,7 +58,7 @@ analytics.identify('userId123', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('SignUp') diff --git a/src/connections/destinations/catalog/podsights/index.md b/src/connections/destinations/catalog/podsights/index.md index 5aab1cf84d..1edc20ca4f 100644 --- a/src/connections/destinations/catalog/podsights/index.md +++ b/src/connections/destinations/catalog/podsights/index.md @@ -25,7 +25,7 @@ Once you start sending data to the Podsights' Destination it will take up to 20 ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() @@ -33,7 +33,7 @@ analytics.page() Page calls will be sent to Podsights as a `view` event. -Podsights is an attribution platform, and as such, we need more context about the visitor than just a User ID. Analytics.js [automatically collects context fields](https://segment.com/docs/connections/spec/common/#context-fields-automatically-collected). Podsights requires certain context fields and properties for page calls. Below is an example of a raw JSON payload that contains the minimum requirements. +Podsights is an attribution platform, and as such, we need more context about the visitor than just a User ID. Analytics.js [automatically collects context fields](/docs/connections/spec/common/#context-fields-automatically-collected). Podsights requires certain context fields and properties for page calls. Below is an example of a raw JSON payload that contains the minimum requirements. ```js { @@ -58,7 +58,7 @@ The `context` and `properties` object are required, along with the fields in the ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Order Completed', { @@ -72,14 +72,14 @@ analytics.track('Order Completed', { Track calls will be mapped to Podsights events. Podsights' support the following from the Segment Spec: -* [Signed Up](https://segment.com/docs/connections/spec/b2b-saas/#signed-up) as `lead` -* [Product Viewed](https://segment.com/docs/connections/spec/ecommerce/v2/#product-viewed) as `product` -* [Product Added](https://segment.com/docs/connections/spec/ecommerce/v2/#product-added) as `addtocart` -* [Checkout Started](https://segment.com/docs/connections/spec/ecommerce/v2/#checkout-started) as `checkout` -* [Order Completed](https://segment.com/docs/connections/spec/ecommerce/v2/#order-completed) as `purchase` +* [Signed Up](/docs/connections/spec/b2b-saas/#signed-up) as `lead` +* [Product Viewed](/docs/connections/spec/ecommerce/v2/#product-viewed) as `product` +* [Product Added](/docs/connections/spec/ecommerce/v2/#product-added) as `addtocart` +* [Checkout Started](/docs/connections/spec/ecommerce/v2/#checkout-started) as `checkout` +* [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) as `purchase` For track events Podsights requires a `context` object that contains a `userAgent` and an `ip` Podsights also requires a `page` object that contains a `referrer` and a `url` field. -Analytics.js [automatically collects context fields](https://segment.com/docs/connections/spec/common/#context-fields-automatically-collected). Podsights requires certain context fields for track calls. Below is an example of a raw JSON payload that contains the minimum requirements. +Analytics.js [automatically collects context fields](/docs/connections/spec/common/#context-fields-automatically-collected). Podsights requires certain context fields for track calls. Below is an example of a raw JSON payload that contains the minimum requirements. ```js { diff --git a/src/connections/destinations/catalog/posthog/index.md b/src/connections/destinations/catalog/posthog/index.md index df4ff2f76e..d4552c54dc 100644 --- a/src/connections/destinations/catalog/posthog/index.md +++ b/src/connections/destinations/catalog/posthog/index.md @@ -21,7 +21,7 @@ This destination is maintained by PostHog. For any issues with the destination, ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -32,7 +32,7 @@ Segment sends Page calls to PostHog as a `$pageview`. ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```obj [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -43,7 +43,7 @@ Segment sends Screen calls to PostHog as a `$screen` event. ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -56,7 +56,7 @@ Segment sends Identify calls to PostHog as an `identify` event. Data from Identi ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -66,7 +66,7 @@ Segment sends Track calls to PostHog as a `track` event. ## Alias -If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](https://segment.com/docs/connections/spec/alias/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like: ```js analytics.alias('507f191e81') diff --git a/src/connections/destinations/catalog/productbird/index.md b/src/connections/destinations/catalog/productbird/index.md index 6ea23fd548..853a069495 100644 --- a/src/connections/destinations/catalog/productbird/index.md +++ b/src/connections/destinations/catalog/productbird/index.md @@ -18,7 +18,7 @@ This destination is maintained by ProductBird. For any issues with the destinati ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/profitwell/index.md b/src/connections/destinations/catalog/profitwell/index.md index bfbec5337f..cc63039437 100644 --- a/src/connections/destinations/catalog/profitwell/index.md +++ b/src/connections/destinations/catalog/profitwell/index.md @@ -22,7 +22,7 @@ You can find your public token in the [Retain control center](https://www2.profi ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/proof-experiences/index.md b/src/connections/destinations/catalog/proof-experiences/index.md index d6fbc172ed..161b3b9a9c 100644 --- a/src/connections/destinations/catalog/proof-experiences/index.md +++ b/src/connections/destinations/catalog/proof-experiences/index.md @@ -25,7 +25,7 @@ This destination is maintained by Proof. For any issues with the destination, [c ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -36,7 +36,7 @@ Page calls will be sent to Proof Experiences as a `pageview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -51,7 +51,7 @@ Identify calls will be sent to Proof Experiences as an `identify` call along wit ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button', { diff --git a/src/connections/destinations/catalog/qualaroo/index.md b/src/connections/destinations/catalog/qualaroo/index.md index 922d4eb203..24037af2b8 100644 --- a/src/connections/destinations/catalog/qualaroo/index.md +++ b/src/connections/destinations/catalog/qualaroo/index.md @@ -19,7 +19,7 @@ This document was last updated on September 5, 2018. If you notice any gaps, out ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('8888', { @@ -42,7 +42,7 @@ When you call `identify` we call `_kiq.push(['identify', userId]);` with the `us **Note:** The use of [a custom property to trigger a survey](https://help.qualaroo.com/hc/en-us/articles/201441516) made available by utilizing a Segment Track call is currently not supported due to some code changes. The below section will *not* trigger a survey at this time. -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track("Shadow Seen", { diff --git a/src/connections/destinations/catalog/quanticmind/index.md b/src/connections/destinations/catalog/quanticmind/index.md index 23fbe8c195..6240f0e5f0 100644 --- a/src/connections/destinations/catalog/quanticmind/index.md +++ b/src/connections/destinations/catalog/quanticmind/index.md @@ -18,7 +18,7 @@ This document was last updated on January 09, 2019. If you notice any gaps, outd ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page(); @@ -28,7 +28,7 @@ Page calls to Segment result in us pushing a "click" event to QuanticMind. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('12091906-01011992', { @@ -39,7 +39,7 @@ analytics.identify('12091906-01011992', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track("Button Clicked", { diff --git a/src/connections/destinations/catalog/quora-conversion-pixel/index.md b/src/connections/destinations/catalog/quora-conversion-pixel/index.md index 22bca4f837..c9d638e48b 100644 --- a/src/connections/destinations/catalog/quora-conversion-pixel/index.md +++ b/src/connections/destinations/catalog/quora-conversion-pixel/index.md @@ -26,7 +26,7 @@ This document was last updated on June 15th, 2018. If you notice any gaps, outda ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Completed Purchase', { diff --git a/src/connections/destinations/catalog/recombee-ai/index.md b/src/connections/destinations/catalog/recombee-ai/index.md index 8451947fa2..bf23add1bf 100644 --- a/src/connections/destinations/catalog/recombee-ai/index.md +++ b/src/connections/destinations/catalog/recombee-ai/index.md @@ -38,7 +38,7 @@ Once you send the data from Segment to the Recombee destination you can: ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -49,7 +49,7 @@ Segment sends Page calls to Recombee as a [Detail View](https://docs.recombee.co ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Video Content Playing', { @@ -62,28 +62,28 @@ analytics.track('Video Content Playing', { ``` #### Sending semantic spec events to Recombee -Recombee Destination can process several [Semantic Events](https://segment.com/docs/connections/spec/semantic/): +Recombee Destination can process several [Semantic Events](/docs/connections/spec/semantic/): -[Ecommerce](https://segment.com/docs/connections/spec/ecommerce/v2/): - - [Product Viewed](https://segment.com/docs/connections/spec/ecommerce/v2/#product-viewed) - sends a [Detail View](https://docs.recombee.com/api.html#add-detail-view) - - [Product Added](https://segment.com/docs/connections/spec/ecommerce/v2/#product-added) - sends a [Cart Addition](https://docs.recombee.com/api.html#add-cart-addition) - - [Product Removed](https://segment.com/docs/connections/spec/ecommerce/v2/#product-removed) - sends a [Delete Cart Addition](https://docs.recombee.com/api.html#delete-cart-addition) - - [Order Completed](https://segment.com/docs/connections/spec/ecommerce/v2/#order-completed) sends a [Purchase](https://docs.recombee.com/api.html#add-purchase) for each of the ordered products -- [Product Added to Wishlist](https://segment.com/docs/connections/spec/ecommerce/v2/#product-added) - sends a [Bookmark](https://docs.recombee.com/api.html#add-bookmark) -- [Product Shared](https://segment.com/docs/connections/spec/ecommerce/v2/#product-added) - sends a [Bookmark](https://docs.recombee.com/api.html#add-bookmark) +[Ecommerce](/docs/connections/spec/ecommerce/v2/): + - [Product Viewed](/docs/connections/spec/ecommerce/v2/#product-viewed) - sends a [Detail View](https://docs.recombee.com/api.html#add-detail-view) + - [Product Added](/docs/connections/spec/ecommerce/v2/#product-added) - sends a [Cart Addition](https://docs.recombee.com/api.html#add-cart-addition) + - [Product Removed](/docs/connections/spec/ecommerce/v2/#product-removed) - sends a [Delete Cart Addition](https://docs.recombee.com/api.html#delete-cart-addition) + - [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed) sends a [Purchase](https://docs.recombee.com/api.html#add-purchase) for each of the ordered products +- [Product Added to Wishlist](/docs/connections/spec/ecommerce/v2/#product-added) - sends a [Bookmark](https://docs.recombee.com/api.html#add-bookmark) +- [Product Shared](/docs/connections/spec/ecommerce/v2/#product-added) - sends a [Bookmark](https://docs.recombee.com/api.html#add-bookmark) -[Video](https://segment.com/docs/connections/spec/video/): +[Video](/docs/connections/spec/video/): - Following events send a [View Portion](https://docs.recombee.com/api.html#set-view-portion): - - [Video Playback Started](https://segment.com/docs/connections/spec/video/#video-playback-started) - - [Video Content Playing](https://segment.com/docs/connections/spec/video/#video-content-playing) - - [Video Playback Paused](https://segment.com/docs/connections/spec/video/#video-playback-paused) - - [Video Playback Completed](https://segment.com/docs/connections/spec/video/#video-playback-completed) + - [Video Playback Started](/docs/connections/spec/video/#video-playback-started) + - [Video Content Playing](/docs/connections/spec/video/#video-content-playing) + - [Video Playback Paused](/docs/connections/spec/video/#video-playback-paused) + - [Video Playback Completed](/docs/connections/spec/video/#video-playback-completed) If you want to send interactions from other events, set them to [Track Events Mapping](#track-events-mapping-optional) in Settings. ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```obj-c [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -94,7 +94,7 @@ Segment sends Screen calls to Recombee as a [Detail View](https://docs.recombee. ## Alias -If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](https://segment.com/docs/connections/spec/alias/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like: ```js analytics.alias("507f191e81"); @@ -113,7 +113,7 @@ You can tell Recombee that a specific interaction is based on a successful recom Recombee recognizes the `recomm_id` property in all the events that send interactions. -In case of [Order Completed](https://segment.com/docs/connections/spec/ecommerce/v2/#order-completed), set the `recomm_id` to the object of the product (`products.$.recomm_id`) that was ordered because of a successful recommendation. +In case of [Order Completed](/docs/connections/spec/ecommerce/v2/#order-completed), set the `recomm_id` to the object of the product (`products.$.recomm_id`) that was ordered because of a successful recommendation. Sending the `recomm_id` gives you precise numbers about successful recommendations in the KPI section of the [Recombee Admin UI](https://admin.recombee.com). This explicit feedback also helps you optimize your recommendation models. @@ -136,14 +136,14 @@ For each [Recombee interaction](https://docs.recombee.com/api.html#user-item-int You can set the **Item ID Property Name** to specify the Segment event property to use as the `itemId`. If you don't provide an **Item ID Property Name**: -- `product_id` is used for [Ecommerce Events](https://segment.com/docs/connections/spec/ecommerce/v2/). -- `content_asset_id` or `asset_id` is used for [Video Events](https://segment.com/docs/connections/spec/video/). +- `product_id` is used for [Ecommerce Events](/docs/connections/spec/ecommerce/v2/). +- `content_asset_id` or `asset_id` is used for [Video Events](/docs/connections/spec/video/). - `name` property is used if it exists. ### Track Events Mapping (Optional) -Recombee can automatically handle different [Ecommerce Events](https://segment.com/docs/connections/spec/ecommerce/v2/) and [Video Events](https://segment.com/docs/connections/spec/video/) in the *Track* call type (see the [Track section](#track)). +Recombee can automatically handle different [Ecommerce Events](/docs/connections/spec/ecommerce/v2/) and [Video Events](/docs/connections/spec/video/) in the *Track* call type (see the [Track section](#track)). If you use some custom Events, you can set which Recombee interaction to send for each one. @@ -156,7 +156,7 @@ The value of the mapping is the name of your event, and the key can be one of: - [Rating](https://docs.recombee.com/api.html#ratings) - a property `rating` must exist and contain a number from interval [-1.0,1.0], where -1.0 means the worst rating possible, 0.0 means neutral, and 1.0 means absolutely positive rating. - [View Portion](https://docs.recombee.com/api.html#set-view-portion) - - the portion (how much of the content was consumed by the user) is computed from the `position` and `total_length` properties (see [Content Event Object](https://segment.com/docs/connections/spec/video/#content-event-object)), or can be given as the `portion` property (a number between 0 and 1). + - the portion (how much of the content was consumed by the user) is computed from the `position` and `total_length` properties (see [Content Event Object](/docs/connections/spec/video/#content-event-object)), or can be given as the `portion` property (a number between 0 and 1). ### API URI (Optional) diff --git a/src/connections/destinations/catalog/refersion/index.md b/src/connections/destinations/catalog/refersion/index.md index 07e3a6fdf7..15d100537d 100644 --- a/src/connections/destinations/catalog/refersion/index.md +++ b/src/connections/destinations/catalog/refersion/index.md @@ -27,7 +27,7 @@ You have two options to connect - either automatically within your Refersion das ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` { diff --git a/src/connections/destinations/catalog/refiner/index.md b/src/connections/destinations/catalog/refiner/index.md index e7a24f45dd..bc94669306 100644 --- a/src/connections/destinations/catalog/refiner/index.md +++ b/src/connections/destinations/catalog/refiner/index.md @@ -19,7 +19,7 @@ This destination is maintained by Refiner. For any issues with the destination, ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() @@ -29,7 +29,7 @@ Segment sends page() calls to Refiner as a `pageview` event. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -41,7 +41,7 @@ Segment sends identify() calls to Refiner as an `identify` event. ## Group -If you haven’t had a chance to review our spec, take a look tounderstand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you haven’t had a chance to review our spec, take a look tounderstand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```js analytics.group("0e8c78ea9d97a7b8185e8632", { @@ -57,7 +57,7 @@ Group calls are the equivalent of providing an account object in a `identifyUser ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/responsys/index.md b/src/connections/destinations/catalog/responsys/index.md index d3898fe0dd..65e54b1c81 100644 --- a/src/connections/destinations/catalog/responsys/index.md +++ b/src/connections/destinations/catalog/responsys/index.md @@ -76,7 +76,7 @@ analytics.identify('rick', { ``` **IMPORTANT**: In order to merge records properly, our destination requires that all `.identify()` contain at least a `userId` or a `traits.email`! -The above call will try to first find an existing record in the provided Profile List with a matching `userId` of `'rick'` and or `email` of `'wubba-lubba-dub-dub@morty.com'`. If a record is found, we will update the rest of the columns so long as you pass the information using our [identify spec](https://segment.com/docs/connections/spec/identify). The below is how we map our spec'd Segment traits to Responsys' semantic Profile List columns: +The above call will try to first find an existing record in the provided Profile List with a matching `userId` of `'rick'` and or `email` of `'wubba-lubba-dub-dub@morty.com'`. If a record is found, we will update the rest of the columns so long as you pass the information using our [identify spec](/docs/connections/spec/identify). The below is how we map our spec'd Segment traits to Responsys' semantic Profile List columns:
diff --git a/src/connections/destinations/catalog/retently/index.md b/src/connections/destinations/catalog/retently/index.md index 40a5718d3c..6a2e024a8d 100644 --- a/src/connections/destinations/catalog/retently/index.md +++ b/src/connections/destinations/catalog/retently/index.md @@ -48,7 +48,7 @@ When a Segment Track event fires, Retently performs the following actions: The only property that Retently **requires** is `email`. All other properties can be assigned as optional customer properties in Retently. To learn how to manage customer properties using Segment track events [see the Retently documentation](https://help.retently.com/en/articles/4097690-set-up-segment-transactional-email-surveys). -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Subscription Activate Button Clicked', { diff --git a/src/connections/destinations/catalog/sailthru/index.md b/src/connections/destinations/catalog/sailthru/index.md index 0f7a9e0150..312f8eed40 100644 --- a/src/connections/destinations/catalog/sailthru/index.md +++ b/src/connections/destinations/catalog/sailthru/index.md @@ -39,7 +39,7 @@ analytics.page('Page Name', { }) ``` -See our [documentation](https://segment.com/docs/connections/spec/page/#properties) for more info on the `keywords` property. +See our [documentation](/docs/connections/spec/page/#properties) for more info on the `keywords` property. - - - diff --git a/src/connections/destinations/catalog/salescamp-crm/index.md b/src/connections/destinations/catalog/salescamp-crm/index.md index ae8e345464..e6e823fa47 100644 --- a/src/connections/destinations/catalog/salescamp-crm/index.md +++ b/src/connections/destinations/catalog/salescamp-crm/index.md @@ -26,7 +26,7 @@ The Salescamp destination makes it simple to integrate from Segment and send dat Let's go through a quick javascript example of identifying a customers -If you aren't familiar with the Segment Spec, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('YOUR_USERS_ID', { diff --git a/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md b/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md index 8449b370ee..5ffdf27d70 100644 --- a/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md +++ b/src/connections/destinations/catalog/salesforce-marketing-cloud/index.md @@ -88,7 +88,7 @@ If possible, you should enable batching for your SFMC destination before you sen ## Set up to send Identify calls to SFMC -To use the Journey Builder to send campaigns to your users, you need to have data about those users in SFMC. The most common way to send data to SFMC is to send Segment [Identify](https://segment.com/docs/connections/spec/identify/) calls to an SFMC Data Extension which you specify. When you call `identify`, Segment creates a Salesforce Marketing Cloud Contact, and upserts (updates) the user’s `traits` in the Data Extension. +To use the Journey Builder to send campaigns to your users, you need to have data about those users in SFMC. The most common way to send data to SFMC is to send Segment [Identify](/docs/connections/spec/identify/) calls to an SFMC Data Extension which you specify. When you call `identify`, Segment creates a Salesforce Marketing Cloud Contact, and upserts (updates) the user’s `traits` in the Data Extension. > note "" > **Note**: By default, `identify` events create or update contacts in SFMC. To prevent Identify calls from creating or updating a Contact when they update a Data Extension, enable the "Do Not Create or Update Contacts" option in the Destination Settings. @@ -237,7 +237,7 @@ You might use more than one primary key if, for example, you want to track if a ## Using context properties from Identify or Track calls -The Segment SDKs and libraries automatically collect many [context properties](https://segment.com/docs/connections/spec/common/#context), and you can pass these properties into SFMC as Data Extension attributes. +The Segment SDKs and libraries automatically collect many [context properties](/docs/connections/spec/common/#context), and you can pass these properties into SFMC as Data Extension attributes. To use context properties, you must create attributes in the Data Extensions that use specific naming conventions. The table below lists the Segment context properties available for SFMC, and the Data Extension attribute names they map to. @@ -287,7 +287,7 @@ Personas sends audience membership and computed trait values to SFMC using Ident When you sync to an existing Data Extension, note these additional requirements: - The table cannot have an existing **Primary Key**, unless it is the `Contact Key` field, and the field type is `Text`. - All fields in the Data Extension must be nullable (meaning optional, or not required), except the `Contact Key` field. -- Any fields that you send with Segment, and which already exist in the Data Extension, must be of the correct data type. The standard identifiers Segment sends come from the [Context object](https://segment.com/docs/connections/spec/common/#context), and appear in the image below. +- Any fields that you send with Segment, and which already exist in the Data Extension, must be of the correct data type. The standard identifiers Segment sends come from the [Context object](/docs/connections/spec/common/#context), and appear in the image below. ![](images/existing-dext-data-types.png) diff --git a/src/connections/destinations/catalog/savio/index.md b/src/connections/destinations/catalog/savio/index.md index 1827a40eb6..89f08c8fb8 100644 --- a/src/connections/destinations/catalog/savio/index.md +++ b/src/connections/destinations/catalog/savio/index.md @@ -17,7 +17,7 @@ This destination is maintained by Savio. For any issues with the destination, [c ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -36,7 +36,7 @@ Once created you will be able to associate the `Person` with feedback in the Sav ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ``` analytics.group("0e8c78ea9d97a7b8185e8632", { diff --git a/src/connections/destinations/catalog/screeb/index.md b/src/connections/destinations/catalog/screeb/index.md index 278f59d098..f09d4530ed 100644 --- a/src/connections/destinations/catalog/screeb/index.md +++ b/src/connections/destinations/catalog/screeb/index.md @@ -20,7 +20,7 @@ This destination is maintained by Screeb. For any issues with the destination, [ ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -35,7 +35,7 @@ The traits provided along with the identity can be listed on the [Screeb platfor ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -47,7 +47,7 @@ The provided events can be listed on the [Screeb platform](https://admin.screeb. ## Alias -If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](https://segment.com/docs/connections/spec/alias/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like: ```js analytics.alias('newUserId') diff --git a/src/connections/destinations/catalog/scuba-analytics/index.md b/src/connections/destinations/catalog/scuba-analytics/index.md index a7b88a3d8d..66f9161648 100644 --- a/src/connections/destinations/catalog/scuba-analytics/index.md +++ b/src/connections/destinations/catalog/scuba-analytics/index.md @@ -33,7 +33,7 @@ All methods will be tracked as a new event in Scuba Analytics with the associate ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -41,7 +41,7 @@ analytics.page() ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -49,7 +49,7 @@ If you're not familiar with the Segment Specs, take a look to understand what th ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. Identify methods can be used with Actors properties and Flow Properties in Scuba Analytics to update the associate with the user in the Identify method. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. Identify methods can be used with Actors properties and Flow Properties in Scuba Analytics to update the associate with the user in the Identify method. An example call would look like: ``` analytics.identify('userId123', { @@ -59,7 +59,7 @@ analytics.identify('userId123', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/segmetrics/index.md b/src/connections/destinations/catalog/segmetrics/index.md index 8bf101ef34..7ce5c376a2 100644 --- a/src/connections/destinations/catalog/segmetrics/index.md +++ b/src/connections/destinations/catalog/segmetrics/index.md @@ -21,7 +21,7 @@ This destination is maintained by SegMetrics. For any issues with the destinatio ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -31,7 +31,7 @@ Segment sends `page` calls to SegMetrics as `view` events, which are available i ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track("User Registered", { @@ -44,7 +44,7 @@ Segment sends `track` calls to SegMetrics as `view` events, which are available ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/sentry/index.md b/src/connections/destinations/catalog/sentry/index.md index a8da47320e..b90b1b705e 100644 --- a/src/connections/destinations/catalog/sentry/index.md +++ b/src/connections/destinations/catalog/sentry/index.md @@ -17,7 +17,7 @@ title: Sentry Destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123'); diff --git a/src/connections/destinations/catalog/serenytics/index.md b/src/connections/destinations/catalog/serenytics/index.md index 1e4c7efc40..33893efd21 100644 --- a/src/connections/destinations/catalog/serenytics/index.md +++ b/src/connections/destinations/catalog/serenytics/index.md @@ -31,7 +31,7 @@ From Segment Destinations Catalog: ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -42,7 +42,7 @@ To view your page calls in Serenytics, open the datasource called `Segment_Pages ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -52,7 +52,7 @@ To view your screen calls in Serenytics, open the datasource called `Segment_Scr ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -65,7 +65,7 @@ To view your identify calls in Serenytics, open the datasource called `Segment_I ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Article Completed') diff --git a/src/connections/destinations/catalog/signl4-alerting/index.md b/src/connections/destinations/catalog/signl4-alerting/index.md index 5db13d902d..d4404959c8 100644 --- a/src/connections/destinations/catalog/signl4-alerting/index.md +++ b/src/connections/destinations/catalog/signl4-alerting/index.md @@ -24,7 +24,7 @@ Ife you do not have SIGNL4 installed already, you can download the SIGNL4 App fr ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -35,7 +35,7 @@ Segment sends Page calls to SIGNL4 Alerting as a `pageview`, which can also be s ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```obj-c [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -46,7 +46,7 @@ Segment sends Screen calls to SIGNL4 Alerting as a `screenview`, which can also ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -59,7 +59,7 @@ Segment sends Identify calls to SIGNL4 Alerting as an `identify` event, which ca ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -69,7 +69,7 @@ Segment sends Track calls to SIGNL4 Alerting as a `track` event, which can also ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.group('0e8c78ea9d97a7b8185e8632', { @@ -85,7 +85,7 @@ Segment sends Group calls to SIGNL4 Alerting as a `group` event, which can also ## Alias -If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](https://segment.com/docs/connections/spec/alias/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like: ```js analytics.alias("507f191e81"); diff --git a/src/connections/destinations/catalog/singular/index.md b/src/connections/destinations/catalog/singular/index.md index 5ecaf59dd1..bab00866c9 100644 --- a/src/connections/destinations/catalog/singular/index.md +++ b/src/connections/destinations/catalog/singular/index.md @@ -27,7 +27,7 @@ This destination is maintained by Singular. For any issues with the destination, ## Install Attribution -Enable automatic tracking of lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) using initialization config parameters ([iOS](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#application-lifecycle-tracking), [Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/#step-2-initialize-the-client)) to track installs and sessions in Singular. The Singular "**session**" will be sent automatically by the integration as long as you are including the events above. +Enable automatic tracking of lifecycle events (`Application Opened`, `Application Installed`, `Application Updated`) using initialization config parameters ([iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#application-lifecycle-tracking), [Android](/docs/connections/sources/catalog/libraries/mobile/android/#step-2-initialize-the-client)) to track installs and sessions in Singular. The Singular "**session**" will be sent automatically by the integration as long as you are including the events above. ## Apple Search Ads Attribution @@ -82,7 +82,7 @@ Singular has explicitly mapped the `Application Installed` lifecycle event to pr ## Tracking Custom Events -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call (in Android) would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call (in Android) would look like: ```java Analytics.with(context).track("Signup") @@ -103,7 +103,7 @@ Analytics.with(context).track("Order Completed", new Properties().putRevenue(1.9 ``` ## Custom User ID -For the cloud-mode destination, Singular has mapped the **Custom User ID** to the Segment [User ID](https://segment.com/docs/connections/spec/identify/#user-id) value. Follow the steps here to configure for: [iOS](https://segment.com/docs/connections/sources/catalog/libraries/mobile/ios/#identify), [Android](https://segment.com/docs/connections/sources/catalog/libraries/mobile/android/#identify). +For the cloud-mode destination, Singular has mapped the **Custom User ID** to the Segment [User ID](/docs/connections/spec/identify/#user-id) value. Follow the steps here to configure for: [iOS](/docs/connections/sources/catalog/libraries/mobile/ios/#identify), [Android](/docs/connections/sources/catalog/libraries/mobile/android/#identify). For the device-based destination, Singular’s SDK uses the ​identify​ method to map Segment’s ​User ID​ value to the Custom User ID. diff --git a/src/connections/destinations/catalog/slack/index.md b/src/connections/destinations/catalog/slack/index.md index b1d841cbcf..2952e54208 100644 --- a/src/connections/destinations/catalog/slack/index.md +++ b/src/connections/destinations/catalog/slack/index.md @@ -17,7 +17,7 @@ This document was last updated on January 25, 2018. If you notice any gaps, out- 4. Enter this in your Segment UI settings under 'Incoming Webhook URL'. The Slack channel you selected will be the default channel which will receive events. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123', { @@ -30,7 +30,7 @@ analytics.identify('userId123', { By default, your `identify` calls will not be sent through to Slack unless you have whitelisted a `trait` and the `identify` call contains that `trait`. If you whitelist multiple `traits` in the Segment app's destintation settings under "Whitelisted Traits", then the `identify` call must contain all of them in order to be sent into your Slack. Following the code example above, we can whitelist the trait names of `name` and `email`. ### Identify Template -Once you've saved your whitelisted traits, you can now use them alongside [Handlebars expressions](http://handlebarsjs.com/expressions.html) syntax within a template. Make sure you reference the spec for the [Identify method](https://segment.com/docs/connections/spec/identify/) and [common object](https://segment.com/docs/connections/spec/common/). `Identify` events that contain the whitelisted `traits` will appear as a Slack message with the following default template: +Once you've saved your whitelisted traits, you can now use them alongside [Handlebars expressions](http://handlebarsjs.com/expressions.html) syntax within a template. Make sure you reference the spec for the [Identify method](/docs/connections/spec/identify/) and [common object](/docs/connections/spec/common/). `Identify` events that contain the whitelisted `traits` will appear as a Slack message with the following default template: ``` Identified user \{{name}}. \n\{{traits}} ``` @@ -58,7 +58,7 @@ The user John Doe has an email of john.doe@example.com ``` ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call using the analytics.js library would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call using the analytics.js library would look like: ```javascript analytics.track('Email Opened', { @@ -68,17 +68,17 @@ analytics.track('Email Opened', { ``` ### Event Channels -By default, all `track` events are sent to the default Slack channel configured in the Segment UI when [getting started](https://segment.com/docs/connections/destinations/catalog/slack/#getting-started). To prevent events from sending you will need to modify your track call to use [selective integrations](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#selecting-destinations-with-the-integrations-object). Business Tier customers also have the option to filter the events within the "Schema" section of the Segment UI. +By default, all `track` events are sent to the default Slack channel configured in the Segment UI when [getting started](/docs/connections/destinations/catalog/slack/#getting-started). To prevent events from sending you will need to modify your track call to use [selective integrations](/docs/connections/sources/catalog/libraries/website/javascript/#selecting-destinations-with-the-integrations-object). Business Tier customers also have the option to filter the events within the "Schema" section of the Segment UI. If you would like to have specific events be sent to a particular channel (#channel) or user (@user) using a direct message, you can specify this in the "Events Channels" settings within the Segment UI. ### Event Templates -Event templates also use [Handlebars expressions](http://handlebarsjs.com/expressions.html) syntax. Make sure you reference the spec for the [Track method](https://segment.com/docs/connections/spec/track/) and [common object](https://segment.com/docs/connections/spec/common/). `Track` events will trigger a Slack message with the following default template: +Event templates also use [Handlebars expressions](http://handlebarsjs.com/expressions.html) syntax. Make sure you reference the spec for the [Track method](/docs/connections/spec/track/) and [common object](/docs/connections/spec/common/). `Track` events will trigger a Slack message with the following default template: `'\{{name}} did \{{event}}.'` -where "event" is the event name and "name" is found with the same logic as that of the "name" in the [Identify template](https://segment.com/docs/connections/destinations/catalog/slack/#identify-template). +where "event" is the event name and "name" is found with the same logic as that of the "name" in the [Identify template](/docs/connections/destinations/catalog/slack/#identify-template). The basic Track structure: @@ -122,9 +122,9 @@ More information on regex can be found [here](http://www.zytrax.com/tech/web/reg ## Troubleshooting ### Page, Identify, Group calls are not showing up -The Slack Destination does not support `page` or `group` calls. Only `track` events are supported by default. Remember that [`track.properties` object](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#track) is an open dictionary and may include any data you choose. +The Slack Destination does not support `page` or `group` calls. Only `track` events are supported by default. Remember that [`track.properties` object](/docs/connections/sources/catalog/libraries/website/javascript/#track) is an open dictionary and may include any data you choose. -In order for `identify` events to work, make sure you [whitelist the traits](https://segment.com/docs/connections/destinations/catalog/slack/#whitelisted-traits). +In order for `identify` events to work, make sure you [whitelist the traits](/docs/connections/destinations/catalog/slack/#whitelisted-traits). ### I'm seeing [object Object] in my Slack message If you try to print an object (eg., `\{{properties}}`), you will see [object Object] in Slack. Drill down to a primitive type value (eg., `properties.plan`). diff --git a/src/connections/destinations/catalog/slicingdice/index.md b/src/connections/destinations/catalog/slicingdice/index.md index c79fb46d29..68efab4e3b 100644 --- a/src/connections/destinations/catalog/slicingdice/index.md +++ b/src/connections/destinations/catalog/slicingdice/index.md @@ -19,7 +19,7 @@ This destination is maintained by SlicingDice. For any issues with the destinati ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -46,7 +46,7 @@ Screen calls will be sent to SlicingDice using the following columns: ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -62,7 +62,7 @@ Identify calls will be sent to SlicingDice using the following columns: ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') @@ -78,7 +78,7 @@ Track calls will be sent to SlicingDice using the following columns: ## Groups -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ``` analytics.group("0e8c78ea9d97a7b8185e8632", { name: "Initech", @@ -95,7 +95,7 @@ Group calls will be sent to SlicingDice using the following columns: * `{source_name}-groups-{attribute_name}`: contains the `traits` attributes of a Group call, saving each one as an individual column * `{source_name}-groups-context-{attribute_name}`: contains the "context" attributes of a Group call, saving each one as an individual column - *Observation: Group calls will also be sent to SlicingDice using the following [Account](https://segment.com/docs/connections/storage/warehouses/schema/) columns that holds the latest state of a group.* + *Observation: Group calls will also be sent to SlicingDice using the following [Account](/docs/connections/storage/warehouses/schema/) columns that holds the latest state of a group.* * `{source_name}-accounts-group-id`: contains the `groupId` attribute of a Group call * `{source_name}-accounts-{attribute_name}`: contains the `traits` attributes of a Track call, saving each one as an individual column * `{source_name}-accounts-context-{attribute_name}`: contains the `context` attributes of a Track call, saving each one as an individual column diff --git a/src/connections/destinations/catalog/smartlook/index.md b/src/connections/destinations/catalog/smartlook/index.md index 88a74f611d..6e33154dfa 100644 --- a/src/connections/destinations/catalog/smartlook/index.md +++ b/src/connections/destinations/catalog/smartlook/index.md @@ -23,7 +23,7 @@ Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.j ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. Identify calls sent to Segment will be transformed and sent to [Smartlook's](https://smartlook.github.io/docs/web/identify-visitor/) `identify` method. An example call would look like: ``` @@ -35,7 +35,7 @@ analytics.identify('userId123', { ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. Track calls sent to Segment will be transformed and sent to [Smartlook's](https://smartlook.github.io/docs/web/custom-events/) `track` method. An example call would look like: diff --git a/src/connections/destinations/catalog/snapboard/index.md b/src/connections/destinations/catalog/snapboard/index.md index 29c409cc92..4d2b9ff332 100644 --- a/src/connections/destinations/catalog/snapboard/index.md +++ b/src/connections/destinations/catalog/snapboard/index.md @@ -35,7 +35,7 @@ And then select the [Workspace Name] that your would like to send your Segment e ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() @@ -46,7 +46,7 @@ Page calls are sent to Snapboard as a `pageview`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/screen/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/screen/) does. An example call would look like: ```objc [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -57,7 +57,7 @@ Screen calls are sent to Snapboard as a `screenview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -70,7 +70,7 @@ Identify calls are sent to Snapboard as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -81,7 +81,7 @@ Track calls are sent to Snapboard as a `track` event. ## Alias -If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](https://segment.com/docs/connections/spec/alias/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](/docs/connections/spec/alias/) does. An example call would look like: ```js analytics.alias("507f191e81"); diff --git a/src/connections/destinations/catalog/snapengage/index.md b/src/connections/destinations/catalog/snapengage/index.md index 265854e09d..549bc17f4b 100644 --- a/src/connections/destinations/catalog/snapengage/index.md +++ b/src/connections/destinations/catalog/snapengage/index.md @@ -13,7 +13,7 @@ This document was last updated on October 22, 2018. If you notice any gaps, outd 1. From the Segment web app, click **Catalog**. -2. Search for "SnapEngage" in the Catalog, select it, and choose which of your sources to connect the destination to. - keep in mind that our "SnapEngage" destination is only compatible with our client-side [analytics.js](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/) library. +2. Search for "SnapEngage" in the Catalog, select it, and choose which of your sources to connect the destination to. - keep in mind that our "SnapEngage" destination is only compatible with our client-side [analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/) library. 3. Add your SnapEngage `Widget ID` to your destination settings in Segment. You can find the `Widget ID` in your SnapEngage Javascript snippet. It will look something like this: 0c739ebb-2016-44a0-b1da-a5b5eb272474. Alternatively, the `Widget ID` can also be found under the _Advanced Widget ID_ section of the _Get the Code_ tab in the Admin Dashboard when logged in to SnapEngage. @@ -23,7 +23,7 @@ Remember to remove SnapEngages's snippet from your page. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('ze8rt1u89', { @@ -37,7 +37,7 @@ When sending an `Identify` call to SnapEngage be sure to include an `email` fiel ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. ### Record Live Chat Events diff --git a/src/connections/destinations/catalog/split/index.md b/src/connections/destinations/catalog/split/index.md index e85ea92f9b..fa7d0dbefc 100644 --- a/src/connections/destinations/catalog/split/index.md +++ b/src/connections/destinations/catalog/split/index.md @@ -5,9 +5,9 @@ title: Split Destination [Split](https://split.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners) powers your product decisions with a unified solution for feature flagging and experimentation. With Split, you can safely roll out new functionality using sophisticated user targeting, measure impact of change on engineering, product, and business metrics, and rapidly iterate to refine functionality anywhere in the application stack. -Split also maintains [integration specific documentation](https://docs.split.io/docs/segment#section-advanced-functionality) which include additional troubleshooting and frequently asked questions. +Split also maintains [integration specific documentation](https://help.split.io/hc/en-us/articles/360020742532-Segment) which include additional troubleshooting and frequently asked questions. -This destination is maintained by [Split](https://split.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners). For any issues with the destination, [contact the Split IO Support team](https://help.split.io). +This destination is maintained by [Split](https://split.io/?utm_source=segmentio&utm_medium=docs&utm_campaign=partners). For any issues with the destination, [contact the Split IO Support team](https://help.split.io/hc/en-us). {% include content/beta-note.md %} @@ -19,11 +19,11 @@ This destination is maintained by [Split](https://split.io/?utm_source=segmentio 2. Search for Split in the Catalog, select it, and choose which of your sources to connect the destination to. 3. Enter the "API Key" into your Segment Settings UI. -To find your key, log into Split and navigate to "Admin Settings" > "Integrations" > select your desired workspace > "Segment". There you can find the key for each configured integration. If you don't have an integration configured, be sure to configure your integration in the section "Configure as a destination in Segment" and click save to generate a key. For more information, learn more in Split's [integration documentation](https://docs.split.io/docs/segment). +To find your key, log into Split and navigate to "Admin Settings" > "Integrations" > select your desired workspace > "Segment". There you can find the key for each configured integration. If you don't have an integration configured, be sure to configure your integration in the section "Configure as a destination in Segment" and click save to generate a key. For more information, learn more in Split's [integration documentation](https://help.split.io/hc/en-us/articles/360020742532-Segment). ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page({ @@ -41,7 +41,7 @@ If you would not like Split to receive `page` calls, you can configure in your i ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.screen({ @@ -60,7 +60,7 @@ If you would not like Split to receive `screen` calls, you can configure in your ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify("userId1", { @@ -71,15 +71,15 @@ analytics.identify("userId1", { }); ``` -Identify calls will be sent to Split as an `identify` event. The `identify` event's userId (or anonymousId) will be mapped to the selected Split [traffic type](https://docs.split.io/docs/selecting-the-traffic-type). +Identify calls will be sent to Split as an `identify` event. The `identify` event's userId (or anonymousId) will be mapped to the selected Split [traffic type](https://help.split.io/hc/en-us/articles/360019916311-Traffic-type). -Any traits you provide will be displayed in Split as traffic type attributes. Learn more about attributes in Split's [documentation](https://docs.split.io/docs/identifying-customers). +Any traits you provide will be displayed in Split as traffic type attributes. Learn more about attributes in Split's [documentation](https://help.split.io/hc/en-us/articles/360020529772-Identifying-customers). If you would not like Split to receive `identify` calls, you can configure in your integration settings in Split. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track("Registered", { diff --git a/src/connections/destinations/catalog/stonly/index.md b/src/connections/destinations/catalog/stonly/index.md index 3d18a3112e..79620c882e 100644 --- a/src/connections/destinations/catalog/stonly/index.md +++ b/src/connections/destinations/catalog/stonly/index.md @@ -12,7 +12,7 @@ This destination is maintained by Stonly. For any issues with the destination, [ ## Getting Started -Before you start, make sure Stonly destination supports the source type and connection mode you’ve chosen to implement. You can learn more about [connection modes here](https://segment.com/docs/connections/destinations/#connection-modes). +Before you start, make sure Stonly destination supports the source type and connection mode you’ve chosen to implement. You can learn more about [connection modes here](/docs/connections/destinations/#connection-modes). {% include content/connection-modes.md %} @@ -25,7 +25,7 @@ Before you start, make sure Stonly destination supports the source type and conn ## Identify -If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like this [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you’re not familiar with the Segment Specs, take a look to understand what the Identify method does. An example call would look like this [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify("userId", { @@ -48,7 +48,7 @@ If one of your traits is of the date property type it should be sent as an ISO s ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track("TicketCreated", { diff --git a/src/connections/destinations/catalog/stormly/index.md b/src/connections/destinations/catalog/stormly/index.md index 3c35495578..f401ce208e 100644 --- a/src/connections/destinations/catalog/stormly/index.md +++ b/src/connections/destinations/catalog/stormly/index.md @@ -44,7 +44,7 @@ Stormly supports nested properties and traits, except for nested arrays. ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -55,7 +55,7 @@ Segment sends Page calls to Stormly as a `pageview`. ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```obj-c [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -66,7 +66,7 @@ Segment sends Screen calls to Stormly as a `screen`. ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -79,7 +79,7 @@ Segment sends Identify calls to Stormly as an `identify` event. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/survicate/index.md b/src/connections/destinations/catalog/survicate/index.md index e3be559f6c..b4b9009530 100644 --- a/src/connections/destinations/catalog/survicate/index.md +++ b/src/connections/destinations/catalog/survicate/index.md @@ -19,7 +19,7 @@ This destination is maintained by Survicate. For any issues with the destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -66,7 +66,7 @@ The above described call creates following respondent's traits in Survicate: ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ``` analytics.group('group123', { diff --git a/src/connections/destinations/catalog/talonone/index.md b/src/connections/destinations/catalog/talonone/index.md index 6aa2593602..27c33e27be 100644 --- a/src/connections/destinations/catalog/talonone/index.md +++ b/src/connections/destinations/catalog/talonone/index.md @@ -11,7 +11,7 @@ This destination is maintained by Talon.One. For any issues with the destination {% include content/beta-note.md %} > warning "" -> Data collection that affects promotions should be collected using a Segment **server-side** implementation. Client-side implementations exposes you to risks of fraud. (e.g. a user changing a custom trait relating to their profile using JS modification tools, which triggers them to receive a higher discount than they are entitled to) For more information [read this](https://segment.com/docs/guides/how-to-guides/collect-on-client-or-server/). +> Data collection that affects promotions should be collected using a Segment **server-side** implementation. Client-side implementations exposes you to risks of fraud. (e.g. a user changing a custom trait relating to their profile using JS modification tools, which triggers them to receive a higher discount than they are entitled to) For more information [read this](/docs/guides/how-to-guides/collect-on-client-or-server/). ## Getting Started @@ -25,7 +25,7 @@ This destination is maintained by Talon.One. For any issues with the destination ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { diff --git a/src/connections/destinations/catalog/tamber/index.md b/src/connections/destinations/catalog/tamber/index.md index a7c0f09ec2..739301a006 100644 --- a/src/connections/destinations/catalog/tamber/index.md +++ b/src/connections/destinations/catalog/tamber/index.md @@ -22,7 +22,7 @@ This destination is maintained by Tamber. For any issues with the destination, [ ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -39,7 +39,7 @@ Identify calls will be sent to Tamber as a [`user-update`](https://tamber.com/do ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call to Segment would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call to Segment would look like: ``` analytics.track("Watched", { @@ -61,4 +61,4 @@ analytics.track("Watched", { Track calls will be sent to Tamber as [`event-track`](https://tamber.com/docs/api/#event-track) calls and increment both Event and Item counts within the Tamber UI. You can also [retrieve](https://tamber.com/docs/api/#event-retrieve) events, and [retrieve](https://tamber.com/docs/api/#item-retrieve) or [list](https://tamber.com/docs/api/#item-list) items from Tamber. -**NOTE:** [`item`](https://tamber.com/docs/api/#item) is a required property but can be renamed within the Tamber UI under Custom Field Definition for Item. Make sure that the name passed into your Track call matches what you have set in the Tamber UI. If you are using Segment's [E-Commerce](https://segment.com/docs/connections/spec/ecommerce/v2) or [Video](https://segment.com/docs/connections/spec/video) APIs, you can configure Tamber to automatically handle item loading – either during set up or at any time in the Tamber Dashboard Sources > Segment section – and ignore this information. +**NOTE:** [`item`](https://tamber.com/docs/api/#item) is a required property but can be renamed within the Tamber UI under Custom Field Definition for Item. Make sure that the name passed into your Track call matches what you have set in the Tamber UI. If you are using Segment's [E-Commerce](/docs/connections/spec/ecommerce/v2) or [Video](/docs/connections/spec/video) APIs, you can configure Tamber to automatically handle item loading – either during set up or at any time in the Tamber Dashboard Sources > Segment section – and ignore this information. diff --git a/src/connections/destinations/catalog/trackier/index.md b/src/connections/destinations/catalog/trackier/index.md index 9b87357727..16f887d2c7 100644 --- a/src/connections/destinations/catalog/trackier/index.md +++ b/src/connections/destinations/catalog/trackier/index.md @@ -20,7 +20,7 @@ This destination is maintained by Trackier. For any issues with the destination, ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track("Item Sold", { diff --git a/src/connections/destinations/catalog/trafficguard/index.md b/src/connections/destinations/catalog/trafficguard/index.md index f5ddc97bdb..0084a60d34 100644 --- a/src/connections/destinations/catalog/trafficguard/index.md +++ b/src/connections/destinations/catalog/trafficguard/index.md @@ -26,7 +26,7 @@ NOTE: For TrafficGuard to successfully validate calls, `context.ip` and `context ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -37,7 +37,7 @@ Page calls will be sent to TrafficGuard as a `pageview` event. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -48,7 +48,7 @@ Screen calls will be sent to TrafficGuard as a `pageview` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/trustpilot/index.md b/src/connections/destinations/catalog/trustpilot/index.md index 34fb301859..e3dc2430c3 100644 --- a/src/connections/destinations/catalog/trustpilot/index.md +++ b/src/connections/destinations/catalog/trustpilot/index.md @@ -19,7 +19,7 @@ This destination is maintained by Trustpilot. For any issues with the destinatio ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Order Completed', { diff --git a/src/connections/destinations/catalog/tune/index.md b/src/connections/destinations/catalog/tune/index.md index 7aa80e5fff..7d5ef5d9d1 100644 --- a/src/connections/destinations/catalog/tune/index.md +++ b/src/connections/destinations/catalog/tune/index.md @@ -13,7 +13,7 @@ This destination is maintained by TUNE. Their code is publicly available for [iO 1. From your Segment UI's Destinations page click on "Add Destination". 2. Search for "TUNE" in the Catalog, select it, and choose which of your sources to connect the destination to. -3. Add your TUNE Advertiser ID in the Segment Settings UI from [your TUNE Dashboard](https://developers.tune.com/sdk/finding-your-advertiser-id-and-conversion-key/). +3. Add your TUNE Advertiser ID in the Segment Settings UI from the TUNE Dashboard]. 4. In your TUNE account, ensure that you have created a new app by navigating to Applications > Apps > Add A New App. 5. Depending on library you've installed, follow the additional steps below to finish setting up! @@ -57,7 +57,7 @@ AdvertisingIdClient.Info adInfo = AdvertisingIdClient.GetAdvertisingIdInfo(this. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify({ @@ -75,7 +75,7 @@ If your app has user accounts, you may want to identify these users when they lo ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track({ @@ -131,7 +131,7 @@ Install attribution is the most common use case for mobile attribution tools. To ### Special Events -TUNE supports special events beyond install attribution which are mapped to the Segment [Ecommerce Spec](https://segment.com/docs/connections/spec/ecommerce/v2/): +TUNE supports special events beyond install attribution which are mapped to the Segment [Ecommerce Spec](/docs/connections/spec/ecommerce/v2/): | Segment Event | TUNE Event | |---------------------------|--------------------| @@ -146,4 +146,4 @@ If you send an event with a name not included in the list above, Segment will se ## Postbacks -In addition to sending data to TUNE to be attributed, Segment allows you to route that data back into other tools that you have enabled. For example, you might want to use a particular analytics tool's dashboards to compare the different channels of your mobile ad campaign. To do this, enable postbacks in TUNE and provide them with your source write key, as explained in [TUNE's documentation](https://help.tune.com/marketing-console/segment-integration/). +In addition to sending data to TUNE to be attributed, Segment allows you to route that data back into other tools that you have enabled. For example, you might want to use a particular analytics tool's dashboards to compare the different channels of your mobile ad campaign. To do this, enable postbacks in TUNE and provide them with your source write key. diff --git a/src/connections/destinations/catalog/twitter-ads/index.md b/src/connections/destinations/catalog/twitter-ads/index.md index 8422145593..5a061b4161 100644 --- a/src/connections/destinations/catalog/twitter-ads/index.md +++ b/src/connections/destinations/catalog/twitter-ads/index.md @@ -61,7 +61,7 @@ Thus the example `.track()` event above would fire this tag: ### Advanced Conversion Tracking and Dynamic Ads -Our Twitter destination supports [Advanced Conversion Tracking](https://business.twitter.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites.html#advanced) which can be used to run **Dynamic Ads Campaigns**. Once you create your conversion events using **Universal Website Tag** inside Twitter's UI, just follow our [Ecommerce V2 Spec](https://segment.com/docs/connections/spec/ecommerce/v2) and we will automatically map select events (listed below). Keep in mind that you **must** provide the **Universal Website Pixel ID** in your settings for this feature to work. +Our Twitter destination supports [Advanced Conversion Tracking](https://business.twitter.com/en/help/campaign-measurement-and-analytics/conversion-tracking-for-websites.html#advanced) which can be used to run **Dynamic Ads Campaigns**. Once you create your conversion events using **Universal Website Tag** inside Twitter's UI, just follow our [Ecommerce V2 Spec](/docs/connections/spec/ecommerce/v2) and we will automatically map select events (listed below). Keep in mind that you **must** provide the **Universal Website Pixel ID** in your settings for this feature to work. *NOTE*: *For each of these Segment events, we will still check if you had mapped any of them to a* **Single Event Website Tag** *in your Segment settings and fire those tags in addition to these advanced conversion tags.* diff --git a/src/connections/destinations/catalog/unwaffle/index.md b/src/connections/destinations/catalog/unwaffle/index.md index 7c8c8da008..ec3413386c 100644 --- a/src/connections/destinations/catalog/unwaffle/index.md +++ b/src/connections/destinations/catalog/unwaffle/index.md @@ -21,7 +21,7 @@ This destination is maintained by Unwaffle. For any issues with the destination, ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('12345', { @@ -35,7 +35,7 @@ Identify calls will be sent to Unwaffle as an [`AddParticipant`](https://unwaffl ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('TrialStart') @@ -43,4 +43,4 @@ analytics.track('TrialStart') Track calls will be sent to Unwaffle as an [`AddAction`](https://unwaffle.com/api/docs/#addaction) event. -**IMPORTANT:** Unwaffle does not support anonymous activity. Ensure that you have [identified](https://segment.com/docs/connections/destinations/catalog/unwaffle/#identify) the user before calling Track. +**IMPORTANT:** Unwaffle does not support anonymous activity. Ensure that you have [identified](/docs/connections/destinations/catalog/unwaffle/#identify) the user before calling Track. diff --git a/src/connections/destinations/catalog/upcall/index.md b/src/connections/destinations/catalog/upcall/index.md index 92a6b917be..686578993e 100644 --- a/src/connections/destinations/catalog/upcall/index.md +++ b/src/connections/destinations/catalog/upcall/index.md @@ -21,7 +21,7 @@ This destination is maintained by Upcall. For any issues with the destination, [ ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call in [Node](https://segment.com/docs/connections/sources/catalog/libraries/server/node/) would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call in [Node](/docs/connections/sources/catalog/libraries/server/node/) would look like: ``` analytics.identify({ userId: 'userId12345', @@ -41,4 +41,4 @@ When you call Identify, you must include a phone number (in US or E.164 format) If they do not exist, the lead will be added to the campaign and immediately called (if the campaign is live). If they do exist in the campaign, no action will be taken. -The `campaign_id` parameter is optional and is added to the [integrations object](https://segment.com/docs/connections/sources/catalog/libraries/server/node/#selecting-destinations). If not provided, we will add the lead to the most recent campaign (in pending, live or paused state). It is recommended to specify it otherwise leads might get mixed up in multiple campaigns. +The `campaign_id` parameter is optional and is added to the [integrations object](/docs/connections/sources/catalog/libraries/server/node/#selecting-destinations). If not provided, we will add the lead to the most recent campaign (in pending, live or paused state). It is recommended to specify it otherwise leads might get mixed up in multiple campaigns. diff --git a/src/connections/destinations/catalog/useriq/index.md b/src/connections/destinations/catalog/useriq/index.md index e922587e21..644d3e2a85 100644 --- a/src/connections/destinations/catalog/useriq/index.md +++ b/src/connections/destinations/catalog/useriq/index.md @@ -19,7 +19,7 @@ This destination is maintained by UserIQ. For any issues with the destination, [ ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page("pageName") @@ -30,7 +30,7 @@ Page calls will be sent to UserIQ as a `pageview`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -41,7 +41,7 @@ Screen calls will be sent to UserIQ as a `screenview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -54,7 +54,7 @@ Identify calls will be sent to UserIQ as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/userleap/index.md b/src/connections/destinations/catalog/userleap/index.md index 782ab9d229..c18e1245dd 100644 --- a/src/connections/destinations/catalog/userleap/index.md +++ b/src/connections/destinations/catalog/userleap/index.md @@ -20,7 +20,7 @@ This destination is maintained by UserLeap. For any issues with the destination, **Note**: UserLeap's Segment integration does not support In-Product Surveys ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -34,7 +34,7 @@ Use Segment's Identify method to identify your users in UserLeap. Segment `trait **Important:** Only Identify calls can create new users in UserLeap. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Button Clicked'); @@ -45,7 +45,7 @@ Use Track calls to track events and use them as filtering criteria for your Surv Create Triggered Events in your UserLeap [Events dashboard](https://app.userleap.com/events) and map them to your Segment Track event names before you start sending Segment data to UserLeap. ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -56,7 +56,7 @@ Segment sends Page calls to UserLeap as a `pageview` which you can use as filter Add Page URLs in your UserLeap [Events dashboard](https://app.userleap.com/events) and map them to your Segment Page call's `properties.url` field before you start sending Segment data to UserLeap. ## Alias -If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](https://segment.com/docs/connections/spec/alias/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like: ```js analytics.alias('newUserId'); diff --git a/src/connections/destinations/catalog/userlike/index.md b/src/connections/destinations/catalog/userlike/index.md index 9baef05545..9bf45558af 100644 --- a/src/connections/destinations/catalog/userlike/index.md +++ b/src/connections/destinations/catalog/userlike/index.md @@ -19,7 +19,7 @@ This document was last updated on October 22, 2018. If you notice any gaps, outd Once you enable the destination from the Segment web app, your changes appear in the Segment CDN in about 45 minutes, and then Analytics.js starts asynchronously loading Userlike's javascript onto your page. Remember to remove Userlike's snippet from your page. ## Track - If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. + If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. ### Record Live Chat Events diff --git a/src/connections/destinations/catalog/userlist/index.md b/src/connections/destinations/catalog/userlist/index.md index 4b9898f3fe..329c218118 100644 --- a/src/connections/destinations/catalog/userlist/index.md +++ b/src/connections/destinations/catalog/userlist/index.md @@ -22,7 +22,7 @@ This destination is maintained by Userlist. For any issues with the destination, ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123', { @@ -46,7 +46,7 @@ Here's how Segment fields map to Userlist users: ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track('Project created', { @@ -74,7 +74,7 @@ analytics.track( ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```javascript analytics.group('companyId123', { diff --git a/src/connections/destinations/catalog/userpilot/index.md b/src/connections/destinations/catalog/userpilot/index.md index ef959110e3..6993831563 100644 --- a/src/connections/destinations/catalog/userpilot/index.md +++ b/src/connections/destinations/catalog/userpilot/index.md @@ -18,7 +18,7 @@ This destination is maintained by Userpilot. For any issues with the destination 3. Enter the "App Token" into your Segment Settings UI which you can find from your [Userpilot dashboard](https://app.userpilot.io/settings/setup) within the code snippet that looks like this `` where `73fe57o8` is the value you want to use. ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() @@ -28,7 +28,7 @@ Calling the `page` from `analytics.js` triggers the `userpilot.reload` method th ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('userId123', { @@ -46,7 +46,7 @@ Data passed in the `identify` can be organized under different categories. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/uservoice/index.md b/src/connections/destinations/catalog/uservoice/index.md index 4274c0dc90..a3f5cf94a8 100644 --- a/src/connections/destinations/catalog/uservoice/index.md +++ b/src/connections/destinations/catalog/uservoice/index.md @@ -23,7 +23,7 @@ Remember to remove UserVoice's native snippet from your page. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('ze8rt1u89', { @@ -43,7 +43,7 @@ When you call `identify` the `userId` and `traits` included in the call will be ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ``` analytics.group("0e8c78ea9d97a7b8185e8632", { @@ -59,7 +59,7 @@ When you call `group` the `traits` included in the call will be set to the curre ## Alias -If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](https://segment.com/docs/connections/spec/alias/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Alias method](/docs/connections/spec/alias/) does. An example call would look like: ``` analytics.alias("507f191e81"); diff --git a/src/connections/destinations/catalog/variance/index.md b/src/connections/destinations/catalog/variance/index.md index 1d49485997..a5ef7116b3 100644 --- a/src/connections/destinations/catalog/variance/index.md +++ b/src/connections/destinations/catalog/variance/index.md @@ -26,7 +26,7 @@ Variance supports the following methods of the [Segment Spec](/docs/connections/ ### Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -37,7 +37,7 @@ Segment sends Page calls to Variance as a `Page` Event Type. ### Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```obj-c [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -48,7 +48,7 @@ Segment sends Screen calls to Variance as a `Screen` Event Type. ### Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -61,7 +61,7 @@ Segment sends Identify calls to Variance as a `Contact`. ### Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/vero/index.md b/src/connections/destinations/catalog/vero/index.md index 5dbef55a16..bcad5c4553 100644 --- a/src/connections/destinations/catalog/vero/index.md +++ b/src/connections/destinations/catalog/vero/index.md @@ -82,7 +82,7 @@ analytics.alias('example@example.com', '8765309') ### Tags -The destination is capable of both adding and removing tags in Vero for a given user. Because `tags` is not a common property of events, this functionality is invoked using an [destination specific option](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#selecting-destinations-with-the-integrations-object). +The destination is capable of both adding and removing tags in Vero for a given user. Because `tags` is not a common property of events, this functionality is invoked using an [destination specific option](/docs/connections/sources/catalog/libraries/website/javascript/#selecting-destinations-with-the-integrations-object). To start using this feature, pass an object called `tags` with the following properties: diff --git a/src/connections/destinations/catalog/vespucci/index.md b/src/connections/destinations/catalog/vespucci/index.md index be9baeef14..8902156d97 100644 --- a/src/connections/destinations/catalog/vespucci/index.md +++ b/src/connections/destinations/catalog/vespucci/index.md @@ -22,7 +22,7 @@ This destination is maintained by Vespucci. For any issues with the destination, ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -31,7 +31,7 @@ analytics.page() Segment sends Page calls to Vespucci as a `screen`. ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```objc [[SEGAnalytics sharedAnalytics] screen:@"Home"]; ``` @@ -40,7 +40,7 @@ Segment sends Screen calls to Vespucci as a `screen`. ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify('userId123', { @@ -53,7 +53,7 @@ Segment sends Identify calls to Vespucci as an `identify` event. ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') diff --git a/src/connections/destinations/catalog/vidora/index.md b/src/connections/destinations/catalog/vidora/index.md index 1429d223ad..ec0a280135 100644 --- a/src/connections/destinations/catalog/vidora/index.md +++ b/src/connections/destinations/catalog/vidora/index.md @@ -19,7 +19,7 @@ This destination is maintained by Vidora. For any issues with the destination, [ ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track("event_name", { @@ -33,7 +33,7 @@ Segment sends Track calls to Vidora as a `track` event with the `event_name` as ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page({ @@ -50,7 +50,7 @@ Segment sends Page calls to Vidora as a `pageview` event along with the `page na ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```obj-c [[SEGAnalytics sharedAnalytics] screen:@"screen_name" @@ -64,7 +64,7 @@ Segment sends Screen calls to Vidora as a `screenview` event along with the `scr ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify("userId123", { @@ -78,7 +78,7 @@ Segment sends Identify calls to Vidora as an `identify` event along with any cor ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.group("groupId", { diff --git a/src/connections/destinations/catalog/vitally/index.md b/src/connections/destinations/catalog/vitally/index.md index b0d21f46a1..b8e20986a4 100644 --- a/src/connections/destinations/catalog/vitally/index.md +++ b/src/connections/destinations/catalog/vitally/index.md @@ -53,7 +53,7 @@ Passing along the following traits will correspond to what is displayed in Vital ## Track -If you haven't had a chance to review the spec, take a look tounderstand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you haven't had a chance to review the spec, take a look tounderstand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('enabled-slack-integration', { @@ -66,7 +66,7 @@ Track calls are used in Vitally to [track and analyze](http://docs.vitally.io/en ## Group -If you haven't had a chance to review the spec, take a look tounderstand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you haven't had a chance to review the spec, take a look tounderstand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```js analytics.group("accountId123", { diff --git a/src/connections/destinations/catalog/voucherify/index.md b/src/connections/destinations/catalog/voucherify/index.md index 6fcbfe9694..c8d5a780b5 100644 --- a/src/connections/destinations/catalog/voucherify/index.md +++ b/src/connections/destinations/catalog/voucherify/index.md @@ -27,7 +27,7 @@ On the Voucherify Dashboard page: ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify('cust_9032_re_3234', { @@ -61,7 +61,7 @@ With setting _Identify Mapping_ you can customize the conversion from the event ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Registration Completed', { diff --git a/src/connections/destinations/catalog/walkme/index.md b/src/connections/destinations/catalog/walkme/index.md index fb9ff3ac99..65cc44269b 100644 --- a/src/connections/destinations/catalog/walkme/index.md +++ b/src/connections/destinations/catalog/walkme/index.md @@ -21,7 +21,7 @@ This destination is maintained by WalkMe. For any issues with the destination, [ ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -32,7 +32,7 @@ Page calls will be sent to WalkMe as a `pageview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -45,7 +45,7 @@ Identify calls will be sent to WalkMe as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/watchtower/index.md b/src/connections/destinations/catalog/watchtower/index.md index 6e40e13ac8..e83054d2da 100644 --- a/src/connections/destinations/catalog/watchtower/index.md +++ b/src/connections/destinations/catalog/watchtower/index.md @@ -21,7 +21,7 @@ This destination is maintained by Watchtower. For any issues with the destinatio ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ``` analytics.page() @@ -32,7 +32,7 @@ Page calls will be sent to Watchtower as a `pageview`. ## Screen -If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Screen method](/docs/connections/spec/page/) does. An example call would look like: ``` [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -43,7 +43,7 @@ Screen calls will be sent to Watchtower as a `screenview`. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -56,7 +56,7 @@ Identify calls will be sent to Watchtower as an `identify` event. ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Clicked Login Button') diff --git a/src/connections/destinations/catalog/whale-alerts/index.md b/src/connections/destinations/catalog/whale-alerts/index.md index 99be1cf303..835a23a174 100644 --- a/src/connections/destinations/catalog/whale-alerts/index.md +++ b/src/connections/destinations/catalog/whale-alerts/index.md @@ -20,7 +20,7 @@ Whalr puts you back in control. You can see who is using your system, you know If you haven't already, you'll need to sign up at whalr.com. You'll receive your Whalr member ID and password to log in to the Whalr member console where you will find key information that you will need to turn on the Whalr destination. -After you have deployed Segment's [analytics.js](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/quickstart/) script to your web site, Segment will begin sending PAGE events to Whalr. However, at this stage there is no information on users or potential leads and sales targets being sent to Whalr, so intelligence is not yet actionable. +After you have deployed Segment's [analytics.js](/docs/connections/sources/catalog/libraries/website/javascript/quickstart/) script to your web site, Segment will begin sending PAGE events to Whalr. However, at this stage there is no information on users or potential leads and sales targets being sent to Whalr, so intelligence is not yet actionable. This is an introduction to how Segment and Whalr work together and how to get Whalr to produce actionable intelligence. diff --git a/src/connections/destinations/catalog/wigzo/index.md b/src/connections/destinations/catalog/wigzo/index.md index c3eb87e98c..04c3fc70dc 100644 --- a/src/connections/destinations/catalog/wigzo/index.md +++ b/src/connections/destinations/catalog/wigzo/index.md @@ -10,7 +10,7 @@ This destination is maintained by Wigzo. For any issues with the destination, [c ## Getting Started -The first step is to make sure Wigzo supports the source type and connection mode you've chosen to implement. You can learn more about what dictates the connection modes we support [here](https://segment.com/docs/connections/destinations/#connection-modes). +The first step is to make sure Wigzo supports the source type and connection mode you've chosen to implement. You can learn more about what dictates the connection modes we support [here](/docs/connections/destinations/#connection-modes). 1. From the Segment web app, click **Catalog**. 2. Search for "Wigzo" in the Catalog, select it, and choose which of your sources to connect the destination to. @@ -19,7 +19,7 @@ The first step is to make sure Wigzo supports the source type and connection mod ## Page -If you're not familiar with the Segment Specs, take a look to understand what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```javascript analytics.page(); @@ -29,7 +29,7 @@ When you call `.page()` in the browser, we will pass all the properties of the p ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123', { @@ -41,7 +41,7 @@ When you call `.identify()`, user's data will be sent to Wigzo's server along wi ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```javascript analytics.track('Clicked Button'); diff --git a/src/connections/destinations/catalog/windsor/index.md b/src/connections/destinations/catalog/windsor/index.md index 1e4ff58d85..6d7b3b068e 100644 --- a/src/connections/destinations/catalog/windsor/index.md +++ b/src/connections/destinations/catalog/windsor/index.md @@ -28,7 +28,7 @@ You can find more information on Windsor on [the Windsor docs site](https://docs ## Page -If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](https://segment.com/docs/connections/spec/page/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Page method documentation](/docs/connections/spec/page/) to learn about what it does. An example call would look like: ```js analytics.page() @@ -39,7 +39,7 @@ Segment sends Page calls as tracked events for each [user](https://app.windsor.i ## Screen -If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](https://segment.com/docs/connections/spec/screen/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Screen method documentation](/docs/connections/spec/screen/) to learn about what it does. An example call would look like: ```objc [[SEGAnalytics sharedAnalytics] screen:@"Home"]; @@ -50,7 +50,7 @@ Segment sends Screen calls to Windsor to the tracked events for each [user](http ## Identify -If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](https://segment.com/docs/connections/spec/identify/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Identify method documentation](/docs/connections/spec/identify/) to learn about what it does. An example call would look like: ```js analytics.identify("user-123", { @@ -79,7 +79,7 @@ You can find [additional best practices on using Identify with Windsor here](htt ## Track -If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](https://segment.com/docs/connections/spec/track/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Track method documentation](/docs/connections/spec/track/) to learn about what it does. An example call would look like: ```js analytics.track('Login Button Clicked') @@ -89,14 +89,14 @@ Segment sends Track calls to Windsor as tracked events for each [user](https://a To get the best experience with Windsor, we recommend that you follow the Segment's specs for your industry or application . -- [Mobile App](https://segment.com/docs/connections/spec/mobile/) -- [E-Commerce](https://segment.com/docs/connections/spec/ecommerce/v2/) -- [B2B SaaS](https://segment.com/docs/connections/spec/b2b-saas/) -- [Video](https://segment.com/docs/connections/spec/video/) +- [Mobile App](/docs/connections/spec/mobile/) +- [E-Commerce](/docs/connections/spec/ecommerce/v2/) +- [B2B SaaS](/docs/connections/spec/b2b-saas/) +- [Video](/docs/connections/spec/video/) ## Group -If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](https://segment.com/docs/connections/spec/group/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Group method documentation](/docs/connections/spec/group/) to learn about what it does. An example call would look like: ```js analytics.group("group-id"); @@ -106,7 +106,7 @@ You can use group calls to attach an internal property to users who belonging to ## Alias -If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](https://segment.com/docs/connections/spec/alias/) to learn about what it does. An example call would look like: +If you aren't familiar with the Segment Spec, take a look at the [Alias method documentation](/docs/connections/spec/alias/) to learn about what it does. An example call would look like: ```js analytics.alias("new-user-id"); @@ -114,4 +114,4 @@ analytics.alias("new-user-id"); Segment sends Alias calls to Windsor to help correctly match users behind the scenes. It merges any user previously identified using the old `userID` with a user identified with the new `userID`. If a user does not exist with the new `userID`, Windsor will create a new user with the newly entered `userID` -This is an advanced method and will irreversibly merge users on Windsor (and possibly other destinations too). Make sure to [read the Segment docs](https://segment.com/docs/connections/spec/alias/) when implementing Alias. +This is an advanced method and will irreversibly merge users on Windsor (and possibly other destinations too). Make sure to [read the Segment docs](/docs/connections/spec/alias/) when implementing Alias. diff --git a/src/connections/destinations/catalog/wootric-by-inmoment/index.md b/src/connections/destinations/catalog/wootric-by-inmoment/index.md index 79425c7a02..57f615156d 100644 --- a/src/connections/destinations/catalog/wootric-by-inmoment/index.md +++ b/src/connections/destinations/catalog/wootric-by-inmoment/index.md @@ -30,12 +30,12 @@ Mobile implementations require additional settings. Navigate to your **InMoment Settings > API** to add your **Client ID** to the respective part of the Segment Settings UI. -**IMPORTANT:** The incoming responses and surveys will not be tied to a user until you [identify](https://segment.com/docs/connections/destinations/catalog/wootric-by-inmoment/#identify) your user. +**IMPORTANT:** The incoming responses and surveys will not be tied to a user until you [identify](/docs/connections/destinations/catalog/wootric-by-inmoment/#identify) your user. ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('userId123', { @@ -62,7 +62,7 @@ When you call Track, the user’s information is passed along with the event nam ## Page -If you aren't familiar with the Segment Spec, you should first read about what the [Page method](https://segment.com/docs/connections/spec/page/) does. An example call would look like: +If you aren't familiar with the Segment Spec, you should first read about what the [Page method](/docs/connections/spec/page/) does. An example call would look like: ```js analytics.page() diff --git a/src/connections/destinations/catalog/xtremepush/index.md b/src/connections/destinations/catalog/xtremepush/index.md index 4807c3fa1f..65dbc960a2 100644 --- a/src/connections/destinations/catalog/xtremepush/index.md +++ b/src/connections/destinations/catalog/xtremepush/index.md @@ -20,7 +20,7 @@ This destination is maintained by Xtremepush. For any issues with the destinatio ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ``` analytics.identify('userId123', { @@ -45,7 +45,7 @@ If a trait does not match a custom Xtremepush User Profile Attribute and is not ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ``` analytics.track('Product Purchased', { diff --git a/src/connections/destinations/catalog/youbora/index.md b/src/connections/destinations/catalog/youbora/index.md index 3be5064b6d..1bfe8e3313 100644 --- a/src/connections/destinations/catalog/youbora/index.md +++ b/src/connections/destinations/catalog/youbora/index.md @@ -152,7 +152,7 @@ When playback of a video is interrupted, use the [Video Playback Interrupted](/d ### Video Playback Completed To track the completion of the video playback session, use our [Video -Playback Completed](https://segment.com/docs/connections/spec/video/#playback-events) event. +Playback Completed](/docs/connections/spec/video/#playback-events) event. **Example** @@ -187,7 +187,7 @@ analytics.track('Video Ad Started', { session_id: 1, title: 'Test Ad Title', ad_ ### Video Ad Completed To track the completion of an ad, use our [Video Ad -Completed](https://segment.com/docs/connections/spec/video/#ad-events) event. +Completed](/docs/connections/spec/video/#ad-events) event. **Example** diff --git a/src/connections/destinations/catalog/zendesk/index.md b/src/connections/destinations/catalog/zendesk/index.md index 1f57b36012..b9782f43c6 100644 --- a/src/connections/destinations/catalog/zendesk/index.md +++ b/src/connections/destinations/catalog/zendesk/index.md @@ -22,7 +22,7 @@ This document was last updated on April 30, 2018. If you notice any gaps, outdat ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```js analytics.identify("97980cfea0067", { @@ -115,7 +115,7 @@ You may map to custom user fields within Zendesk by passing your custom field ke ## Track -If you're not familiar with the Segment Specs, take a look to understand what the [Track method](https://segment.com/docs/connections/spec/track/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Track method](/docs/connections/spec/track/) does. An example call would look like: ```js analytics.track('Article Completed', { @@ -148,7 +148,7 @@ analytics.track('Article Completed', { ## Group -If you're not familiar with the Segment Specs, take a look to understand what the [Group method](https://segment.com/docs/connections/spec/group/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Group method](/docs/connections/spec/group/) does. An example call would look like: ```js analytics.group("0e8c78ea9d97a7b8185e8632", { diff --git a/src/connections/destinations/catalog/zopim/index.md b/src/connections/destinations/catalog/zopim/index.md index a32f9b0936..029b9ad188 100644 --- a/src/connections/destinations/catalog/zopim/index.md +++ b/src/connections/destinations/catalog/zopim/index.md @@ -42,7 +42,7 @@ Your changes appear in the Segment CDN in about 45 minutes, and then Analytics.j ## Identify -If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](https://segment.com/docs/connections/spec/identify/) does. An example call would look like: +If you're not familiar with the Segment Specs, take a look to understand what the [Identify method](/docs/connections/spec/identify/) does. An example call would look like: ```javascript analytics.identify('ze8rt1u89', { diff --git a/src/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md b/src/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md index e5ed7a3f00..e3c5aab7b0 100644 --- a/src/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md +++ b/src/connections/sources/catalog/cloud-apps/amplitude-cohorts/index.md @@ -19,7 +19,7 @@ Segment `identify` events. 4. From the new Source's Overview page, copy the Segment `writeKey`. 5. To export users from Amplitude to Segment, first, in Amplitude, create the cohort of users you wish to export. You can read more about the different - types of cohorts you can create in [Amplitude's documentation](https://amplitude.zendesk.com/hc/en-us/articles/231881448-Behavioral-Cohorts). + types of cohorts you can create in [Amplitude's documentation](https://help.amplitude.com/hc/en-us/articles/231881448-Behavioral-Cohorts). 6. In your Amplitude account, navigate to your Behavioral Cohort and paste the Segment `writeKey` under "Sync to" -> "Add Integration" if the Segment integration is not already set up for your project. **NOTE:** If you diff --git a/src/connections/sources/catalog/cloud-apps/zendesk/index.md b/src/connections/sources/catalog/cloud-apps/zendesk/index.md index a17f3ca4e1..e9e8e484d2 100644 --- a/src/connections/sources/catalog/cloud-apps/zendesk/index.md +++ b/src/connections/sources/catalog/cloud-apps/zendesk/index.md @@ -28,7 +28,7 @@ If you notice any gaps, outdated information or simply want to leave some feedba ### Rate Limits -The Zendesk source uses both Zendesk's [Core API](https://developer.zendesk.com/rest_api/docs/core/introduction) and [Incremental Exports API](https://developer.zendesk.com/rest_api/docs/core/incremental_export). The source's requests to the Incremental API do not count towards your Zendesk account's rate limits, but requests to the Core API do. By default, we cap our requests to Zendesk's Core API to a rate of 200 requests per minute to avoid triggering [Zendesk's Rate Limits](https://developer.zendesk.com/rest_api/docs/core/introduction#rate-limits). If you'd like us to increase or decrease the request rate for your source, [let us know](https://segment.com/help/contact/), and we'll get it set up. We'll add support for this in the UI soon! +The Zendesk source uses both Zendesk's [Core API](https://developer.zendesk.com/api-reference/) and [Incremental Exports API](https://developer.zendesk.com/rest_api/docs/core/incremental_export). The source's requests to the Incremental API do not count towards your Zendesk account's rate limits, but requests to the Core API do. By default, we cap our requests to Zendesk's Core API to a rate of 200 requests per minute to avoid triggering [Zendesk's Rate Limits](https://developer.zendesk.com/api-reference/ticketing/account-configuration/usage_limits/). If you'd like us to increase or decrease the request rate for your source, [let us know](https://segment.com/help/contact/), and we'll get it set up. We'll add support for this in the UI soon! ## Components diff --git a/src/connections/sources/catalog/libraries/server/net/index.md b/src/connections/sources/catalog/libraries/server/net/index.md index f14517849e..baa69fe2c7 100644 --- a/src/connections/sources/catalog/libraries/server/net/index.md +++ b/src/connections/sources/catalog/libraries/server/net/index.md @@ -41,7 +41,7 @@ Your website will use our .NET library to `identify` and `track` users. You can Install-Package Analytics -Version ``` -**Note:** the Analytics package has a dependency on [Newton.JSON](http://json.codeplex.com/). +**Note:** the Analytics package has a dependency on [Newton.JSON](https://www.newtonsoft.com/json). You can also accomplish the same thing in the Visual Studio `Tools` menu, select `Library Package Manager` and then click `Package Manager Console`. diff --git a/src/connections/sources/catalog/libraries/server/php/index.md b/src/connections/sources/catalog/libraries/server/php/index.md index 9ec7a0494f..b7a09ebf17 100644 --- a/src/connections/sources/catalog/libraries/server/php/index.md +++ b/src/connections/sources/catalog/libraries/server/php/index.md @@ -517,6 +517,6 @@ $ sudo service cron reload # reload the cron daemon ## 3rd-Party Libraries -If you only need support for PHP5, the team at [Underground Elephant](http://undergroundelephant.com/) has released a [3rd-party library](https://github.com/uecode/segment-io-php) based on Guzzle. +If you only need support for PHP5, the team at Underground Elephant has released a [3rd-party library](https://github.com/uecode/segment-io-php) based on Guzzle. If you're using Laravel 4 our friends at Catchet have written a wrapper for you! Docs and GitHub repo can be found here: https://github.com/cachethq/Laravel-Segment diff --git a/src/connections/storage/catalog/postgres/index.md b/src/connections/storage/catalog/postgres/index.md index a8988f0ffc..acbe558a2b 100644 --- a/src/connections/storage/catalog/postgres/index.md +++ b/src/connections/storage/catalog/postgres/index.md @@ -31,7 +31,7 @@ This guide explains how to set up a Postgres database with Heroku. Heroku is a c 3. Create a new app and go to the Data page. - To get to the Data page, either [click here](https://postgres.heroku.com/databases) or in the Dashboard menu dropdown, select Data. + To get to the Data page, in the Dashboard menu dropdown, select Data. ![](images/heroku1.png)