kopairDocumentation
Dashboard ↗
Documentation / Define success

Goals and versions

A goal defines success. Site goals are reusable; an experiment uses a specific version and a Primary/Secondary role.

Reviewed: 25.10.2026 · Based on current product behavior
01URL → success page
02Click → interest
03Event → confirmation
kopair workflow diagram.

Step by step

  1. Open Goals, select the site and create a URL destination, element click or custom-event goal. Use the visual picker to choose a button and review its page filter.
  2. Attach the chosen version to a draft experiment. Choose one Primary goal for the main decision; use Secondary goals for supporting metrics.
  3. Editing a site goal creates a new version. Update a draft explicitly if it should use that version. After first launch the experiment goal definitions and roles are locked. Archiving a site goal does not rewrite old experiments.
Practical example

Tilda: /thank-you after a successful form is a URL goal. Shopify: an add-to-cart button is a click goal, not a paid-order goal. WordPress AJAX forms need a success event if they do not navigate.

How to verify

Test a positive and negative case, including the URL filter. A button inside a third-party iframe is outside the parent page picker. Test repeated buttons and choose the intended single element or group.