> ## Documentation Index
> Fetch the complete documentation index at: https://dub-client-tracking-lead-sale.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Client-side tracking
> Learn how to track sales conversion events with Dub on the client-side
When it comes to [conversion tracking](/conversions/quickstart), a `sale` event happens when a user purchases your product or service. Examples include:
* Subscribing to a paid plan
* Usage expansion (upgrading from one plan to another)
## Prerequisites
Before you get started, make sure you follow the [Dub Conversions quickstart guide](/conversions/quickstart) to get Dub Conversions set up for your links:
1. [Enable conversion tracking for your links](/conversions/quickstart#step-1%3A-enable-conversion-tracking-for-your-links)
## Quickstart
Before you can track conversions on the client-side, you need to generate a publishable key from your Dub workspace.
To do that, navigate to your [workspace's Analytics settings page](https://app.dub.co/settings/analytics) and generate a new publishable key under the **Publishable Key** section.
Then, you'll need to allowlist your site's domain to allow the client-side conversion events to be ingested by Dub.
To do that, navigate to your [workspace's Analytics settings page](https://app.dub.co/settings/analytics) and add your site's domain to the **Allowed Hostnames** list.
This provides an additional layer of security by ensuring only authorized domains can track conversions using your publishable key.
You can group your hostnames when adding them to the allow list:
* `example.com`: Tracks traffic **only** from `example.com`.
* `*.example.com`: Tracks traffic from **all subdomains** of `example.com`, but **not** from `example.com` itself.
When testing things out locally, you can add `localhost` to the **Allowed
Hostnames** list temporarily. This will allow local events to be ingested by
Dub. Don't forget to remove it once you're ready to go live!
Next, install the Dub analytics script in your application.
You can install the `@dub/analytics` script in several different ways:
Add Dub Analytics to your React app
Add Dub Analytics to your website
Add Dub Analytics via GTM
}
href="/sdks/client-side/installation-guides/framer"
>
Add Dub Analytics to your Framer site
Add Dub Analytics to your Shopify store
Add Dub Analytics to your WP site
Add Dub Analytics to your Webflow site
You must configure the **publishable key** you generated in step 1 when installing the analytics script. Without this key, client-side conversion tracking will not work.
```typescript React
import { Analytics as DubAnalytics } from '@dub/analytics/react';
export default function RootLayout({
children,
}) {
return (
{children}
);
}
```
```html Other
```
## Client-side sale tracking
Once the analytics script is installed, you can start tracking sale events in your application on the client-side.
```typescript React
import { useAnalytics } from "@dub/analytics/react";
import { useState } from "react";
export function CheckoutForm() {
const { trackSale } = useAnalytics();
// …
}
const handleSubmit = (e: React.FormEvent) => {
e.preventDefault();
// Track the sale event
trackSale({
eventName: "Purchase",
customerExternalId: "cus_RBfbD57H",
amount: 5000, // $50.00
invoiceId: "in_1MtHbELkdIwH",
});
};
return (
);
}
```
```html Other
Checkout
```
Here are the properties you can include when sending a sale event:
| Property | Required | Description |
| :------------------- | :------- | :----------------------------------------------------------------------------------------------------------------------------------------------------- |
| `customerExternalId` | **Yes** | The unique ID of the customer in your system. Will be used to identify and attribute all future events to this customer. |
| `amount` | **Yes** | The amount of the sale in cents. |
| `paymentProcessor` | No | The payment processor that processed the sale (e.g. [Stripe](/conversions/sales/stripe), [Shopify](/conversions/sales/shopify)). Defaults to "custom". |
| `eventName` | No | The name of the event. Defaults to "Purchase". |
| `invoiceId` | No | The invoice ID of the sale. Can be used as a idempotency key – only one sale event can be recorded for a given invoice ID. |
| `currency` | No | The currency of the sale. Defaults to "usd". |
| `metadata` | No | An object containing additional information about the sale. |
**When to track sale**
Track sale events only after a user successfully completes a purchase or payment-related action, such as:
* Completing a checkout or order
* Subscription payment
* Invoice payment
* Any paid trial or demo conversion
Ensure the event is triggered **only after the backend confirms the payment was successful**. This guarantees accurate sale data and prevents false or incomplete entries.
Client-side conversion tracking comes with some limitations: - **Ad
blockers**: Users with ad blockers may prevent tracking scripts from loading -
**JavaScript disabled**: Events won't be tracked if users have JavaScript
disabled - **Network issues**: Failed network requests won't retry
automatically - **Privacy concerns**: Some users may block client-side
tracking for privacy reasons For more accurate conversion tracking, consider
using [server-side conversion tracking](/api-reference/endpoint/track-sale).
## View conversion results
And that's it – you're all set! You can now sit back, relax, and watch your conversion revenue grow. We provide 3 different views to help you understand your conversions:
* **Time-series**: A [time-series view](https://app.dub.co/dub/analytics?view=timeseries) of the number clicks, leads and sales.
* **Funnel chart**: A [funnel chart view](http://app.dub.co/analytics?view=funnel) visualizing the conversion & dropoff rates across the different steps in the conversion funnel (clicks → leads → sales).
* **Real-time events stream**: A [real-time events stream](https://app.dub.co/events) of every single conversion event that occurs across all your links in your workspace.
