Data & measurement

Why Some Customers Never Get Your Customer.io Email

When a Customer.io message references a customer attribute that is missing and has no fallback, the message does not go out blank. Customer.io blocks the send for that recipient entirely and logs it as Failed, while everyone else with complete data gets the message fine. A Liquid default filter on every personalization tag is what prevents it.

A graphite envelope with a gap cut into it where a name tag should be, stamped in solid orange with the word Failed

What matters

  • Per Customer.io's own documentation, a Liquid tag that cannot resolve, like a missing first_name, blocks the entire message from sending. It does not render blank.
  • The failure shows as Failed in Customer.io's message logs, scoped to that one recipient, not a platform-wide outage.
  • A Liquid default filter on every personalization tag prevents it: {{ customer.first_name | default: "there" }} is the fix in Customer.io's own docs.
  • Because the failure is per-recipient, it reads as random non-delivery instead of a clear error unless someone checks message logs for Failed status.

A welcome email goes out to 10,000 new signups. 9,840 get it. The other 160 don’t, and nothing in the dashboard explains why: no bounce, no spam complaint, no unsubscribe. The campaign just looks like it skipped them.

Customer.io does not send an incomplete message, it blocks it

Customer.io’s own documentation is direct about this: if a Liquid tag in a message can’t resolve, like a customer who doesn’t have a first_name attribute, the message will not send. That is a deliberate choice, not a bug, built to stop people from receiving a message with a visible hole in it, a “Hi ,” instead of a name. The cost of that protection is that the send fails outright for that recipient, and shows up as Failed in the message log rather than as a warning anyone sees in open or click rates.

Why it looks random instead of broken

The failure is scoped to the recipient, not the campaign. Only the people missing that specific attribute fail to receive the message. Everyone else, with a first_name on file, gets it without a problem. From the outside that reads as a handful of customers randomly not getting an email, not as a platform issue, because 98% of the send worked fine. The only place the pattern shows up is the message log, filtered to Failed, which most teams check after a bounce spike, not after a quiet gap in delivery.

The fix is one filter, not a new tool

  1. Audit every personalization tag in your active journeys, not just the welcome series. Any tag pulling a customer attribute, first name, company, plan tier, is a candidate for a missing value on some fraction of your base.
  2. Add a default filter to each one. {{ customer.first_name | default: "there" }} keeps the send alive with a generic fallback instead of blocking it. Customer.io’s docs note the filter needs their current Liquid version, so confirm which version an older message is running before assuming the filter will apply.
  3. Use an if/else block where a filter isn’t available, same logic, more lines: show the personalized value if it exists, a fallback line if it doesn’t.
  4. Check the Failed count in message logs on a schedule, not only when something else breaks. It is the only signal this problem leaves, and it never shows up in open rate, click rate, or deliverability reports.

This is the same root cause behind why a CDP can split one customer into two profiles: a gap in the data that the platform assumes will always be there. The fix for both is the same discipline, treating every personalization field as something that can be missing, not something you plan growth automation around assuming it never is.

Frequently asked questions

Why did some of my customers never get a Customer.io email that everyone else received?

Most likely a Liquid tag in that message, a customer attribute like first_name, was missing for those specific recipients and had no fallback value. Customer.io blocks the send entirely for anyone missing that data instead of sending an incomplete message, and logs it as Failed in your message logs.

Does one missing attribute break the whole campaign send?

No. Only the recipients missing that specific attribute fail. Everyone with complete data for that tag gets the message normally, which is exactly why the failure looks like random non-delivery instead of an obvious outage.

How do I stop Customer.io from failing sends over missing data?

Add a default filter to every personalization tag, for example {{ customer.first_name | default: "there" }}, or wrap the tag in an if/else block as a fallback. Customer.io notes the default filter only works on their current Liquid version, so check which version a given message uses.

Keep reading

All topics

×

Hi! 👋

How can we help you today?

Please write a message first.