SmartyPOS

Ads that learn from what was actually sold.

Clicks are not revenue. We send each paid check from the POS back to Meta and Google Ads as a conversion, so the algorithms optimise for guests who really ordered.

Live

What is connected

POS to Meta CAPI

Every paid check becomes a conversion. Sole Mio's event match quality reached 8.93.

Google Ads offline conversions

The same checks go to Google Ads. Calls from ads are matched to POS checks by phone number.

Audiences from the POS

103,000 customer records uploaded as Customer Match with 0 errors; existing guests excluded from acquisition ads.

Weekly ROAS reports

With recommendations, plus a marketing data warehouse joining Google Ads, Meta, GA4 and POS.

An example from Eleni's

Matching calls to checks showed Google Maps Local at 5.44x return against Search at 0.68x. That split is invisible in the ad platform alone, and it moved budget.

Every campaign we run is geo-restricted to the area the restaurant really serves, and we verify spend by region after launch.

Frequently asked questions

Is this a POS feature or a service?

It is a service built on the POS data we can read through the API. We set it up and monitor it.

Do you send guest data to ad platforms?

Only hashed identifiers in the formats Meta and Google require, and only for guests whose data we are allowed to use.

See it on your menu, your orders, your numbers.

A 45-minute call. We open Syrve with your concept in mind, show what is live today, and tell you straight whether it fits.