Setting Up
Browser Conversions
3 min
if you're unable to use server side conversions , you can always fallback to browser conversions with browser based tracking, you can trigger conversion events directly in the browser, ensuring accurate attribution for your ads this method allows you to send purchase (order success) events directly from the frontend how to trigger browser conversions fire the purchase event when an order is successfully completed key fields email ( required ) – the customer’s email transaction id ( required ) – a unique identifier for deduplication transaction amount ( required ) – the purchase amount (use as a separator) transaction currency – currency code (e g , usd, eur) transaction description ( required ) – description of the purchase first name, last name, name, phone (optional) – additional customer details ⚠️ important notes ensure the weberlo tracking code is loaded before executing the event tracking code use unique transaction id values to prevent duplicate order tracking browser conversions should be used as a fallback when server side tracking is not available