SeersAi

  If your business has a website and a mobile app, you may wonder: Do I really need a different CMP for my app? The short answer is that web and mobile apps need consent to work in their own environments. A setup made for your website does not automatically handle everything happening inside your app. Here is the simple difference. What is a Web CMP? A Web CMP manages consent on websites. It works with the browser and the tools running on your website. These can include analytics, advertising tags, and other services that collect or use visitor data. For example, a visitor may choose to allow analytics but reject advertising. Your consent setup can then pass those choices to the relevant website tools. This is why a web CMP is closely connected to your website's tags and browser environment. If you are looking for a web-based consent management setup, Seers supports websites and helps businesses manage visitor consent from one place. What is a Mobile CMP? A Mobile CMP manages co...

  Migrating from client-side to server-side Google Tag Manager is one of the most common analytics projects on marketing team backlogs right now. Ad blockers, Safari's Intelligent Tracking Prevention and consent regulations keep removing events before they reach GA4 or Google Ads. What server-side GTM actually is Client-side GTM loads a container script in the visitor's browser. That script fires tags. Server-side GTM adds a second container that runs on your own cloud infrastructure and receives events over a subdomain of your website. The browser sends one lean request to your subdomain. The server container reads it, applies any transformation or filtering logic, then forwards clean events to Google Ads, GA4, Meta Conversions API and any other supported endpoint. Why the migration matters Cookies set by your subdomain read as first-party, so Safari keeps them beyond the seven-day limit that hits browser-set cookies. Requests to your own subdomain sit outside typical ad...

  Search for "how to make a mobile app GDPR compliant" and you will find hundreds of guides. Most of them repeat the same surface points and stop there. Apps that actually pass GDPR reviews go a lot deeper, and the depth is not in the privacy policy. This piece walks through the layers that decide compliance in a modern mobile app. Layer 1: The consent banner Shown on first launch. Accept and Reject placed side by side with equal design weight. Toggles cover analytics, advertising, personalisation, and functional purposes. Layer 2: The SDK gate Every analytics, ad, and attribution SDK waits for the consent layer to report back before it starts. This is the layer most apps skip. It is also the layer regulators check first with a network proxy on the first launch. Layer 3: The consent record Every choice is stored as a signed IAB TCF v2.2 string, plus a full audit log with timestamps and versions. Layer 4: The user rights flow Users can view, export, and delete their d...

  If you own or run a mobile app, you have probably heard about privacy laws like GDPR and Apple's tracking prompt. And you have probably wondered what your app actually does behind the scenes, and whether any of it might get you in trouble. The short answer is that most apps are already doing something risky, and nobody told the team that built the app. What happens the second your app opens Inside every mobile app there are tiny bits of software called tracking tools. Names you might know include Firebase, Google Analytics, AppsFlyer, and Adjust. Their job is to record what users do inside the app. Installs, taps, screen views, purchases, and the ad that brought the user in. The problem is timing. These tools usually start collecting the moment the app opens. That happens before the user has even seen the consent banner. Under GDPR, that alone is enough for a fine. The full guide on how tracking works inside apps breaks it down clearly. Why this keeps happening Two reasons...

  Cookie consent tools used to be simple to pick. In 2026, they're not. Prices have moved sharply, feature lists overlap, and the choice you make now affects ad revenue, app releases, and regulator response for years. What a modern CMP actually needs to do At a base level, a consent management platform must block non-essential cookies before consent, log every choice, and pass the right signals to Google Consent Mode v2. That is the floor. Anything less and you risk both regulator fines and broken ad attribution. Above the floor, the real differences appear. Pricing model matters more than price Cookiebot charges per domain and roughly doubled base pricing in August 2025. OneTrust removed self-serve pricing and now starts around $10,000 a year, with 20 to 40 percent renewal increases reported by many customers. Osano and Didomi keep pricing behind sales calls. Visitor-based pricing tracks real business growth instead. Seers AI publishes tiers openly: a free plan for 100 visit...

  Every marketing team wants clean GA4 numbers and a compliant cookie setup. The trouble is, most teams still run a configuration that ignores a big update from 15 June 2026. Since that date, Google Signals no longer controls your Google Ads data inside GA4. Consent Mode does. Old configurations quietly lose users, shrink audiences and drop conversions. What Google Signals is Google Signals connects sessions from the same person across their phone, laptop and tablet. It only turns on when the visitor is signed in and has Ads Personalisation on in their Google account. It does not manage cookies. It only enriches data already collected with consent. What Consent Mode v2 is Consent Mode v2 is the switchboard. It reads a visitor's cookie choice before any Google tag fires. Four flags are involved: ad_storage, analytics_storage, ad_user_data and ad_personalisation. Basic mode blocks tags until consent is given. Advanced mode fires cookie-less pings that GA4 can later model into...

