Which token goes where
Every numbered field has a type: what kind of content mxAURA is allowed to put in it. There are four.
| Type | Use it for | Where it usually sits |
|---|---|---|
| Text | A line or short paragraph, no formatting | A heading, a sentence inside a paragraph, alt text |
| HTML | Formatted content: bold, links, lists | A whole text module or table cell on its own |
| Link | A web address people click | A button's link box, an <a href> |
| Image | A web address of a picture | An image module's URL box, an <img src> |
mxAURA works out the type from where you put the token
- In an image module's URL box, or inside
<img src="...">: Image - In a button or link box, or inside
<a href="...">: Link - Alone in a text module or table cell: HTML
- Inline with other words: Text
- Typed into a box whose label says Image, Logo, Link or URL: matched to the label
Each guess carries a confidence. A token found in an image source is a strong guess. A token sitting alone in a cell is a weak one, because it could be a heading or a paragraph. A token mxAURA has never seen in a place it recognises is unknown.
Type unknown
After import, the template lists any fields marked Type unknown. Pick a type for each. The template saves either way, but it stays blocked from messages until no field is unknown.
If you want to skip the guessing, declare the type in the template. In a coded template, put a comment next to the token:
{# mxa: field_3 label="Proof point" type=link #}
A declared type always wins, and it survives re-import.
What a type changes
- Editor: text gets a single line, HTML gets a formatting editor, link and image get a URL box with a check.
- Checks: links and images must start with
http://orhttps://. Text has a length limit. - Tracking: link fields are wrapped so clicks are counted. Image fields are never wrapped.
- AI drafting: the type tells the writer what to produce.
Related: Build a template mxAURA can fill, The tracking block.