A table tag within email content is how you can utilize the data within a selected relational table from your account, rather than using contact tags which utilize the contact lists in your Maropost account. Table tags are specific to the table that you plan on utilizing within your content. For all table tags, the middle section is the table’s name, and the end section is the field.

Example: {{table.example_email}}, where ‘example’ is the table’s name, and ’email’ is the field within your relational table that you wish to utilize.

(i) You can have as many different table tags as you need, as long as the field within your relational table that matches with the ‘end’ section of the tag.
(ii) All tables have an ‘all’ option ( e.g. {{table.example_all}} ) which will pull all of the details stored in a table and store it as an array.
(iii) If there are more than 1 categories that you wish to have displayed within your content (e.g. while applying for jobs, the contact has applied to multiple job IDs), be sure to include the loop code<! — {% endfor %} –> to loop back to the beginning of the table tags.
(iv) You can use the code sort: ‘example_email’ to sort the table by email (or replace ’email’ with any field from your table).

Example: {% assign sorted_postings = table.job_postings_all | sort: ‘posting_date’ | reverse %}
OR

{% for postings in sorted_postings %}
Where sorted_postings is the array of data, and % is the variable.

When creating a table, you will have the option to select ‘sendable’ for a field within the table. The field that should be selected as ‘sendable’ is a column that holds contact email addresses. You can have many email address columns as you want, but only one sendable column. This is how to establish a link between a contact’s database and the contact record in a table.

Maropost uses liquid script. To learn more, visit: https://shopify.github.io/liquid/