MäD

Open a wallet, pick a world, and place your brand where players gather. MäD makes metaverse ad buying a clear flow. Connect your wallet, browse supported worlds and districts, and preview live inventory on a map. Choose formats—billboards, video walls, portals, or 3D objects—then set dates, caps, and goals. Upload assets or use templates to generate variants; add UTM tags if needed. Submit for review, fund the campaign, and let the scheduler handle time zones and rotations. During the flight, a dashboard shows occupancy, reach, heatmaps, and clicks on interactable items. Pause, swap creatives, or extend a placement in one click when a venue trends.

Parcel owners use MäD to turn idle scenes into income. Link parcels, verify ownership, and define ad slots with clear rules (sizes, content, quiet hours). Set a floor price or revenue share, choose approval steps, and decide auto-rotate or exclusive deals. MäD routes eligible campaigns to your space based on fit and time. Preview creatives in a test scene and approve with one tap. Earnings accrue in a wallet-ready balance; withdraw or reinvest. Calendars, alerts, and occupancy forecasts help you plan events around demand.

Creators and agencies build, test, and ship assets in MäD’s workspace. Use spec sheets and starter kits for common engines to export compliant 2D, video, or glTF objects. Swap copy, fonts, and materials; produce day/night versions for lighting. A/B test headlines or CTAs while keeping the same mesh. Bundle themes—launch week, holiday, esports—and publish to a shared library. Bill clients through project folders; rights attach to each placement. QA tools check poly count, audio levels, and load impact before go-live.

Quality stays community-led. Curators score inventory, flag mismatches, and maintain brand-safe lists advertisers can toggle. Members propose changes, adjust fees, and vote on incentives through on-chain governance with public logs. Developers add new worlds through an open SDK, dropping a lightweight component that fetches placements, caches assets, and reports proofs. Webhooks and exports feed your BI stack; a REST API syncs spend and revenue to finance tools. If something breaks, incident reports and rollback controls pause affected slots without touching the rest of a campaign.