Create a goal

​

Access the Goals page

​

Create a new goal

​

Name and describe your goal

1. Click New goal on the Goals page. The Add a new goal modal opens.
2. Fill in the details Kameleoon needs to identify your goal:
   • Name: A name for your goal.
   • Project: The site the goal applies to, chosen from a dropdown of your site URLs.
   • Description (optional): Up to 120 characters describing the purpose of your goal. This information helps you analyze results later.
   • + Add tags: Attach one or more tags to the goal for later filtering.
3. Click Next to continue, or Cancel to close the modal without creating the goal.

​

Choose a goal type

• Click tracking: Triggered when a user clicks on a specific element.
• Time spent: Triggered when a user spends a defined time on your site.
• Access to a page: Triggered when a user visits a specific page.
• Retention rate: Triggered when a user clicks after landing on the first page of their visit.
• Number of pages viewed: Triggered when a user views a defined number of pages.
• Scroll tracking: Triggered when a user reaches a certain percentage of the page height.

• Custom Goal: Target highly specific visitor behaviors by defining your own events.
• Data warehouse tracking: Sync events from Snowflake, BigQuery, or other external data sources.

• Ratio metric: Measure relative performance by dividing one metric goal by another.

1. Select a card.
2. Click Create to continue, or Back to return to the previous modal without selecting a type.

​

Click tracking

• With the Visual Editor: Select the interactive element you want to track with the graphical editor.
• Using CSS selector: Specify the CSS selector of the element you want to track.
• From an existing experiment: Track an element that was previously added in one of your variations.
• With the Prompt-based Editor: Describe the element you want to track, and Kameleoon generates the goal.

​

Using CSS selector

1. In the Click targets field, enter one or more selectors, separated by commas.
   
2. Clicking + Add selector opens a dropdown with the same four methods: with the Visual Editor, using a CSS selector, from an existing experiment, or with the Prompt-based Editor, which stays off. Choose one to add another target using a different method.
   

​

Manually with the Visual Editor

1. An Open visual editor dialog asks “On which page (URL) do you want to track clicks?” and prefills the field with your site’s URL. Click Open Editor to continue, or Cancel to close the dialog.
   
2. The editor opens a split view: your live site renders on the left, and a Define click tracking panel opens on the right. Click each element you want to track in the preview area. Clicking an element:
   • Adds a highlighted outline box around the element in the preview, confirming your selection.
   • Auto-fills the panel’s Selector field with the element’s CSS selector. For example, clicking a button auto-fills a selector like #pbx-btn-send.
   
3. Use the field’s clear (X) control or its three-dot options menu to adjust a selection, or click + Add selector to pick more elements. Click Next to save your selections, or Cancel to close the editor without saving.

​

Choose where to track this goal

• Anywhere on the site (default): Records a conversion whenever a visitor clicks the element. If several pages share the same CSS selector, every matching click counts.
• Only on specific pages: Records a conversion only when the click happens on a page that matches URL conditions you define. Selecting this option reveals a URL-condition builder: choose a match type (for example, URL contains) and enter a URL in the text field, such as www.kameleoon.com/products/. Click + Add target URL to add further conditions.

​

Scroll tracking

1. URL of the page: The URL of the page on which you want to create the scroll tracker.
2. visitor scrolls down to: How Kameleoon measures scroll depth, chosen from a dropdown:
   • the selected element: Visualize the elements of the page by hovering over them, then click the one you want to use as the scroll target. The level appears directly below the selected element.
   • a precise percentage (default): Enter a percentage of the page height using the numeric stepper, for example 60%. The percentage measures from the top of the page: 0% places the level at the very top, 50% in the middle, and 100% at the very bottom.
   • a height in pixels: Enter a fixed height in pixels using the numeric stepper. 0 pixels corresponds to the very top of the page, and the maximum height correlates with the page size.

​

Access to a page

• contains: Targets all pages sharing the same URL fragment.
• matches exactly: Targets only the page with the exact URL you entered.
• matches the regular expression: Targets a URL and its variations, according to the regular expression you enter. For help creating regular expressions, see Regular expressions.

