Quick answer: If Systeme.io collects a lead but the welcome email never arrives, trace the chain in order: form submission, campaign subscription, active email, sending conditions, sender authentication, then delivery. A successful Save and test email does not prove that your signup automation works. Do not rebuild the funnel, buy a higher plan, or repeatedly resend to the whole list before locating the broken step.
This guide is for a small lead-magnet funnel: an opt-in page, a thank-you page and a welcome campaign. For the full setup, use our step-by-step sales funnel tutorial.
Evidence note — November 5, 2026: Screenshots below come from our earlier Systeme.io free-plan build. This procedure combines that build record with the official help articles linked beside each check. We have not reproduced every failure mode, and this is not a deliverability benchmark.
Start here: which part is failing?
| What you observe | Check first | What it tells you |
|---|---|---|
| The page redirects, but the new address is missing from Contacts | The published form and selected funnel step | Confirm lead capture before troubleshooting email delivery. |
| The contact exists, but did not enter the campaign | The rule’s trigger, selected page and campaign action | The gap is between capture and enrollment. |
| The contact entered the campaign, but no email was sent | Activation, delay, sending day/time and account notices | A saved email may be inactive or waiting. |
| A test email arrives, but a live signup gets nothing | The actual signup path with a fresh address | The editor test and the automation path are different tests. |
| The message is sent, but not visible in the inbox | Spam, Promotions, recipient address, bounces and authentication | A sending event does not guarantee inbox placement. |
| The email arrives, but the PDF is inaccessible | The published attachment or download URL | Delivery and resource access need separate checks. |
Use one consenting test recipient, not your full subscriber list. Record what happened before changing a setting so you can distinguish the effects of each change.
1. Confirm that the live form created the contact
Open the published opt-in page, submit an address you control and check CRM → Contacts. Note the address and submission time. A thank-you page is not your complete test result: establish that the contact was captured and entered the expected campaign.
Check the URL you actually shared. A copied funnel, a different step or an old link may look identical while pointing at a different signup path. Keep your test narrow: one page, one intended campaign and one new submission.
If the address is already on your list, use a fresh address or an alias that you can receive. This reduces confusion about previous enrollment or completed campaign steps; it is not a claim that every existing contact must re-enroll in the same way.
2. Match the automation trigger to the page you tested
The official sequence instructions use this rule for an opt-in form:
Trigger: Funnel step form subscribed Selected step: the exact opt-in page you submitted Action: Subscribe to campaign Selected campaign: your welcome sequence
Go to Automations → Rules and inspect the saved rule. Confirm both selections, not just its name. If you use Tag added instead, the official instructions say the tag must be added after the rule is configured. An old tag is not proof that the event fired.
In our build record, an incomplete trigger/action selection left the rule unable to save. Filling in a rule is not the same as saving a complete one. After correcting it, test through the published form again.
Official reference: Automate an email sequence.
3. Activate the email and check every sending condition
The campaign instructions distinguish saving an email from activating it. Inspect the first email’s status and check: is it active, which previous email is selected, what delay is configured, and whether a sending time or weekday is also required?
The documentation says all configured conditions must be satisfied. A short delay with a Friday-only restriction does not mean immediate sending on Tuesday.
Distinguish relative delay from your intended calendar. To send on day 0, day 1 and day 3, the third email can be two days after the second. Three days after a day-1 email instead targets day 4, before additional timing restrictions. Compare the intended schedule with the actual predecessor and delay.
Official reference: Campaign activation and sending delays.
4. Confirm the sender and authenticate the sending domain
A domain connected to a landing page and a domain authenticated for email are separate checks. Inspect email settings rather than assuming a working website proves that the sender is ready.
The official domain guide says a custom sending domain must be authenticated. Follow the CNAME and DMARC records generated for your account. Do not copy another site’s example records or overwrite unrelated DNS records. The sender email address also needs confirmation.
You cannot authenticate a domain owned by a personal email provider such as Gmail or Yahoo. Use a custom domain you control.
Official references: Domain authentication and Sender-address confirmation.
5. Separate the editor test from the end-to-end test
Save and test checks a message’s appearance. It does not exercise your published form, trigger and campaign subscription as one chain. The test-email guide notes that substitute variables do not populate in test emails, and recommends a live email to yourself to preview the final result. It also recommends a test recipient different from the sender address.
- Use the editor test to check layout.
- Use the published form with your test recipient to check enrollment and the live email.
- Open the actual message and inspect the resource link or attachment.
Official reference: Sending a test email.
6. Check for a sending pause instead of repeatedly resending
The official “Why aren’t my emails being sent?” article describes pauses involving new-account checks, imported-list reviews, suspicious content and large sending volumes. It says repeatedly resending a pending email is unnecessary.
If your account shows a review or restriction, follow its instructions. Do not import a purchased list or generate extra sends to force an account through a check. If none of the documented cases fits, contact support.
Official reference: Sending pauses and support.
7. Check the download as a recipient
An email can arrive while the lead magnet fails. Open the download in a signed-out browser. Confirm that it is the promised resource, not an editor preview, private document or leftover template.
An on-page copy is a useful fallback for a simple resource. Our free tool-stack checklist is readable without waiting for an email. If you later add email delivery, describe it separately and test it before promising it.
The minimum useful support ticket
Send support the published page URL, campaign name, relevant rule, submission timestamp and timezone, whether the contact appeared, and the last step that worked. Share recipient details only through private support. Never post account credentials or a subscriber list in a public forum.
FAQ
Why does a test email work but the automation fail?
The editor test bypasses the published signup path. Check contact capture, the selected rule and campaign, activation, and sending conditions separately.
Can I manually subscribe a contact to isolate the problem?
Yes. The official manual-subscription guide shows Contacts → More actions → Subscribe to campaign and selection of the starting step. Use a consenting test contact. Success helps isolate the campaign from the form trigger; it does not prove the original rule works.
Should I upgrade before troubleshooting?
Not automatically. A higher plan does not diagnose an incorrect rule, inactive email or sender setup. Check the exact restriction in your account. Our pricing guide separates plan limits from setup work.
Can correct setup guarantee the primary inbox?
No. Authentication and a successful test do not guarantee placement for every recipient. Record actual outcomes instead of treating a preview as proof.
Next steps
Start with the last step you can prove worked. Change one thing, repeat one controlled test and record the result. For a fresh build, use the setup tutorial; for suitability and limitations, read our hands-on review.
Affiliate disclosure: ToolVerdict Lab participates in affiliate programs, including Systeme.io’s. This guide has no direct referral link and does not require an upgrade. Some linked reviews and pricing guides contain affiliate links, which may earn us a commission at no additional cost to you.
