New aggregated insights just released Learn more →

Conversion detection methods: URL, DOM, JS, server

Pick the most reliable trigger for each conversion

Written by Trace Team Updated 14-04-26

Detection method overview

  • URL match: conversion fires when a URL pattern is visited.
  • DOM event: conversion fires on element interaction (for example button submit).
  • JS callback: conversion fires from explicit JavaScript trigger.
  • Server-side: conversion is submitted from backend systems.

Choosing the right method

  • Use URL match for thank-you or confirmation pages.
  • Use DOM event when no dedicated confirmation URL exists.
  • Use JS callback for single-page apps and custom funnels.
  • Use server-side for payment systems and backend-confirmed outcomes.

Reliability guidance

  • Prefer deterministic signals (server-side, dedicated URL) for revenue events.
  • Avoid brittle DOM selectors that can break with UI changes.
  • Document owner for each conversion type so changes are managed safely.

Troubleshooting

  • URL method not firing: validate exact path/query matching rules.
  • DOM method flaky: harden selector and ensure event binding occurs after render.
  • JS/server method missing events: confirm payload fields and authentication context.

Still need help?

Contact our support team and we will get back to you as soon as we can.

support@usetrace.io