GDPR
Law 195/2024 and advertising: keeping Google Ads and Meta conversions after cookie rejection
After a cookie banner, Google Ads reports fewer conversions. How to choose a Consent Mode approach, pause Meta Pixel until consent and use CRM data under Law 195/2024.
Once a cookie banner goes live, Google Ads often reports fewer conversions. Usually nothing is broken: visitors who click “Reject” stop sending full data to the ad platforms. A website owner needs two things here. Rejection must actually stop the data, and advertising should still receive as much information as the law and the visitor’s choice allow.
This article follows “GDPR and consent in Moldova: what to check on your website”, which covered the banner and forms. Here we look at what happens next in Google Ads, GA4 and Meta.
In brief
- Moldova’s Law No. 195/2024 has applied since 23 August 2026. Consent for advertising and analytics cookies must be active, given separately for each purpose and provable.
- With an honest banner, some conversions disappear from reports. Expect this and account for it when you judge campaign results.
- Google Consent Mode comes in a basic and an advanced form. Pick one together with whoever is responsible for data protection, because it decides what reaches Google before consent.
- Meta Pixel can be paused until consent with
fbq('consent', 'revoke'). - Sales data from your CRM makes advertising less dependent on cookies. It also needs a lawful basis and a privacy notice.
What changed for advertising on 23 August
Law No. 195/2024 on personal data protection took effect on 23 August 2026 and follows the EU GDPR. Three requirements of Article 7 matter most for advertising. The business must be able to show that the person consented. Withdrawing consent must be as easy as giving it. If the consent request sits alongside other terms, it must be clearly separated from them.
Websites usually send data to Google and Meta, which are companies outside Moldova. Your privacy policy has to say so and give the legal ground for the transfer.
Fines are phased in. According to Moldova’s data protection authority (CNPDCP), 10% of the sanction applies in the first year, 40% in the second and the full amount from the third. The authority adds that a breach does not automatically mean a fine: the law also provides for warnings and corrective measures.
Why your reports show fewer conversions
Before the banner, Google and Meta tags set cookies for every visitor. Now a visitor who rejects either sends no data or sends a reduced version. Reports show it like this:
- Google Ads records fewer conversions for the same number of clicks;
- GA4 shows a larger share of traffic with no source;
- Meta Ads Manager receives fewer Pixel events.
A simple test separates data loss from a broken tag. In a clean browser, accept all cookies and send a test enquiry. If the conversion is recorded, the tag works and the drop comes from rejections. If not, look for a setup error.
Demo example. A dental clinic website with made-up numbers. Before the banner, Google Ads reported 40 enquiries a month. After it, the same 1,000 clicks produce 28 reported conversions, while the CRM still shows about 40 enquiries. The campaign performs as before and simply sees part of the result. Cutting the budget “because conversions fell” would cost the business real patients.
Consent Mode: basic or advanced
Consent Mode is how Google passes the visitor’s choice to its tags. Google describes two ways to implement it.
Scroll the table horizontally →
| Mode | Before consent and after rejection | What advertising gets |
|---|---|---|
| Basic | Google tags do not load until the visitor chooses. After rejection nothing goes to Google, not even the rejection itself | Conversion modelling based on a general Google model |
| Advanced | Tags load straight away. After rejection no cookies are set, but cookieless pings still go to Google: consent state, the fact of a conversion, page load events | Modelling based on an advertiser-specific model, usually more precise |
Google says these pings carry limited information, such as whether the URL contained a click ID, the consent state and a random number. It is still a transfer of data before consent. Choose advanced mode deliberately, after assessing the lawful basis with whoever is responsible for data protection. The technical contractor implements the chosen mode; the decision belongs to the business. Primary source: Google Ads, About consent mode.
Also check that the banner sends all four consent signals to Google: ad_storage, analytics_storage, ad_user_data and ad_personalization. If it sends only the first two, advertising features work with an incomplete picture.
Meta Pixel and the Conversions API
Meta has its own mechanism. Its documentation recommends calling fbq('consent', 'revoke') on every page before the Pixel initialises, and fbq('consent', 'grant') once the visitor agrees. Until then the Pixel sends no events. Primary source: Meta, Pixel and GDPR.
If the site also uses the Conversions API, which sends events from your server, that channel must respect the visitor’s choice too. A common mistake is a Pixel that is paused in the browser while the server keeps sending the same events. Events Manager shows it: after a rejection, no events should arrive.
Feeding advertising with CRM data
The most valuable data about ad results sits in your CRM: which enquiry became a customer and for how much. Google Ads can take it in two ways.
- Offline conversion import. The form stores the GCLID click identifier with the enquiry. When a sales manager marks the lead as a customer, a conversion with that GCLID is uploaded to Google Ads.
- Enhanced conversions for leads. The site sends a hashed email or phone number from the form, and the CRM later uploads the same hashed data when the lead converts. Primary source: Google Ads, About enhanced conversions for leads.
Hashing does not make data anonymous, since Google matches it to accounts. The transfer therefore belongs in your privacy policy, needs a lawful basis and should respect the ad_user_data signal. In return, campaigns learn from sales, and this keeps working when many visitors reject cookies.
A 15-minute check
- Open the site in a new browser profile without extensions.
- Open developer tools (F12), go to the Network tab and filter by
google|facebook|doubleclick. - Click “Reject” in the banner. Go to another page and send a test enquiry.
- Look at the requests. In basic mode there should be no requests to advertising domains. In advanced mode only cookieless requests are acceptable, and there should be none to
facebook.com/tr. - Repeat in a fresh profile and click “Accept all”. This time the conversion should be recorded.
If full requests still go out after rejection, the banner is decoration. If a conversion is not recorded after consent, measurement is broken and the campaign is learning blind.
How Search Boost helps
We run Google Ads and Meta campaigns and set up consent so that advertising stays manageable. The work follows this order:
- an audit of tags, GTM and server integrations: what runs before a choice, after consent and after rejection;
- choosing a Consent Mode approach with your data protection contact, then implementing it;
- configuring Meta Pixel and the Conversions API to follow the visitor’s choice;
- connecting CRM conversions where that suits the business;
- a test record and instructions for your team.
Lawful bases and policy texts are agreed with your data protection contact and a legal adviser where needed. Technical setup does not replace a legal assessment.
Check what your tags send after “Reject”. See how we test and configure consent and what you receive at the end. Forms and CRM are covered in “Leads, CRM and newsletters under Law 195/2024”.
Search Boost editorial team. Sources checked on 29 October 2026. The demo example is illustrative. General information; legal assessment depends on the specific processing activities.
Let's find where enquiries are lost
Tell us what you advertise and how the path from click to enquiry works. We will reply with a verification plan — no guarantees.
The form requires JavaScript. Call or email us:
