Personalized copy and cross-channel recipient workflows
Use supported text placeholders, stable IDs and recipient events without exposing private data.
2 min read
Screenshots show the real application in an isolated demo environment with fictional example data. Setup notices and controls may differ by environment, plan and role. Click an image to view it full-size, and always use the values generated in your own workspace.
Artwork placeholders versus sender merge tags
Campaign text supports {first_name}, {full_name}, {custom1} and {custom2} where personalization is enabled in the supported workflow. These are countdown-artwork placeholders. They are different from your email provider’s merge-tag syntax.
The provider tags supply actual values in the generated URL/workflow. CountdownFlow then substitutes those values into the artwork. Typing a provider tag directly into the campaign headline is not a substitute for setting up recipient values.
Headline example: Hi {first_name}, your early-access window ends soon.
Your browser blocked clipboard access. Select the text and copy it manually.
Missing or unresolved values
Unexpanded provider tags are not treated as real personal names. Missing values are cleaned up or fall back according to the supported renderer behavior. Always test both a complete contact and one missing optional fields so the final copy remains natural.
Recipient events and 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. Use the effective deadline returned by the app rather than calculating a conflicting deadline independently.
A recorded first-open transition can be caused by a mail proxy request. It is a clock/event boundary, not certification that the recipient read the offer. Keep analytics identifiers and business authorization separate.
A safe workflow checklist
- 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.