Azimea Academy · Tutorial
Event products: content supplied by an event
Explore the product component used with event data and compare its display and spacing controls. The designer's sample is a layout preview; no customer event or live automation is triggered.
The video could not load. Try again or read the guide below.
What you will see
- Explore the product component used with event data and compare its display and spacing controls.
- The designer's sample is a layout preview; no customer event or live automation is triggered.
Transcript
Event-based product blocks use the items associated with a cart or order context.
We will review their layout and presentation in a supported event template.
The design defines how the items appear. The actual recipient context supplies the product information when the message is used.
We will add this component as a separate block in the welcome email.
That gives it an independent place in the layout and its own settings.
We can refine its content and appearance while keeping the surrounding message in view.
An internal name makes this component easier to recognize while editing a longer email.
It helps distinguish similar blocks by their role in the message.
This name organizes the designer. It does not add another visible heading or label to the email.
Content settings define what this component communicates and where it leads.
We will establish that information first, then refine its presentation.
Keeping the message separate from the styling makes it easier to reuse the design when the content changes.
The layout sets how the items are arranged within this component.
A list and a grid create different reading patterns, even when they contain the same information.
Compare the images, names, and prices together, then review the result on a phone.
The total label explains the amount displayed beneath the items. We will use a short, clear phrase that fits the language of the email.
The wording is editable, while the amount still comes from the real cart or order context when the message is used.
The total summarizes the amount beneath the collection of items. This setting controls its visibility in the email, while the connected
cart or order supplies its value. Compare the collection with and without the total, choosing the treatment that best explains the
With the content established, we can refine the visual treatment.
These settings apply to the selected component. We will compare each adjustment with the canvas, keeping it consistent with the
surrounding email rather than treating the block as a separate design.
The top spacing creates room between this component and nearby content.
It is separate from the text size and from the padding of the overall email.
Watch the selected block as the value changes, and consider how that gap supports the surrounding layout.
The right spacing creates room between this component and nearby content.
It is separate from the text size and from the padding of the overall email.
Watch the selected block as the value changes, and consider how that gap supports the surrounding layout.
The bottom spacing creates room between this component and nearby content.
It is separate from the text size and from the padding of the overall email.
Watch the selected block as the value changes, and consider how that gap supports the surrounding layout.
The left spacing creates room between this component and nearby content.
It is separate from the text size and from the padding of the overall email.
Watch the selected block as the value changes, and consider how that gap supports the surrounding layout.
Separate spacing lets each side have its own value. Returning to a shared value provides a simpler way to keep the treatment even.
The choice changes how we manage the space around this component rather than changing the content inside it.
One shared spacing value adjusts the room around the component together.
This can make routine layout changes quicker and more consistent.
Consider the padding on neighboring rows and blocks too, because several small spacing values can combine into a much larger gap.
The phone layout deserves its own review. A component can look balanced on desktop and still need a different treatment on a narrow
screen. We will compare the available mobile settings with the smaller layout before returning to the complete email.
Hide on phone removes this component from the smaller layout. This can simplify a message when the element is decorative or repeated
elsewhere. We will demonstrate the difference and restore it for this example, preserving the content in both views.
The configuration is ready to keep in our reusable demonstration template.
Saving records the changes. It does not send an email to contacts.
We can return to this component later without rebuilding the rest of the message.
We now have a configured component with a clear role in the message.
Review its content, check any destinations, and compare the desktop and phone layouts before using the template.
Those checks help the design stay consistent wherever your audience reads it.