Book a strategy call

BlogStrategy

Crypto Advertising Policy: Google, Meta and X Rules in 2026

What Google, Meta and X actually require before a crypto ad goes live in 2026, and why clearing platform review isn't the same as being compliant in the UK.

Cameron StubbsNov 4, 2026 · 8 min read

Crypto ads are allowed on Google, Meta and X in 2026, but each platform gates them differently, and clearing one platform's review tells you nothing about whether you've cleared the others. Google runs certification through your ad account. Meta requires written permission for most product categories before you can run anything. X loosened its rules in March 2026 but reporting on exactly which markets that covers is still inconsistent. If your audience includes UK consumers, there's a second gate behind all three: the FCA's financial promotion regime, which none of the platforms enforce on your behalf.

We run paid crypto campaigns for clients who've already been burned by assuming platform approval was the whole job. It isn't. Here's what each platform actually requires, why ads get rejected, and the checklist we use before anything goes to review.

What Google Ads requires for crypto in 2026

Google's biggest change this year moved the application process, not the underlying rules. From May 2026, Google lets all advertisers apply for crypto certification directly inside their Google Ads account, rather than through a separate Help Center form. The four certification categories are cryptocurrency exchanges and software wallets, hardware wallets, coin trusts, and complex speculative financial products.

The rollout started gradually in February 2026, so if you don't see the option in your account yet, that's expected rather than a fault on your end.

Two things stay true regardless of where you apply:

Certification is country-specific. You need a separate application for each market you're targeting, and each one assumes a regulatory registration already sits behind it. In the UK, that means FCA cryptoasset registration under the Money Laundering Regulations 2017. The EU equivalent is MiCA CASP licensing, and the US one is FinCEN registration. Google isn't assessing your product here, it's checking that the regulator in your target country already has.

DeFi trading protocols, ICOs and investment-signal products remain banned, certified or not. No application fixes a prohibited category.

The most common cause of disapproval we see isn't a banned category at all. It's Google's automated review misclassifying what the business actually does, usually because the landing page or ad copy leads with language the system reads as a different category than the one you applied under. Clean, literal product description on the landing page matters more here than clever copy.

What Meta requires for crypto products

Meta's gate sits earlier than Google's: for most categories, you need written permission before the ad account can run anything, not after an ad gets flagged.

Exchanges, lending products, and wallets that let users buy, sell or swap all need that written permission. Mining software sits in the same bracket. Storage-only wallets and educational, non-transactional content generally don't, which is why you'll see plenty of crypto explainer content running as Meta ads with no special approval attached.

Meta's enforcement history makes the practical boundary clear even where the exact policy wording shifts between updates: ads that use deceptive or misleading tactics get pulled, and that net catches return projections and anything implying a guaranteed outcome, along with urgency language like "don't miss out" or a countdown timer stamped on the price. If your creative team's instinct is to borrow DTC ecommerce urgency tactics for a token launch, that instinct is the thing to override before submission, not after rejection.

What X allows after the March 2026 policy change

X made the biggest single move of the three platforms this year. In March 2026, it removed its entire financial-products restriction category, which had covered loans, investment services and crypto together since June 2024, and replaced it with a separate Paid Partnership label system that sits apart from standard ad review.

That's a genuine loosening, but it comes with a carve-out most summaries skip: multiple outlets covering the change agree that sponsored crypto content stays blocked in the UK, EU and Australia, where financial-promotion law is stricter than X's new baseline. What's actually unsettled is narrower than that carve-out. There are reports that part of the change was walked back shortly after launch, which makes the live policy page, not this writeup or any other from March 2026, the thing to check before you build a UK campaign plan around X's new openness.

Platform approval doesn't replace the FCA financial promotion rules

This is the part the vendor guides on this topic consistently skip, and it's the one that actually costs UK-facing teams money when they get it wrong.

Google, Meta and X are each checking your ad against their own commercial policy, which comes down to whether the category is permitted and whether the business holds the certification it claims to hold. None of that is an assessment of the UK's financial promotion regime.

If your ad reaches UK consumers, it needs the FCA's prescribed risk warning and, in most cases, approval from an FCA-authorised person under PS23/6, regardless of what the platform's own review decided. An ad can be fully certified on Google, fully approved on Meta, and still be an unlawful financial promotion in the UK if it skips that second gate. We've covered the FCA side in detail, including the four lawful routes to compliant promotion and what changed in the July 2026 regulatory update, in our crypto marketing compliance guide.

Treat the platform's approval and the FCA's approval as two separate sign-offs that happen to run in parallel, not one process with two names.

Why crypto ads get rejected, and how to fix it before resubmitting

Most rejections we see trace back to the same handful of causes, and each one is fixable before you resubmit rather than after.

Misclassification is the one that surprises people most, because the product itself was never the problem. The platform's automated review read the business as a different category than the one applied for, usually because the landing page headline or the first paragraph used language the system matched to something else. Strip that ambiguity out and make the product category the first thing a reviewer, human or automated, would read.

Missing jurisdiction-specific registration catches teams who certified correctly in one market and assumed the same certification carried over to the next. It doesn't. Confirm the underlying regulatory registration in every target country before the certification application goes in, not alongside it.

Then there's the landing page itself. We've seen the ad pass review cleanly while the page it points to buried the risk disclosure below the fold, or dropped the FCA-prescribed warning text entirely. The fix there is almost embarrassingly simple: the warning needs to be visible without scrolling or clicking, on the ad and the destination page both.

Appealing a rejection without fixing the underlying cause just restarts the same review against the same problem. We've watched accounts burn two or three cycles on a landing page issue a five-minute audit would have caught first.

A pre-submission checklist you can run this week

Before you submit a crypto ad to any of the three platforms, run this against the campaign:

  1. Certification or permission status confirmed for the specific platform and the specific product category, not a general "we're certified" assumption carried over from a different market.
  2. Regulatory registration verified in every country you're targeting (FCA in the UK, MiCA CASP in the EU, FinCEN in the US), checked before the certification application, not during it.
  3. Landing page leads with plain product description, with the category unambiguous in the first screen a reviewer sees.
  4. FCA risk warning present and visible without scrolling, on both the ad creative and the landing page, if any part of your audience is in the UK.
  5. No return projections, urgency framing, or guaranteed-outcome language anywhere in the creative, which Meta and the FCA both flag independently.

If you're running the same campaign across Google, Meta and X simultaneously, that checklist runs three times with three different answers, which is where most in-house teams lose the weeks that an agency running all three in parallel doesn't. If you want a second pair of eyes on a campaign before it goes to review, book a call and we'll walk through what's actually blocking approval.