Skip to main content
If you’ve built email in Marketo or HubSpot, most of what you know still applies. The big change is where things live. Those platforms keep layout, editable content, and personalization together in one template. allGood splits them into three separate pieces.

​
The core difference

In allGood, your layout is built from approved components, your words live in a separate copy document, and personalization is a merge field filled in at send time. Each piece has its own versions and is published on its own. See the Email overview.

​
Watch out for one naming difference

In Marketo, an email template is the layout an email is built on. In allGood, that job belongs to components. An allGood email template is closer to the pre-baked email in a program template: the layout, standard personalization, and default content already in place, ready to clone and edit for each campaign.

​
Side by side

Marketo and HubSpot vary by version and setup, so read the first two columns as the common case, not every configuration.

​
What carries over

  • Marketers edit words, not layout. You already rely on this in Marketo’s editable elements and HubSpot’s module fields. allGood enforces it more strongly, because layout edits are checked against your approved blocks.
  • Tokens still personalize. A first-name merge with a fallback works the way you expect. See Personalizing an email.

​
What’s different

  • Copy fields are the closest thing to My Tokens, but they don’t inherit. A copy field belongs to one email’s copy document. It doesn’t flow down from a folder or program, so shared wording lives on an asset the email depends on. See Tokens compared.
  • Copy is its own asset. You can review, version, and reuse the words without opening the email.
  • allGood checks compliance for you. It stops any send that is missing an unsubscribe link or postal address. See Before an email can send.
  • Variants come from a router. A/B testing is two versions plus a router, not a separate test tool. See Copy and variants.
  • Layout is written in MJML, the email-building language allGood uses, and allGood handles the rest. You don’t hand-write table-based HTML. The deep-dives below map the syntax.
If you’re mid-migration, allGood can send through your existing Marketo instance instead of its own email delivery. Marketo never sees allGood’s layout language. allGood fills in your Marketo template’s modules for you.

​
Tokens compared

Marketo’s tokens are grouped by where the value comes from, and so are allGood’s merge fields. The first word of each placeholder says which group it belongs to. Marketo’s token behavior varies by instance, so read this as the common case.

​
Template syntax

Building templates, not just emails? Compare MJML with other email tools maps Marketo templates, HubSpot modules, and hand-coded HTML to allGood’s MJML components and copy schema.