Backscreen integrates Didomi CMP for unified OTT consent across web, mobile and CTV. Baltic OTT platform provider Backscreen has partnered with consent and preference management specialist Didomi to offer broadcasters and streaming operators a single consent layer across web, mobile apps and connected TV. The integration combines Backscreen's cross-generation OTT platform with Didomi's CMP, aiming to simplify deployment in multi-device environments where consent collection and user experience on TV apps can be difficult to standardise. The companies said the implementation supports IAB Europe's Transparency & Consent Framework, including TCF 2.3, and is Google-certified. Mikus Narvils, acting CPO at Backscreen, said consistency and compliance "across all devices" is non-negotiable for streaming platforms, while Didomi said connected TV has been a long-standing "blind spot" for consent management because of fragmented devices and limited UX options. Backscreen has been expanding its footprint with broadcaster and telco deployments across the Nordics and Baltics, including work with LNK in Lithuania and previous partnerships focused on OTT analytics and monetisation. Didomi has been building out its privacy stack through acquisitions, including Addingwell (server-side tagging) and Sourcepoint, to extend capabilities across consent, preferences and data activation.

Decoupling Data & consent: Why this CMP is a masterclass. A summary of what to expect in this post about its experience with the Didomi CMP: * Clean Data, Clear Conscience: Why Its New CMP is a Commercial Game-Changer * Stop Leaking Data: Didomi: The Shopify Integration That Actually Works * The ROI of Trust: How a Spectacular CMP Boosted Its Tech Credibility * How to Master the Privacy Paradox: Balancing UX with Ironclad Consent * There's more than just a Banner: How Didomi supported Duga to deliver a working CMP on Shopify * Technically very capable * Multi-platform support * Zero-to-live in minutes * Shopify capability * High quality support * Shoulda done it sooner! * Pay attention to your configuration to get the best performance At Duga, Dugadigital believe privacy is a key part of the data foundation, not a friction point. Dugadigital were motivated by a gnarly challenge: how to integrate tech stacks while ensuring every byte of data is ethically sourced. Dugadigital has seen "compliance-lite" solutions fail to integrate with complex data architectures. By partnering with Didomi, Dugadigital bridged this gap. Dugadigital now see a consent-first ecosystem that eliminates technical lag and race conditions. This spectacular success proves that, with the right orchestration, you never have to sacrifice commercial performance for regulatory integrity. While Dugadigital is celebrating the technical capabilities of the Didomi CMP, please note: I am a Technical Marketer, not an attorney/lawyer/legal expert. This article reflects its technical implementation and should not be taken as legal advice. Dugadigital think Dugadigital has got its moral compass pretty well aligned on the user privacy front but you do you. Implementing the Didomi CMP on dugadigital.com. This isn't an exhaustive run through of the setup process as it's largely intuitive. I'll call out key steps. Dugadigital started with a scan of the site. Dugadigital has minimal data collection so the consent challenge is trivial. Dugadigital went with a basic consent banner but made some minor wording and style changes. In the 'Customization' section, choose the notice format carefully - this is a key choice in the Shopify section discussed later. This can vary with each regulation in the "Specific Settings section. Implementing the CMP is a breeze - drop in the provided script before the GTM snippet. Dugadigital use Wix to host the site, not exactly a warm hug, but not exactly hostile. Easy enough so far. Now to address the Consent Mode functionality. The GTM tag template is available in the GTM gallery. Super straightforward to use. Nice touch, acknowledging the EU regulation with a simple checkbox. That is SO easy to miss as can totally hose your data. A CMP banner that's region aware but a CoMo solution that isn't is a great way to drop off a cliff. If your CMP banner is region aware, make sure the consent signals in the data are too. With zero drama, a few minutes of config, it's live and functional: BIIIIG elephant in the room. Doing basic analytics on Shopify is totally fine with the standard GA integration. Doing anything remotely sophisticated in the GMP space requires GTM. That needs a custom pixel solution to function across the site including the scary dark place called "The Shopify Checkout". GTM Preview mode for client side containers still doesn't function normally thanks to the sandboxing but the dataLayer is clearly working fine - checkout the nice early consent default and update events - more on those shortly. How hard can it be? Right, so you have the Addingwell app providing GTM capability - what about Didomi? Going through this experience was a superb example of how good the Didomi support was - thanks Clara! What's the big deal? From previous experience, if the CMP solution isn't properly integrated with Shopify, your data is toast. Say you hit the homepage to start a session, open the dev tools network tab, and filter for requests going to GA and you'll see the GA events firing. Take note of the sid value. Add a product to your cart, and hit the checkout with the console open in dev tools. This is where it gets challenging. The Shopify checkout is sandboxed so APIs that use event listeners to extract consent cookie data don't function as you'd expect. There's actually a console log about this - not exclusive to Shopify but common in sandboxed execution environments: In a sandboxed environment, addEventListener may not behave as expected. So, if no consents can be detected, _ga can't be read, so a new session starts and all the revenue is attributed to Direct. #Fail. That's bad for your data obvs. How does Didomi solve this? First, the standard implementation requires the line of script to be dropped in head, add a Didomi snippet and then add the render line below: Assuming you've got the Didomi tag in GTM, that pretty much takes care of the setup apart from the checkout. In the checkout, Dugadigital need to perform consent cookie functionality using code in the custom pixel. Handily, the Addingwell custom pixel code section is where the Didomi script lives too - happy partnerships work well like this. But there's a key detail to be aware of. The standard Didomi CMP uses a super efficient consent string to encode consents. You need to turn this off: With the didomi_dcs disabled, the older consent string, didomi_token, is used, and this can be easily parsed in the custom pixel code. Event with the best will and tech solution in the world, the Shopify checkout will not completely lay down and play nicely. If you land on the checkout without consent cookies/local storage, the banner cannot be injected. This can mean data loss. So, you might take the decision to adjust the banner style to a pop in: With the pop in, ya gotta make a choice - no getting round it. This pretty much seals the deal, if you get to the checkout, you're most likely carrying consent signals. Good: The Duga Shopify test site banner above has standard wording, and button position, but the custom JSON prevents banner dismissal: The result is spectacular. The GA session id is maintained through the checkout and your data quality is preserved. In closing. The "Shopify Sandbox" has long been the graveyard of accurate attribution, but this implementation proves that you don't have to choose between legal compliance and data integrity. By moving away from a "bolt-on" banner approach and treating consent as a core architectural requirement, we've managed to preserve the user journey from the first landing page right through to the final "Thank You" screen. The partnership between Didomi, Addingwell, and Duga has turned a notorious technical hurdle into a seamless, high-performance solution. For the data gurus, it means clean, reliable session data. For the privacy folks, it means ironclad regulatory peace of mind. And for the business, it means a commercial edge built on a foundation of trust. If you've been watching your Shopify revenue fall into the "Direct" bucket or struggling with race conditions in your tag firing, it might be time to stop patching and start orchestrating.

