From 12 November, Meta Pixel will start counting a broader set of actions as conversions. This applies automatically to any dataset already sending events, so if you have not touched your settings, the change happens without you doing anything. The matching that recovers these extra conversions runs on the shopper's own device rather than through Meta's servers.
The practical effect for a business in Oman running Meta ads is simple: your conversion numbers are likely to go up after 12 November, even if actual sales, bookings, or leads stay flat. Meta has not confirmed whether these newly counted conversions feed back into how its bidding algorithm optimises your campaigns. That matters, because if your ad account starts chasing a broader, looser definition of success, your cost per genuine sale could quietly rise while the dashboard looks better.
This is not a reason to panic, but it is a reason to check your settings before the switch happens and to be careful about trusting the first few weeks of post-change numbers. Compare conversion volume and cost per result from before and after the date, not just the headline total.
If your team reports monthly numbers to ownership or a board, flag this change now so a jump in conversions on 12 November is not read as a win before anyone understands why it happened.
What to do about it
- Open Meta Events Manager and review which datasets are set to receive expanded conversions
- Decide before 12 November whether to opt out, and document that decision
- Keep a record of conversion volume and cost per result from the two weeks before the change
- Compare that baseline against the two weeks after 12 November before changing any budgets
- Confirm with whoever manages your account whether Conversions API is also affected
Useful to someone on your team?