QuizFlow LabsQuizFlow Labs
Log in
Docs

Subscribe Block

Published August 2, 2026

Use Subscribe when the participant’s primary action is joining a newsletter or recurring email update. It is available in both Flow and Bio Funnel builders on Pro and Teams.

Subscribe is intentionally narrower than Lead Capture and Custom Form. Email is always required, the subscription permission is explicit, and accepted submissions automatically create or update a contact in the Flow’s subscription Audience.

What the block records

  • The submitted email and any enabled optional identity fields.
  • The selected Flow-scoped Audience.
  • The subscription purpose and sender identity.
  • The exact displayed permission wording and its version.
  • The affirmative Subscribe action, timestamp, block, Flow, and response.
  • The resulting contact, Audience membership, and subscription state.

Contact identity, Audience membership, and subscription status remain separate. An unsubscribed person can remain in the CRM for audit history without being eligible for future newsletter delivery.

Add and configure Subscribe

  1. Add Subscribe from the Lead Capture section of the block gallery.
  2. QuizFlow Labs creates or reuses a visible Flow name — Subscribers Audience for that Flow.
  3. Customize the title, description, and Subscribe button label.
  4. Keep Email enabled and choose whether to collect name, phone, company, or other supported contact fields.
  5. Enter the sender or publication name participants should recognize.
  6. Review the subscription purpose and permission wording. Use a custom purpose when “Newsletter subscription” is not specific enough.
  7. Add a privacy-policy URL.
  8. Choose whether subscriptions should be active immediately or stored as pending for a future double opt-in confirmation.
  9. Preview, publish, and submit a test subscription before sharing the Flow.

Flow-scoped Audience behavior

The default Audience belongs to the individual Flow or Bio Funnel—not to every subscription form in the account. This prevents consultants and agencies from mixing subscribers belonging to different clients.

  • Additional Subscribe blocks in the same Flow reuse its default subscription Audience.
  • You can deliberately choose another existing Audience when subscribers should be shared.
  • Cloning a Flow must use a new empty default Audience; contacts are never copied.
  • Renaming an Audience does not break the block because its immutable ID is retained.
  • Deleting a Flow does not silently delete contacts, consent evidence, or subscription history.

Consent presentation

The Subscribe button is the affirmative action. The notice immediately above it identifies the sender and explains what the participant is joining. It is never preselected or inferred from silence.

Do not use vague copy such as “Send” or “Continue.” Prefer a specific label such as Subscribe to the weekly newsletter. If you add another optional purpose, keep it separate and unchecked.

QuizFlow Labs stores the rendered notice, purpose, sender, version, timestamp, response source, and affirmative action. Account owners remain responsible for ensuring their wording and email practices meet the laws that apply to them.

New, duplicate, and returning subscribers

| Situation | Result | | --- | --- | | New email | Creates a contact, Audience membership, consent evidence, and subscription. | | Existing CRM contact | Reuses the contact and updates only explicitly submitted identity values. | | Already active | Does not duplicate the contact or membership; records an idempotent already-active event. | | Previously unsubscribed | Records new consent and a resubscribe event without deleting history. | | Double opt-in enabled | Stores the subscription as pending until a connected provider confirms it. | | Permission not accepted | Does not create an active subscription. |

Plans and future integrations

  • Pro: Subscribe block, Flow-scoped Audience, automatic first-party contact capture, consent evidence, and subscription status.
  • Teams: Everything in Pro and the planned integration layer for newsletter and CRM platforms.
  • Basic and Free: Subscribe is unavailable because lifecycle contacts and Audiences are not included.

Beehiiv, Mailchimp, Kit, and other providers are not required for first-party capture. The internal subscription record is provider-neutral so future connectors can synchronize without changing the block or losing the original consent evidence.

Testing checklist

  • Submit a new email and verify the contact appears only in the configured Audience.
  • Open the Response and contact records and verify the consent wording, purpose, version, timestamp, and source link.
  • Submit the same email again and confirm no duplicate contact is created.
  • Test the block on mobile and with keyboard-only navigation.
  • Confirm the sender, button label, privacy link, and success state are clear.
  • If double opt-in is enabled, confirm the subscription remains pending until provider confirmation is available.

Related guides

Share