How to Set Default Values for Custom Fields with Conditional Sending

By Sparkforge Support Team ·Last reviewed May 3, 2026

Conditional Sending in Sparkforge email shows or hides content blocks based on custom field data. Use it to display a personalized greeting when a field has data and a default greeting when it doesn't.

Personalize emails with custom field data — name, company, location — and use Conditional Sending to show a default value when a field is empty. The result: no awkward blank greetings or broken merge tags.

What Conditional Sending does

Conditional Sending shows or hides content blocks based on a contact's custom field values. You write two versions of a block: one for when the field has data, one for when it doesn't.

Why use it

Polished output — no missing names or empty merge fields.
Personalization — every contact sees a relevant greeting.
Consistency — the email reads cleanly even when data is incomplete.
Higher engagement — personalized email gets opened and read more.

Example: dynamic greeting

Goal: show Dear {{contact.first_name}}, when First Name has a value, or Dear Customer, when it doesn't.

Step 1: Enable Conditional Sending

Toggle Conditional Sending on in the content block's sidebar.

Step 2: Set up the personalized greeting block

Add a text block: Dear {{contact.first_name}},
Under Set your conditions, select the custom field First Name.
Set the condition to Is Not with the value left blank.

The block displays only when First Name has a value.

Step 3: Set up the default greeting block

Add another text block: Dear Customer,
Under Set your conditions, select First Name.
Set the condition to Is with the value left blank.

The block displays only when First Name is empty.

Step 4: Preview and test

Use the preview feature with test contacts that have and don't have a First Name to confirm both paths render correctly.

Limits

Only one custom value can be used under Conditional Sending per content block.
You can't apply multiple conditional settings to the same field within a single block or section.

Tips

Always preview with test contacts before sending.
Keep default values friendly and on-brand.

FAQ

Does this work with custom fields besides First Name?

Yes. The pattern works with any custom field on the contact record.

Can I use multiple custom fields in one block?

No. One custom value per content block.

What does leaving the value blank do?

The condition checks for empty or non-empty fields, which is what drives the show/hide behavior.

Can I use any default value?

Yes. Customize the default to fit your brand voice.

Frequently Asked Questions

Can I use Conditional Sending for fields other than First Name?

Yes. The same pattern works for any custom field on the contact record — company, city, last name, custom attributes, anything you've defined.

Can I use multiple custom fields in one content block?

No. Conditional Sending supports only one custom value per content block. To check multiple fields, use multiple blocks.

What does leaving the value blank do in the condition?

It tells the condition to check whether the field is empty or non-empty. That's how the same field can drive both the populated and the default block.

Can I customize the default value?

Yes. Set whatever default copy fits your brand. The example uses Dear Customer but any string works.

How do I test that both branches render correctly?

Use the preview feature with two test contacts — one that has the custom field populated and one that doesn't — to confirm each block displays as expected.