Wonderkind

When a campaign fails to deploy, Wonderkind records the error returned by the ad platform. This article explains the most common deployment failures and how to resolve them.

Check the status badge. It will show Draft or Error if deployment failed.

Click ⋯, Deployment history to see the full error log.

1. Open the campaign that failed to deploy.
2. Check the status badge. It will show Draft or Error if deployment failed.
3. Click ⋯, Deployment history to see the full error log.

Cause: The Meta ad account linked to this Wonderkind Account is no longer accessible. This happens after a token expiry, permission revocation, or if the ad account was disabled in Meta Business Manager.

Go to Account Settings, Integrations.

Reconnect Meta by clicking Connect and completing the OAuth flow.

1. Go to Account Settings, Integrations.
2. Reconnect Meta by clicking Connect and completing the OAuth flow.
3. Retry the campaign deployment.

Cause: The creative asset does not meet Meta's requirements.

Check the Renditions tab. If a Meta rendition shows Error, click Retry.

If the original image is too small (less than 1200 × 628 px), upload a higher resolution version.

Redeploy the campaign once the rendition shows Ready.

1. Open the asset in Asset Studio.
2. Check the Renditions tab. If a Meta rendition shows Error, click Retry.
3. If the original image is too small (less than 1200 × 628 px), upload a higher resolution version.
4. Redeploy the campaign once the rendition shows Ready.

Cause: Meta's automated policy review rejected one or more ad headlines or descriptions. Common triggers:

References to personal attributes (race, religion, political affiliation, health conditions)

Misleading claims or superlatives without substantiation ("the best job ever")

Too much text in the image (&gt;20% coverage)

- References to personal attributes (race, religion, political affiliation, health conditions)
- Misleading claims or superlatives without substantiation ("the best job ever")
- Too much text in the image (&gt;20% coverage)

Review the rejected ad copy in the campaign.

Edit the flagged headline or description to remove policy-violating language.

If an image was flagged for text overlay, open the asset in Asset Studio, go to the Studio tab and adjust the crop to reduce visible text, or upload a version of the image with less text.

1. Review the rejected ad copy in the campaign.
2. Edit the flagged headline or description to remove policy-violating language.
3. If an image was flagged for text overlay, open the asset in Asset Studio, go to the Studio tab and adjust the crop to reduce visible text, or upload a version of the image with less text.
4. Redeploy.

Cause: Meta requires a minimum daily budget (varies by currency, typically €1–€5).

Increase the daily budget above the minimum.

1. Edit the campaign.
2. Increase the daily budget above the minimum.
3. Redeploy.

Cause: The Google account used to authorize access no longer has permission to manage the Customer ID.

1. Go to Account Settings, Integrations.
2. Reconnect Google Ads.
3. Retry the deployment.

Cause: Google Display requires minimum dimensions for each format.

Go to Renditions and retry any Google renditions showing Error.

If the original image is too small, upload a larger version.

1. Open the asset in Asset Studio.
2. Go to Renditions and retry any Google renditions showing Error.
3. If the original image is too small, upload a larger version.
4. Redeploy.

Campaign deploys but shows no impressions

Cause: The campaign is in Learning phase (Meta) or pending platform review. Most new campaigns take 24–48 hours to exit this phase.

What to do: Wait 24 hours. If still no delivery, check the campaign in Meta Ads Manager directly for any account-level flags or spend limits.

Campaign shows "Pending" status indefinitely

Cause: A deployment request is still in progress, or a confirmation was not received.

If still Pending, click ⋯, Retry deployment.

If the retry also stays Pending, contact Wonderkind support.

1. Wait 15 minutes.
2. If still Pending, click ⋯, Retry deployment.
3. If the retry also stays Pending, contact Wonderkind support.

Connecting Meta (Facebook &amp; Instagram)

- Publishing &amp; Deploying Campaigns
- Connecting Meta (Facebook &amp; Instagram)
- Connecting Google Ads

Campaign Deployment Errors

