Browse documentation

Type to search the documentation. Press Esc to close.

How do merge fields work in a Scribble message?

Put a field name in double braces and it is replaced per recipient: {{first_name}}, {{full_name}}, {{company}}, {{job_title}}, {{city}}, {{state}} and {{sender_name}} are always available, plus any extra column from your upload, named after the header in snake_case.

On this page

#The fields you always have

Built-in merge fields
FieldValue
{{first_name}}The contact's first name.
{{last_name}}The contact's last name.
{{full_name}}First and last together, or the full name column if you imported one.
{{company}}The company on the contact.
{{job_title}}The job title on the contact.
{{city}}The contact's city.
{{state}}The contact's two-letter state code.
{{sender_name}}Whatever you set as Signed by on the campaign, the rule or the hook. A campaign-level fact, so it is the same on every card in a run.
{{years}}Work anniversary rules only. The number of years since the start date. Not substituted when the count is zero.

#Your own columns

Any column you did not map to a known field becomes a merge field named after the header in snake_case. A column headed Personal note becomes {{personal_note}}; Account manager becomes {{account_manager}}.

#What happens when a field is empty

The person is skipped, with a reason, rather than sent a card with a hole in it. In a campaign, the preflight runs over every single row before anything is charged and tells you which rows are short. In an automation, the skip is recorded against that person on the run.

You have three fixes: fill the value in, set a fallback for that field on the campaign or rule, or take the field out of the message.

#Writing a message that works

  • Keep it to a card's length. Three or four short lines. If it needs more room it wants to be a letter.
  • Write it as a person, not as a company. The medium is a handwritten card; corporate register on a handwritten card is uncanny.
  • Check the long names. The preview cycles through real recipients including the awkward ones. Look at those, not the first one.
  • Use \n\n for a paragraph break if you are sending through the API. The card follows your line breaks.
A message that does the job
Happy birthday, {{first_name}}!

Everyone here is glad you're on the team. Have a
brilliant day — and take the afternoon if you can
get away with it.

{{sender_name}}

Last checked against the product on . Something wrong or missing? Tell us.