• To a specific product page:
  • Select matches exactly and enter the full, precise URL. For example: https://www.mysite.com/products/product-1
• To all product pages:
  • Select contains and type in /products/. Your goal then applies to all pages that include the /products/ fragment in their URL.
• For URLs with common variations (for example, “product” vs. “products”):
  • If your product page URLs sometimes contain “product” instead of “products,” use a regular expression. For instance, https://www.mysite.com/products* matches URLs containing either “products” or “product” at that point.

​

Time spent

• more than: The visitor must spend at least a given time on the page.
• exactly: The time spent must match exactly.
• less than: The time spent must not exceed a given duration.

​

Number of pages viewed

​

Retention rate

​

Custom goal

​

Option 1: Using a front-end event triggered by the JS Activation API

• How it works: Kameleoon provides a specific function (Kameleoon.API.Goals.processConversion(ID), where ID is your goal’s unique identifier) that you insert into your JavaScript code. When the user performs the action you are tracking, your code executes this function to send the conversion signal directly to the Kameleoon platform.

​

Option 2: Using a back-end event via SDK (for example, Node JS)

trackConversion({visitorCode, goalId})

• visitorCode is the visitor’s unique identifier you want to target.
• goalId is the goal’s unique identifier.

​

Option 3: Using custom JavaScript code

• How it works: The code you enter in the wider code-editor panel runs automatically once your site is ready. Within that code, use the triggerGoal() method to fire a conversion. You can also optionally pass revenue and metadata parameters.

1. Go to GTM > Tags > New > Tag Configuration > Custom HTML and insert the following code:
   <script>
   window.kameleoonQueue = window.kameleoonQueue || [];
   kameleoonQueue.push(['Goals.processConversion', goalId, revenue]);
   </script>
   
2. Select the trigger that sends the goal conversion call to Kameleoon.

​

Data warehouse tracking

• BigQuery asks for a BigQuery project ID and a Region.
• Snowflake asks for a Warehouse, a Database, and a Schema.
• Databricks asks for a Catalog and a Schema.
• Redshift asks whether your cluster runs in Provisioned or Serverless mode, a Redshift cluster ID, a Region, and a Database.

• Use BigQuery as a source
• Using Snowflake as a source
• Use Databricks as a source
• Use Amazon Redshift as a source

​

Ratio metric

​

Metadata

​

What’s metadata?

​

Using metadata

1. Define a custom data. For more information, see Create custom data.
2. Link the custom data as metadata when creating or editing a goal by selecting it from the dropdown.

​

Advanced settings

​

Handle outliers

​

Usage

• Make this goal only available for specific experiments: By default, this goal is available for all experiments. Enable this toggle to select which ones can use it.
• Make this goal only available for specific personalizations: By default, this goal is available for all personalizations. Enable this toggle to limit which ones can use it.
• AI Predictive Targeting: Trains a model on this goal at the key moments you define, to target visitors by their likelihood to convert. Enabling this toggle reveals an Add prediction trigger button. Click it, then select the triggers you want to enable. More about triggers

​

Data sharing

const enum GoalType {
	CLICK = "CLICK",
	CUSTOM = "CUSTOM",
	SCROLL = "SCROLL",
	PAGE_VIEWS = "PAGE_VIEWS",
	URL = "URL",
	TIME_SPENT = "TIME_SPENT",
	RETENTION_RATE = "RETENTION_RATE",
}

​

The goal summary page

• Insights: the goal’s performance data, including key metrics, a daily events timeline, and impacted campaigns. For details, see Goal reporting.
• Summary: the goal’s configuration, selected by default right after you create the goal.

• Definition: the triggering condition you set in Step 1, plus any metadata attached to conversions. Click Edit to change these settings.
• Usage: the toggles you set in Step 2 that control who can use the goal, plus a Set this goal as your project primary goal toggle that defines this goal as your project’s main success metric. Only one goal can be primary per project. Click Edit to change these settings.
• Data sharing: the integrations you selected in Step 2 to receive data when the goal converts, or No data sharing tools if you didn’t select any. Click Edit to change this setting.