How to Set Up Forms, Analytics, and Conversion Tracking Before Launch
Set up and test form submissions, GA4 events, GTM, Search Console, conversion goals, phone links, email routing, and post-launch monitoring.
Launching with tracking that doesn't work costs more than any ugly hero section ever will. A form that silently fails or a conversion event that never fires means you're flying blind on the one thing a marketing site exists to do: capture and measure demand. And these failures are invisible until you go looking, which is usually a month and a lot of lost leads too late.
We set up and test the full conversion stack before every launch. It's unglamorous and it's where real money is won or lost. Here's the sequence.
Tracking is part of the product, not an afterthought
Treat analytics and forms as launch-blocking deliverables, not a "phase two" task. A site that looks finished but can't prove a single lead reached the inbox isn't finished. The work below is small if you do it before launch and painful if you reconstruct it after a campaign already ran on broken tracking.
Define the events that signal intent
Start by listing the actions that actually indicate buying intent, not every click. For B2B that usually means form submit, demo request, pricing CTA click, phone tap, and a few high-intent outbound clicks like a security PDF or case study download. Pick three to five meaningful events, not forty micro-events nobody will ever review. Clarity here keeps your analytics legible later.
Install tags the right way for your team
Add GA4 either directly via gtag or through Google Tag Manager. Use GTM when marketing needs to add and edit tags without a developer deploy; use direct gtag when the stack is simple and developers own every change. Either is fine. What matters is that you document what's live and can verify it. There's no universally correct answer, only the one that fits who maintains tracking.
Wire events to real interactions
Connect your defined events to the actual interactions: form submissions, CTA clicks, phone taps, and email clicks. The common failure is assuming a tag "covers" an event it never actually listens to. Wire each one deliberately and label it clearly so the data is readable in GA4 without a decoder ring.
Test that forms actually deliver leads
This is the step teams skip and regret. Submit each form from both mobile and desktop with a realistic test payload, then confirm the lead lands in the CRM or inbox within about sixty seconds. Check the spam folder and any CRM automation rules that might silently discard a test submission. A form that posts a success message but delivers nothing is the single most expensive silent failure on a marketing site.
Connect Search Console early
Connect Search Console before launch if the domain already exists. Baseline data is worth having. At minimum, verify the property and submit your sitemap within 24 hours of DNS cutover. Waiting weeks means you're blind to crawl issues exactly when they're most likely to appear.
Monitor after launch
Tracking setup doesn't end at go-live. Watch GA4 realtime, Search Console, and the actual lead inbox in the first hours and days. Confirm events fire from real visitor traffic, not just your test clicks. Real users behave differently than your QA pass, and the first day of traffic is when remaining gaps surface.
| Step | Verify before launch |
|---|---|
| Events defined | 3–5 intent actions named |
| Tags installed | GA4 direct or GTM, documented |
| Events wired | Forms, CTAs, phone, email tracked |
| Delivery tested | Lead reaches CRM/inbox in ~60s |
| Search Console | Verified, sitemap submitted |
What to do next
List your three to five intent events this week and test one form end to end today. You'll likely find something. If you'd rather launch knowing every lead path works, Metamatter sets up and verifies the full conversion stack as part of every launch.
Write down what working means
Tracking quietly breaks over time: a form plugin updates, a tag gets removed, a CRM rule changes. Protect yourself by documenting the working state at launch: which events fire, where each form delivers, and how to test each path in under five minutes. Store it where the next person will find it, not in one engineer's memory. Then schedule a recurring check (monthly is plenty) to resubmit a test lead and confirm events still land. The teams that never lose leads aren't lucky; they treat tracking like any other system that needs monitoring. A documented, re-testable setup turns "I think analytics is fine" into something you can actually prove the next time someone asks where the leads went.
FAQ
GA4 direct or Google Tag Manager?
GTM when marketing will add tags without deploys. Direct gtag when the stack is simple and developers own all changes. Either works: document what's live and test in DebugView.
What counts as a conversion event for B2B?
Form submit, demo request, pricing CTA click, phone tap, and high-intent outbound clicks like a security PDF or case study. Pick three to five, not forty micro-events nobody reviews.
How do we verify forms actually deliver leads?
Submit from mobile and desktop with a test payload. Confirm CRM or inbox receipt within sixty seconds. Check the spam folder and CRM automation rules that might discard tests.
When should Search Console be connected?
Before launch if the domain exists: baseline data helps. At minimum within 24 hours of DNS cutover with the sitemap submitted.
