Articles
Didomi Solutions
Didomi X Poool: Gather compliant consent and monetise your audience simultaneously
Didomi Solutions
new

Didomi X Poool: Gather compliant consent and monetise your audience simultaneously

Published  

4/28/2021

by 

Amy Arnell

4
min read

Published  

April 28, 2021

by 

Amy Arnell

10 min read
Summary

At Didomi, we know how important cookies are to publishers and their monetization strategies. But what if a visitor declines cookies? How can you continue to benefit from them if you can’t gain ad revenue or analyse how they use your site? This is why we’ve partnered up with Poool to bring you the optimal alternative cookie wall solution—gather compliant user consent and monetise your audience simultaneously.  

 

What is a wall, and who is Poool?

 

A wall can take many forms (paywall, registration wall, cookie wall, to name a few), but what they all have in common is that access to content is blocked, and the user is required to give some form of value exchange. 

 

A paywall, for example, asks a visitor to pay for content on a publisher’s website, whilst a registration wall only requires that they create an account before gaining access. 

 

Walls are Poool’s specialty. Their dynamic solution gives publishers a fully personalizable and easy-to-integrate wall that can help achieve goals in various areas of business, including monetization, increasing engagement, and growing a registered user base.

 

Using Poool’s dashboard, a publisher can design every aspect of the wall, from messaging to style, and allocate compensation choices to different audience segments based on a user’s context (such as type of content or device).

 

DIDOMI WHITEPAPER | Cookiewalls, paywalls, advertising… What does the future hold for media monetization? 

Want to find out more about walls? This whitepaper discusses what the law says about cookie walls and what this means for users and for monetization.

Poool - Monetisation - Socials (Rectangle) (EN)

 

So, if Poool does walls and Didomi provides a bespoke consent management solution, how about we combine the two? Introducing the alternative cookie wall. 

 

The Didomi X Poool integration 

 

As normal, a visitor to your site is presented with Didomi’s CMP, asking for consent to use cookies. If they accept, the user can carry on as normal. However, if they decline, an alternative cookie wall will appear, blocking content and asking for something in exchange for access. They can either consent to cookies or choose the other compensation chosen by the publisher. This could be anything from subscribing to registering or paying a monthly fee.

 

 

Given the importance of cookies in many publishers’ monetization strategies, readers' rejection of cookies negatively affects the content producer’s business model. However, an alternative cookie wall solution will not only give a second chance for a reader to accept cookies but also offer them an alternative that requires them to contribute to your business in some other way. 

 

Therefore, this Didomi and Poool partnership will allow you to consolidate your CMP and paywall solution into a single model, generating revenue and meeting compliance requirements at the same time. 

 

{{discover-our-cmp}}

 

The best bit? Our new alternative cookie wall is free for all Didomi clients (if they are already Poool clients) and incredibly easy to integrate! Simply add Poool as a vendor on your consent notice and voilá. They say nothing worth having comes easily, but we beg to differ.

 

Benefits of the Didomi x Poool integration: 

  • Free for Didomi clients if you are already Poool's client
  • Full integration into your existing infrastructure (colour, branding, wording)

  • A variety of compensation choices to pick between (based on your strategy)

  • Easy access to the alternative cookie wall implementation from your console
  • Fully compliant (of course)

 

<.com/G4oxyU8c9grn2EbkaPOVH6DROxZmVRyKaaE9fun82AB-3RiY1FwdwKVX7wBkdTI7XztPaRVVGthxiCsPdw_6Flv1NUYSPY2ZmaxYeBVHdNRXEDJKrNQxRIt7egQEbwogjnJv-Fcd" width="774" loading="lazy" style="width: 774px;">