Merge tags in Dapple are placeholders like /CreatorName or /OrganisationName that automatically fill with the right information when a message is sent. Use them to personalise messages to creators at scale — write one template that addresses every recipient by name and signs off with your details. Type / in the message editor to bring up the picker.
Why use merge tags?
Personalisation at scale — every recipient gets their own name in the subject line and body, not a generic 'Hello there'.
Efficiency — write a template once, reuse it across every project and round.
Accuracy — Dapple inserts the correct value automatically; no typos, no copy/paste errors.
Consistency — your organisation name, logo, and signature stay uniform across every message.
Which merge tags are available?
Merge tag | What it inserts |
/OrganisationName | Your organisation's name (from Settings → Organisation) |
/OrganisationLogo | Your organisation's logo (from Settings → Organisation) |
/CreatorName | The name of the creator you're messaging |
/CreatorEmail | The creator's email address |
/CurrentDate | Today's date (in your organisation's time zone) |
/CurrentTime | Current time |
/MyName | Your name (the user sending the message) |
/MyEmail | Your email address |
Note: the merge tag list grows over time. Open the template editor and type / to see the latest set — anything in the dropdown is available.
How to use merge tags in a message
Open the message editor — Messages tab on a submission, or the bulk-message composer.
Position the cursor where you want the personalised value to appear.
Type / — a dropdown of available merge tags appears.
Click the tag you want (e.g. /CreatorName).
The tag inserts; when you send, Dapple replaces it with the actual value.
How to use merge tags in a template
Open Settings → Message Templates.
Create or edit a template.
Use merge tags anywhere — subject line, greeting, body, signature.
Save.
Any project that uses this template now sends personalised messages automatically.
Best practice
Keep merge tag use intentional — don't pepper every line with placeholders.
Always test a template by sending to yourself first. Confirm the merge tags resolve correctly.
Ensure your organisation name and logo are set in Settings → Organisation before using /OrganisationName and /OrganisationLogo.
Use /MyName in personal sign-offs to make team-sent messages feel personal even when they're templated.
Where to go next