More and more sites are being built with AI tools like Lovable, Bolt, Replit and v0. Seeka works great on these sites. The AI-Built App install gives you a ready-made prompt to paste straight into your AI tool, plus a fix for the one habit AI builders have that can silently break your tracking.
⚠️ The golden rule: every form needs a unique form ID and every important button needs a stable, descriptive class name. Without these, Seeka can't bind events to them and your lead tracking will silently fail. Seeka gives you a ready-made prompt to fix this (Step 2 below).
Before you start
You'll need:
Access to your AI builder project (Lovable, Bolt, Replit, v0, or any other AI code tool)
Access to your Seeka account
Step 1 - Copy the install prompt into your AI tool
Log in to your Seeka account
In the left-hand menu, click Apps
Search AI-Built App and click Connect
Click Copy prompt - this copies the install prompt and your Seeka tracking script to your clipboard
Paste it into your AI tool's chat and let it apply the change
Once your AI tool has applied the change, deploy your app for the tracking to go live
Step 2 - Fix your form classes (recommended)
It's common for AI tools to generate forms and buttons with generic or missing class names. If you're planning to track form submissions or button clicks with Seeka, use the second prompt on the setup screen:
On the same Seeka setup screen, click Copy form fix prompt
Paste it into your AI tool and let it apply the changes before you set up events
Deploy again so the fixed identifiers are live
Why this matters
Seeka tracks events like Lead and Sign Up by binding to specific elements on your page. It watches for a submit on this form or a click on this button. To do that, it needs a reliable way to tell your elements apart, and that's exactly what a unique form ID or a stable button class provides.
AI builders often generate code that breaks this in three ways:
No IDs at all. Forms are generated as plain
<form>elements with nothing to identify them. Seeka has no selector to bind to, so a form-submit event can never be attached.Duplicate or generic identifiers. Every button gets the same auto-generated styling classes and every form looks identical. Seeka either can't tell which element you mean, or binds to the wrong one, your newsletter form fires your "contact sales" event, or nothing fires at all.
Identifiers that change on every regeneration. Some builders regenerate class names each time you make a change. The selector Seeka bound to yesterday no longer exists today, and tracking quietly stops.
The form fix prompt tells your builder to give every form a unique, permanent ID and every important button a stable, descriptive class and never to auto-generate or change them.
Step 3 - Set up your events
Page views are captured automatically. For all other events, such as form submissions, use the Express Setup Tool - set up an event once and Seeka will deliver it to all connected destinations:
On the Seeka setup screen, paste the URL of your deployed app and click Launch Express Setup Tool
Navigate through your pages creating the events you require
Events are live in real time as you create them
💡 Event setup requires access to Seeka and cannot be completed by an external developer.
Step 4 - Test your events
Once your events are configured, test them with the diagnostic streamer - it shows your events firing in real time so you can verify everything is working:
On the Seeka setup screen, paste the URL of any page on your app and click Launch diagnostic
Navigate through your app and trigger the events you want to test
The diagnostic streamer will display each event as it fires, including what data was sent and to which destinations
You can also access the full diagnostic streamer with advanced view from Settings later, once you're all set up.
Troubleshooting common issues
My form isn't gathering leads
This is nearly always a form ID or button class problem. Work through the following:
Run the Copy form fix prompt from Step 2 through your AI builder, redeploy, then re-bind the event with the Express Setup Tool.
To check manually: right-click your form on the live site, choose Inspect, and confirm the
<form>tag has a uniqueidattribute and the submit button has a stable, descriptive class.If you've recently regenerated or restyled the page, check whether the IDs/classes changed. If they did, your event bindings need updating to match.
No View Page events at all
Confirm the app was actually deployed after the builder added the Seeka script - the change only takes effect on the live app.
Use How to check if a pixel is already installed on your website to confirm the Seeka script is present in your page source.
Some builders strip or relocate header scripts on deploy - ask the builder to confirm the Seeka script tag is in the
<head>of every page.
Events worked, then stopped after a redesign
Your AI builder likely regenerated the form IDs or button classes during the redesign. Re-run the form fix prompt, redeploy, and update the bindings via the Express Setup Tool. Then remind the builder those identifiers must never change.
If you've worked through the above and are still stuck, start a chat with us and include your app URL and which form or button isn't tracking.
Connecting your data destinations
A data destination is somewhere you would like to send data to, such as Meta™ Ads, TikTok™ Ads or Google Analytics 4™. The great news is that you only have to connect each destination once, and then anywhere you install Seeka will automatically send that rich data to your connected destinations.
Where to get help
Questions about your Seeka account or event setup - start a chat with us here in the Help Centre.
Questions about your AI builder's generated code - ask the builder itself; they're usually very good at explaining and fixing their own output when given the form fix prompt.