How to Set Up the Sales Tracking Pixel

The Sales Tracking Pixel records a conversion when a visitor reaches a conversion page after completing a desired action, such as purchasing a product, scheduling a call, completing an application, or registering for a follow-up event.

The generated image snippet sends the webinar ID, attribution mode, and conversion value to StealthSeminar. The conversion can then be reflected in the webinar’s Stats view.

Conceptual workflow illustration. This image is not an exact product screenshot.

Step-by-Step Configuration Instructions

Step 1: Choose the Correct Attribution Mode

Choose the pixel type based on how your conversion page is used.

Conversion-page scenario	Pixel to use	Result
The page is shared across multiple webinars or receives non-webinar traffic	Tracking with Attendee IP Confirmation	Records the conversion only when the request IP matches an attendee or attendee event for that webinar
The page is dedicated to one webinar, and unmatched conversions should still be recorded	Tracking without Viewer IP Confirmation	Allows the conversion to be recorded without requiring an attendee match; the conversion may be anonymous

IP confirmation is an attribution method based on the request IP address. It is not proof of identity.

Step 2: Open Sales Tracking Pixel

Navigate to Customize Your Webinar > Advance setup.
Expand Sales Tracking Pixel.

The current V2 editor uses the exact tab label Advance setup. The Sales Tracking Pixel settings appear as an accordion section within that tab.

Step 3: Enter and Save the Conversion Value

Enter the value to report for one conversion, such as 97 or 499.00 .
Use a non-negative number with no more than two decimal places.
Click the lowercase update button beside the value field.
Wait for the save to complete before copying either pixel snippet.

The V2 field uses a 0.01 step, while the /conversion endpoint validates the val parameter as a non-negative number with a maximum precision of two decimal places. Use this format consistently.

If you change the value later, save it first and copy a fresh snippet. Do not manually edit the generated value or webinar ID.

Step 4: Copy the Generated Pixel Snippet

Copy the option that matches the attribution mode selected in Step 1.

The IP-confirmed snippet follows this structure:

<img src="<CONFIGURED_WEBINAR_API_BASE>/conversion?id=<WEBINAR_UUID>&confirmIp=true&val=<VALUE>" />

The non-confirmed snippet uses confirmIp=false :

<img src="<CONFIGURED_WEBINAR_API_BASE>/conversion?id=<WEBINAR_UUID>&confirmIp=false&val=<VALUE>" />

Copy the snippet exactly as generated. Do not change:

The webinar ID
The confirmIp parameter
The val parameter
The configured API base URL

The application generates these values automatically. [4]

Step 5: Add the Snippet to the Final Conversion Page

Open the external page visitors see after the purchase or other conversion action is complete.
Add the copied snippet as raw HTML or through the page builder’s HTML/image element.
Publish the page or save the thank-you-page configuration.
Confirm that the snippet is present on the final page the visitor reaches, not only on a checkout form, preview page, or intermediate step.
If the same page serves multiple webinars, keep each generated snippet associated with the correct webinar and test each flow separately.

When the browser loads the image, it sends a GET request to the /conversion endpoint. StealthSeminar processes that request and returns the tracking-pixel image.

Step 6: Review Conversions in Stats

After completing a controlled conversion and allowing time for the normal Stats refresh or indexing process:

Open the webinar’s Stats view.
Review the overall conversion count.
Review the total dollar value.
Check attendee or registrant-level reporting when applicable.

A non-confirmed conversion that cannot be matched to an attendee may contribute to overall totals without appearing under a specific attendee. Anonymous conversions may also be absent from some attendee- or webinar-instance-specific views.

Additional Help Topics

Prerequisites and Upstream Requirements

Before configuring the Sales Tracking Pixel:

Identify the exact action that should count as a conversion.
Use the page displayed after that action is complete. Do not place the pixel on the registration page, checkout form, webinar page, or a general public page unless those visits are intentionally being counted as conversions.
Confirm that the page builder, checkout platform, or thank-you-page editor can render raw HTML or an HTML/image element.
Decide whether the conversion page is shared across webinars or receives unrelated traffic.
Choose a non-negative conversion value with no more than two decimal places.
Do not test by directly opening your own live thank-you URL. Loading the pixel is itself a conversion request and can affect webinar statistics.

Controlled Test and Verification

