Why Your Website Builder Can't Tell You Where Your Leads Came From (And What Conversion Tracking Actually Requires)

Somebody in your office is spending money on ads right now. Google Ads, maybe Meta, maybe both. The phone rings. A form gets submitted. Someone books a tour or a consultation. Someone gives online.

Now ask the question underneath all of it: which ad produced that? Which page did they read first? Which search brought them in?

Most small business owners, church admins, and nonprofit directors I talk to can't answer that. Not because they're bad at their jobs. Because website builder conversion tracking, the ability to trace a lead back to the ad or page that produced it, was never built into the platform they're standing on.

There's nothing wrong with the platform. Wix, Squarespace, Tithe.ly, Subsplash: they do real work, and for a lot of sites, what they document is genuinely enough to run on. But here's the deal. Running a website and answering "where did that lead come from" are two different bars, and most builders clear the first one without touching the second.

A website builder can tell you how many people visited your site last month and roughly where they came from, search, social, a direct link. What it usually can't tell you is which specific page, ad, or search term produced the call, the form, the booking, or the gift, because the events that count as a lead are either undocumented, locked behind a paid tier, or happening inside another company's iframe, a page loaded inside your page that your own analytics can't see into.

None of that means switching platforms. It means knowing exactly where the gap sits, and what closing it actually requires.

Traffic Is Not Leads

Every builder on the market can show you a number that goes up. Visitors, sessions, page views. That number feels like progress, and in a way it is.

But traffic is not leads. A visitor is someone who showed up. A lead is someone who called, filled out a form, booked something, or gave. The distance between those two words is where most tracking quietly fails.

Three questions worth asking yourself honestly:

• Can you say which page someone was reading right before they called you?
• Can you say which ad, if any, produced last week's form submission?
• Can you say whether last month's gift came from an email, a retargeting ad, or someone who just typed your name into Google?

If you answered no to any of those, you're not alone, and you're not behind. In our experience auditing sites, somewhere between 65 and 80 percent have no events configured at all, mostly because nobody told the owner they needed them. You're running a site that reports traffic without reporting leads. Whether your SEO is working at all is the earlier question, one we've walked through in how to check if your SEO is working. Once people are showing up, the next question is what they actually did once they got there.

What Is a GA4 Key Event?

A GA4 key event is Google's own name for the moment on your site that actually matters, not just a visit. Google defines it plainly: "An event that measures an action that's particularly important to the success of your business." In practice, that means a phone tap, a form submission, a completed booking, a gift.

