Integration detail

Appetier + Google Analytics integration

Google Analytics gets your order events, so each channel's revenue sits next to its traffic.

What works

With your access: Paste your GA4 measurement ID, which starts with G-, into Integrations. Appetier sends your page views and ordering events to your property and reads nothing back.

On our own: Without your ID, Appetier still measures every storefront and shows your numbers in the console's Insights tab for 7, 30, or 90 days.

What it does

Sends ordering and funnel events to Google Analytics, from landing page to paid order.

Who it's for

Owners and marketers who want to know which channel brought in paying guests.

Every step from menu to purchase shows in Google Analytics

Every storefront sends one page view per page a guest opens. Four ordering events follow the guest down the funnel. The first fires when the menu shows. The next fires on each add to cart, with the item, quantity, and price including modifiers. Opening checkout sends one more with the cart's value. The last is the purchase, sent once per paid order. They use Google Analytics 4's standard ecommerce names, so GA4's built-in reports read them.

When an order counts as a purchase

A purchase is sent only when the order isn't cancelled and its payment isn't pending or failed. Its transaction ID is the Appetier order number. Google Analytics drops a repeat purchase with the same transaction ID, so a guest who refreshes the confirmation page isn't counted twice. The purchase carries the order total, the currency, and each item with its quantity. That lets you compare revenue by channel against the traffic each channel sent.

Your property sits beside Appetier's

Appetier measures every storefront whether or not you connect anything. Your own numbers show up in the console's Insights tab for 7, 30, or 90 days. To see the same events in your own Google Analytics, paste your GA4 measurement ID into Integrations. It starts with G-. Older Universal Analytics IDs are refused. Your property then gets every page view and ordering event as a second destination. Appetier keeps measuring, so adding or removing your ID never breaks the console numbers.

What Google Analytics never receives

No event carries a guest's name, email, phone number, or address. Guests in the European Economic Area, the UK, and Switzerland are asked first, and analytics storage waits for their consent. The branded apps send none of these events, so Google Analytics shows web traffic only. Order history, loyalty points, and payment details stay in Appetier. Each event is labelled with your brand, which is how the console separates your traffic from other restaurants.

Setup steps

Where it fits in Appetier

Track which campaigns bring guests back to order.

See restaurant marketing
  • Paste your GA4 measurement ID into Integrations
  • Place a test order
  • Check that the purchase shows in Google Analytics
  • Compare channels by revenue

Common questions

What events does Appetier send to Google Analytics?
A page view for each page, then four ordering events: the menu shown, each add to cart, checkout opened, and the purchase. They use Google Analytics 4's standard ecommerce names.
Does Google Analytics replace Appetier reporting?
No. It puts the same order data where your other marketing numbers already live.

Launch first, then connect it

Your storefront goes live in minutes from your logo and a photo of your menu. Add this connection whenever you're ready.