Dynamically embed marketing or affiliate tracking codes within your registration page URLs, calls to actions, etc.
Use the five tracking variables — v1 , v2 , v3 , v4 , and v5 — to pass affiliate IDs, lead sources, campaign IDs, referral values, or other attribution data through a webinar registration link.
Each variable can hold unlimited unique values. For example, you can use v1 for affiliate IDs and use it to track thousands of different affiliates. The value captured during registration can then be reused in supported attendee-facing content, including Call to Action links.

Step-by-Step Configuration Instructions
Step 1: Choose a Tracking Variable
- Assign one variable to the value you want to track, such as an affiliate ID or lead source.
- Record the assignment so you use the same variable consistently.
- Use the exact lowercase token name.
| Variable | Example use |
|---|---|
v1 |
Affiliate ID |
v2 |
Lead Source |
v3 |
Campaign or partner ID |
v4 |
Referral value |
v5 |
Additional tracking value |
The five-variable limit is not a five-value limit. Each variable can contain unlimited unique values.
Step 2: Add the Tracking Variable to the Registration URL
- Start with the registration page URL:
https://joinnow.live/s/1234
- Add the first query parameter with
?:
https://joinnow.live/s/1234?v1=AFFILIATE-123
- In the affiliate or marketing platform, replace
AFFILIATE-123with that platform’s merge field. The completed link template will look similar to this, but the merge-field syntax varies by platform:
https://joinnow.live/s/1234?v1={AFFILIATE_ID}
- If the registration URL already contains a query parameter, add the tracking variable with
&:
https://joinnow.live/s/1234?source=email&v1={AFFILIATE_ID}
- Generate the links through the external platform so each affiliate, campaign, or source receives its own value.
If the registration flow uses an embed, custom HTML page, third-party page, redirect, or API, verify that the full query string or equivalent link-parameter data reaches the registration request. Otherwise, the value may not be available when the Call to Action is rendered.
Step 3: Add the Matching Value to a Call to Action Link
- Navigate to Webinar Editor > Customize > Calls to Action.
- In Calls to Actions, complete the blank Call to Action form or click Edit for an existing Call to Action in the table.
- In CTA Name, enter an internal name for the Call to Action.
- In CTA Type, select Text/HTML.
- Configure the Call to Action’s start time, duration, and location as needed.
- In Message, enter the text that should be clickable.
- Highlight the text and click the link control in the editor toolbar.
-
Enter the destination URL with the matching tracking token. Keep the token exactly as written; do not replace it with one specific affiliate’s value.
If
v1contains the affiliate ID, use:
https://awesomesite.com/yourproduct?affiliate={v1}
If the destination URL already contains a query parameter, use & for the tracking parameter:
https://awesomesite.com/yourproduct?plan=pro&affiliate={v1}
Here, affiliate is the parameter name expected by the destination platform, and {v1} is the StealthSeminar tracking token.
The current editor does not display a separate Template Tag Builder in this CTA field. Enter the token directly in the link URL and verify it with a real attendee test.
- Click Add in the link dialog.
- Click Save in the CTA editor.
You can use the same pattern with v2 –v5 or supported UTM tokens, such as {utm_source} and {utm_campaign} , when those values are present in the registration URL.
Step 4: Configure Additional Tracking Values
- Use a different variable for each category you want to keep separate. For example, use
v1for Affiliate ID andv2for Lead Source. - Add the matching query parameter to the registration link.
- Add the matching token to the Call to Action destination URL.
- Keep the destination parameter name aligned with the system receiving the value.
Do not create a new variable for every affiliate. Use one variable, such as v1 , and let the affiliate platform supply a different value for each affiliate link.
Prerequisites and Upstream Requirements
Before you begin:
- Open the webinar you want to promote.
- Copy the webinar’s registration page URL.
- Decide what each tracking variable represents. For example, use
v1for an Affiliate ID andv2for a Lead Source. - Confirm the merge-field syntax used by the marketing or affiliate platform that will generate your links.
- Prepare the destination URL that the Call to Action should open.
- Use a real test registration when verifying attendee-specific values. A preview does not create a normal attendee context.
Verification Gateway
Complete this test before launching the campaign.
- Create a test registration URL with a recognizable value:
https://joinnow.live/s/1234?v1=TEST-AFFILIATE-001
- Open the URL in a private browser window.
- Register with a new test email address.
- Join the attendee watch experience.
- For a recorded Call to Action, wait until its configured start time. For a live Call to Action, navigate to Live Webinar Console > Calls to Action and turn it on.
- Open the Call to Action link from the attendee view.
- Inspect the final destination URL and confirm that it contains the resolved value:
https://awesomesite.com/yourproduct?affiliate=TEST-AFFILIATE-001
- Repeat the test with a second value to confirm that the link is dynamic rather than hard-coded.
- If the destination platform provides conversion reporting, confirm that it received the same value.
The Call to Action preview is useful for checking layout and link formatting, but it is not a substitute for a real attendee test. Missing v1 –v5 or UTM values resolve to a single blank space in the current renderer.
Common Issues & Solutions
| Symptom | Root Cause | Resolution |
|---|---|---|
| The CTA preview does not show the real tracking value. | Preview mode does not represent a real attendee context. | Create a test registration from a URL containing the tracking parameter and test from the attendee watch experience. |
The destination contains affiliate= but no value. |
The attendee did not register with v1 , or an embed, redirect, or third-party registration flow removed the parameter. |
Check the original registration URL and verify that the complete query string reaches the StealthSeminar registration request. |
The destination still contains {v1} . |
The token was entered in a field that does not process tracking tokens, or the CTA content was not saved. | Confirm that the token is in the CTA link URL, click Add in the link dialog, click Save, and retest with a real registration. If it remains literal, escalate with the webinar URL and test steps. |
| The CTA saves but the destination URL is malformed. | The query-string separator is incorrect. | Use ? for the first query parameter and & for additional parameters. |
| Different affiliates produce the same value. | The registration links use a hard-coded value, or the external platform is not supplying different values. | Compare two generated registration URLs and confirm that each contains the intended value. |
| The affiliate platform does not credit the sale. | The final URL uses a parameter name or merge field that does not match the external platform’s configuration. | Compare the final destination URL with the platform’s required parameter name, then update the external link template or CTA URL. |
| The CTA is not visible during testing. | Its timing, duration, location, availability, or live activation is incorrect. | Review the CTA settings. For live content, navigate to Live Webinar Console > Calls to Action and turn it on. |
| The expected value is not available in a connected marketing tool. | The registration path or integration does not pass the stored link parameters through to that tool. | Confirm the registration source, inspect the registration data, and verify the integration’s supported fields before escalating. |