Understanding Movago Ads

Movago Ads is a browser-based workspace for brands to manage advertising campaigns and creatives across Movago placements. This article explains understanding movago ads, including the main workflow, relevant conditions, and what to expect in the app.

Overview and key details

Movago Ads is where a business pays to show creatives inside the Movago apps.
Three objects, in this order of meaning:
1. Ad set — a reusable delivery template. It stores placement (where the ad can appear), pay type (view or click), and audience. It is not a charge by itself.
2. Campaign — the paid flight. It picks an objective, an existing ad set, a budget, and dates, then charges a card once for the budget plus the 2.2% platform fee.
3. Ad — the creative attached to an active, paid campaign. Image or video, copy, button, and landing URL. Creating an ad does not charge the card. The campaign charge is what pays for delivery.
Ads appear in the Movago rider experience (home, trips, events, marketplace, and the other placements listed below). They do not run as a separate public website.
Support in this product is the Ask Movago Ads Assistant panel on the dashboard overview. Maya greets first. Suggested questions sit under that greeting until the person sends a message. Clicking a suggestion sends it.

What to expect

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.

If something is unavailable

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.