Campaign-based Dynamic Web Content¶
Creating the request¶
Use a Campaign Decision for Request Dynamic Content to use Campaign-based Dynamic Content. The Campaign Decision checks if a Campaign member visits a page where a Dynamic Content slot is. Visitors to a page with a Dynamic Content slot receive the Dynamic Content.
The following fields are available:
- Name - the Campaign event. Start the name with something like
Req-DWC: so when you’re looking at Campaign Reports, you can see the event type. - Requested Slot Name - Mautic checks for the slot name. You can see how many Contacts got to the Campaign event where you’re checking if their visits request the slot.
As an example, these two fields might look like: Req-DWC: Country-Header in the Contact history. The requested slot name is the slot Mautic looks for on the page. If it’s on a 3rd-party page, it’ll be in the code you use to add the Dynamic Content slot to your page. If it’s on a Mautic Landing Page, define the slot name on the Landing Page.
- Select Default Content - choose the content which displays to visitors who don’t meet the conditions set at the next step of the Campaign. Users may see the default content first, before Mautic pushes the Dynamic Content.
Creating the filters¶
Once created, you can add filters on the affirmative path to determine which Contacts see the different variations. This happens with Conditions - read more in Creating Campaigns.
As an example, you might use the condition of Country = United States of America to filter only people located in the country.
Pushing the Dynamic Web Content¶
Once the relevant filters are in place, you can add the Campaign action of ‘Push Dynamic Content’ which triggers Mautic to send the relevant content to the Contacts matching the filters.
With all this in place, it might look something like this:
You may wish to decide on a naming convention for your Campaigns, for example prefixing with DWC: when you’re pushing Dynamic Web Content.