Working with HTML components
HTML components are reusable blocks of HTML, CSS, and JavaScript — created once and included anywhere using @include(component-name). Update once, change everywhere.
TL;DR
Access: Campaign settings → HTML components → + New HTML component. Set: name (lowercase-hyphen), component group (for organization), trim result, parent layout (optional). Write HTML in the editor — supports all placeholders, @if/@else, @foreach, and nested @include. Use via @include(component-name) in emails, pages, forms, and other components. JS only works on webpages (not in emails). Common uses: email signatures, booking buttons, meeting type selectors, reusable headers/footers.
Get started in 3 steps
Create the component
Go to Campaign settings → HTML components → + New HTML component. Set Name using lowercase-hyphen style (e.g. booking-signatur, e-mail-signatur, knap-til-faktura). Select a Component group to organize related components. Write HTML in the editor — use Ctrl+K / Cmd+K for placeholders, @if/@else for conditional content. Add CSS in the CSS section and JS (for webpages only) in the JS section. Save.
Use the component
In any email, webpage, form, or other component, insert @include(component-name). The exact syntax is shown in the Placeholder column of the component list — click to copy. Components can be nested: a component can @include other components. Use @if around @include for conditional inclusion.
Organize and maintain
Create Component groups (e.g. "Signatures", "Buttons", "Forms", "Layout") via + New HTML component group. Edit a component to update it everywhere it is used — no manual updates in templates. Before deleting a component, check what uses it (deletion breaks any template containing the @include). For emails: always use inline CSS (email clients strip external styles).
Common searches
HTML component • @include • reusable content • email component • component groups • booking button component • email signature
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article