Universal consent means one central record of every yes and no a person gives you, read by every system you run and updated the moment it changes. Your banner only sees one of those channels. Most companies collect consent well and carry it badly. Here's a plain walk through what happens when it works, plus the one arrival almost nobody has planned for. Step 1: Someone answers They land on your site. Or open your app. Or tick a box on a paper form at your counter. Or reply STOP to a text. All four are consent events. All four count in law, and only the first one usually gets built properly. Step 2: The answer goes to one place Rather than saving into whichever tool caught it, the answer gets written to a single central record. Stored alongside it: who they are, what they agreed to, when, which channel, and which law applied to them at that moment. That last field does a lot of quiet work. It's how you answer "was this lawful?" two years later. Step 3: Everything else ...

  GDPR uses one sentence to define personal data. Article 4(1) calls it "any information relating to an identified or identifiable natural person". Everything else follows from that sentence, so it helps to read it slowly. Two words do the work. Identified means you already know who it is. Identifiable means you could work it out. Things that count The European Commission gives a plain list: a name and surname, a home address, an email address, an IP address, an identification card number, a cookie ID, and the advertising identifier of your phone. Video recording from CCTV is on the list too. Things that do not count A company registration number is not personal data. A generic mailbox such as info@company.com is not personal data. Truly anonymised information is outside GDPR, and only when the anonymisation cannot be reversed. The six mix ups Assuming work emails are exempt. A named address like sarah.jones@company.com identifies a person, so it counts. Treating coded record...

The short answer If your purchases dropped soon after you added a cookie banner, the banner is almost certainly the cause. The Meta Pixel starts in a paused state and needs a signal to switch on. Many banners send the pause and never send the switch. Reinstalling the pixel will not fix that. Here is the full list, in the order worth checking. 1. Your cookie banner never sends the "on" signal Meta's developer documentation describes pausing pixel fires until consent is granted, then sending them once it is. The two states are revoke (paused) and grant (active). Plenty of banners handle the first half correctly and forget the second. The pixel then waits forever. How to test: open your site in a private window, accept cookies, then open your browser's network tab and look for requests going to facebook.com/tr. If nothing appears after you accept, the "on" signal never arrived. 2. You have two pixels on the page A theme app and a manual install both adding the ...

