Skip to main content

Overview

Click counts tell you which A/B test variant attracted more visitors. Conversion tracking tells you which variant actually drove revenue or leads. This guide covers how to send conversion events from your partner site to TyrionURL using your API key.

Prerequisites

Before setting up conversion tracking:
  1. ✅ You have created an A/B test on a TyrionURL short link
  2. ✅ You have generated an API key in Settings
  3. ✅ You have access to add code to the landing page or checkout confirmation page on your partner site

How Conversion Tracking Works


Sending a Conversion Event

On your confirmation page (order thank-you page, lead form success page, etc.), make a server-side API call to TyrionURL:
Always send conversion events from server-side code (not client-side JavaScript) to protect your API key from being exposed in browser source code.
TODO: Needs Product Verification — Confirm the exact conversion API endpoint path, request schema, and supported eventType values with the TyrionURL engineering team.

Conversion Event Fields


Passing the Short Code Through Your Funnel

For TyrionURL to attribute the conversion to the correct variant, your landing page needs to know which short code referred the visitor. The recommended approach is to append the short code as a URL parameter when linking from TyrionURL: Example destination URL in Variant A:
Your landing page reads the sc parameter and passes it through your checkout flow (via a hidden form field or session cookie) to the confirmation page, where the conversion event is sent.

Viewing Conversion Data

After conversion events are flowing, view results in your link’s A/B test analytics panel:
A/B test results with conversion and revenue data

Best Practices

Start sending conversion events from day one of an A/B test — retroactive attribution isn’t possible for past clicks.
Use the metadata field to store order IDs so you can cross-reference TyrionURL conversions with your own order management system.
Only fire the conversion event on confirmed completions (e.g., order confirmation page) — not on button clicks or form starts.

A/B Testing Setup

Configure your split test before tracking.

API Keys

Generate and manage your integration credentials.