Send offline events to destinations
Once you’ve chosen your sales channels and subscription app, Settings → Offline Events lets you turn on offline conversions for each destination separately.
Eligible destinations
Section titled “Eligible destinations”| Destination | What it receives |
|---|---|
| Meta Conversions API | A Purchase event, sent with action_source: physical_store for POS orders or system_generated for recurring/subscription orders. |
| TikTok Events API | A CompletePayment event, sent with an offline event source. |
| Pinterest Conversions API | A checkout event, sent with action_source: offline. |
| Google Ads Offline Conversions | An offline conversion import, only for orders that carry a Google click ID captured earlier by the storefront pixel. |
Each destination has its own toggle, and each is gated on that destination already being configured, you need a Meta Pixel with the Conversions API enabled, a TikTok Pixel with the Events API and catalog connected, a Pinterest Conversion Tag with the Conversions API enabled, or a Google Ads account with a customer ID and conversion actions set up, before its offline toggle becomes available. Meta, TikTok, and Pinterest also each have a separate toggle specifically for recurring subscription orders, so you can send one-time offline orders and subscription renewals to a destination independently of each other.
What customer data is sent, and how
Section titled “What customer data is sent, and how”Offline conversions carry hashed customer identifiers so the destination can match the order to the right ad audience, using the same SHA-256 hashing method Meta, TikTok, Pinterest, and Google all expect for enhanced matching:
- Email and phone, hashed.
- Name, street, city, state/region, postal code, and country, hashed.
- Customer ID, hashed, when the order is tied to a Shopify customer account.
Google Ads’ offline import additionally uses the plain (unhashed) postal code and country, since Google’s own address-matching format requires those two fields unhashed, everything else follows the same hashing as above.
Máximo never sends plaintext email or phone to a destination. Only the hashed forms are transmitted.
Beyond identifiers, an offline conversion carries the order value, currency, and line items (matched to the same catalog IDs used in your product feeds), so it reconciles cleanly with the rest of your conversion data.
No historical backfill
Section titled “No historical backfill”Turning on offline events only affects orders paid after you enable it, Máximo doesn’t retroactively send past orders to a destination when you turn on a new channel or destination toggle. If you need a destination to reflect offline sales from before you enabled it, those historical orders won’t be sent.
Verifying delivery
Section titled “Verifying delivery”After enabling a destination, check the Delivery monitor to confirm offline conversions are arriving successfully. It groups delivery attempts by destination and surfaces the reason for any failures, which is the fastest way to tell whether an offline order actually reached a given platform.