Skip to content

Commit 269104a

Browse files
committed
Adding links to specific help doc pages
1 parent 2d0eaa0 commit 269104a

File tree

1 file changed

+3
-3
lines changed
  • src/connections/destinations/catalog/actions-kameleoon

1 file changed

+3
-3
lines changed

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

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -31,7 +31,7 @@ Kameleoon (Actions) provides the following benefits over the classic Kameleoon d
3131
4. Select the Source you want to connect to Kameleoon (Actions) and click **Confirm Source**.
3232
5. On the **Basic Settings** side panel, complete the required fields:
3333
- **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”}.
3535
- **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”}.
3636
6. Enable the destination by clicking the **Enable Destination** toggle switch.
3737
7. Click **Save Changes**.
@@ -40,13 +40,13 @@ Kameleoon (Actions) provides the following benefits over the classic Kameleoon d
4040
{% include components/actions-fields.html %}
4141

4242

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”}.
4444

4545

4646
## Migration from the classic Kameleoon destination
4747

4848
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”}.
5050
2. Define mapping and filters on the destination configuration page.
5151
3. Test events to ensure accurate goal creation and conversion tracking.
5252
4. Activate the Kameleoon (Actions) destination when everything is ready and tested.

0 commit comments

Comments
 (0)