v0
v0 redrew the page. The call to action moved, or left.
A regenerated component can keep the same colors and lose the href, the server action, or the env var that was only ever discussed in the chat.
v0 generates an interface. The conversion path is whatever survived the last generation and whatever you remembered to copy into the host's project settings.
FunnelWatch maps the path from a sentence and a URL you own. A renamed label can update the script. A missing checkout link is an alert, with a prompt aimed at the editor you use next.
What usually breaks
The checkout link disappeared in a regeneration
The new component looks like the old one. The button is a div, or the href is “#”. A visual pass does not catch it. A replay does.
Env vars that never reached the host
The chat told you which Stripe key to use. The Vercel project, or whichever host you deployed to, does not have it. Preview on the generator and production disagree.
A server action that was not deployed
The form calls a function that existed in the generated file and was never wired on the host. Submit refreshes the page and nothing is created.
A relative action that 404s after a redesign
The form posts to /api/checkout. The route was renamed to /api/billing in the next generation. The marketing page still loads.
The price rendered as text, not as the session
The page shows $19. The Checkout Session is created for a different price id. Customers notice on the payment page. A price assertion notices first.
Watch the next break before a customer does.
Free checks the public URL. Pro replays the path after you verify the domain.