You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/algolia-insights/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -22,7 +22,7 @@ This destination is maintained by [Algolia](https://www.algolia.com/). For any i
22
22
23
23
1. From the Segment web app, click **Catalog**.
24
24
2. Search for "Algolia" in the Catalog, select it, and choose which of your sources to connect the destination to.
25
-
3. Enter the "App ID" & "API Key" into your Segment Settings UI which you can find from your [Algolia Dashboard](https://www.algolia.com/apps/), under API Keys menu.
25
+
3. Enter the "App ID" & "API Key" into your Segment Settings UI which you can find from your Algolia Dashboard, under API Keys menu.
26
26
27
27
_**NOTE:** The Algolia Insights Destination is not a plug-and-play integration. It requires you to modify your frontend code to send additional Algolia-related data like index name, queryID, etc._
@@ -239,7 +239,7 @@ In addition to the integration available for both iOS and Android, there is a cl
239
239
240
240
### Pre-defined Events and Parameters
241
241
242
-
The integration currently only supports the `FBSDKAppEventNameActivatedApp` pre-defined event (via the `activateApp` handler). All other events are forwarded as [custom events](https://developers.facebook.com/docs/app-events/ios#custom). If other [pre-defined events](https://developers.facebook.com/docs/app-events/ios#manual) are important to you, [contact us](https://segment.com/help/contact/).
242
+
The integration currently only supports the `FBSDKAppEventNameActivatedApp` pre-defined event (via the `activateApp` handler). All other events are forwarded as [custom events](https://developers.facebook.com/docs/app-events/getting-started-app-events-ios). If other pre-defined events are important to you, [contact us](https://segment.com/help/contact/).
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/kameleoon/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -44,7 +44,7 @@ If you use Kameleoon Full Stack, please refer to the [Kameleoon SDK documentatio
44
44
45
45
Kameleoon supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
46
46
47
-
If the Segment event name matches exactly the name of an existing [goal](https://help.kameleoon.com/create-new-goal/){:target="_blank"} in your Kameleoon account, a conversion for this goal will be associated to the visitor. If the goal does not exist, Kameleoon will create a [custom goal](https://help.kameleoon.com/create-new-goal/#Custom_goal){:target="_blank"} by using the Segment event name and associate the conversion to the visitor. The goal will appear in the Kameleoon [goals page](https://help.kameleoon.com/manage-goals/){:target="_blank"} with the name convention 'SegmentIO eventType - eventName'. Once the goal has been created, you can use them in any of your [campaign](https://https://help.kameleoon.com/set-up-goal-campaign/){:target="_blank"}.
47
+
If the Segment event name matches exactly the name of an existing [goal](https://help.kameleoon.com/create-new-goal/){:target="_blank"} in your Kameleoon account, a conversion for this goal will be associated to the visitor. If the goal does not exist, Kameleoon will create a [custom goal](https://help.kameleoon.com/create-new-goal/#Custom_goal){:target="_blank"} by using the Segment event name and associate the conversion to the visitor. The goal will appear in the Kameleoon [goals page](https://help.kameleoon.com/manage-goals/){:target="_blank"} with the name convention 'SegmentIO eventType - eventName'. Once the goal has been created, you can use them in any of your [campaign](https://help.kameleoon.com/set-up-goal-campaign/){:target="_blank"}.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/proof-experiences/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -19,8 +19,8 @@ This destination is maintained by Proof. For any issues with the destination, [c
19
19
20
20
1. From the Segment web app, click **Catalog**.
21
21
2. Search for "Proof Experiences" in the Catalog, select it, and choose which of your sources to connect the destination to.
22
-
3. Enter the "API Key" into your Segment Settings UI which you can find from your [Proof Experiences dashboard](https://app.proof-x.com/account/apikeys).
23
-
4. You should see data flowing into your Proof dashboard in the [event debugger](https://app.proof-x.com/settings/events) within 1 minute of creating your API key and activating your Proof Experiences integration.
22
+
3. Enter the "API Key" into your Segment Settings UI which you can find from your Proof Experiences dashboard.
23
+
4. You should see data flowing into your Proof dashboard in the event debugger within 1 minute of creating your API key and activating your Proof Experiences integration.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/tamber/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,6 @@ analytics.track("Watched", {
59
59
});
60
60
```
61
61
62
-
Track calls will be sent to Tamber as [`event-track`](https://works.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.
62
+
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.
63
63
64
-
**NOTE:**[`item`](https://works.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 <strong>Sources</strong> > <strong>Segment</strong> section – and ignore this information.
64
+
**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 <strong>Sources</strong> > <strong>Segment</strong> section – and ignore this information.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/woopra/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -30,7 +30,7 @@ When you call `identify` on analytics.js, we call Woopra's `woopraTracker.addVis
30
30
31
31
### Server Side
32
32
33
-
When you call `identify` from the server-side languages, we call Woopra's [HTTP REST API](http://www.woopra.com/docs-old/tracking/http-tracking-api/) with the traits that you pass in.
33
+
When you call `identify` from the server-side languages, we call Woopra's [HTTP REST API](https://docs.woopra.com/reference/intro-http-tracking) with the traits that you pass in.
Copy file name to clipboardExpand all lines: src/connections/destinations/catalog/zopim/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ rewrite: true
3
3
title: Zendesk Chat (Zopim) Destination
4
4
---
5
5
6
-
[Zendesk Chat](https://developer.zendesk.com/rest_api/docs/chat/introduction), (previously called Zopim) is a live chat solution that helps businesses increase sales conversion by engaging important leads on their websites. The `analytics.js` Zendesk Chat Destination is open-source. You can browse the code [on GitHub](https://github.com/segment-integrations/analytics.js-integration-zopim).
6
+
[Zendesk Chat](https://developer.zendesk.com/rest_api/docs/chat/introduction), (previously called Zopim) is a live chat solution that helps businesses increase sales conversion by engaging important leads on their websites. The `analytics.js` Zendesk Chat Destination is open-source. You can browse the code [on GitHub](https://github.com/segmentio/analytics.js-integrations/tree/master/integrations/zopim).
7
7
8
8
**NOTE:** Zendesk Chat currently offers [two types of widgets](https://support.zendesk.com/hc/en-us/articles/115007912068-Using-the-Chat-JavaScript-API): a standalone `Chat Widget`, which is mainly designed to provide chat related features, and a `Web Widget`, which incorporates both Zendesk Chat and Zendesk Support functionalities. At the moment, Segment only supports the `Chat Widget`. For more details refer to the "Getting Started" section below.
**NOTE**: We only send feedback back to Segment on surveys triggered from Segment initially. This ensures all feedback we send to Segment is identified and enriched with Segment information.
0 commit comments