Skip to main content
A component is one approved piece, like a hero or a footer. A template arranges components into a design and lists the copy each email needs. An email is the finished message you send, with its own copy and personalization for each recipient. See the Email overview.
No. You describe what you want to Mary, allGood’s AI, and edit the result in plain language. MJML, the email-building language allGood uses, only matters if you want to change an email’s code yourself. You can do that under Edit Source. See Editing an email’s code. Components can’t be edited by hand yet, though you can view their code.
No. An email is self-contained, so a template change shows up in the next email you make from it, not in emails already built. See Changing an email template.
They come from your sending domain’s settings. See Set up an email domain. An individual email can override the From name, the part of the From address before the @, and the reply-to. There’s no screen for this yet, so an agent or developer sets it. The postal address and the domain always come from your domain settings. See Personalizing an email.
No. Formulas are for lists and rules, such as filtering a list or adding a calculated column. An email’s design uses merge fields and Liquid instead. Formulas can still decide who receives an email by filtering the list it sends to. See Personalizing an email.
Either the person you previewed has no value for that field, or the field name is misspelled. A misspelled merge field shows up blank and nothing warns you. See Personalizing an email for how to fix both.
No. Two versions plus a router is the whole mechanism. Reporting on which version performed better isn’t available for emails. See Copy and variants.
No, not as a merge field. Only the recipient’s company name is available. Write company-specific details into the email’s copy. See Personalizing an email.
Can’t find your answer? Reach out to support@allgoodhq.com.