Advertising creative sizes and specifications

The dimensions below are JollyBee's recommended starting canvases. They match each placement's intended shape and give the community a consistent specification to send to advertisers, although responsive rendering can crop the artwork differently on some surfaces.

They are recommendations, not upload validation. The placement's Dimensions field is free text and JollyBee does not reject an image solely because its pixel dimensions differ. Artwork with the wrong aspect ratio can still be cropped or letterboxed badly, so build to the recommendation whenever possible.

General image specification

For the safest result across web, mobile, email and print:

• Supply PNG or JPG artwork. The general creative uploader also accepts WebP and GIF, but PNG/JPG work on every current surface; the day-permit PDF can embed PNG/JPG only.
• Keep each upload at or below 10 MB.
• Start with the recommended canvas and aspect ratio, even if you export at a higher pixel density. Responsive page cards may still crop it differently.
• Keep the logo, offer, price, faces and all essential text inside a central safe area with roughly 10% clear space on every edge.
• Make type large enough for a phone. Section banners also run in mobile browsers and the app.
• Avoid a tiny button drawn at the edge. The whole visual unit is clickable.
• Add a short Headline even for an image creative; it becomes useful alternative text on web, widget and email surfaces when the image cannot be seen.
• Add a complete http:// or https:// Target URL and test it. Without a valid web destination, a tracked click falls back to the JollyBee home page.

JollyBee-hosted page cards and mobile-app image slots use fixed-height crops to fill their cards. Widget and email artwork scale proportionally with automatic height. Important content therefore belongs near the centre, not against an edge.

Page, app and dashboard placements

• Premium page banner — 970 × 120 px (970x120). A wide strip below the community navigation, seen by both public visitors and signed-in members. Keep it panoramic and use very little copy.
• Section banner (web & app) — 728 × 90 px (728x90). Runs on the visitor-facing community overview, in feed and forum areas, and in mobile community banner positions. Treat the middle as the safest mobile crop.
• Overview tile — 300 × 250 px (300x250). A medium rectangle on the joined-member overview, in deals areas and on the mobile home experience. This is the one tall visual unit; a centred product, portrait or short offer works better than a panoramic scene.

Commerce, events and embedded widgets

• Shop sponsor — 600 × 200 px (600x200). Appears with the community store. Keep the offer relevant to shopping and leave room for the external Sponsored label.
• Event sponsor — 600 × 200 px (600x200). Appears on the events area and individual event pages. Put event-specific dates in the creative only when the campaign will be completed promptly after that event.
• Widget banner — 728 × 90 px (728x90). Appears in a community storefront embedded on its own website. It is still served and tracked by JollyBee even though the surrounding page is on another domain.

Email placements

• Email notices footer — 600 × 150 px (600x150). A compact strip at the end of eligible community email. Marketing sends may carry it automatically. Transactional notices carry it only when the community enables Sponsored footers on notice emails under Communications → Settings.
• Newsletter — 600 × 200 px (600x200). An in-body newsletter unit. The community can position it with the designer's Sponsored slot block. Email sponsorship uses one shared priority: an eligible Newsletter campaign is chosen first and Email notices footer is the fallback. This ordering also applies when resolving a regular footer, so a live Newsletter campaign can pre-empt a separate footer campaign.

Email clients scale the image down to the available width without cropping it. Avoid animation-dependent messaging: even when a GIF uploads, some inboxes show only one frame. Put the full offer in the first frame or use a static PNG/JPG.

Day-permit sponsor

• Day permit sponsor — 1600 × 260 px (1600x260). A print-ready band below the ticket on the day-permit PDF, approximately 189 × 31 mm on the page.

Use PNG or JPG for this placement. The PDF renderer cannot embed WebP or GIF and falls back to the creative's headline and body if it cannot load the artwork. Paper is not clickable, so JollyBee prints a QR code that uses the tracked target link; use a short CTA that still makes sense beside a QR code.

Placements without a banner size

• Sponsored message — no image size. The advertiser identity comes from the campaign, but an active creative record is still required even though no artwork is shown. The message displays the advertiser name inside the community's sponsored-line template. The community must set that line under Communications → Settings, normally This message is brought to you by {{sponsor}}. Leave it blank and the sponsored attribution is disabled. If the line is configured but no sponsored-message campaign is eligible, the current sender substitutes JollyBee for the sponsor and still appends the line. Current queued marketing campaigns add the line to in-app, push and free-text or in-session WhatsApp messages, not pre-approved WhatsApp templates. Multi-channel cascade sends add it to in-app, push, SMS and free-text WhatsApp. Email sponsorship uses the email placements above.
• Sponsored map pin — no image size. The pin uses a registered business profile's name, logo and coordinates. Complete Address, Latitude and Longitude in the business Profile. A logo is recommended. When an active creative exists, the pin uses its tracked click, so give that creative a valid Target URL; with no active creative, the business website is used directly when available and the visit is not recorded as an ad click.

A manual advertiser without a registered business profile cannot supply the business identity and coordinates a map pin needs. Book map inventory from a verified business account.

Map-pin inventory is currently network-wide rather than limited to the community whose placement was booked: an eligible business can appear on JollyBee's main Map and Events maps. The maps show one pin per business. Avoid overlapping active map-pin campaigns for the same business because only one pin is shown and which campaign receives creative click attribution is not guaranteed.

Image, text and HTML formats

Choose Image for finished artwork. On current web, app and email units, the image is the visible body; the Headline, Body and CTA fields do not overlay it, so bake essential visible copy into the artwork.

Choose Text when the placement should render a headline, supporting body and JollyBee-styled CTA without artwork.

The owner console also lists HTML. It does not accept or publish arbitrary markup: current serving surfaces render its safe Headline, Body and CTA fields like structured text. Use Text unless the community has a tested reason to label the record HTML.

Multiple variations and weights

A campaign may hold several active creatives. For placements other than sponsored map pins, JollyBee rotates them using their positive integer Weight:

• 1 and 1 give two variations an even opportunity over time.
• 2 and 1 give the first roughly twice the opportunity of the second.
• Paused creatives receive no impressions.

Rotation is random and weighted, so a small sample will not match the ratio exactly. Sponsored map pins do not use creative weights. Current analytics combine results at campaign level rather than showing CTR by creative, so use weights to manage delivery but do not treat the dashboard as a variation-level comparison.