How thank-you pages and intermediate confirmation pages work
🎯 General principle
Blastform lets you customize the end-of-form experience using thank-you pages or intermediate confirmation pages.
These pages also play a key role in triggering conversion pixels, depending on your tracking and lead-filtering needs.
🟩 A) Thank-you pages
🔸 a) Thank-you page — Pixel disabled
This configuration displays the thank-you page directly at the end of the form, with no intermediate step.
No pixel will be triggered on this page.
💡 Recommended use:
If certain types of leads don't interest you (off-target or invalid), you can show them this page without reporting a conversion.
📄 Behavior summary:
Form completed → Thank-you page (chosen text) → ❌ No pixel triggered
🔸 b) Thank you page – Pixel enabled
This configuration also displays the thank-you page directly, but the pixels are triggered there according to your conditional logic.
💡 Recommended use:
For qualified leads or standard conversion scenarios.
📄 Behavior summary:
Form completed → Thank-you page (chosen text) → ✅ Pixels enabled
🟦 B) Intermediate confirmation pages
Intermediate pages are displayed before the thank-you page, in order to validate a phone number (manually or via SMS code).
They let you secure lead quality and adapt when pixels are triggered.
🔹 a) Manual phone confirmation page – Pixel disabled
This page displays an intermediate step where the visitor must manually confirm their phone number entered in the form.
They can change it if needed.
No pixel is triggered on this page.
Once the number is confirmed, the user lands on the thank-you page with pixels enabled.
💡 Recommended use:
For forms where users often enter a landline number.
📊 How it works:
Form submission → Manual phone validation page → Thank-you page (pixels enabled ✅)
🖼️ Visual example (screenshot of the manual validation interface)

🔹 b) SMS code confirmation page – Pixel enabled
This page displays an intermediate step asking the visitor to enter a 4-digit code received by SMS.
The pixels are triggered on this page, according to your conditional logic.
Once the code is validated, the user lands on the thank-you page where pixels are disabled.
💡 Recommended use:
For forms where users enter a mobile number.
📊 How it works:
Form submission → Mobile validation page (4-digit code, pixels enabled ✅) → Thank-you page (pixels disabled ❌)
🖼️ Visual example (screenshot of the SMS code validation interface)

🔹 c) SMS code confirmation page – Pixel disabled
Same principle as above, but pixels are not triggered on the validation page.
They are only activated on the final thank-you page after the SMS code is validated.
💡 Recommended use:
For scenarios where you want to measure only complete conversions (after the code is validated).
📊 How it works:
Form submission → Mobile validation page (4-digit code, no pixel ❌) → Thank-you page (pixels enabled ✅)
🖼️ Visual example (screenshot of the SMS code validation interface)

🧭 Quick checklist
✅ You have chosen the right page type (thank-you or confirmation).
✅ You know when your pixels fire.
✅ You test the full scenario before going live.
✅ You use conditional logic to target the right leads.