How to Track Website Visitors When Your Site Was Built With AI

Add a tag manager, then route its data through your own server. AI builders like Cursor, Lovable, Bolt and v0 either install client-side Google Analytics or skip tracking entirely, and client-side is where the losses happen. Ask your AI to add Google Tag Manager if it isn't there, then point that container at a server-side container running on your own subdomain.

The form worked and the tracking request didn't. Ad blockers and browser privacy features block requests to known analytics domains while leaving your form endpoint alone, so the submission lands and the event never fires. This is the most common symptom of client-side-only tracking, and it is why ad platforms undercount conversions on sites that look like they're working fine.

Yes, in the EU, UK and a growing number of US states. Moving tracking server-side changes how data travels, not whether you had permission to collect it. Under GDPR and ePrivacy rules, analytics cookies must be blocked until the visitor agrees. A banner that displays a message without actually blocking scripts is not compliant, whatever your tracking setup looks like.

Not entirely. Server-side tagging still sets cookies, but it sets them from your server rather than from JavaScript in the browser. That matters because Safari's tracking prevention caps script-set cookies at seven days, while server-set first-party cookies last longer. You get more accurate returning-visitor counts, though you are still processing personal data and still need consent.

Usually it speeds it up. Moving tags off the browser means fewer third-party scripts loading on the page, which cuts render-blocking requests and JavaScript execution time. The tradeoff sits on your side of the wire instead: you take on a server that processes the requests, handled either by a cloud instance you manage or by a provider that bundles the infrastructure.

Cost tracks request volume, so it scales with your traffic rather than being a flat fee. Self-hosting on Google Cloud means paying for the instance directly, while managed providers fold the infrastructure into a subscription. For a small site running a few thousand sessions a month, it is typically the smallest line item in a paid ads budget.

No. It fixes collection from the day you switch it on, and nothing before that is recoverable. That matters when you're judging past campaign performance, because those historical numbers stay understated permanently. Give the ad platforms two to four weeks of clean data before comparing results or making bidding decisions on the new figures.

Yes, on any platform that lets you install Google Tag Manager and add a DNS record. The setup is identical everywhere: a client-side container on the site, a server container on a subdomain such as insights.yourdomain.com, and a CNAME record pointing one at the other. On WordPress, a plugin handles the GTM installation step.