Meta Conversions API for Commerce7: every option compared

Why a Commerce7 winery needs the Conversions API

The Meta pixel runs in the visitor’s browser. Ad blockers and Safari’s privacy settings stop a share of it, and it never sees a sale that doesn’t happen on the website. Meta’s Conversions API is the server route: events go from a server straight to Meta, with the buyer’s email and phone hashed so Meta can match them to an account.

For most online shops the gap is the blocked browsers. For a winery it’s bigger, because so much is sold where no browser is involved: the tasting room, phone orders, club signups taken in person, and bookings. Whether those reach Meta depends on the option you choose.

The five options

1. Meta’s own one-click setup

Since spring 2026, Events Manager offers a free one-click server connection, shown as Conversions API with Meta or Set up with Meta. Meta runs a server copy of the events your pixel already sends from the browser. It’s free and needs no developer, but it only covers web events: anything your pixel doesn’t send, it doesn’t send either, and there is nothing to configure.

2. Server-side Google Tag Manager

Your Tag Manager sends events to a server container, hosted on Google Cloud or by a service such as Stape, which forwards them to Meta. It’s flexible and also serves Google Analytics and Google Ads. On Commerce7 it starts from the dataLayer events the storefront pushes, so it covers the website. Tasting room and club sales need a developer to send Commerce7’s order webhooks into the container. See 1Pixel vs Stape for this route in detail.

3. Facebook Conversion Tracking, by Treefrog Digital and 5forests

The longest-running Commerce7 app for this, listed since 2020. Its page says it reports web, tasting room, phone and chat orders, with in-store and phone sales sent as physical-store purchases, plus club signups and reservations with a value you assign to each. Every install includes a Google Tag Manager container that places the pixel, and product view and collection tracking is built to order.

4. Facebook Conversions API, by Highway 29 Creative

Its listing says it sends Commerce7 orders, reservations, club signups and email subscribers to Meta using Commerce7 webhooks, following Meta’s Conversions API best practices.

5. 1Pixel, by 7Labs

1Pixel is ours. It sends every paid Commerce7 order (online and tasting room, with in-store sales marked as such), club signups and cancellations, Commerce7 reservations, new customer accounts and Tock bookings on Tock’s Full sync. Club shipment orders are left out by default. An optional website script adds page views, wine views, add to cart and checkout starts with the wine and its price, and an Event Log lists every event with its Commerce7 order number.

Side by side

Option	Sales outside the website	Website events	Listed price	Installs
Conversions API with Meta	No	A copy of what your pixel sends	Free	Not applicable
Server-side Tag Manager	Only if a developer connects Commerce7 webhooks	What your tags send	Hosting from free, plus setup time	Not applicable
Facebook Conversion Tracking	Tasting room, phone and chat orders, club signups, reservations	Pixel placed by an included Tag Manager container; product views built to order	$50 to $150/mo by Commerce7 plan	52
Facebook Conversions API	Orders, reservations, club signups, email subscribers	Not described in the listing	$39/mo	13
1Pixel	Tasting room orders, club signups and cancellations, reservations, Tock bookings, new customers	Optional script: page, wine, cart and checkout events with the wine and price	$29.99/mo	12

Install counts are the numbers Commerce7 published for each app on the date checked above. Treefrog and 5forests’ app is the most installed by a wide margin, and 5forests is a long-established wine marketing agency, which matters if you want your ads and your tracking handled by one company.

How to choose

1. How much do you sell outside the website? If the tasting room and club are a large share of revenue, you want one of the Commerce7 apps, not a web-only route.
2. Who will look after it? Server-side Tag Manager needs someone who maintains containers. The apps run on their own once connected.
3. Do you use Tock? Check each app’s documentation for Tock. 1Pixel documents it; Tock bookings only reach Commerce7 on Tock’s Full sync.
4. Do you need wine-level website events? For catalog ads and retargeting by wine, Meta needs ViewContent and AddToCart with the wine’s ID and price.
5. What does your agency already use? An agency with its own Tag Manager setup may prefer to keep the website events and add an app only for the sales it can’t see.

The mistake to avoid: counting sales twice

Meta counts a sale twice when two sources send the same Purchase without a shared event ID. On Commerce7 sites we see it most often when:

• A Purchase tag in Google Tag Manager stays live after a Conversions API app is installed.
• Tock has its own Meta Pixel ID entered while an app also sends Tock bookings.
• Two apps send to the same pixel, or Meta’s one-click setup is switched on next to an app that already sends the same web events.

Pick one source for each event. If two must run, give both the same event ID. Then compare a week of orders in Commerce7 with purchases in Events Manager: a ratio close to two is the giveaway. A free check.wine check also lists the Meta tags each page sends.

Questions

Is Meta’s free one-click Conversions API enough for a winery?

Only if nearly all your sales happen on the website and your pixel already sends Purchase with the order value. It copies browser events, so tasting room, phone and club sales still never reach Meta.

Which Commerce7 app sends tasting room sales to Meta?

Facebook Conversion Tracking by Treefrog Digital and 5forests and 1Pixel both say they send tasting room orders as in-store purchases. Highway 29 Creative’s listing says it sends Commerce7 orders without naming the channel, so ask them.

Can I install two of these apps?

Not for the same pixel and the same events, or Meta counts sales twice. If you switch apps, turn the old one off on the day the new one goes live.

Do I still need the Meta pixel on my site?

Yes. The pixel and the Conversions API work together: the browser events help Meta match visitors to ad clicks, and the server events fill in what the browser misses.