Ask AI
How can we help? 👋

V197 | Release Notes - June 2024

Date of Release: Mon 1 & Tue 2 July, 2024

Beta: Monday 24 June, 2024

After the busy presale period, this release offers a big move in some core features, including a complient new Cookie Banner, user friendly mailing via the Query Builder, and fully integrated unsubscribe features in all mail browsers. At the same time we say goodbye to the old Cookie Banner and the old way of mailing visitors. A pre-summer cleanup if you will.

Mailing with Query Builder

From release 197 all mailing modules will be configured to schedule mailings using Query Builder. We announced the End-of-life of using Mailing List in our June newsletter, and covered the reasons in depth in our webinars on 28 May and 18 June. You can watch the 18 June session back here.

 

Mailing with the Query Builder is very easy and far less prone to errors, reducing the risk of mailing the entire database. As you can build queries in advance and reuse existing queries saving time when sending similar mailings. Colleagues can select premade and approved queries without needing to select additional filters before sending the mailing i.e. making sure you always include the correct GDPR opt-ins. Also, after selecting the query for your mailing, you will instantly see the number of recipients, which is a great extra check to make sure you selected the correct target audience.

Mailings screen where you select the query to be used in mail
Mailings screen where you select the query to be used in mail

To get started, we provided some quick steps to help you transition your old Mailing Lists into queries.

Knowledge Base Article - Transitioning from Mailing Lists to Queries in your Mailings

One Cookie Banner to rule them all

From release 197, we say goodbye to the (very) old Cookie Banner with only one button and move to a compliant Cookie Banner with 3 buttons.

The (very) old banner
The (very) old banner
The (old) compliant banner
The (old) compliant banner

The newly updated Cookie Banner will solve two issues:

  1. The previous Cookie Banner does not conform to DMA/DSA legislation that clearly states all choices should be presented equally and not hidden behind an extra link or step.
  1. The (slightly) newer compliant banner did address this problem. However, by itself resulted in a much bigger banner, blocking a big part of the (mobile) screen, and sometimes not even fitting on a screen at all.

The latest iteration of the Cookie Banner is fully compliant with DMA/DSA and has a more efficient way of presenting information in a smaller area. Specific explanations next to each of the three buttons are no longer necessary. They can now easily be integrated in the introduction text, or hidden behind the fold-out “more information”. The new banner layout will not change the way consent is given, that stays exactly the same.

The new and improved Cookie Banner
The new and improved Cookie Banner

We have transferred most of your cookie texts over to the new banner template text fields.

There are two situations in which you might need to check your texts:

  • You first had the (very) old banner in which you changed the default text and created your own introduction, and later transferred to the compliant cookie banner. The original text for the first banner will be used in the new banner and might not be exactly what you want to communicate now.
  • You first had the (very) old banner in which you changed the default text and in that text you referred to the link “adjust settings” for other cookie consent options. Since the link “adjust settings” is no longer available, your text should be updated and that part of the text should be deleted.

All new texts can be found in these three fields in your template text module:

  • FE3_cookies_intro - The text you see right away
  • FE3_cookies_explanation - The text you see after clicking “more information”
  • FE3_cookies_intro_inline - The text you see blocking a youtube video or any other embedded third party media when the visitor did only give consent for functional cookies
The Cookie consent notification you see instead of social media embeds on webpages when only functional consent is given initially
The Cookie consent notification you see instead of social media embeds on webpages when only functional consent is given initially
💡
If you want to retrieve your original compliant cookie banner text, don’t worry! We kept it in the template text module: FE3_cookies_intro_compliant
Knowledge Base Article - Cookie Consent Banner Settings

Improve handling of unsubscribes via link unsubscribe header and add to statistics

We have completed the work on the new unsubscribe headers in mailings. In every mail browser a visitor can now directly unsubscribe from mailings without having to go to the mail footer. As long as the mailing was using a query with an opt-in filter, the unsubscribe process will find the correct opt-in and unsubscribe the visitor from that opt-in.

If a mailing was sent with a query without any opt-in filter, we cannot unsubscribe the visitor automatically, so a mail will be sent to the theatre to inform you that the user needs to be unsubscribed manually. This is by design. This is a different mail than the unsubscribe mails you would have previously received. Those should all be gone now, as long as you use an opt-in filter in your mail queries. This is also part of the reason we are declaring the old way of mailing without the query builder end of life this sprint.


Courses: support genres with slugs and descriptions

Courses can now have dedicated pages per genre/tag which come with their own url, for example,  /courses/music (this is what we call the “slug”) and their own introduction. You can add the url name and the text to the genre or tag in the Genres and tags module in the “Courses” section.

This feature was already available for default productions, movies and long term events. So if you missed that memo, now is your time to take a look at these cool features!

Notion image

Additional Updates

  • Confirm email address changes using magic code: Added a magic code confirmation for changing e-mail address in the visitor account. This now works similar to logging in, and solves a rare issue of an unsuccessful change of e-mail address
  • Reduce server load generated by Narrowcasting
  • Parts: iFrames are now multilingual
  • Optimized showcase-header-alignment on mobile
  • Implement a one tile layout on mobile for 4 grid media gallery tiles (it used to be 2 tiles on mobile)
Notion image
  • Optimized mobile-ish card styling when there is a “more info” link in the tagline
  • Google Tag Manager: Trigger dataLayer event when event opens in pop-up in brochure layout
  • Events Feed now accepts both startDate and endDate for exporting specific periods of events
 

Related articles

Did this answer your question?
😞
😐
🤩