A steadier way through crypto advertising rules

Start with what you’re asking people to see

A useful first check starts with the offer, not the ad format. Write down what the project does. Note who will advertise it and where the campaign should appear. Then check those details against the current rules for Google, Meta or X. A campaign that describes a token may raise different questions from one promoting a wallet or software product.

Keep the first note short. Name the legal entity behind the advertising account. Note the destination page, product in everyday words, and countries or regions you have in mind. If any of those details are still undecided, mark them as open. Don’t fill in assumptions.

This small record gives the team a shared starting point. It also makes changes easier to spot. If the landing page shifts from explaining software to promoting a financial offer, pause. Check eligibility again before preparing new ads. For broader launch planning, our token launch checklist can help connect campaign choices with the rest of your release plan.

Three checks before anyone drafts an ad

Before writing creative, take 3 checks in order. This keeps the team from polishing an ad for a product or market that needs a different plan.

1. Describe the product. Write one plain sentence about what it is. Say what a visitor can do with it. Note whether it’s a token, exchange, wallet or software service. Avoid broad labels that leave the offer unclear.
2. Name the market and account owner. List the locations you hope to reach. Identify the legal entity that controls the ad account. Check current platform guidance for those details. Don’t assume another campaign’s eligibility carries over.
3. Compare the destination. Read the landing page beside the product description. Confirm that the page explains the same offer. Check that its main claims match what the ad will say.

Imagine a team plans to promote a wallet in one market. Then it considers adding other countries. We’d pause at that change and check the relevant requirements again. We’d do that before the team drafts new versions. For community-first alternatives to paid campaigns, our Telegram community guide offers a separate starting point.

When might Google certification enter the picture?

Google certification is an eligibility step for some cryptocurrency-related ads. It isn’t a blanket approval for every product or campaign. Check Google’s current policy for the exact product and locations you plan to target. Then confirm what information its application asks you to provide.

Put the application details in one place

Gather the advertiser’s legal identity and the website being promoted. Add a clear description of the offer, the target market and any relevant authorization details. Use the same facts in the account, application and landing page. If those details don’t match, fix the difference before submitting. Google makes the decision. Our Google Ads support for crypto projects can help you prepare campaign materials and an account plan.

Keep certification separate from ad review

Certification and the review of a particular ad are not the same task. Keep a copy of the application and its decision. Then check each new creative and destination before submission. If the offer, target locations or page changes, revisit the current policy and application requirements. That gives the account owner a clear record of what was checked. It also shows what still needs attention.

Make the campaign easy to understand at a glance

Picture a product manager at an infrastructure startup, after a quiet month of posting. The team is ready to test paid ads. But the draft calls the product a token platform while the landing page describes developer software. We’d put the two side by side. Then we’d help the team settle on a clear, accurate description before submission.

A straightforward campaign gives the reviewer and visitor the same account of the offer. Before the account owner submits, check these points:

• The ad names the product in terms a new visitor can follow.
• Each factual claim can be explained and supported by the team.
• The landing page matches the ad and makes the next action clear.
• Links work, and the page can be read on a phone.
• The team saves the exact ad and page versions it submitted.

Say the creative changes after a colleague edits its call to action. Check the destination again, too. A small edit can create a mismatch with the page. Our guide to making a crypto hashtag trend on X covers a different kind of campaign. Keep its planning separate from paid ad review.

Keep a small record the whole team can use

A simple campaign record helps the team understand what it sent. It also shows what the platform said in response. It doesn’t need to be a complicated document. Save the policy guidance you checked, the product and market notes, and the application materials. Keep the final creative, landing-page version and any review message, too.

Choose one person to coordinate edits. That person can note which item changed. They can also make sure the ad and destination still describe the same offer. If a platform raises an issue, read its notice first. Identify whether it points to the account, product description, creative or destination. Then make a focused revision. Keep the earlier version alongside the new one. That way, the team can see what changed.

Imagine two teammates updating the page and ad on the same afternoon. A shared record lets them compare versions before either change goes live. For teams weighing community work alongside paid media, our community growth guide can help you plan that conversation. It keeps the discussion distinct from paid advertising.

Bring the right pieces to a first review

A first review works best when we can see the offer, intended market and actual campaign materials together. At Brand Community, we compare the product description, draft ad and landing page side by side. Then we send one written list of what is clear and what needs attention. The account owner stays in control of platform access and submission.

You can prepare a useful handoff in 3 parts. Start with a short product description and the legal account owner. Add the target locations and the platform you’re considering. Then include draft creative and its destination page. Add any certification or authorization details you already have. We can then help identify inconsistencies and organize the next checks. You won’t need to gather unrelated material.

Once eligibility is clearer, we can help connect the policy check to Google Ads support or another channel plan. Send Brand Community the product summary, target locations and draft destination. We’ll start by putting those pieces beside each other. You’ll see what is ready before the account owner submits.

How it works

1. Describe the offerWrite down what the project promotes. Note who owns the ad account and which locations you are considering.
2. Check the platformReview current requirements for Google, Meta or X separately. Note the guidance you used and whether certification may apply.
3. Compare the materialsRead the draft ad and landing page together. Align the product description, claims and next action before submission.
4. Submit and saveHave the account owner submit the campaign materials. Save the versions, application details and platform response.
5. Make a focused revisionIf the platform identifies an issue, check the named part of the campaign. Revise it and keep the new version with the record.