Does your website show the same cookie banner to every visitor? If it does, you are likely doing two things at once: over-asking people in relaxed regions and falling short in strict ones. Geo-targeted cookie banners fix that by matching the notice to the visitor's location. What geo-targeting actually does When someone lands on your site, the consent system checks their IP against a geolocation database and works out their country or region. It then shows the banner built for that jurisdiction. A visitor in Germany sees a GDPR opt-in. A visitor in California sees a CCPA opt-out with a Do Not Sell or Share option. A visitor in a region with light rules may see a short notice or none at all. Why one banner cannot cover everyone The laws simply do not agree. GDPR requires opt-in before non-essential cookies load. CCPA follows an opt-out model. Brazil's LGPD asks for consent per purpose. A single banner either restricts users who do not need a full opt-in or under-complies fo...

  Imagine you open a website and the first box asks you to agree to cookies. But the words are in a language you do not know. What do you do? Most people close the box or leave the site. That one moment can cost a business a customer. This is why the language of your cookie banner matters so much. It is often the first thing a visitor reads. If it feels foreign, it starts the visit on the wrong foot. The law wants clear language GDPR Article 12(1) says privacy information must be in clear, plain words that people can understand. A banner shown only in English to French, German, or Japanese visitors does not meet that test. If people cannot read what they agree to, their consent is weak. This is not just theory. In 2021 the Dutch privacy watchdog fined TikTok because it showed its privacy notice only in English to Dutch users. The message was simple: people must understand what they say yes to. How a multi-language banner works The banner finds the visitor's language in one of...

  You added a cookie banner to follow the law. A week later, your Google Ads conversions fell. Many owners hit this and think the setup is broken. It is not. Let us walk through what really happens and how to fix it. First, the cause. A cookie banner lets users say yes or no to cookies. When a user says no, Google tags cannot write cookies for that person. So Google cannot track the sale the normal way. Your reports show fewer conversions, even though your real sales did not change. The drop is a tracking gap, not a sales problem. Now, the fix. Google Consent Mode reads the choice from your banner and passes it to Google. It does not show the banner itself. It tells Google what each visitor allowed. This lets Google act on the choice instead of losing the data. There are two ways to run it. Basic consent mode blocks Google tags until the user clicks the banner. If the user says no, no data is sent. Advanced consent mode loads the tags with consent set to denied by default. While...

  Adding a cookie consent banner is the right thing to do. It keeps your website on the correct side of privacy law. But many marketers notice something odd soon after: their Facebook and Instagram ad reports start showing fewer conversions, even though real sales have not dropped. If that sounds familiar, this guide explains what is happening and how to fix it. The hidden problem Your Meta Pixel usually fires the moment a page loads. Once you add a consent banner, every visitor who clicks "Reject" should not be tracked with cookies.  An unmanaged pixel handles this badly. It either keeps tracking people who said no, which breaks the law, or it loses their activity completely. In the EU, UK, and several US states, declined visitors can be a large part of your traffic, so the data gap is real. Why it matters There are two costs here. The first is legal. GDPR and the ePrivacy Directive require consent before non-essential cookies load. Fines reach up to €20 million or 4% o...

Mobile app compliance means meeting the legal and technical rules that govern how your app collects, uses, and stores personal data. In 2026 that covers privacy laws such as GDPR, CCPA, and LGPD, and also the frameworks Apple and Google enforce through their app stores. Getting it wrong risks fines, store removal, and advertising data you cannot legally use. Which laws apply to your app The laws that apply depend on where your users are, and this catches many app owners out because a company registered in one country can still owe duties in many others. If you have users in the EU or UK, GDPR requires explicit opt-in consent before non-essential data processing, and consent must be specific to each purpose.  If you have users in California, CCPA gives them the right to opt out of the sale or sharing of their data, and since 2026 businesses must confirm they have processed opt-out requests, including Global Privacy Control signals. Brazilian users fall under LGPD, and several ...

