Crypto ads on Google, Meta and X: the buyer's checklist

Which crypto ad check comes first?

First 24 hours: map the offer, advertiser and destination before writing ads. Google certification may be an eligibility step. It does not replace ad review. Meta and X have separate policy checks. A decision on one platform does not settle another.

Start with the platform tied to your planned campaign. Check the other channels separately. Choose Google if certification or account requirements apply to your offer.

Choose Meta or X if those are your planned placements. Review their current rules before creative is final. Keep the product facts consistent across all three.

This is a planning order, not an approval timeline. For paid campaign planning, see Google Ads for crypto projects.

5 checks before each platform submission

5 checks, in order: define the offer, verify eligibility, prepare evidence, test the destination, then log the response. This sequence catches basic gaps before platform review. Run it separately for Google, Meta and X.

1. Describe the offer. State what the product does. Name the action the ad invites.
2. Identify the advertiser. Match the responsible organization across the account, site and campaign materials.
3. Check the platform. Review current policy and account notices. For Google, confirm whether certification applies to this offer and location.
4. Compare claims and destination. Ensure the page explains the advertised product. Check that it supports the ad's claims.
5. Save the submission. Keep the exact creative, destination URL and platform response together.

Do not treat an older campaign decision as reusable clearance. Product, location, account details or creative may differ.

If your campaign supports a token launch, align its ad review with the token launch marketing checklist. Name one owner for the final copy and destination. That makes the submitted version easy to identify.

6 inputs for a useful policy check

6 inputs make a pre-submit check concrete: product, advertiser, locations, account status, draft ad and destination. Send the same factual description that appears on your site. Differences in names or offer details make policy questions harder to resolve.

• Product: a plain-language description of what people can access.
• Advertiser: responsible organization and relevant account details.
• Locations: every market the campaign intends to target.
• Certification: current Google status or application details, if relevant.
• Creative: final or near-final text and image for each placement.
• Destination: working page URL, including the action users can take.

Add supporting records only when the current platform process requests them. Do not assume a social profile can explain missing landing-page information. Make the offer, responsible advertiser and next action clear on the destination itself.

For projects combining paid promotion with organic discussion, assign separate owners to each channel. The crypto Telegram community guide covers community planning. It does not replace ad-policy checks. Keep the core product description aligned across both.

When should each crypto ad check happen?

3 review windows keep the work in order: before creative, before submission and after a platform response. Use the first window for eligibility and product clarity. Use the second for the finished ad and destination. Use the third to record the decision and requested edits.

Keep the windows distinct. Certification, where applicable, addresses eligibility. The submitted ad and destination still receive their own review.

If a notice asks for a change, compare it with the saved version. Do not rely on memory. Record the platform, date checked, ad version and next action in one campaign file.

3 review points that can stop a submission

3 common gaps deserve a direct check: unclear eligibility, unsupported claims and a destination that does not explain the offer. Find them before submission. That leaves time to revise the ad and landing page together.

• Eligibility gap: the offer, target location or advertiser details are unclear.
• Claim gap: the ad promises something the destination does not support.
• Destination gap: the page fails to identify the product or explain the next action.

Google may apply certification requirements to eligible offers. Google, Meta and X each decide on submitted ads and destinations. No checklist controls those decisions or promises acceptance or continued delivery. We can verify the materials and agreed review work.

1 campaign file for ads across Google, Meta and X

1 campaign file makes cross-platform review easier to manage. Store shared product facts once. Keep a separate policy check, creative version and response for each platform. This prevents a Google decision from being mistaken for clearance on Meta or X.

Track the product description, advertiser, target locations, destination URL and current creative. Add the platform checked, policy questions raised, version submitted and response received. When wording changes, keep the old record and platform notice. Retain both versions so the team can trace what changed.

DigitalMedia1 reviews the product description, platform eligibility notes, creative and landing page together before submission. You get a focused list of gaps to resolve. We do not send generic instructions to revise everything.

This helps when a launch plan also includes creator work. See the crypto KOL campaign guide. Keep its materials separate from paid ads.

Send us the product description, advertiser details, target locations, draft creative and destination URL. We will check them together. You will get the policy questions and page or copy changes to address before submission.

How it works

1. Describe the offerState what the product does, who advertises it and what action the ad asks a user to take. Name the intended locations.
2. Check each platformReview Google, Meta or X separately. Note current certification or account requirements that apply.
3. Gather requested recordsCollect materials requested by the current platform process. Align the product and advertiser details across them.
4. Review the destinationCheck that the page works and explains the offer. Confirm it supports the creative's claims.
5. Submit and logSave the exact version sent and the platform response. Record each change before resubmission.