Skip to main content
Banners are promotional tiles shown in the mobile app, on eCommerce pages and in other web channels. You configure them centrally, target them at an audience or a set of stores, and the app fetches whichever ones apply to the customer in front of it.
Your integration only ever reads banners. Creating and scheduling them is done by marketers in the Admin Portal — your job is to fetch the right ones and render them.
Each banner carries an image, a navigation action, a priority and a schedule. Priority controls the order when several banners compete for the same slot.

Lifecycle

Only published banners inside their scheduled window are returned to your channel. A banner that has expired or been disabled simply stops appearing — there is no separate signal, so do not cache the list indefinitely.

Targeting

Banners are filtered before they reach you. Two mechanisms combine:
  • Audience — segments from Audience — Lobyco Segmentation.
  • Chain and store — location-specific campaigns, so a store-scoped banner only reaches customers shopping that estate.
You do not implement this filtering. Request banners for the customer and render what comes back. Every banner has an action that fires when a customer taps it. If you render your own web content in the wrapper, read Web Content in Mobile App first — it covers the constraints that apply inside it.

Images

Banner images are uploaded through the Admin Portal, stored in Azure Blob Storage and delivered to you as URLs. Various formats and dimensions are supported, so treat the image as arbitrary remote content: size it responsively rather than assuming fixed dimensions.

API reference

Endpoint documentation for this service: Banner.
Last modified on August 12, 2026