Odoo 20 Email Marketing Release Notes

For users

From a sent mailing, click the Clicked statistic to see who clicked which link, instead of only the list of recipients who clicked.

For developers

mailing.mailing.action_view_clicked now calls link.tracker.click._action_view_mailing_statistics (new view link_tracker_click_view_list_simplified, filter groupby_email). link.tracker.click gets related fields email and url.

Upgrading from Odoo 19

Custom code that overrode action_view_clicked or _action_view_documents_filtered('clicked') should be checked.

For users

One mailing can carry content for several audiences: blocks that do not match a recipient are left out of that recipient's email.

For developers

The option stores a JSON domain in data-filter-domain on the block. When the body is converted to email HTML, preprocessFilterDomains turns it into t-if="object.filtered_domain(domain)", evaluated by QWeb for each recipient at send time. Changing the recipient model clears the conditions.

Upgrading from Odoo 19

No migration. Custom body post-processing should keep the generated t-if attributes.

For users

Select contacts, then Actions > Add to Mailing List and pick one or more lists. A partner form shows a Mailing Contacts smart button. Portal users find a Subscribed Newsletters card that opens /mailing/my.

For developers

The mailing.contact.to.list wizard now has partner_ids and a many2many mailing_list_ids (was a single list); res.partner gets mailing_contact_ids and action_open_mailing_contacts. New action mass_mailing.res_partner_to_list_action bound to res.partner.

Upgrading from Odoo 19

Code calling the wizard with the old single mailing_list_id field must be adapted to mailing_list_ids.

For users

Pick a recipient model such as Contact, then choose one or more Dynamic Lists next to it. The recipient count follows the lists. They are managed under Recipients > Dynamic Lists.

For developers

mailing.mailing.mailing_filter_id (many2one) is replaced by mailing_filter_ids (many2many, table mail_mass_mailing_filter_rel). mailing_domain is computed as the OR of the selected filters' domains. mailing.filter is described as 'Mailing Dynamic List'.

Upgrading from Odoo 19

Custom code or views using mailing_filter_id must switch to mailing_filter_ids.

For users

In a mailing, the Recipients dropdown now lists Employee and Purchase Order next to Contact, Lead and the others.

For developers

hr.employee and purchase.order now set _mailing_enabled = True, which makes them selectable in mailing_model_id (domain is_mailing_enabled).

Upgrading from Odoo 19

No data migration. Custom models can opt in the same way with _mailing_enabled = True.

For users

Reuse a signature, a promo banner or a footer in every mailing without rebuilding it.

For developers

Odoo 19 removed SaveSnippetPlugin from the mailing builder; Odoo 20 keeps it and adds mass_mailing.SaveSnippetPlugin (custom notification). Saved blocks are ir.ui.view records created by ir.ui.view.save_snippet under the mass_mailing.email_designer_snippets template (snippet_custom group).

Upgrading from Odoo 19

No migration. Saved blocks are shared views, so they are visible to all mailing users.

For users

No more editing inside the small form area: every design change happens in the full screen editor.

For developers

MassMailingIframe renders an o_mass_mailing_can_edit_overlay (label fullscreenButtonLabel) that calls toggleFullScreen(true); the builder is only shown in full screen. Tours that edited the body inline must click the overlay first.

Upgrading from Odoo 19

Custom tours or tests of the mailing editor need the extra click to enter full screen.

For users

Useful for links that must stay readable or that break when redirected (for example some app store or calendar links).

For developers

The popover adds a data-no-tracking attribute on the link; mass_mailing mail_render_mixin skips link shortening for nodes that have it. The option is hidden for /unsubscribe_from_list, /view and /cards links.

Upgrading from Odoo 19

No migration.

For users

Build a design once, save it, and start later mailings from it. Templates have their own kanban (Templates menu) with a My Templates filter.

For developers

mailing.mailing gets is_template (replacing the Odoo 19 favorite flag and action_set_favorite), action_save_as_template, action_fetch_templates and action_new_mailing_from_template. New action mailing_mailing_action_templates and menu mass_mailing_template_menu. A cog menu item is registered in the cogMenu registry.

Upgrading from Odoo 19

The Odoo 19 favorite field and action_set_favorite no longer exist on mailing.mailing; custom code using them must switch to is_template. Not verified from the supplied source code how favorites are converted during upgrade.

For users

More design freedom, with a clear hint of which fonts are safe for email.

For developers

FONT_FAMILIES is now grouped (mail and google). GOOGLE_FONTS in mass_mailing_iframe_utils.js maps each web font to a CSS stack ending with a safe font (for example "Lato,Arial,sans-serif"), and the fonts are loaded in the editor iframe.

Upgrading from Odoo 19

Code importing FONT_FAMILIES as a flat name to stack map must be adapted to the grouped structure.

For users

More ready-made starting points and blocks for common emails (catalog, policy update, event news).

For developers

New theme entries catalog, terms_update and event_updates in mass_mailing_themes; new snippet templates in mass_mailing views. Snippet views were also turned into templates (commit aff69b309930).

Upgrading from Odoo 19

Custom themes or snippets that xpath into the standard snippet views should be checked, as the snippet files were reorganised.

For users

Promote a product or an event without copying its details by hand: drop the block, choose the record, and the block is rebuilt with its data.

For developers

Blocks with class s_record_snapshot and data-model/data-fragment-key get the record_snapshot_option. Each model registers its fields and fragments in the registry category mass_mailing.record-snapshot-snippet-info. New module website_mass_mailing_event provides the event blocks.

Upgrading from Odoo 19

Nothing to migrate. Other models can register their own snapshot info to get autofill blocks.

For users

Set the company's social accounts once and every mailing footer shows the right icons and links, styled to match the design.

For developers

New builder options SocialMediaLinks and SocialMediaOption on .s_social_media; links come from the res.company social fields through _get_social_media_links and are saved with update_social_links (mass_mailing/models/res_company.py) from the CompanyUpdateDialog.

Upgrading from Odoo 19

Mailings built in Odoo 19 keep their static icons; the new options apply to the Social Media block.

For users

Reports by source stay clean (one Mass Mailing source); to know which mailing produced a click, lead or order, look at the Reference field.

For developers

utm.mixin gets utm_reference, a Reference field (selection _selection_target_model, tracked with url parameter and cookie odoo_utm_reference). utm.source.mixin is removed; mailing.mailing no longer inherits it and fills utm_reference = 'mailing.mailing,ID' on links.

Upgrading from Odoo 19

Custom modules inheriting utm.source.mixin or relying on one source per mailing must be adapted; reports grouped by source now need utm_reference to split by mailing.