Attribution after Consent Mode v2
What Google Consent Mode v2 changes for measurement: basic and advanced mode, modelled conversions, server-side tagging, and which numbers to trust.

In short
Meta ads for D2C brands work when three things hold: a simple account Meta’s delivery system can learn from, a steady supply of creative, and purchase data you can trust. This guide covers each, and how to measure when consent hides some sales.
A storefront that sells on a phone, purchase tracking you have tested, a product catalogue connected to Meta, and a break-even ROAS for each product group. Without these, spend buys data you cannot read.
Our guide to ROAS vs ACoS shows how to work out break-even, and our page on D2C website development covers the storefront side.
With few campaigns, each with one job and enough budget to learn. Meta’s delivery system finds buyers from the people who respond to each ad, and it learns faster when results are not split across many small ad sets.
| Campaign | Its job | Audience | Judge it on |
|---|---|---|---|
| Prospecting | Find new buyers | Broad, with recent buyers excluded | New-customer orders and cost per purchase |
| Advantage+ campaign | Sales, with Meta’s automation choosing audiences and placements | Meta’s choice; the older cap on existing-customer spend has gone, so keep repeat buyers out with exclusions or a separate campaign | Purchases and value against break-even |
| Catalogue retargeting | Bring back people who viewed products | Recent visitors and abandoned carts | Orders, read with caution: many would buy anyway |
| Existing customers | Repeat orders and launches | Customer lists uploaded with consent | Repeat orders against what they cost |
Exclude recent buyers from prospecting so it is judged on new customers, keep retargeting small and capped, and give every ad set enough budget to record a steady flow of purchases. Meta calls the early period the learning phase, and significant edits can restart it.
Optimise for purchases, not add-to-carts or landing-page views. The cheaper event finds people who browse; the purchase event finds people who buy, which is what the budget is for.
Name campaigns, ad sets and ads by a fixed pattern, such as job, audience, offer and date, so a year of reports can still be read.
Start broad, and let the creative do the targeting. Meta’s automated audience options treat interests and lookalikes as suggestions more than limits, so a tightly drawn audience often costs more without reaching better buyers.
An ad about a gift for a new mother finds a different audience from one about a work bag, without any targeting at all. Write each ad for the buyer you want, and let the system find more of them.
Use your own customer lists for exclusions and repeat campaigns, uploaded in hashed form and only for customers who agreed to marketing. Whether your consent wording covers that is a question for your legal adviser under the Digital Personal Data Protection Act, 2023.
One idea at a time, judged on purchases. Change the hook, the angle, the offer or the format, but not all four at once, and decide before launch how many purchases or how much spend settles each test.

Judge tests on cost per purchase and purchase volume, with click-through rate as a clue rather than a verdict. Move winners into the main campaigns, keep a log of what each test asked and answered, and test regional-language versions if your buyers read them.
Refresh before fatigue sets in. When frequency, how often the same person sees an ad, climbs while click-through falls, put new ads live while the old ones still deliver, so there is no gap.
Creator content must carry the paid-partnership disclosure that advertising rules and Meta require, and every claim about materials, benefits or results must be one you can prove.
Meta reviews ads against its own advertising policies, and the code of the Advertising Standards Council of India (ASCI) applies to advertising in India. Buyers who feel misled also send products back.
Once your storefront has enough products and visitors for Meta to show each person something relevant. Catalogue ads build each ad from your product feed, showing people the products they viewed or ones like them, so the feed is the creative.
Use catalogue ads for retargeting first, capped so the same person is not chased for weeks, and test them for prospecting once the feed is reliable. Meta has renamed these ads more than once; a clean feed matters under any name.
Because the Pixel alone misses purchases. The Meta Pixel reports events from the visitor’s browser, which ad blockers, browser privacy settings and declined consent can stop; Conversions API (CAPI) reports the same events from your server or storefront platform.
Run both, and give each purchase the same event name and event ID from both sources, so Meta counts it once. Send hashed customer details, such as email and phone, where consent allows: they raise the event match quality score that Events Manager reports.
Send Meta the same purchase value your targets use, with or without GST and shipping, and the same value you send to Google. Server events must honour the visitor’s consent: CAPI changes how data travels, not what the visitor agreed to.
On Shopify, Meta’s own sales channel app sends server events; on WooCommerce, Meta’s plugin does, once configured and checked. Our conversion tracking setup covers both, with test events checked in Events Manager.
Your purchase event usually fires when the order is placed. A cash-on-delivery (COD) order that later comes back undelivered, an RTO or return to origin, still counts as a sale, and the campaign that found it is rewarded for it.
Our guide on how to reduce RTO covers the confirmation and address checks that cut it at source.
Against your own orders, not Meta’s count alone. When visitors decline tracking, Meta observes fewer purchases and models some of the rest, and its default attribution includes some purchases after a view rather than a click.
Record your attribution setting and change it rarely, so this month’s figures can be compared with last month’s. Our article on attribution after Consent Mode v2 covers the Google side of the same problem.

Usually not as a default. Meta generally cannot see purchases made on a marketplace, so it cannot learn from them, and the marketplace keeps the customer’s details. Send Meta traffic to your own storefront, where the purchase event and the customer are yours.
There are exceptions. A product with strong ratings on a marketplace and none on a new storefront may convert better there. Treat such traffic as a test with its own budget, judged on the marketplace’s sales report.
Our comparison of marketplace vs D2C sets out what each route gives you.
Enough for each ad set to record a steady run of purchases every week at your expected cost per purchase. Below that, the delivery system has too little to learn from, and splitting a small budget across many ad sets makes it worse.
Work it out before launch: multiply the cost per purchase you can afford, from your break-even ROAS, by the weekly purchases Meta’s current guidance asks of an ad set. If the answer is more than you can spend, run fewer ad sets, not smaller ones.
Grow in steps, from campaigns already above break-even, with creative supply growing alongside. Large, sudden budget increases can send an ad set back into learning and raise costs.
Our performance marketing services set budgets and stop rules from your margin before any spend goes live.
We are an operator, not an agency: we run brands of our own as well, so we read your Ads Manager from the side of the business paying for the clicks. Ad accounts stay in your name, and we work through the access you grant.
Our Google Ads and Meta Ads management runs the campaigns, creative briefs and weekly checks described here, with purchases reconciled against your orders before anyone reads a ROAS.
If you are comparing Meta ads agencies, ask each one whose name the ad account will be in, and how its reported purchases will be checked against your orders.
We run Facebook and Instagram campaigns with few, well-funded ad sets, creative tested against written questions, and purchase events checked against your orders.
What Google Consent Mode v2 changes for measurement: basic and advanced mode, modelled conversions, server-side tagging, and which numbers to trust.
How ROAS, ACoS, TACoS and MER are worked out, how they convert, and how to set a break-even ROAS from your margin.
GST for online sellers: registration, the GST invoice, TCS on marketplace payouts, input tax credit and monthly reconciliation.
Tell us what you sell and where. We reply with our questions and a scope, with GST on its own line.