Template variables
SignatureCat templates use {{variable}} tokens that resolve per user at apply time. There are nine person variables (filled from Google Directory), two image tokens and two conditional tags. Token names are lowercase and matched case-insensitively - {{Phone}} works the same as {{phone}}. Unknown tokens are rejected when the template is saved.
Person variables (Google Directory)
Values come from each user's record in your Google Workspace directory. Keep the directory tidy and every signature stays accurate automatically.
A value stored for a user on the Data tab takes precedence over the directory for that user and that field alone, everywhere the signature is rendered: the preview, Set me a test signature and the real rollout to mailboxes. Fields you leave to the directory keep coming from the directory. See User data. One exception: when a signature is written to a send-as alias, {{email}} and {{domain}} always follow the alias address, even if they are overridden.
| Token | Value | Notes |
|---|---|---|
{{firstname}} | First name | |
{{lastname}} | Last name | |
{{email}} | Primary email address | When applying to an alias, resolves to the alias address instead. |
{{domain}} | Domain part of the email | Follows the alias when applying to an alias. |
{{jobtitle}} | Job title | From the user's primary organization entry in Directory. |
{{department}} | Department | From the same organization entry. |
{{photo}} | Profile photo | Standalone, the token renders a ready-made profile photo - round by default, square if the template is switched to that shape (default 115x115 px, shape and size are set per template); users without a Directory photo get no image at all instead of a broken icon. Inside your own <img src="{{photo}}"> it resolves to the HTTPS photo URL (auto-scaled to 400 px) and your markup is untouched. |
{{address}} | Formatted address | The user's primary address entry. |
{{phone}} | Phone number | First non-empty of: work, then mobile, then home. |
Empty values render as empty text. The signature never breaks, but you may be left with a dangling label like "Phone:" - that is what conditional blocks are for.
Image tokens
| Token | Value |
|---|---|
{{logo}} | The template's selected company logo - 115x115 px by default, resizable per template (24-300 px). |
{{banner}} | The template's selected campaign banner - 450x100 px by default (a library entry can define its own size), resizable per template, scaled down on narrow screens. |
Images come from the per-workspace library and are selected per template; if nothing is selected, a neutral placeholder renders. If the library image has a click-through link, the image is wrapped in it automatically - and each template can override that link. Sizing details and the resize handles are described in the visual editor and Banners and logos.
If the library entry carries an Image description (ALT), that text is emitted as the alt attribute of the rendered image - for images you uploaded and for entries that point at your own URL alike. It is what recipients read when their mail program blocks or cannot load images. The description belongs to the library entry, so every template using that image shows the same one; an entry without a description renders an empty alt.
Conditional blocks: del and delete
Two wrapper tags remove whole fragments of the signature when data is missing:
{{del}} ... {{/del}}- soft: the block is removed only when every person variable inside is empty. If at least one is filled, the block stays (empty variables inside render as empty text).{{delete}} ... {{/delete}}- hard: the block is removed when any person variable inside is empty. Use it when a fragment only makes sense complete.
Example - a phone line that disappears for users without any phone number:
{{del}}<tr><td>Tel: {{phone}}</td></tr>{{/del}}Blocks can be nested; inner blocks are evaluated first. Unbalanced tags are rejected at save time, and the tags themselves are never written into the final Gmail signature.
A guard can also wrap a whole table cell, a run of neighbouring cells or an entire table row. In the visual editor that is a conditional column, set from the column's own toggle.
Testing how variables resolve
Use Render as in the template editor to preview against any real user's record, and Set me a test signature to apply the result to your own mailbox. Both are described in Create your first template.