---
title: Browser Conversions
slug: browser-conversions
docTags: 
createdAt: 2025-02-16T18:42:09.470Z
---

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.

:::BlockQuote
weberlo('order-success', \{
  email: 'customer\@example.com', // Required 
  transaction\_id: 'unique\_id\_for\_deduplication', // Required
  transaction\_amount: '30.00', // Required (use . as separator) 
  transaction\_currency: 'USD',
  transaction\_description: 'Test Product Purchase', // Required 
  first\_name: 'Alice',
  last\_name: 'Smith',
  name: 'Alice Smith',
  phone: '+987654321'
});
:::

**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.