Getting Started

Conversion Tracking

Track conversions, measure campaign performance, and optimize your ad spend.
Prompt for coding agents

I want to set up Koah's conversion tracking pixel. Read https://docs.koahlabs.com/SKILL.md and follow its instructions.

Install the conversion pixel and/or conversion API on your website to track visitor actions like purchases, sign-ups, and page views. We provide guides for popular website platforms to help you integrate seamlessly.

Why use Koah Conversion Tracking?

Koah Conversion Tracking helps you understand how users interact with your website after viewing or clicking your ads. By tracking conversion events, you can:

  • Measure ROI - See which campaigns drive real business results
  • Track the full customer journey - From ad impression to conversion
  • Complete transparency - View all tracked events in real-time through your Koah dashboard

The Koah Conversion Tracking supports multiple events. Each event can include custom parameters like value, currency, and content details to give you deeper insights into user behavior.

Conversion Pixel vs Conversion API

Koah offers 2 methods for tracking visitor actions:

  1. The conversion pixel is a JavaScript snippet that sends visitor actions to Koah directly from the user's browser.
  2. The conversion API is a REST API endpoint that accepts visitor actions from your website's server.

You can set up the pixel, API, or both. There are pros and cons to each approach:

Conversion Pixel

  • The pixel is simple to integrate; just add a couple script tags and lines of JavaScript to your webpages. It automatically tracks events coming from the same user and links them back to the ad click that led to your site.
  • The pixel may not track actions reliably for users who have opted out of analytics, disabled cookies, or disabled JavaScript.

Conversion API

  • The API tracks visitor actions more reliably than the pixel since it does not require client-side scripts or users to opt in to analytics.
  • The API offers you more fine-grained control over which analytics data to send to Koah, and compliance with security requirements against 3rd-party scripts on your site.
  • API integration involves more technical configuration on your site, as you need to write code to send us events directly rather than our script sending them automatically.
  • The API needs to manage persistent user and Koah click identifiers across server and browser. See the API docs for details.

Both

  • Use both the pixel and API to report user actions with higher accuracy than either approach in isolation, so Koah can better optimize your campaign performance and spend.
  • When you use both, each event is tracked separately, and Koah needs a way to de-duplicate the same event coming from both sources. See de-duplicating events for details.
  • This approach is the most configuration-intensive on your end, as there are 2 systems to add to your site, and you must configure them to work together.
Was this helpful?