Campaigns can use **Push** with a plain-text title and message. Review the current message and eligible recipient count before queueing a saved draft. Saving or editing a draft does not send it. Email and SMS remain separate choices; **Both** means email and SMS.

Push requires the client's current consent for your venue, enabled notification preferences and an eligible Consumer or venue Branded app device. Installing an app or buying something does not grant marketing consent. Clients can change their venue's Push consent in their privacy preferences. Quiet hours and daily limits still apply. When these delay delivery, the campaign continues later with its original recipients and checks permission again. Once delivery starts, changing the message requires a new draft.

Delivery details distinguish provider acceptance from later device-service receipts. A client with several devices is counted once when a device request is accepted. The report shows accepted, failed, suppressed, pending and uncertain device counts. Provider acceptance or a receipt does not prove the person read the notification.

Select clients with confirmed provider acceptance to prepare a correction or apology as a new draft, including a Push draft. Consent is checked again before that draft is sent. An uncertain original request is not automatically resent. If a campaign pauses, inspect its original delivery details before preparing follow-up.

Push test delivery is unavailable in the campaign editor. The Business app links to the authenticated web delivery report; campaign authoring remains on the web.

Purchase-history rules retain their existing policy restriction. This update does not enable history targeting or change the venue-specific catalogue choices and custom purchase dates.