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/actions-kameleoon/index.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ Kameleoon (Actions) provides the following benefits over the classic Kameleoon d
31
31
4. Select the Source you want to connect to Kameleoon (Actions) and click **Confirm Source**.
32
32
5. On the **Basic Settings** side panel, complete the required fields:
33
33
-**Name**: Enter a name to help you identify this destination in Segment
34
-
-**API Key**: Paste your Kameleoon API key. To generate an API Key, see [Kameleoon's documentation](https://help.kameleoon.com/){:target="_blank”}.
34
+
-**API Key**: Paste your Kameleoon API key. To generate an API Key, see [Kameleoon's documentation](https://help.kameleoon.com/setting-up-segment-destination-actions/#Kameleoon_setup){:target="_blank”}.
35
35
-**Sitecode**: Paste your Kameleoon project sitecode. You can find it in the [project dashboard](https://help.kameleoon.com/question/how-do-i-find-my-site-id/){:target="_blank”}.
36
36
6. Enable the destination by clicking the **Enable Destination** toggle switch.
37
37
7. Click **Save Changes**.
@@ -40,13 +40,13 @@ Kameleoon (Actions) provides the following benefits over the classic Kameleoon d
40
40
{% include components/actions-fields.html %}
41
41
42
42
43
-
The integration requires that you use the same system of identifiers for both tools. While Segment uses the userId, Kameleoon uses the kameleoonVisitorCode. In order to identify which visitor triggered the forwarded Segment events, you must include the kameleoonVisitorCode inside your Segment events. To know more, see [Kameleoon's documentation page](https://help.kameleoon.com/){:target="_blank”}.
43
+
The integration requires that you use the same system of identifiers for both tools. While Segment uses the userId, Kameleoon uses the kameleoonVisitorCode. In order to identify which visitor triggered the forwarded Segment events, you must include the kameleoonVisitorCode inside your Segment events. To know more, see [Kameleoon's documentation page](https://help.kameleoon.com/setting-up-segment-destination-actions/#Matching_an_Segmentio_user_with_a_Kameleoon_visitor){:target="_blank”}.
44
44
45
45
46
46
## Migration from the classic Kameleoon destination
47
47
48
48
To migrate from the classic Kameleoon destination:
49
-
1. Include the `kameleoonVisitorCode` in your Segment events for accurate visitor tracking. To know more, see [the dedicated documentation page](https://help.kameleoon.com/){:target="_blank”}.
49
+
1. Include the `kameleoonVisitorCode` in your Segment events for accurate visitor tracking. To know more, see [the dedicated documentation page](https://help.kameleoon.com/setting-up-segment-destination-actions/#Matching_an_Segmentio_user_with_a_Kameleoon_visitor){:target="_blank”}.
50
50
2. Define mapping and filters on the destination configuration page.
51
51
3. Test events to ensure accurate goal creation and conversion tracking.
52
52
4. Activate the Kameleoon (Actions) destination when everything is ready and tested.
0 commit comments