Build a welcome email sequence around subscriber interests

Design the question before designing the email

Ask something that will change what you send. “What would you like to explore?” with two concrete answers is more useful than collecting a preference you never use. Keep the email address required and make the interest question optional if it would otherwise discourage signup.

Use a dropdown or radio buttons for one choice. Checkboxes allow multiple choices, which changes the automation: someone interested in both topics may qualify for both follow-ups. Decide whether that is desirable before writing the messages.

In the widget editor, you can put the interest question on a separate form page. Keep the promised resource available regardless of the answer. More questions are not automatically better personalization.

Save the answer where the automation can use it

Open the widget's Contacts tab and map the email field to the contact's email address. Add a custom contact field for the interest and map the form answer to it using the variable picker. A question appearing in the widget is not a substitute for configuring its destination in the contact profile.

Alternatively, use conditional tags in the same tab. An If rule can assign a ceramics-interest tag when the matching radio option is selected. Another rule can assign a table-styling tag. The Always rule is useful for a source tag identifying this particular signup form.

Use fields when you want to preserve an answer as data; use tags when you want a convenient audience label. You do not need both for every question. Keeping the setup small makes later filters easier to understand.

Submit the form yourself and inspect the resulting contact before building the emails. Verify the address, interest, and source tag. Test a submission with no optional answer, too.

Connect the correct signup event

Create an automation with the Form submission trigger and select the intended widget. Check whether its contact setting should include all submitting contacts or only new ones. Someone already in your database may still submit this form to request a new resource; excluding them could prevent delivery of that promise.

For Shopify stores, New subscriber is a different trigger: it follows subscribers added to Shopify's customer list. Use it when that is your intended entry point. Avoid connecting both routes to the same welcome message without checking whether a signup qualifies for both.

Place restrictions that apply to the entire journey in the trigger's Filters. Keep topic-specific restrictions on the individual email actions. If ceramics interest is an entry requirement, table-styling subscribers cannot reach even the shared welcome email.

Give each message a separate job

The delays and number of follow-ups are editorial choices. For an initial test, deliver the promised resource first and wait two days before the topic email. Add another message only when it contributes something new.

Each email action needs its own filter. Do not assume that matching the first topic stops the other topic actions. If only one follow-up should be sent, use a single-choice question and make the conditions mutually exclusive. A general alternative must exclude both known interests; leaving it unfiltered sends it to everyone.

Write the welcome message around the promise

Subject

Your guide to a more welcoming table

Preview

Start with three simple changes you can try tonight.

Welcome — we're glad you're here.

Here's the table-setting guide you requested. It starts with the pieces you already own, then shows three ways to arrange them for an everyday meal.

Over the next few days, we'll share a little more about the topic you chose when signing up.

Read the guide→

Thanks for inviting us to your table. We hope the first idea makes tonight feel a little more special.

Only mention a chosen topic when one was actually collected. For the general route, replace that sentence with an accurate description of what subscribers will receive.

In the email editor, start from a premade welcome layout or choose a layout from Design ideas. Keep the resource button above secondary promotions. Add names or saved preferences through the variable picker, and preview a contact with missing optional information before relying on it in a greeting.

A custom field stores information; it does not write a tailored paragraph for you. Write separate topic emails and filter them when the advice itself needs to change.

Keep the handoff from widget to email consistent

The widget's success page should say where the promised resource will arrive. Its wording, the first subject line, and the destination page should describe the same resource. Do not announce an immediate download if the next step is an email.

If you use several signup widgets with the same promise, you can select multiple forms for one automation. If they promise different resources, separate the delivery paths or explicitly filter them. Reusable Workflow sequences can handle a shared introduction, but deliver each form's distinct promise before sending contacts into generic follow-ups.

Test three contacts, not just one email

Run the sequence with a ceramics answer, a table-styling answer, and no answer. Confirm that all three receive the resource and only the intended follow-up. If you permit multiple interests, add a fourth test with both selected.

Inspect the contact record first when the wrong message arrives. A missing mapping, a mismatched tag, and an incorrect email filter create similar symptoms but need different fixes. The automations guide explains the available condition groups; contact management covers fields, tags, and segments.

After launch, compare visits to the resource and topic guides. A preference question has earned its place when it leads to a more useful next message, rather than simply a fuller database.