Sign In

Conversions

Configure which events count as conversions

Conversion types let you define which events count as conversions in your metrics. This gives you control over how conversion rates are calculated and displayed.

Events vs Conversions

Every action tracked by the pixel is an event. Common events include:

  • Page View - A visitor views a page
  • Purchase - A visitor makes a purchase
  • Register - A visitor creates an account
  • Download - A visitor downloads a file

A conversion is an event that you've designated as valuable for your business. Only events matching your configured conversion types are counted in conversion metrics like conversion rate and revenue.

Example

If you configure Purchase as a conversion type, your conversion rate shows what percentage of clicks result in purchases. Events like Page View are tracked but don't affect conversion metrics.

Primary and Secondary Types

You can designate conversion types as primary or secondary to control how they're displayed:

Type Description
Primary The main conversion metric displayed prominently in analytics. Every team must have exactly one primary type.
Secondary An optional secondary metric shown alongside the primary. Useful for tracking a supporting goal like signups alongside purchases.

Default Types

New teams start with two conversion types already configured:

  • Purchase (purchase) - Set as primary
  • Register (register) - Set as secondary

You can change these designations or add additional types at any time.

Predefined Types

qklnk provides predefined conversion types for common use cases:

Event Name Label Use Case
purchase Purchase Completed transactions
register Register Account signups
add_to_cart Add to Cart E-commerce cart additions
checkout Checkout Checkout initiations
download Download File or resource downloads
subscribe Subscribe Newsletter or subscription signups

Custom Types

Create custom conversion types for events specific to your business. Custom event names must:

  • Use only lowercase letters, numbers, and underscores
  • Be unique within your team
  • Match the event name used in your qklnk.event() calls
JavaScript
// Track a custom event
qklnk.event('free_trial_started');

// Then add 'free_trial_started' as a conversion type in settings

Default Values

Each conversion type can have a default value. When an event is recorded without a value property, this default is used for revenue calculations.

JavaScript
// If 'register' has a default value of 10.00:
qklnk.event('register'); // Uses default value of 10.00

// Explicit value overrides the default:
qklnk.event('register', { value: 25.00 }); // Uses 25.00

First Conversion Only

Enable First conversion only for conversion types where each visitor can only convert once, such as account registrations or newsletter signups.

When enabled:

  • Only the first event per visitor counts toward conversion metrics
  • Subsequent events are still recorded for behavioral analysis
  • The uniqueness is determined by visitor ID, event type, and name

Multiple Named Conversions

If you use the name property, each unique name counts separately. For example, a visitor can have one "first conversion" for subscribing to "Weekly Newsletter" and another for "Monthly Digest".

JavaScript
// Each name is tracked separately
qklnk.event('subscribe', { name: 'Weekly Newsletter' }); // Counts
qklnk.event('subscribe', { name: 'Weekly Newsletter' }); // Does not count (duplicate)
qklnk.event('subscribe', { name: 'Monthly Digest' });    // Counts (different name)

Tracking Names

Use the name property to label any event. This appears in the Name column of the Recent Conversions table on your link details page.

JavaScript
// Track a purchase with product name
qklnk.event('purchase', {
    value: 149.99,
    name: 'Pro Plan'
});

// Track add to cart
qklnk.event('add_to_cart', {
    name: 'Starter Plan'
});

// Track a subscription
qklnk.event('subscribe', {
    name: 'Weekly Newsletter'
});

// Track a download
qklnk.event('download', {
    name: 'Product Brochure PDF'
});
You can also pass a metadata property to store additional custom data with your events. See the Event Tracking documentation for details.

Managing Conversion Types

Configure your conversion types in Settings → Events & Conversions. From there you can:

  • Add predefined or custom conversion types
  • Set primary and secondary designations
  • Configure default values
  • Remove types you no longer need

Note

You cannot remove a conversion type that is set as primary or secondary. Change the designation to another type first, then remove it.