Glossary

Dynamic content

Dynamic content changes based on recipient data at send time. When logic fails or data is missing, the platform often reports success while subscribers receive blank sections or incorrect offers.

Definition

What dynamic content is

Dynamic content is email content that renders differently for different recipients based on attributes like location, purchase history, subscription tier, or behaviour. A welcome email might show one product recommendation to a customer in Melbourne and a different one to a customer in Sydney. An abandoned cart reminder might include items left in the cart, pulled from an external database at send time.

The mechanism is conditional logic inside the email template. If a field is populated, show block A. If it is empty, show block B. If a value matches a certain range, render this offer instead of that one. The logic runs at send time, so the same template produces different rendered emails for different recipients.

How it breaks

Common failure modes

1

Missing fallback

The template checks for a field that is empty and has no fallback defined. The subscriber sees a blank block where content should be.

2

Logic error

The conditional statement contains a typo, incorrect operator, or references a field that no longer exists. The block either does not render or renders the wrong variant.

3

Data source timeout

The content pulls from an external API at send time. The API is slow or unavailable, and the template times out before the data arrives. The block remains empty.

4

Field rename

Someone renames a field in the CDP or database. The email template still references the old field name. The condition evaluates as false or undefined, and the wrong content shows.

Why the platform does not catch it

The send succeeds, the content fails

The platform reports success when the email successfully leaves the outbound queue. Whether the dynamic block rendered correctly is a separate question. The SMTP handshake completed, the message reached the inbox, the platform logged it as sent. But the inbox contains an email with a missing product block, a broken merge tag, or an offer intended for someone else.

I have seen a Saturday-morning promotional newsletter that failed to render the hero product image for the first hour of the send window. The platform reported 100 percent delivery success. The inbox showed a grey placeholder box where the image should have been. The cause was a data-source timeout on the image URL lookup. The external service recovered after an hour, and the rest of the batch rendered correctly. But the first cohort of subscribers received broken emails, and the only signal was someone checking their own inbox.

How monitoring catches it

Live-journey checks from the inbox

Telltide monitors watch for expected content at the inbox level. A test identity enrolled in the live journey receives the email the same way a real subscriber does. The monitor checks that the dynamic block is present, that merge tags have rendered with real values, and that links resolve. If the block is missing, if a merge tag is still in curly braces, or if the rendered content does not match the expected pattern, the monitor alerts.

The check is receive-side. Telltide does not parse the platform's internal logs or inspect the template before send. It waits for the email to arrive in a monitored inbox and checks what actually rendered. This catches logic errors, missing fallbacks, and data-source failures that would otherwise be invisible until a customer complains.

Related terms

Concepts that travel with dynamic content

  • Merge tag: the simplest form of dynamic content, where a single field inserts into the template at send time.
  • Triggered flow: the most common context for dynamic content, where each recipient enters the flow with different attributes.
  • Silent send: when the entire email fails to arrive. Dynamic content failures are partial, the email arrives but the content is wrong.
  • Heartbeat monitoring: useful for high-volume flows where dynamic content is consistent, and deviations in cadence signal an upstream issue.

Monitor dynamic content from the inbox

One monitor free. Paid plans from $49 USD per month.

Or try it in 60 seconds without an account →