How Domino's turns cravings into orders

What the published story shows#

Domino's published Meta story describes localised demand generation at national scale: brand creative adapted per market, ordering journeys kept short, and delivery occasions matched to dayparts. The directional lesson is localisation without fragmentation. Browse Meta own business success stories for the original, then apply the frame below.

Multi-location brands should read this as structure, not statistics: your catchments, ticket values and dayparts differ, so copy the localisation method and test the outcomes. The hub places the story in the family, and our local playbook extends the method.

Localisation without fragmentation#

Localise the creative, consolidate the structure: one national campaign frame with store-catchment ad sets and localised copy beats fifty micro-campaigns that never exit learning. Location targeting with sensible radii keeps delivery honest. Location targeting sets the radii, consolidation protects learning.

Swap the store name, the local offer and the hero image per catchment while the concept stays national; difference lives in relevance, not reinvention. Diversification explains why concepts scale and variants localise.

Review catchment radii quarterly against delivery data: new stores open, zones reshape, and audiences drift across boundaries over time. Keep a simple map of spend versus store revenue per catchment so winners fund tests and strugglers get diagnoses, not just more budget.

Message journeys for the hungry#

Click-to-message ads catch buyers mid-craving with a question, not a form: opening hours, deals tonight, order tracking. Keep the automated replies short, factual and always escorted to ordering, with a human handoff where value justifies it. Our message guide builds the flow.

Measure cost per conversation started and conversations that reach ordering, not vanity replies. Route message leads into the same reporting as app and web orders so channels compete fairly. Meta own click-to-message specs list the supported placements.

App demand as the home base#

Where an app exists, App campaigns with app events as the optimisation goal turn Meta into a re-ordering machine: installs for growth, purchases and re-orders for value. Deep-link every ad past the app homepage to the deal or menu it promised. Our app playbook stages the event ladder.

Split new installers from lapsed re-engagement so budgets reflect value: a returning customer outbids a cold install most weeks. Prospecting splits apply inside the app funnel too.

Feed app events back through the SDK plus server-side matching so re-order value trains the auction on profit, not installs. Creative for lapsed buyers should lead with what is new since they left: menu additions, faster tracking, loyalty rewards.

Reading store-level demand#

Report by catchment, daypart and journey, never as one blended CPA: a national average hides the ten stores that need help and the ten that fund everything. Thumb-stop and CTR judge creative, conversation and order rates judge the journey, store revenue judges the account.

Hold out matched catchments when testing new creative so reads survive local noise like weather and fixtures. Our A/B rules set the clean-read standard, and attribution windows should match the craving cycle, not the default.

Copy this structure this week#

One consolidated campaign frame, catchment ad sets with localised copy, message journeys for questions and app or web journeys for orders, catchment-level reporting. That is the Domino's pattern at frame level.

Start localisation with location setup, wire journeys per the message guide, and ask our team for a multi-location audit before your next peak occasion.

Frequently asked questions#