Topics
Topics
Advertising / Build a campaign
Movago Ads is a browser-based workspace for brands to manage advertising campaigns and creatives across Movago placements.
Movago Ads is a browser-based workspace for brands to manage advertising campaigns and creatives across Movago placements. This article explains why an advertisement may not be delivering, including the main workflow, relevant conditions, and what to expect in the app.
Use this when they say “my ad isn’t showing” or “I created it but nothing happened”:
1. Brand Kit has the image, or the video plus a cover, and the video is 30 seconds or less.
2. Ad set exists, with the placement and audience they expect.
3. Campaign uses that ad set, has dates that include today, is Active (not paused, stopped, completed, rejected, depleted, pending review, or processing), and the card charge succeeded.
4. Ad is published on that campaign and is Active, with a landing URL and a button.
5. Placement matches where they are looking in the Movago app. A home ad does not have to appear on a trip screen.
7. Forecast numbers are estimates. Low inventory, a small audience, or high competition can limit delivery.
8. A depleted campaign needs a refill. A rejected campaign needs review. Pending review and processing are not live yet.
Ad sets define delivery, campaigns pay for that delivery, and ads supply the creative. Each has its own status and requirements. Changes become visible when the corresponding action succeeds; an unavailable button, incomplete setup, or pending payment means the next stage has not yet been reached. Always rely on the status displayed for the particular item rather than assuming it has progressed.
Review the eligibility requirements and status described above. Missing required information, an earlier incomplete step, or an account-level limitation may prevent the action. Where the application displays a specific reason or a required next step, that message is the best guide to resolving the issue. For payments or decisions requiring review, use the relevant in-app support channel rather than assuming an automatic reversal or approval.
Did this answer your question?