Mautic 2.0 introduced the ability to embed content on a web page dynamically for both anonymous visitors and known contacts.
There are 2 types of Dynamic Web Content items (or DWC):
This feature allows you to configure filters (like in segments) so a Landing Page with a DWC token or slot can show content based on specific conditions.
data-param-slot-name="myslot"to the Requested Slot Name of your DWC item):
<div data-slot="dwc" data-param-slot-name="myslot"> <h1>Dynamic web content for myslot</h1> </div>
There are several steps involved in setting this up.
You can set up as many items as you need. The default will be delivered via the "Request Dynamic Content" decision in a campaign. If you want to push something different based on a set of criteria, you create those here and deliver them via a "Push Dynamic Content" action.
The key to this step is naming the "slot". This can be anything you want as long as it's unique across your dynamic content campaigns. The pull request is processed and determines if the person on the landing page is a known contact.
If you want to serve up different information based on certain criteria, you can use a push request.
<div data-slot="dwc" data-param-slot-name="dwc"> <h1>Dynamic web content for myslot</h1> </div>
Note the data-slot-name matches the slot name in the campaign.
Watch a video tutorial.
Dynamic web content supports translated content. When creating/editing a dynamic web content item, there are the options to set a language and select a translation parent. By selecting a translation parent, the current item is then considered to be a translation in the selected language of that parent item.
Dynamic web content supports these tokens:
Found errors? Think you can improve this documentation? edit this page on Github