Tilda Forms: why leads go to spam (and you blame marketing)

You launched a beautiful Tilda landing page, drove paid traffic, and the form is converting. Then your sales team says "we're not getting leads". You blame marketing for the wrong targeting. Marketing blames sales for ghosting replies. The real culprit is usually neither — it's the notification email from the Tilda form, silently landing in Junk.

The awkward truth about form-builder platforms like Tilda is that you don't own the SMTP pipe. Your form submission is delivered by a Tilda-controlled mail server on a shared sender domain. You cannot add a DKIM record. You cannot change the envelope. You can basically only measure what happens.

Why Tilda form emails break placement

Tilda's built-in notification uses an envelope like noreply@tilda.cc or a numbered subdomain. The From display name may be your company, but the authenticated sender is Tilda. Mailbox providers see:

• From domain: your project alias — but SPF and DKIM align to Tilda, not to you.
• Reputation: shared pool. Every Tilda user's complaints, spam traps and blasts drag the pool down.
• DMARC: if your own domain has p=reject, any Tilda mail claiming to be from you is guaranteed to fail DMARC and land in Spam or be bounced.

What you cannot fix from Tilda's side

On the self-serve plans — which is how most Tilda customers use it — you cannot:

• Add your own DKIM selector for Tilda's outgoing mail.
• Change the bounce / return-path envelope.
• Move to a dedicated IP or dedicated subdomain.
• Switch off Tilda's own tracking headers which some Outlook rules dislike.

This is not a Tilda failing — it is the nature of hosted form builders. The deal is: you get drag-and-drop landing pages, they get to operate the mail infrastructure at scale. Control is traded for convenience.

Measure first: seed the form notification

Before you rebuild anything, verify the problem is real and measure the size:

1. Add 20+ seed addresses across Gmail, Google Workspace, Outlook.com, Microsoft 365, Yahoo, Mail.ru, Yandex and ProtonMail to the Tilda form notification recipients list (Site Settings → Forms → Email).
2. Submit the form from an incognito window with realistic filler data.
3. Record per-provider placement: Inbox, Promotions, Junk, or missing entirely.
4. Repeat on weekday and weekend, morning and evening — placement varies with reputation cycles.

The result tells you whether this is a Tilda problem (broad drop across Gmail and Outlook) or a your-domain problem (only one provider, maybe a blocklist).

Three escape routes when placement is bad

Route 1 — Webhook to your own ESP

Turn on Tilda's webhook integration on the form. Route the submission to a tiny serverless function (Vercel, Cloudflare Workers) that calls SendGrid, Postmark, or Resend's API on your authenticated domain. Notifications now come from a sender you control.

// Minimal Cloudflare Worker example
export default {
  async fetch(req) {
    const data = await req.json();
    await fetch('https://api.resend.com/emails', {
      method: 'POST',
      headers: {
        Authorization: 'Bearer ' + RESEND_KEY,
        'Content-Type': 'application/json',
      },
      body: JSON.stringify({
        from: 'leads@yourdomain.com',
        to: 'sales@yourdomain.com',
        subject: 'New lead: ' + data.name,
        html: '<p>' + data.message + '</p>',
      }),
    });
    return new Response('ok');
  },
};

Route 2 — Zapier or Make → Gmail / Outlook

If you do not want to write code, a no-code Zap "Tilda webhook → Gmail: Send Email" gives you Gmail-authenticated notifications in two clicks. Placement is effectively as good as Gmail-to-Gmail.

Route 3 — Direct to CRM / Slack

For many teams the real fix is to stop relying on email notifications at all. Route the webhook to HubSpot, Pipedrive, or Slack, and leave email for external marketing only. The form lead appears where the sales team already works.

Decide: migrate, stay, or switch builder

The decision tree is short:

• Placement is fine (all major providers green in the seed test): keep Tilda's built-in notification. Re-test monthly.
• Placement is patchy (Gmail OK, Outlook bad): use Route 1 or 2. The ESP or Gmail API fixes it in under an hour.
• Placement is terrible everywhere: route to CRM or Slack and treat email as optional. Consider whether Tilda is the right platform long-term.

FAQ