Is delivery rate enough to judge performance?
No. Delivery tells you whether the campaign reached people. It does not tell you whether the message, segment, or offer actually drove the outcome you wanted.
Track campaign performance in layers: audience targeted, messages delivered, customer responses, and downstream order behavior. Restaurants usually get better decisions when they separate campaign activity from campaign outcome. Delivery alone is not performance, and revenue alone is too late if you never learn which audience, channel, or message actually moved.
Owners often know campaigns went out, but they cannot explain why one worked and another failed. Without clear reporting, the team keeps guessing on audience, message, and channel every time a slow week appears.
The goal is to see both execution quality and business outcome, because those are not the same thing.
| Tracking layer | What to record | Why it matters |
|---|---|---|
| Audience and channel | Who you targeted and where the message was sent. | You cannot compare results meaningfully if the audience changes every time. |
| Delivery outcome | Sent, delivered, failed, and timing details. | A weak campaign idea looks different from a delivery problem. |
| Downstream result | Return orders, redemptions, or channel-attributed conversions. | This is where campaign activity becomes business performance. |
No. Delivery tells you whether the campaign reached people. It does not tell you whether the message, segment, or offer actually drove the outcome you wanted.
You can still learn a lot by comparing audience, channel, delivery, and repeat ordering patterns consistently from campaign to campaign.
Audience segment, channels used, total recipients, sent, delivered, failed, and the downstream action you care about most.
Industry context, Settro public claims, and public app proof are labeled separately so operators can see what is broader restaurant context, what comes from Settro's site, and what is surfaced here from the product workflow itself.
More owner questions in this cluster. Use the question pages when you want the answer first, then jump back to the main workflow page when you are ready to evaluate options.
If you need a reporting model that goes past simple send counts, review the campaign hub that now surfaces delivery and dashboard proof from the product workflow.