Click conversion metrics
Read time: 2 minutes
Last edited: Mar 01, 2023
This topic explains how to create a click conversion metric for an experiment in LaunchDarkly.
SDKs send events at regular intervals, such as every five seconds. If a browser redirects an end user to another page, any events that occurred between when the SDK last sent events and when browser redirected the end user will be lost. To avoid this, call track and then flush when you know the browser will redirect an end user to another page, such as on click.
For example, you might want to track how often a customer clicks a "Save" button when it is red versus how often a customer clicks the "Save" button when it is blue. You can create a metric that monitors clicks on the button as designated by a CSS selector located at a specific URL.
You can even monitor clicks on the button across different URLs by telling the metric to track different URLs based on substrings or simple matches. For example, you could track an event on every URL with
/checkout-page/ in the URL path.
Understanding CSS selectors
CSS selectors designate specific areas of your product UI, like buttons or images, that your end users can interact with. You can create a metric that monitors interaction with one or more CSS selectors.
For example, some CSS selectors include:
The CSS selector must be present in your application after the end user interacts with it in order for LaunchDarkly to record the metric. For example, if the end user clicks an element that is dynamically removed from your application in response to the click, then LaunchDarkly will not record the metric event.
If the CSS selector will not be present after the end user interacts with it, we recommend using a custom conversion metric instead. To learn more, read Custom conversion metrics.
Creating click conversion metrics
To create a click conversion metric:
- Navigate to the Experiments list.
- Click the Metrics tab.
- Click Create metric. The "Create a new metric" panel appears.
- Enter a human-readable Name for the metric.
- (Optional) Enter a Description.
- (Optional) Type or choose from available Tags.
- (Optional) Choose a Maintainer. By default, the person who creates the metric is set as the Maintainer.
- Click the Event kind menu and select "Click."
- Enter one or more CSS selectors in the Click targets field. If you include multiple CSS selectors, separate them with commas.
- Specify the type of Target URL you want to track behavior on. There are four types of URL matching:
|URL matching schema||Description||Example|
|Simple match||This sends an event when the end user accesses a URL, or clicks on an element hosted at a URL, that matches the string you enter in the Target URL field or a formulation of that URL that included appended parameters. If you want events to record for URLs with substrings, specify each URL individually.||If you specify:|
|Exact match||This sends an event when the end user accesses a URL, or clicks on an element hosted at a URL, that exactly matches what you enter in the Target URL field. Identical base URLs with different substrings do not send events.||If you specify:|
|Substring match||This sends an event when the end user accesses a URL, or clicks on an element hosted at a URL with a specific string of text in it.||If you specify:|
|Regular expression||This sends an event based on a regex expression you specify. This lets you designate more precise locations to send click and page view events.||If you specify:|
- Enter the webpage URL.
- (Optional) Click Add additional URL to track behavior on more than one URL.
- Choose one or more context kinds available for experiments for the metric to measure events from.
Using invalid randomization units will result in invalid experiment results. To learn more, read Randomization units. If you're unsure of which randomization unit to use, contact Support for help determining valid context kind selections.
- Click Save metric.
After you create a metric, you can connect it to an experiment. To learn how, read Building experiments.