Skip to main content
Conversion Goals define what “success” means for a tracked Digital Experience. When a visitor completes a goal, their session is marked as converted, unlocking conversion rate, funnel, and revenue attribution data across your UX Brite reports.

​
How Conversion Tracking Works

UX Brite’s tracker observes every session on your site. When a session triggers any one of your active goals, that session is counted as a conversion. Key behaviors to understand:
  • Per-session matching — A session is marked converted the first time any active goal fires. Multiple goal firings in one session do not multiply the conversion count.
  • Active goals only — Inactive goals are saved but ignored by the tracker until re-enabled.
  • Instant effect — Enabling or disabling a goal takes effect for new sessions immediately; historical sessions are not retroactively updated.
  • Goal type is permanent — Once a goal is created, its type (e.g. Purchase, Form Submit) cannot be changed. Delete and recreate the goal if you need a different type.

​
Goal Types

Each goal uses one of two detection strategies: URL-based or Event-based.

​
URL-Based Goals

The tracker fires when a visitor lands on a specific page URL. Query parameters and trailing slashes are ignored during matching.
/thank-you?order=123 matches a goal configured for /thank-you.

​
Event-Based Goals

The tracker fires when your site’s JavaScript calls uxbrite.track('custom_event', { action: 'YOUR_EVENT_NAME' }). This requires a small code integration on your site.

​
Triggering an Event Goal from Code

Add the following call to your site at the point of conversion (e.g. on form success, after checkout, on download click):
Replace YOUR_EVENT_NAME with the exact event name you configured for the goal. The name is case-sensitive.

​
Managing Conversion Goals

Conversion Goals are managed from the Conversion Goals section inside a Digital Experience’s detail page.

​
Adding a Goal

  1. Navigate to Digital Experiences and open the experience you want to configure.
  2. Scroll to the Conversion Goals card and click Add Goal.
  3. Select a Goal Type from the grid.
  4. Give the goal a descriptive Goal Name (auto-filled from the type, editable).
  5. Enter the Conversion Page URL (URL-based goals) or Event Name (event-based goals).
  6. Click Save Goal.
The goal is created in an active state and begins tracking immediately.

​
Editing a Goal

  1. Find the goal card and open the ⋮ menu (three dots).
  2. Select Edit Goal.
  3. Update the name or configuration value.
  4. Click Update Goal.
Goal type cannot be changed when editing. If you need a different type, delete and recreate the goal.

​
Enabling / Disabling a Goal

Use the toggle switch on any goal card to enable or disable it without deleting it. Disabled goals are preserved with their configuration for later use.

​
Deleting a Goal

  1. Open the ⋮ menu on the goal card.
  2. Select Delete Goal.
  3. Confirm the deletion in the dialog.
Deletion is permanent and cannot be undone. Historical sessions that already converted via this goal are not affected, but future sessions will no longer match it.
For most experiences, we recommend setting up at least one goal from each relevant category to ensure complete conversion coverage:

​
Troubleshooting

Sessions are not being counted as conversions
  • Confirm the UXBrite tracker is installed and active on your site (check the tracker status in the Digital Experience detail page).
  • For URL goals: verify the exact URL the visitor lands on matches the configured URL (ignoring query strings and trailing slashes).
  • For event goals: confirm your site is calling uxbrite.track('custom_event', { action: 'YOUR_EVENT_NAME' }) and the event name matches exactly, including case.
  • Ensure the goal is active (toggle is on).
Goal toggle is not saving
  • If the toggle reverts, there may be a temporary API issue. Refresh the page and try again. An error toast will appear if the update fails.
I need to change the goal type
  • Goal type is locked after creation. Delete the existing goal and create a new one with the correct type.