Key events matter because of what happens next. Google says it directly: "You can create a conversion in Google Ads from a Google Analytics key event." No key event set up in GA4 (Google's free analytics tool) means no conversion in Google Ads, which means your ad platform never learns which ads actually produce leads instead of just clicks.

Most website builders will get you GA4 installed. Almost none of them walk you through defining the key events that make that installation worth anything. A website and SEO audit checks whether yours are even wired up before you spend another dollar chasing clicks that can't prove themselves.

Can Wix or Squarespace Track Where My Leads Came From?

Wix and Squarespace are the two builders on this list that document any real path from a form to a Google Ads conversion. Here's the honest state of each, straight from their own help documentation.

Wix:

• Paid plan and a connected domain, required. GA4 connects through Wix's Marketing Integrations panel, but only on a Premium plan with your own domain attached, not the free site.
• A lead event fires on forms. Wix fires its own "lead" event when someone submits a form or starts a chat.
• Phone and email taps aren't documented. Wix doesn't list a phone tap or an email click as a trackable event.
• Better ad matching takes custom work. Sending richer match data to Google Ads means renaming fields in Velo, Wix's own code editor, plus custom code or Google Tag Manager (a free Google tool that manages tracking code without a developer touching the site every time). Not a setting you flip.

Squarespace:

• Code injection needs Core and up. Code injection means pasting a tracking script straight into your page's code, and it's how Tag Manager gets installed. That takes a Core, Plus, or Advanced plan, and Squarespace says code-based tools like it fall outside what they support.
• A form redirect works as your thank-you page. Point a form block to redirect after submission to a page on your own site, and that page becomes a destination GA4 can count as a key event.
• The built-in conversions panel skips your biggest actions. Squarespace's own Form and Button Conversions panel doesn't track checkout forms, donation forms, or nav and banner buttons, and there's no documented connection from it to GA4 or Ads.
• There's no analytics export. In Squarespace's own words: "It's not possible to export analytics data at this time."

Tithe.ly Sites and Subsplash:

• GA4 install is documented. Tithe.ly takes a measurement ID in a settings field; Subsplash takes one through code injection in the header.
• Almost everything past that is not documented. Neither platform publishes anything on Tag Manager, form events, phone or email taps, Google Ads conversion import, or data export.
• Giving lives somewhere else. Both point giving at a separate address, either embedded or linked out, and neither documents whether that connects back to your site's own analytics.

Why Does My Giving or Booking Page Break My Tracking?

Because the moment someone actually gives or books, they usually aren't on your page anymore, even though it looks that way.

An iframe is a page loaded inside your page. It looks like part of your site, but it's actually a separate document served from a separate company's domain, give.tithe.ly instead of your own church's address, for example. Your GA4 tag lives on your page. It has no way to see what happens inside a window from someone else's house.

A standalone giving or booking link works the same way, without the window dressing: click it, and the visitor leaves your domain entirely for the vendor's.

Google Analytics has a fix for this: cross-domain measurement, which tracks one visitor across two domains. It takes installing the same tag, with the same ID, on both. You can do that on your own site. You generally can't do it on a giving vendor's platform, because you don't control their code. Google's own documentation is blunt about what happens without it: one visitor moving across two domains counts as two separate users and two separate sessions. Your dashboard and the vendor's never meet in the middle.

In practice, once a flow leaves your site you're at the mercy of what that other system already fires. One client of ours runs a separate quoting system that won't let us add custom events at all. Normally that would sink attribution. That platform happened to fire a conversion on every form submission, which gave us enough to narrow down who was actually requesting quotes. We've also hit plenty of third-party tools with zero conversion events and no way to add one, and that makes running ads effectively impossible. Check this before you sign with any tool that sits in your lead path.

The Four Things Nobody Sees

Four things go dark on almost every builder:

• Phone taps. Undocumented on every platform here.
• Email taps. Same story. Someone taps your email address, and nothing records it.
• Off-site giving. It's reported in the vendor's dashboard, not yours, with no documented bridge back.
• The ad that started it. No key event, no real conversion, so Google Ads and Meta spend toward clicks instead of leads.

I've made this mistake myself. In the excitement of launching my first ad, I pushed it live without a thought about conversions. A hundred dollars in, I realized I had zero, because I'd never set them up on the website. Google had no data to tell whether the ads were leading to a single sale. I wrote the whole thing up in what I learned running my first Google ad.

None of that means your platform failed you. It did exactly what it documented, and stopped there.

What Does Website Builder Conversion Tracking Actually Require?

Real conversion tracking requires a short list of things, and every one of them has to exist before launch, not get added later once someone notices the gap.

• Key events defined up front. Every action that counts as a lead, call tap, form, booking, gift, named and set up in GA4 before the site goes live.
• Thank-you states you control. Every form, booking flow, and giving click ends on a page or a moment you own, one your own tag can see and count.
• The tag on both sides of every hand-off. If a flow leaves your domain, cross-domain measurement has to be set up on both ends, not just yours.
• Google Ads and Meta fed from the same events. One set of key events, imported into both ad platforms at once, so they're optimizing toward the same real leads instead of guessing separately.
• Search Console and Google Business Profile read alongside it. Google Business Profile reports calls, directions, and clicks on its own, separate from site analytics. Read together, they tell the whole story.
• A durable export. GA4's BigQuery export is available on standard properties, up to a million events a day, and it means your data outlives any platform decision you make later.

What This Looks Like When It's Built In

Every custom website we build ships with all six of those in place before launch: GA4 key events for plan-a-visit, contact, call taps, email taps, and giving clicks, conversion import to Google Ads and Meta together, Search Console verified, Google Business Profile linked, and giving or booking integrated so the click is measured on your own domain before the hand-off to a vendor happens. Content lives in NewCulture Studio, our own CMS, so your team can update pages without a developer touching the tracking underneath.

The way we wire it is simple on purpose. Each key action fires a direct event to Google through a small custom function on our hosting provider, no tag soup in the page. The same function sends the same event to Meta Ads at the same time, so there's no second system to manage and nothing to reinvent. Adding a new event later is one small change, and it shows up in both ad platforms on its own. Running Google and Meta from the same events also means you can see which actions are actually turning into conversions across both, and shift spend with confidence instead of guesswork.

A School Story

A Raleigh-area school came to us spending thousands a month on ads, and their builder site couldn't say which ad had produced a single tour request. Once we had real tracking live, we saw the actual problem: their conversions had been mapped to page views, not to the things that mattered, like a tour or enrollment form submitted or a phone call placed. Everyone who clicked an ad counted as a conversion. That's ad spend sprawl, and it's impossible to optimize, because Google was being told every click was a win. Retrofitting proper tracking into the platform they were on turned out slower than rebuilding, so we rebuilt with tracking in from the start, and their ad spend could finally lean toward people ready to schedule a tour.

If your church might be at that same point, here are the signs, and here's why ownership matters as much as design. We build the same way for churches and nonprofits: church websites with tracking wired in, and nonprofit websites built to show a board where donations actually come from. For teams who want the build handled and kept up week to week, that's Fully Managed Publishing, from $795 a month.

If You're Staying on Your Builder

Staying on your current platform is a legitimate choice, and to their credit, Squarespace and Wix come out ahead of the church-specific platforms here. Both let you add custom JavaScript, and Wix adds custom components on top, so you can set the events you need to fire. It's a little clunky, but it beats a platform with zero event configuration. If you're staying, fix these in order.

• Upgrade to whatever tier gives you GA4 or Tag Manager. Nothing below it is worth building on.
• Install GA4 and name your key events. Don't stop at the tracking code. Mark every call, form, booking, and gift that counts as a lead.
• Redirect every form, booking, and giving flow to a thank-you page you control. That's what lets GA4 count the action.
• Check Google Business Profile Insights, and ask your giving or booking vendor for their own reporting. Neither shows up in your site analytics. Both will tell you plenty if you go ask.

If you're a church and the honest issue isn't the platform but what's been built on top of it, church website optimization fixes tracking and the rest without a full rebuild. Either way, a website and SEO audit will tell you plainly what's missing before you spend another dollar guessing.

Your Next Step

Open GA4 today. Go to Admin, then Events, and count how many are marked as key events.

If that number is zero, you've found the real problem, before you spend another dollar guessing at it.

You don't have to fix everything this week. You have to know that number. Write it down, and take the smallest next step from where you actually are. I believe you can get this figured out, and your ads deserve the chance to prove what they're actually doing.