Placements

Where you put the ad decides how your users feel about it and how well it converts, which sets your revenue share tier.

One slot per page

Specify shows one ad per page. A single slot in the right place earns more than several competing for attention, and it respects your users. Two slots with the same image format on one page aren't supported.

To compare placements, put them on different pages or show different visitors different variants. See A/B testing with ad unit IDs.

Start with a banner

A banner is the fastest way to go live. It drops into most layouts, and you can iterate from there. The SDK supports four image formats:

See each one with real ads in the playground before you commit to a slot size.

Go native when you can

Ads that feel like part of your app convert better than banners, and they annoy your users less. Native placements that work well:

• Inline recommendations in a list of tokens, pools or protocols the user is browsing
• "Related" cards after the user completes an action, such as a swap or a deposit
• Empty states: when a section has no activity yet, a relevant product reads as a suggestion
• Discovery feeds, where finding new protocols is the point

The common thread: the ad arrives when the user wants something, and tries to be it.

Custom placements

If you have a placement in mind that doesn't fit, book a call and we'll design it with you. Many native placements need nothing new: the existing image formats plus your own layout are enough. A new image format takes longer, because every advertiser then has to produce artwork for it.