Troubleshooting

Most "the widget isn't rendering" issues come down to one of:

1. The placeholder <div data-launchlist-widget> is missing or has the wrong public key. Copy the full snippet again from your dashboard.
2. The script is loading after the placeholder, but blocked by your CSP. Add https://getlaunchlist.com to your script-src and connect-src directives.
3. Your CMS stripped the script tag. Webflow needs an Embed element; WordPress needs a Custom HTML block; Squarespace needs a Code block.
4. An ad blocker is hiding the form. Test in an incognito window.

Still stuck? Open the browser console — the widget logs descriptive errors. Or hit support and we'll diagnose.

Copy link to this answer

A 405 error on submit almost always means the form's action attribute is being rewritten by your CMS or framework. Things to check:

1. Are you using a custom <form> instead of the LaunchList widget snippet? Switch to the widget — the snippet handles the POST internally.
2. Is your hosting provider intercepting POSTs to non-HTTPS endpoints? Make sure your site is HTTPS.
3. Is a router-level rewrite (Next.js, React Router) catching the form submit? The widget submits via fetch, so it should not collide with client-side routing — but if you embedded a raw form HTML, that can.

If you copy-pasted the full LaunchList snippet (script + placeholder div) and still see 405, contact support with the URL.

Copy link to this answer

If the form returns success but the dashboard shows zero signups:

1. Spam protection rejected them. Disposable / blacklisted addresses are silently dropped. Check Settings → Spam protection → Rejected log.
2. You hit your plan cap. Signups continue to be captured but are hidden until you upgrade — see what happens when I hit my limit.
3. The widget is pointing at a different waitlist. Each project has a unique public key — make sure the embedded snippet matches the project you are looking at.
4. Email verification is on and waiting. Submissions appear as "pending" until verified.

If none of these apply, ping support with a sample test email and the project URL.

Copy link to this answer

Two paths:

1. Customize from the dashboard (no code) — under Widget → Customize, change colors, button shape, font, and labels. Most teams match brand in 2 minutes. See Customize widget docs.
2. Override with your own CSS — the widget exposes stable class names like .ll-form, .ll-input, .ll-button, .ll-success. Drop !important overrides if your site's framework wraps them aggressively.

If the widget looks broken specifically (collapsed, overlapping), check that your site's reset CSS is not setting display: none on <form> or <button> elements globally. Tailwind's preflight is fine; aggressive Bootstrap resets occasionally clash.

Copy link to this answer

If admin notifications are not arriving:

1. Check Account → Notifications — make sure new-signup notifications are turned on for the project.
2. Search Spam / Promotions in the inbox — Gmail occasionally aggressive-filters transactional digests.
3. Check the email address on file is correct.

For real-time signal that does not depend on email, set up a Slack notification — most teams switch to Slack-only the moment they hit any meaningful signup volume.

Copy link to this answer

The fix that resolves 90% of these cases is configuring a custom sender domain so welcome emails come from your brand with passing SPF/DKIM/DMARC checks.

Also check:

• Subject line is not all caps or full of !!!.
• Body is not 100% image with no text.
• Plain HTML, not heavy nested tables.
• The reply-to is a real, monitored mailbox.

For a deeper diagnostic, run your domain through mail-tester.com — it'll flag SPF/DKIM/DMARC misalignment in seconds. Full guide: emails going to spam.

Copy link to this answer

The most common reason: the referrer's ?ref=ABC123 parameter is being stripped before the friend lands on the signup page. Check:

1. Did the share link include ?ref=...? The widget appends it automatically — but custom share buttons sometimes don't.
2. Is the friend opening it inside an in-app browser (Instagram, TikTok) that strips query params? Test in a regular browser.
3. Is your site doing a redirect that drops the query string (e.g. trailing-slash rewrite)? Preserve query params on all redirects.
4. Is the friend already on your waitlist? Duplicate signups don't double-count referrals.

If the parameter is intact and the count still doesn't move, share the share link + signup email with support and we'll check the attribution log.

Copy link to this answer

Hosted pages are aggressively cached at the edge for performance, so changes can take a few minutes to roll out globally:

1. Hard-refresh the page (Cmd/Ctrl + Shift + R) to bypass your browser cache.
2. Wait up to 5 minutes for the CDN cache to expire if the change still doesn't appear.
3. Confirm you saved changes in the dashboard — the Save button must turn from green to disabled.

If the page is fully wrong (different brand entirely), you may have copy-pasted the wrong project's slug — double-check Settings → Basic.

Copy link to this answer

LaunchList sends signup emails through a background queue, so there's normally a short delay (seconds to a couple of minutes). If your signups aren't getting their verification or welcome email, work through these:

1. Is the email actually turned on? Verification and welcome emails only send if you've enabled them under Settings → Submissions. If "send welcome email after verification" is on, the welcome won't arrive until the person clicks the verify link first.
2. Check spam / Promotions. Transactional emails sometimes land there. The single biggest deliverability fix is configuring a custom sender domain — see why emails go to spam.
3. The address may be undeliverable. If email validation flags an address as invalid or risky, the mail is held rather than sent to a dead inbox. Some providers (Yahoo, iCloud, regional domains) are stricter than others.
4. Resend it. On the signup's status page there's a "resend" option for the verification email; you can also re-trigger from the dashboard.
5. During a big launch spike? Very large bursts of signups in a short window can lag the email queue. It catches up on its own — but if a lot of people report missing emails during a live launch, contact support with your waitlist name and we'll check the send logs and prioritise your queue.

If a specific address still gets nothing after all of the above, send us that email and the waitlist name and we'll trace it in the delivery log.

Copy link to this answer

This is one of the most common "it works for me but not my visitors" issues, and it's almost always the in-app browser. When someone taps your link inside Instagram, Facebook, TikTok, or LinkedIn, it opens in a stripped-down browser that can't open new tabs and often drops URL parameters. That breaks two things: a form set to open the success page in a new tab silently fails, and the ?ref= referral code gets lost.

How to fix it

1. Use the LaunchList widget snippet, not a raw <form>. The widget submits inline (via fetch) and shows the success state in place — it never relies on opening a new tab, so it works inside in-app browsers. If you hand-built a form that does target="_blank" or a full-page redirect, that's what's failing.
2. For link-in-bio traffic, send people to your hosted waitlist page instead of a deep link into a builder page. The hosted page is built to work in these browsers.
3. Don't rely on a new-tab "thank you" page. Keep the confirmation on the same page (the widget does this by default).
4. Test it the way your visitors arrive. Post the link in an Instagram story/DM to yourself and tap it from the app — don't only test in desktop Chrome.

If referral counts specifically aren't moving, also check why the referral count isn't updating. If you've done all this and signups from a specific app still fail, send support the exact link you're sharing and the app you're testing from.

Copy link to this answer