If you own or manage a mobile app, third-party SDKs are almost certainly inside it. Understanding what they are and what they collect is now a basic requirement for running an app legally. What an SDK actually is A mobile application SDK is a pre-built software toolkit that developers add to an app to get specific functionality without building it from scratch. Analytics, advertising, crash reporting, and payments are the most common uses.  A typical SDK contains an initialisation module that activates when the app loads, an API layer that connects to the provider's service, a data collection module, and a logging component. People often mix up SDKs and APIs. An API is a set of rules that lets two systems talk to each other. An SDK is a bigger package that usually contains APIs along with libraries, sample code, and documentation.  An SDK saves development time, but it also brings a third-party dependency into your app that needs ongoing management. What SDKs collect Eac...

  If you run Google Ads or track visitors with GA4, a cookie banner alone does not tell Google anything. Google Ads and Analytics need structured consent signals, and a standard banner does not send them. This is what a Google consent manager actually does. It is the layer that sits between your visitor's choice and your Google tags, translating "accept" or "reject" into signals Google can read. The four signals that matter Google's Consent Mode covers four parameters: ad_storage , analytics_storage , ad_user_data , and ad_personalization . The first two have existed since the original Consent Mode launch and control advertising and analytics cookies. The other two were added in November 2023, according to Google's developer documentation, and specifically govern whether Google Ads can personalise ads or match Enhanced Conversions using hashed customer data. Basic versus advanced implementation Google offers two ways to run Consent Mode. Basic mod...

  If your mobile app collects any personal data from users in Europe, GDPR applies to you, regardless of where your company is based or how large it is. Many app owners assume GDPR is a website issue. It is not. Mobile apps often collect more personal data than websites, through location tracking, device identifiers, contact lists and behavioural logs. Here is what GDPR compliance actually requires in practice. Start with consent. GDPR requires consent to be freely given, specific, informed and unambiguous. That means no pre-ticked boxes, no bundled permissions, and a separate opt-in toggle for each purpose you process data for. Present Accept and Reject with equal visual weight so neither option is designed to be harder to find. Build a proper privacy policy. It should name your data controller, list every type of data you collect, explain your legal basis for processing it, and set out user rights, including access, correction, deletion, restriction, portability and objectio...

  If your Google Analytics 4 reports show fewer conversions than your CRM, you are not looking at a reporting quirk. You are looking at a data gap — and it is caused by something most marketing teams do not see coming. Ad blockers affect between 25 and 40 percent of web traffic, depending on the industry and device type. Every blocked request is a conversion event your analytics never receives.  Browser privacy tools like Safari's Intelligent Tracking Prevention (ITP) compound the problem further by capping the lifespan of JavaScript-set cookies at just seven days. If a customer converts eight days after their first visit, that attribution gets lost entirely. Why Client-Side Tracking Has a Structural Weakness Client-side tracking works by running JavaScript tags directly in the user's browser. The browser then sends the event data to Google Analytics 4. This approach is simple to set up and has worked for years — but browser privacy controls now sit directly in its path. A...

  If you own or manage a mobile app, privacy compliance has changed significantly in the past two years. Regulators are no longer satisfied with a privacy policy page buried in your settings. They want to see how your app actually handles data at the moment of collection, and app stores have added their own requirements on top of that. This post covers what mobile app compliance means in 2026, which regulations apply, what a proper consent flow looks like, and where most apps fall short. Which Regulations Apply to Your App The regulations that apply depend on where your users are located, not where your company is registered. If your app has users in the EU or UK, GDPR applies. This regulation requires explicit opt-in consent before you collect data for non-essential purposes like analytics or advertising. Pre-ticked boxes and bundled consent do not meet the standard. If your app has users in California, CCPA gives those users the right to opt out of the sale or sharing of ...

  If your Microsoft Ads campaigns target visitors in the EEA, UK, or Switzerland, there is a specific compliance step that has been mandatory since May 5, 2025. Without it, a portion of your conversion data goes unrecorded, your smart bidding operates on incomplete information, and your remarketing lists may include users whose data was collected without valid consent. That step is Microsoft Consent Mode. This article explains what it does, why it matters specifically for B2B advertisers, and how to get it working without a technical team. What Microsoft Consent Mode Does Microsoft Consent Mode connects your UET tag to each visitor's consent decision. The tag reads a signal from your Cookie Consent banner, specifically the ad_storage parameter, and adjusts its behaviour accordingly. When a visitor accepts cookies, UET records the full conversion event as normal. When a visitor declines, UET switches to cookieless mode and sends only anonymised, aggregate signals. No individua...