How to set up your brand kit
How to set up your brand kit in SendBeam: colours, type, logo and icon that new blocks and starters take, usable as merge tags and carried by blueprints.
Last updated
Product overview: Newsletter and email marketing features
Brand, in the left menu under This workspace, is where a workspace's look is defined once. Everything that makes email reads from it, so a designer setting up a client does not re-enter the same colours or re-upload the same logo in every template.
What the kit holds
- Colours — primary (headers and buttons), secondary (headings), accent (links), background, surface (footers and quotes), text and muted.
- Type — a heading and a body family from the email-safe list; each falls back to what the reader's client has.
- Logo, logo on dark, icon — uploaded to the workspace's image hosting, or any https address. The emails SendBeam sends for the workspace (reports, review requests) show the logo on dark when the reader's inbox is dark. Leave it empty and a dark logo on a transparent background gets a light version made for it, and sits on a small plate of the email's colour so it reads in every inbox. Your upload is never changed.
- Postal address and social links — for the footer the law asks for, and the row of icons under it.
A workspace that has not set a kit uses the built-in look, which is exactly what the builder always used.
Filling it from your website
On the Brand page, type your website under Fill from your website and choose Read my website. SendBeam reads your home page once and suggests a brand name, logo, icon, colours, heading and body type, and links to your social profiles. Untick anything that is wrong and choose Use the ticked ones; nothing changes until you do. Fonts are matched to the nearest email-safe family.
For the logo, you choose from the ones your site shows: with its icon, the name on its own, or the icon. Each is shown on a light and a dark background, with your site's own dark version when it has one. An SVG logo is saved as a PNG, because email clients do not show SVG.
The reader identifies itself as SendBeamBrandBot and respects your robots.txt:
a site that disallows it, or every robot, is not read.
Where it is used
- The builder. A new block takes the brand's colours; a starter layout comes in re-coloured to the brand; every colour picker offers the palette as swatches. Emails made before the kit was set keep their own colours — the kit changes defaults, never existing work.
- Merge tags, below, in any template, campaign, automation email or custom block.
- Hosted forms and pop-ups. A form's button takes the primary colour, its copy the text colours and the body type; the hosted page sits on the background colour with the logo above the card. A site that passes its own colours to an embedded form still wins — the kit fills in only what the site does not say.
- The assistants. An email draft comes back in the kit's colours, with the logo at the top when there is one.
- Blueprints. Saving a workspace as a blueprint captures its kit; applying the blueprint to a new workspace sets it.
Merge tags
{{brand_name}}, {{brand_primary}}, {{brand_secondary}},
{{brand_accent}}, {{brand_background}}, {{brand_surface}},
{{brand_text}}, {{brand_muted}}, {{brand_logo_url}},
{{brand_logo_dark_url}}, {{brand_icon_url}}, {{brand_address}},
and {{brand_website_url}}, {{brand_instagram_url}} and the other social links.
They resolve at send time, so a change on the Brand page reaches every email that uses them. A colour tag works anywhere a
hex colour does — in a custom block's style, for example — and a URL tag in an src or href.
{{brand_logo}} is the logo itself rather than its address: put it where the logo goes and it
becomes the image, ready for dark inboxes. A dark logo on a transparent background disappears when the reader's inbox
is dark; with this tag, mail apps that support it switch to your Logo on dark (or one made from your
logo), and the rest show the logo on a small light backing so it stays readable. {{brand_logo_url}}
is just the address of the logo you uploaded, with none of that.
Agencies and several sites
One workspace is one site and one brand, so an agency sets a kit per client and blueprints carry it to the next client
workspace. The API mirrors the page: GET and PUT /api/v1/brand with templates:read
and templates:write.
Stuck, or found a gap? Ask in the community — questions, tips and every release note, with this page as the source of truth.