Use a dedicated test webinar or a controlled test transaction. Do not validate the pixel by repeatedly opening the live thank-you page.

Confirm that the saved pixel value matches the snippet’s val parameter.
For an IP-confirmed test, register a test attendee and verify that the final request uses the same public IP or matching attendee-event path.
For a non-confirmed test, registration is optional, although an attendee match may still be used when one exists.
Complete the controlled test action and allow the browser to reach the exact published thank-you page.
Open browser developer tools before completing the test.
Select the Network panel and filter for conversion .
Confirm that the browser sends a request to /conversion with the expected id , confirmIp , and val values.
Confirm that the request returns the tracking-pixel response.
Allow normal Stats refresh or indexing time, then open the webinar’s Stats view.
Confirm that the overall conversion count and dollar total reflect the controlled test.
If attendee attribution is expected, verify that the conversion is associated with the intended attendee.
Avoid refreshing the thank-you page repeatedly.

A successful HTTP response confirms that the endpoint was reached, but it does not by itself prove that a conversion record was created. IP confirmation may reject the conversion, or the webinar and request IP may already have an existing conversion. Current deduplication is based on the webinar ID and request IP, not an order ID or transaction ID.

Pass criteria: The expected /conversion request is visible, the parameters are correct, the endpoint returns the pixel response, Stats reflects the conversion after refresh or indexing, the value is correct, and attendee attribution matches the selected mode and test conditions.

Common Issues & Solutions

Symptom	Root Cause	Resolution
No `/conversion` request appears	The snippet is missing from the final page, the wrong page was published, or the page builder stripped the HTML.	Inspect the final page DOM or source for the `<img>` element. Confirm that the page is published and that the page builder allows custom HTML.
The request appears, but no conversion is recorded with `confirmIp=true`	The request IP did not match an attendee or attendee event for that webinar.	Confirm that the test attendee belongs to the same webinar. Review attendee and viewing-event IP conditions, and check whether a proxy, CDN, or checkout provider changed the request IP.
The request succeeds, but Stats does not change	The request reached the endpoint, but IP confirmation may have rejected attribution, the webinar/IP pair may already have been deduplicated, Stats may not have refreshed, or the view may be filtered.	Check overall webinar totals, allow time for refresh or indexing, confirm the selected `confirmIp` mode, and capture the timestamp, webinar ID, and parameters for Support.
A conversion is recorded without an attendee	The non-confirmed pixel was used and no attendee or attendee-event match was found.	Confirm that anonymous attribution is acceptable. If attendee attribution is required, verify the request IP and proxy path. Do not expect an unmatched conversion to appear under a specific attendee.
The conversion value is zero or incorrect	The snippet was copied before the value was updated, `val` is incorrect, or the value format is invalid.	Navigate to Customize Your Webinar > Advance setup > Sales Tracking Pixel, enter the correct value, click update, copy a fresh snippet, replace the old snippet, and run one controlled test.
A shared thank-you page credits the wrong webinar	The page contains a snippet with the wrong webinar ID, uses non-confirmed tracking on mixed traffic, or is missing the webinar-specific snippet.	Compare every snippet’s `id` with the intended webinar. Use IP confirmation for shared or mixed-traffic pages, and test each webinar flow separately.
Repeated visits appear to create extra conversions	Multiple snippets are firing, the page is used for multiple webinar IDs, or requests come from different IPs.	Inspect the page for duplicate snippets. Filter Network for every `/conversion` request, compare the webinar ID and request IP, and stop testing on the live conversion page.
Multiple legitimate purchases from one IP are not counted separately	Current deduplication is based on webinar ID and request IP, not order ID or transaction ID.	Do not assume the pixel supports order-level deduplication. Document the purchase flow and escalate the requirement for separate same-IP conversions.
The feature is not visible	The account may be using a different editor version, or the user may not have webinar-scoped edit access.	Confirm that you are using the current V2 editor and that you have permission to edit the webinar. If Sales Tracking Pixel is still unavailable under Customize Your Webinar > Advance setup, contact Support.

Privacy and Data Handling Notes

The conversion URL includes the webinar identifier, confirmation mode, and conversion value. The conversion request also includes the request IP and user agent, and the conversion record may store an attendee association.

Do not place names, email addresses, order numbers, access tokens, or other personal data in the pixel URL. Review the conversion page’s privacy and consent notices according to your organization’s requirements.