Why is consent handling becoming even more important? The short and the long answer is GDPR. 

When third-party content is included in a liveblog, if consent handling has not been enabled, the reader’s data is being unknowingly and/or unwillingly transmitted to the social media platform. That’s why it’s a topic that every platform or news site has to think about. Luckily our liveblog product provides several consent handling options to our partners so that they can choose which solution best fits their needs. While the first option is not recommended for most cases, the other points allow for flexibility with regard to compliancy. 

With Embed JS there are four main options when it comes to third-party content that is being embedded into the liveblog: 

• All third-party embeds can be enabled without consent handling 
• All are disabled without consent handling 
• Integrated consent handling available with our liveblog’s EmbedJS 
  undefined
• Custom consent handling 
  undefinedundefined

There are definite drawbacks to the first two options: one is not GDPR compliant and the other could have a negative impact on the storytelling since not all content is being included that is necessary for the narrative. However, the last two points are not only compliant, but also accommodate our clients’ needs the most. In fact, the integrated consent handling 2-click switch, which we introduced earlier this year in anticipation of this issue, is not only the easiest but also the fastest solution for keeping liveblogs reader-friendly and GDPR compliant. 

For a more technical approach please refer to Tickaroo's Developers' Documentation. 

Our original post about 2-click consent handling can be found here.