Skip to content

Meta’s Pixel Counting Changes on 12 November and Its Business Terms on 20 November: A Pre-White-Friday Checklist for Arab Advertisers

  • Reading time 7 min
  • Summarize with AI
  • Nov. 1, 2026

Meta changes how it counts your sales on 12 November 2026 and what you agree to on 20 November. Both dates fall inside the White Friday run-up, which starts on 27 November this year.

Neither change names an Arab country, and the reports we read list no exemption for one. The Pixel change can raise your reported conversions without a single extra sale. The terms change keeps a clause that lets Meta crawl pages tied to your business. We could not open Meta’s own pages for either, so every Meta detail below comes from reporting, and we mark it that way.

What changes in Meta Pixel counting on 12 November 2026?

From 12 November, Meta starts measuring some website purchases on the shopper’s device as well as on its own servers. PPC Land (27 and 28 October 2026) reports that the setting is called “Measure conversions on customer devices”, sits in Pixel settings in Events Manager, and is switched on by default for every dataset already sending events through the Pixel or the Conversions API. No code change is needed.

The match uses the email the customer gave your business plus temporary device data that Meta calls non-identifying. Meta is told only that a purchase happened and which campaign gets the credit. According to the same reports, a secondary source citing Meta’s help pages says the feature needs the Pixel to sit directly on the page and the site to require a login with an email or mobile number.

Question What the reports say What we could confirm
Start date 12 November 2026 Reported by PPC Land, not read on a Meta page
Default On for every dataset sending events Not confirmed on Meta’s pages
Where to switch it off Events Manager, data sources, your Pixel, Settings Path given by a secondary source
Effect on reports Reported conversions may rise with no change in real sales Unknown for bidding, purchase value and ROAS
Region A secondary source says no effect for people in the EU or UK No Arab country mentioned anywhere

Why does this matter for a White Friday budget?

It matters because your numbers will move 15 days before the busiest sales week, and you will not know whether sales or counting moved them. If last year’s comparison is your yardstick, a higher October-to-November conversion count could simply be the new counting path.

There is a second effect. Meta’s peak-season guidance, as quoted in the reports, says an ad set needs about 50 conversions a week to leave the learning phase. Extra counted conversions could push an ad set across that line without any change in real demand. Treat any jump after 12 November as unproven until you reconcile it with orders.

What changes in Meta’s business terms on 20 November 2026?

Meta moved the effective date of its updated Commercial Terms and Self-Serve Ad Terms from 30 October to 20 November 2026, according to Search Engine Journal (26 October, updated 30 October). Meta said it wanted more time to explain the terms to partners, including how its crawlers work. The text is reported as unchanged apart from the date.

The clause that drew complaints lets Meta use automated software, and create test credentials, to crawl pages tied to a business’s products or services and to pull updates from them. Search Engine Journal reads the Commercial Terms as saying that a business agrees to the updates by continuing to use Meta’s business products after notice. It reports no regional exemption, and it does not say what happens if you refuse. Complaints went to the European Commission and the UK competition authority, and neither ordered the delay.

The older Self-Serve Ad Terms (22 August 2025) already allow crawling of an advertiser’s domains once an ad order is placed. Meta’s developer page lists its crawlers, including FacebookExternalHit and Meta-ExternalAgent, and says robots.txt controls most of them. The same page says two of them may bypass robots.txt in some cases. The new terms do not say whether robots.txt limits what you have granted.

What should an Arab advertiser check before 12 November?

Do five checks, in this order, and keep a dated note of each.

  • Baseline. Export Meta-reported purchases next to your store’s real orders, day by day, for the last 30 days. Salla, Zid, Shopify and WooCommerce stores all let you export orders. Keep the ratio of the two numbers.
  • The setting. Open Events Manager and find the “Measure conversions on customer devices” toggle for each dataset. Decide on purpose whether to leave it on. Do not opt out by default: outside advice quoted in the reports is to keep it on and watch the ratio.
  • Your checkout type. If your customers order by WhatsApp, pay cash on delivery, or check out as guests without logging in, the on-device path may not apply to them. We have not tested this, so check your own events.
  • Server-side tracking. Keep the Conversions API running. The reports describe the new path as an addition to server-side tracking, not a replacement.
  • An annotation. Mark 12 November in your reporting sheet and in GA4. Do not compare a post-12 November Meta conversion count with an October count without it.

What should you check before 20 November?

Read the terms yourself and decide who in your business accepts them, because continued use counts as acceptance. Then check your robots.txt for the Meta crawlers you want to limit, and note that the crawler page says changes can take up to 24 hours to apply. We cover the consent side of your own tracking in our guide to marketing consent law in Arab markets. If you advertise health, finance or legal services, ask your lawyer whether crawling of pages that hold customer data is acceptable under the data protection law that applies to you.

My read on this

We would not opt out of the Pixel setting before White Friday. We would reconcile Meta’s count against orders every day from 5 November, so we know the old ratio before the switch, and again after it. The worse mistake is to credit a Meta campaign with a lift that is only a counting change. The terms are a slower problem: the crawling clause matters most for publishers and for stores with product pages that change often, and less for a clinic with ten static pages.

Frequently asked questions

“My Meta ROAS jumped after 12 November, so did the campaign get better?”

Not yet. Call this the counting lift: reported conversions can rise because Meta recovers purchases it missed, not because more people bought. Compare against real orders for the same days first.

“Do I need to do anything for the 20 November terms?”

The reports say continued use counts as agreement, so the practical step is to read the terms and decide who accepts them. We have not read Meta’s preview pages, because they were blocked to our fetch, so read them directly.

“Does any of this apply in Saudi Arabia, the UAE or Egypt?”

The reports mention no Arab country and list only an EU and UK carve-out for the Pixel feature, from a secondary source. We read that as applying in Arab markets unless Meta says otherwise, and we say it is unconfirmed.

“Should I block Meta’s crawlers in robots.txt?”

That depends on what you sell and what your pages show. Blocking some crawlers can also stop link previews from working, so test a few shared links after any change.

The better question

The useful question is not whether Meta’s new counting is good. It is whether you can tell a real sales lift from a counting lift before you spend your White Friday budget. If you can reconcile Meta’s count against your orders every day, leave the setting on and watch the ratio. If you cannot, fix your order export first: that gap will cost you more than either of Meta’s changes.

If you want a second pair of eyes on your Meta setup, send me the ten queries that matter and we will check how your campaigns and brand show up before the sale.

Sources and limits: PPC Land, 27 and 28 October 2026, on the Pixel setting; Search Engine Journal, 26 October 2026 (updated 30 October), on the business terms; Meta’s developer page on web crawlers. Meta’s own terms previews and Events Manager pages could not be read, so Meta’s wording is reported second-hand. We did not test the setting in an ad account.

Everything else we have run on Paid Media

Written by whoever ran the work, not a content team

22 articles
All articles
Previous article
Did you like the article?
Share:
  • ChatGPT Ads Now Rewrites, Translates and Redirects Your Ads by Default: How Arab Advertisers Switch It Off

  • ChatGPT Ads in the Middle East: How Arab Advertisers Can Start in 2026

  • What a Google Partner Badge Gets an Advertiser in the Gulf and Egypt

  • We Scored 44 ChatGPT Ads Case Studies. Only 2 Passed Every Evidence Check