Personalizing recipient data across channels
Ensure recipient identity remains consistent while customizing text in your timers.
2 min read
Screenshots use fictional demo data. Your controls may differ by plan, role, or environment. Use the values generated in your own workspace.
Placeholders versus merge tags
Campaign text supports {first_name}, {full_name}, {custom1} and {custom2} placeholders when personalization is enabled in the supported workflow. These specific tags are for countdown-artwork and differ from your email provider’s native merge-tag syntax.
Provider tags supply actual values within the generated URL or workflow, which CountdownFlow then substitutes into the artwork. Typing a provider tag directly into the campaign headline will not work; you must configure recipient values via your email provider.
Headline example: Hi {first_name}, your early-access window ends soon.
Your browser blocked clipboard access. Select the text and copy it manually.
Resolving missing values
Unexpanded provider tags are not recognized as personal names. Missing values are either cleaned up or handled according to the specific renderer's behavior. Always test with both a complete contact and one missing optional fields to ensure the final copy remains professional.
Linking events to recipient deadlines
Supported recipient webhooks can include the campaign ID, opaque recipient key, start/open timestamps, effective deadline, extension count, phase and generated image/snapshot/smart URLs. Always use the effective deadline returned by the application rather than calculating a conflicting deadline independently.
A recorded first-open transition may be triggered by a mail proxy request. This acts as a clock/event boundary rather than proof that a recipient viewed the offer. Maintain a separation between analytics identifiers and business authorization logic.
Workflow safety guide
- Use one stable opaque key per recipient across email, smart link and website.
- Verify tag replacement through a real send.
- Keep administrative keys and signing secrets on the server.
- Limit personal data in public URLs and webhook payloads to what your workflow actually needs.
- Deduplicate automation events and apply extension limits rather than resetting a window on every request.