How do you audit email, SMS and ad tracking before a launch, and what breaks most?
Home › Articles › Seam 01: Spend to Attention › Pre launch tracking audit
Updated 2026-11-01
A pre launch tracking audit is a message by message test that every email, text, form and ad link in a launch records who clicked, from where, and what they did next. Before Coach Kyle's launch, Jon Weberg's audit found 20 of 57 messages broken, and repairing them first is how the attribution reconciliation seam starts clean.
- A pre launch audit tests every email, text, form, workflow and ad link before the first send.
- Before the Coach Kyle launch of 30 August 2026, 20 of 57 messages carried broken tracking and were repaired first.
- That launch produced 412 registered, 142 live, 37 applications, 30 calls booked and 4 closes at $6,800.
- Leaf Signal found 98% of 500 leading UK Shopify sites had at least one crucial tracking issue (BusinessCloud, 22 Sep 2026).
- 88% of those sites had missing parameters on live tracking events and 52% had core events missing entirely.
- The audit score is broken messages divided by all messages, and the launch sends at zero.
It is the night before your launch, the ads are approved and you built every message yourself, didn't you, so of the messages in your next launch, how many have you clicked on a phone this week, and how many will tell you where their registrant came from? You would rather find the broken link tonight than on Monday, wouldn't you, which is why you count the messages before you count the money.
What is a pre launch tracking audit?
A pre launch tracking audit tests each message, form and link in a launch for the data it must pass on. The Coach Kyle launch had 57 messages across 23 published workflows.
Your platform records whatever fires, and checking that what fires is right is what lets you see, the morning after, whether each name came from the ad, the second email or the third text.
How often is tracking broken before anyone checks?
Most tracking is broken somewhere before anyone checks it. Leaf Signal tested 500 leading UK Shopify sites and found 98% had at least one crucial tracking issue, as BusinessCloud reported on 22 September 2026. 76% had three or more critical issues. 52% had core events missing entirely. 88% had missing parameters on live tracking events.
Those brands watch one checkout while your registrant crosses an ad, a page, a form and two reminder channels, so which of the eight stages below has nobody tested since your last launch?
What do you check, in what order?
You check in the order a registrant moves: ad, page, form, confirmation, reminders, live room, follow up, booking.
- Ad: source, campaign and ad.
- Landing page: the same parameters after redirects.
- Registration form: source and campaign on the contact.
- Confirmation: contact ID and registration event.
- Reminder emails: source and campaign on every link.
- Reminder texts: source and campaign through the short link.
- Live room link: contact ID for attendance.
- Follow up and booking: the original source on the call.
Table 1. The launch path audit
| Stage | Message or asset | Must carry | How to test | Pass or fail |
|---|---|---|---|---|
| Ad | Destination URL | Source, campaign, ad | Phone preview | Pass if all arrive |
| Landing page | Registration page | Same parameters | Load from the ad | Pass if none drop |
| Registration form | Form | Source, campaign | Submit a test contact | Pass if both fill |
| Confirmation | Email and text | Contact ID, event | Read the timeline | Pass if logged once |
| Reminder emails | Every link | Source, campaign | Click on a phone | Pass if URL keeps both |
| Reminder texts | Every link | Source, campaign | Tap on a phone | Pass if URL keeps both |
| Live room link | Room link | Contact ID | Join as the test contact | Pass if attendance writes |
| Follow up and booking | Messages, calendar | Original source | Book a test call | Pass if the call shows it |
Stages five to seven also decide the show rate seam, so when the AI appointment confirmation employee sends your reminders, its links get the same phone test.
How do you test every link in an email or text?
You send each message to a test contact, click every link on a phone, and confirm the landing URL still carries its parameters. CampaignTrackly's checklist (Milena Mitova, March 2026) names three checks: the UTM parameters, a click on the tagged link, and the channel the visit lands in.
When a registrant arrives from your third reminder text, which field in the contact record says so, and have you watched it fill on a test contact, using one phone and the tapping you do every day?
How do you test forms and workflows?
You submit each form as a new test contact and read the contact record field by field. Trackingplan reports a case (David Pombar, March 2026) of 19 HubSpot workflows overwriting UTM parameters.
How many of your forms write the source to the same field, and which workflow rewrites the original source after the first touch, leaving a webinar registrant who seems to come from nowhere until you open the field you never opened?
What breaks most often?
Redirects that drop parameters, workflows that overwrite the original source, and duplicate forms that write to different fields break most often. CampaignTrackly checks redirects; Trackingplan's case shows overwrites. The Coach Kyle audit of 24 August 2026 covered 57 message actions: 29 emails and 28 texts.
- 20 were repaired: 10 emails and 10 texts.
- Each was a link that reached its page without a consistent source contract.
- Each now runs through a tracked link with one value per UTM field.
- Click tracking is on; automatic UTM generation is off.
- 19 link bearing emails were already correct; 18 texts carry no link.
If 20 of 57 messages broke in one launch, half of them texts, how many of yours would?
How do you score the audit?
The audit score is broken messages divided by all messages; 20 of 57 is 35% (computed). The launch sends at zero.
Table 2. Audit score
| Measure | Value |
|---|---|
| Messages total | 57 |
| Broken | 20 |
| Repaired | 20 |
| Score before (computed) | 35% |
| Score at send | 0% |
What will your registration to call booked rate be if the source field is blank on a third of your registrants? A score turns that unease into a line you watch fall one repair at a time until it reads zero, and a Seam Map of your launch draws the same line across every handoff to the paid invoice.
Who owns the audit?
The person who will report the launch numbers owns the audit, because they inherit every broken field. Seam 01, spend to attention, has no owner until one is assigned.
Who reads the contact record of the first test registrant before the ads go live? Your ad buyer and builder are both capable, nobody owns the handoff between them, it writes as a rate like 20 of 57, and that rate sits on nobody's dashboard, which passes the four tests of a seam, so one name on the audit closes the seam.
What happened at a launch that was audited first?
Coach Kyle's live launch of 30 August 2026 produced 412 registered, 142 live, 37 applications, 30 calls booked, 4 closes at $6,800, after 20 of 57 messages with broken tracking were repaired first.
Picture your morning after with registrations, live count, applications and calls booked lining up in one sheet, the discipline Jon Weberg built into the CRM a $70,000,000 a year business is running on, still running today, which the case studies show launch by launch. A repaired launch still needs matching Meta conversions to paid invoices after the launch, and the audit gives that match clean inputs.
When you want your next launch to send at zero, the install carries a guarantee of triple the fee, conditioned on proper tracking and reporting being in place.
- Click Book My AI Seam Architect Install.
- Bring the list of every message in your next launch.
- On the call, Jon Weberg scores it and names the broken ones.
What else do launch teams ask?
How many days before a launch do you run the audit?
Run it after the last message is built and before ads go live, then again on the first live registrant. A launch that changes one message after the audit needs that message retested. Fixing a broken message before send costs minutes; after send, the data from that send is gone.
Why do results jump after tracking is repaired?
Repaired tracking records results that were already happening. Trackingplan reports a case where measured purchases rose 288% after a broken implementation was fixed, and the author says the gain was previously invisible results (13 Mar 2026, no sample stated).
Do I need a tracking tool for the audit?
No. A test contact, a phone and the contact record cover email, text and form tracking. Tools help at scale. The audit is a list of messages with a pass or fail beside each one.
What is the most common UTM mistake?
Inconsistent naming. CampaignTrackly shows spring-sale, spring_sale, SpringSale and spring2026_sale reporting as four separate campaigns (6 Mar 2026). Pick one naming rule and check every link against it.
Should SMS links carry UTM parameters?
Yes, through a shortener that keeps them. Text messages are the channel most often left untagged because the link is shortened. Click it on a phone and confirm the landing URL still carries source and campaign.
What does the audit not catch?
It does not catch a platform claiming a buyer another platform also claims, or a refund the ad account never hears about. Those are reconciliation problems, matched after the launch against paid invoices.
Jon Weberg is the founder of Profitalize and the originator of The Thirteen Seams, a revenue diagnostic that finds the money a company loses in the handoffs between its teams. About Jon Weberg