Find answers and get help from Intercom Support and Community Experts

Conversations you've started through the messenger will appear here.

No conversations created by you

Try using different keywords or checking for typos.

No conversations found

Title

This site employs cookies and other technologies that we and our third party vendors use to monitor and record personal information about you and your interactions with the site (including content viewed, cursor movements, screen recordings, and chat contents) for the purposes described in our Cookie Policy. By continuing to visit our site, you agree to our {websiteTermsLink}, {privacyPolicyLink} and {cookiePolicyLink}.

This site uses cookies and similar technologies ("cookies") as strictly necessary for site operation. We and our partners also would like to set additional cookies to enable site performance analytics, functionality, advertising and social media features. See our {cookiePolicyLink} for details. You can change your cookie preferences in our Cookie Settings.

We use cookies to make our site work and also for analytics and advertising purposes. You can enable or disable optional cookies as desired. See our {cookiePolicyLink} for more details.

Advertising cookies are set by our advertising partners to collect information about your use of the site, our communications, and other online services over time and with different browsers and devices. They use this information to show you ads online that they think will interest you and measure the ads' performance. Social media cookies are set by social media platforms to enable you to share content on those platforms, and are capable of tracking information about your activity across other online services for use as described in their privacy policies.

These cookies enable the website to provide enhanced functionality and personalisation. They may be set by us or by third party providers whose services we have added to our pages. If you do not allow these cookies then some or all of these services may not function properly.

These cookies are necessary for the website to function and cannot be switched off in our systems.

These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us to know which pages are the most and least popular and see how visitors move around the site.

You have the right to opt out of the sale of your personal information. See our {cookiePolicyLink} for more details about how we use your data.

Your Privacy Choices

We use cookies to enhance your experience. You can customize your cookie preferences below. See our {cookiePolicyLink} for more details.

Cookie Settings

Empty Help Center

Uh oh. That page doesn’t exist.

Home

Search results

Disappointed

Neutral

Smiley

Thinking...

Searching through sources...

Analyzing...

Tickets submitted through the messenger or by a support agent in your conversation will appear here.

No tickets created by you

No tickets found

Track the progress of all tickets related to your company.

Tickets portal.

{assigneeName} needs more information from you

Tickets

No access to tickets portal

Search and ask

Find guides, answers, and references.

Skip the search. Describe what you’re trying to do and get a grounded answer.

Browse articles and guides in this topic.

Create your workspace and invite the people you work with.

Set up your account

Build your first workflow and watch it run end to end.

Ship something

Connect the tools your team already uses to bring data in.

Connect your stack

A quick lap of the product so you know where everything lives.

{appName} in 60 seconds

This prototype demo is aware that you are reading “{title}”. It can point you back to the current article, but a production article-aware Fin contract is still follow-up work.

Prototype article-aware answer

Because you already asked about invitations, this prototype demo can add the follow-up: use the role selector before sending each invite to limit access to the teammate responsibilities.

Prototype role-limiting follow-up

This prototype demo suggests starting with your workspace profile, inviting the team members who need access, and then connecting the integrations you use.

Prototype getting-started answer

In this prototype demo, integrations are configured from workspace settings. Choose the integration, connect the account, and review the enabled permissions.

Prototype integrations answer

In this prototype demo, invite teammates from workspace settings, then choose the access each teammate needs before sending the invitation.

Prototype invite-team answer

This prototype demo does not have a scripted answer for that question yet. Try asking how to invite your team or open a source article. No production Fin API was called.

Prototype answer unavailable

I’ve got this page open. Ask me anything about it and I’ll answer from the docs.

Campaign Deployment Errors

Finding deployment errors

Meta-specific errors

"Ad account not found or not accessible"

"Unsupported image format or dimensions"

"Ad copy rejected by Meta policy"

"Daily budget too low"

Google Ads-specific errors

"Customer ID not authorized"

"Asset rejected: image too small"

General deployment issues

Campaign deploys but shows no impressions

Campaign shows "Pending" status indefinitely

Related articles