If you transmit or make available to Amazon Ads any personal information in connection with your use of any Amazon advertising services in the UK and EEA, you must share a valid consent signal and the country code in which the customer granted consent. The product team at Didomi has been working closely with Amazon to prepare its solutions to support this new framework, benefiting from an exclusive look into its capabilities, requirements, and potential. In this article, Didomi Inc. outline what Amazon Consent Signal entails, how it works, and the steps to take. What is Amazon Consent Signal (ACS), and why does it matter? Amazon has developed its own consent mode framework (Amazon Consent Signal or ACS), similar to Google consent mode, and is expected to enforce its use across Amazon Ads clients: In addition to supporting the Interactive Advertising Bureau's (IAB) Transparency & Consent Framework (TCF) signal and Global Privacy Protocol (GPP), you can also use Amazon Consent Signal (ACS) to transmit the end users' privacy choices to Amazon Ads in the UK and EEA. - Amazon Advertising Companies using Amazon advertising services to run ads in the UK and the EEA must comply with Amazon's consent requirements to ensure that ad delivery, targeting, and measurement are not impacted. Without integration, advertisers may face disruption with their Amazon ads services. Should you implement Amazon consent mode? Benefits of Amazon Consent Signal. The ACS framework can support deeper measurement, targeting, and data quality benefits, especially when paired with Amazon Ad Tech products. Some of the benefits of using ACS with Amazon Ads include: * Cleaner data for Amazon Ads: Consent signals ensure that only valid user data flows into Amazon Ads, providing more accurate attribution, segmentation, and audience insights. * Audience targeting: Consent-aware segments enable compliant retargeting and lookalike building through Amazon DSP, resulting in minimal waste. * Global readiness: ACS supports EEA, UK, and other privacy jurisdictions, preparing your stack for future regulations. * Brand trust: Demonstrating respect for consent and privacy builds long-term credibility with users. Amazon Consent Signal implementation: how does it work? Amazon Consent Signal (ACS), like other consent modes, provides a user-friendly format for advertisers to share their consent choices when uploading or sharing customer data with Amazon Ads. It includes two specific signals: * amzn_user_data: Indicates whether the user has consented to Amazon processing personal data (e.g., an advertising identifier) for advertising purposes. * Acceptable values are "GRANTED" or "DENIED". * amzn_ad_storage: Indicates whether the user has given Amazon consent to read or write advertising cookies or similar technologies on the user's device. * Acceptable values are "GRANTED" or "DENIED". Check out Amazon's technical documentation on consent management for more information, and see the framework in practice with a concrete example of an application: Use case: Amazon Consent Signal (ACS) + Amazon marketing cloud (AMC) in action. Next steps and how to get started with Amazon consent mode and Didomi. Didomi is one of the first CMPs to integrate with Amazon Consent Signal mode. Didomi Inc. is actively collaborating with Amazon to integrate and support the required signal format. If you're running ads in the UK and EEA, you must implement Amazon Consent Signal. Based on your current configuration, your next steps will vary: * If you're a Didomi customer, you benefit from out-of-the-box compliance with Amazon Consent Signal. No custom integration needed. * If you're not a Didomi customer, ensure that your CMP provider is working with Amazon to provide the necessary solutions. If that's not the case, consider migrating to Didomi. * If you don't have a CMP, you have to catch up! Check out its comparison of the best CMPs on the market, or book a demo of ours with one of its experts. Didomi Inc. commit to providing the latest integrations to its customers as part of its broader Privacy Signals solution, which aims to support evolving platform-specific consent modes, including those from Amazon, Microsoft, and Google. Head to its Amazon Consent Signal documentation to learn more, and book a call with one of its experts to discuss your unique setup and how Didomi can help.