Skip to content

Commit 9941819

Browse files
committed
kameleoon edits [netlify-ignore]
1 parent 278d4f0 commit 9941819

File tree

2 files changed

+22
-18
lines changed

2 files changed

+22
-18
lines changed

src/connections/destinations/catalog/kameleoon/index.md

Lines changed: 21 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ rewrite: true
55

66
[Kameleoon](https://kameleoon.com/en) & Segment.io integration
77
---
8-
GDPR, CCPA, and HIPAA compliant, Kameleoon's powerful and easy-to-use A/B testing, full stack, and AI-powered personalization solutions help marketers, product owners, and developers maximize customer engagement and conversion - all from a single platform.
8+
[Kameleoon](https://kameleoon.com/en) provides GDPR, CCPA, and HIPAA compliant A/B testing, full stack, and AI-powered personalization solutions to help marketers, product owners, and developers maximize customer engagement and conversion - all from a single platform.
99

1010
This destination is maintained by Kameleoon. For any issues with the destination, [contact the Kameleoon Support team](mailto:[email protected]).
1111

@@ -15,39 +15,42 @@ This destination is maintained by Kameleoon. For any issues with the destination
1515
{% include content/connection-modes.md %}
1616

1717
Segment’s Kameleoon destination supports the following Kameleoon products:
18-
* [Kameleoon Experiment](https://www.kameleoon.com/en/platform/ab-testing-client-side) (Web Client-side)
19-
* [Kameleoon Full Stack](https://www.kameleoon.com/en/platform/ab-testing-full-stack) (Web or mobile Apps, IoT..)
20-
* [Kameleoon AI Personalization](https://www.kameleoon.com/en/platform/personalization) (Web Client-side)
18+
* [Kameleoon Experiment](https://www.kameleoon.com/en/platform/ab-testing-client-side){:target="_blank"} (Web Client-side)
19+
* [Kameleoon Full Stack](https://www.kameleoon.com/en/platform/ab-testing-full-stack){:target="_blank"} (Web or mobile Apps, IoT..)
20+
* [Kameleoon AI Personalization](https://www.kameleoon.com/en/platform/personalization){:target="_blank"} (Web Client-side)
2121

2222

23-
First, you will have to request an API Key in order to use Kameleoon & Segment.io integration. You can request it to [[email protected]](mailto:[email protected]), by specifying your Kameleoon **account login**.
23+
To begin, request a Kameleoon API key from [[email protected]](mailto:[email protected]).
2424

25-
You will also need to get your **sitecode** key. You can find it from your [Kameleoon Account].(https://help.kameleoon.com/question/how-do-i-find-my-site-id/)
25+
You will also need the **sitecode** key. You can find it in your Kameleoon account, as described in [How do I find my site id?](https://help.kameleoon.com/question/how-do-i-find-my-site-id/){:target="_blank"}.
26+
27+
To add the destination to your Segment workspace:
2628

2729
1. From the Destinations catalog page in the Segment App, click **Add Destination**.
28-
2. Search for "Kameleoon" in the Destinations Catalog, and select the "Kameleoon" destination.
29-
3. Choose which Source should send data to the "Kameleoon" destination.
30-
6. Enter the **API Key** and the **sitecode** in the "Kameleoon" destination settings in Segment.
30+
2. Search for "Kameleoon" in the Destinations Catalog, and select the Kameleoon destination.
31+
3. Choose which Source should send data to the Kameleoon destination.
32+
4. Enter the **API Key** and the **sitecode** in the Kameleoon destination settings in Segment.
3133

3234
## Implementation pre-requisites: matching Users between Kameleoon and Segment
33-
The integration requires that you use the same system of identifiers for both tools, meaning the **userId** value you pass to Segment should be the same value as Kameleoon uses to identify a "visitor". If you use Kameleoon Experiment or Kameleoon AI Personalization on your website, Kameleoon places a cookie that contains an anonymous unique identifier, called the Kameleoon visitorcode, randomly assigned to a visitor. This ID is used to uniquely identify a browser.
3435

35-
Check with your engineers to ensure our **visitorcode** is passed in the **userId** property of the Segment calls to ensure Kameleoon can consolidate data and avoid any analytics discrepancies between the tools in your campaign results.
36+
The integration requires you to use the same system of identifiers for both tools, meaning the `userId` value you pass to Segment should be the same value that Kameleoon uses to identify a "visitor". If you use Kameleoon Experiment or Kameleoon AI Personalization on your website, Kameleoon places a cookie that contains an anonymous unique identifier, called the Kameleoon visitorcode, randomly assigned to a visitor. This ID is used to uniquely identify a browser.
37+
38+
Check with your engineers to ensure Kameleoon's `visitorcode` is passed in the `userId` property of the Segment calls to ensure Kameleoon can consolidate data and avoid any analytics discrepancies between the tools in your campaign results.
3639

37-
To provide a consistent user identifier to Kameleoon, you may specify in Segment calls a user property, **k_visitorCode**, whose value is the Kameleoon visitorcode. You can retrieve the user visitorCode from the browser by using our [Activation API](https://developers.kameleoon.com/activation-api.html#visitor). ```Kameleoon.API.Visitor.code```
40+
To provide a consistent user identifier to Kameleoon, you may specify in Segment calls a user property, `k_visitorCode`, whose value is the Kameleoon visitorcode. You can retrieve the user visitorCode from the browser by using Kameleoon's [Activation API](https://developers.kameleoon.com/activation-api.html#visitor){:target="_blank"}.
3841

39-
If you use Kameleoon Full Stack, please refer to the [Kameleoon SDK documentation](https://developers.kameleoon.com/sdks-overview.html). We always recommend to use your own internal ID to identify users.
42+
If you use Kameleoon Full Stack, please refer to the [Kameleoon SDK documentation](https://developers.kameleoon.com/sdks-overview.html){:target="_blank"}.
4043

4144

4245
## Supported methods
4346

4447
Kameleoon supports the following methods, as specified in the [Segment Spec](/docs/connections/spec).
4548

46-
Behind the scenes, if the Segment event name matches exactly the name of an existing [goal](https://help.kameleoon.com/create-new-goal/) 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) 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/) 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/).
49+
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"}.
4750

4851
### Page
4952

50-
Send [Page](https://segment.com/docs/connections/spec/page/) calls to record whenever a user sees a page of your website, along with any optional properties about the page. Calling page or screen in one of our sources is one of the first steps to getting started with Segment.
53+
Send [Page](/docs/connections/spec/page/) calls to record whenever a user sees a page of your website, along with any optional properties about the page. Calling page or screen in a source is one of the first steps to getting started with Segment.
5154

5255
For example:
5356

@@ -58,7 +61,7 @@ analytics.page('Home', {"k_visitorCode": "oa16i4syt2ve3b0z"});
5861

5962
### Screen
6063

61-
Send [Screen](https://segment.com/docs/connections/spec/screen/) calls to record whenever a user sees a screen, the mobile equivalent of page, in your mobile app, along with any properties about the screen. Calling page or screen in one of our sources is one of the first steps to getting started with Segment.
64+
Send [Screen](/docs/connections/spec/screen/) calls to record whenever a user sees a screen, the mobile equivalent of page, in your mobile app, along with any properties about the screen. Calling page or screen in a source is one of the first steps to getting started with Segment.
6265

6366
For example:
6467

@@ -72,7 +75,7 @@ Segment sends Screen calls to Kameleoon as a `screenview`.
7275
7376
### Track
7477
75-
Send [Track](https://segment.com/docs/connections/spec/track/) calls to record any actions your users perform, along with any properties that describe the action.
78+
Send [Track](/docs/connections/spec/track/) calls to record any actions your users perform, along with any properties that describe the action.
7679
7780
For example:
7881
@@ -82,4 +85,4 @@ analytics.track('Login Button Clicked', {"k_visitorCode": "oa16i4syt2ve3b0z"});
8285

8386
Segment sends Track calls to Kameleoon as a `track` event.
8487

85-
---
88+

vale-styles/Vocab/Docs/accept.txt

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -47,3 +47,4 @@ Lightbox
4747
gmail
4848
(?:P|p)endo
4949
(?:K|k)laviyo
50+
Kameleoon

0 commit comments

Comments
 (0)