1Pixel – Meta CAPI, Facebook Server-Side Tracking & Tock

OVERVIEW

Your Facebook and Instagram ads are working harder than you think — but Meta can't see the results.

Every time a winery customer uses an iPhone, Safari, Firefox, or an ad blocker, the Facebook Pixel gets blocked and Meta never sees the sale. Your Facebook Ads ROAS looks worse than it really is, Meta stops optimizing your campaigns toward buyers, and you end up spending more to get the same results.

1Pixel fixes your Facebook and Meta ad tracking by sending conversion data directly from your Commerce7 store to Meta — no browser involved.

Every wine order, wine club membership, Commerce7 reservation, Tock booking (when synced to Commerce7), and new customer registration gets reported to Facebook Ads Manager automatically. You bypass ad blockers, iPhone iOS 14+ tracking restrictions, and Safari privacy limits. You get accurate conversion tracking, better Facebook and Instagram ad attribution, and a true picture of your winery's return on ad spend.

Core order, club, and reservation tracking works without any website or theme changes.

────────────────────────────────────────

WHAT GETS TRACKED IN FACEBOOK ADS MANAGER

Automatically sent from Commerce7 — no setup beyond the initial install:

• Wine orders — reported as Purchase conversions in Facebook Ads, with full order value and currency. Works for online orders, POS sales, and tasting room purchases.
• Wine club signups — reported as Subscribe conversions, so Facebook knows when your ads turn visitors into club members.
• Wine club cancellations — reported as CancelMembership so your Facebook audience data stays accurate.
• Commerce7 reservations — reported as Lead conversions for bookings created in Commerce7's own reservation calendar (not Tock).
• Tock bookings (Full Commerce7 integration) — when Tock syncs each booking into Commerce7 as an order, 1Pixel sends it to Meta as Purchase by default (with booking value). Optional toggle sends Lead instead if you want Meta to optimize for "booked a tasting" rather than transaction value. Tock bookings show as Source: Tock booking in your Event Log.
• New customer account registrations — tracked as CompleteRegistration events for audience building.

Each event type can be turned on or off individually from your Commerce7 admin.

Optional website activity tracking (adds a small snippet to your public winery website — not Commerce7 admin):

• Page views, product page views, add-to-cart, and checkout starts reported to Facebook.
• Gives Meta more data to find new customers who look like your best buyers (lookalike audiences).
• Works alongside your existing Facebook Pixel — shared event IDs prevent double-counting when both browser and server events are sent.

Purchase, club, and reservation tracking does not require this snippet. Add it only if you want top-of-funnel website events.

────────────────────────────────────────

TOCK RESERVATIONS — WHAT WINERIES NEED TO KNOW

Many wineries use Tock for tastings and events. 1Pixel tracks Tock bookings when they flow into Commerce7 — not when they stay in Tock alone.

Full integration (Tock linked to Commerce7 so each booking creates a Commerce7 order):
• 1Pixel tracks every booking automatically. • Default: sent to Meta as Purchase with dollar value.
• Optional: enable Send Tock bookings as Lead in Configuration.
• Event Log labels them Source: Tock booking so you can filter Tock traffic separately from wine shop orders.
• Use Simulate Tock booking to test Meta before placing a real reservation.

Partial integration (bookings stay in Tock only):
• 1Pixel cannot track these bookings — Commerce7 never receives them.
• Ask whoever manages your Commerce7 and Tock setup to confirm Full integration is enabled.

Tock cancellations are intentionally not sent to Meta, so your conversion data stays clean.

Native Commerce7 reservations (guests book through Commerce7's calendar, not Tock) always send as Lead when the Commerce7 reservations toggle is on. If you only use Tock for bookings, you can ignore the native reservation setting.

────────────────────────────────────────

SETUP TAKES 5 MINUTES

We offer a free onboarding setup, please schedule the meeting by contacting us at 7labs@dmitru.com

1. Install the app from the Commerce7 App Store.
2. Open the app inside your Commerce7 admin and paste in your Facebook Pixel ID and Meta Conversions API access token (both found in Meta Events Manager → your pixel → Settings).
3. Done — your Commerce7 sales start flowing to Facebook and Instagram Ads automatically.

No developer needed. No theme changes required for core purchase, club, and reservation tracking.

────────────────────────────────────────

TEST BEFORE YOU GO LIVE

You don't have to guess whether tracking works:

1. Copy your Meta Test Event Code from Events Manager → Test Events and paste it into Configuration.
2. Click Save configuration.
3. Use Simulate buttons to test Purchase, club signup, reservation, and Tock booking — events appear in Meta's Test Events tab within seconds, not in your live production data.
4. Run Verify connection to confirm your Pixel ID and access token are valid.
5. Place one real order or booking and confirm Event Log shows Sent status with the correct source.

────────────────────────────────────────

WHY FACEBOOK PIXEL ALONE ISN'T ENOUGH ANYMORE

The Facebook Pixel is a piece of JavaScript that runs in your customer's browser. Since Apple's iOS 14 update in 2021, iPhones block that tracking by default. Safari and Firefox block it too. Ad blockers block it. The result: Meta only sees a fraction of your actual sales.

1Pixel sends conversion data from your Commerce7 server to Facebook's Conversions API (CAPI). The server is never blocked. Every sale, every club signup, every reservation gets through — regardless of what browser or device the customer uses.

Wineries typically recover 30–60% of conversions that were invisible to Meta before using server-side tracking.

────────────────────────────────────────

BETTER FACEBOOK AD TARGETING

Every conversion event sent to Meta includes customer matching data — email, first name, last name, phone number, city, state, zip code, and country — so Facebook can accurately match the purchase to the right Facebook account and credit your ad campaign. Better matching means better lookalike audiences, better retargeting, and lower cost per acquisition.

Purchase events include order value, currency, and product IDs when available.

────────────────────────────────────────

RELIABLE DELIVERY

• Automatic retry — if Meta's API is temporarily unavailable, the app retries automatically (at 1 minute, 5 minutes, and 15 minutes) so no conversions are lost.
• No duplicate conversions — when browser Pixel and server CAPI both fire for the same action, Meta's deduplication prevents the same sale from being counted twice.
• Dual pixel support — run two Facebook pixels simultaneously, useful for agency-managed ad accounts or A/B testing.
• Secondary pixel failures are logged — if a second pixel fails, you see the error in Event Log instead of silent data loss.

────────────────────────────────────────

PRIVACY & CCPA COMPLIANCE

• All customer data (email, name, phone, address) is hashed before being sent to Meta — never stored in plaintext, fully compliant with Meta's data requirements.
• Automatically applies Facebook's Limited Data Use (LDU) flag for California customers to comply with CCPA.
• Compatible with the facebook-limited-data-use customer field used by other Meta integrations.

────────────────────────────────────────

MONITOR EVERYTHING INSIDE COMMERCE7

No need to leave your Commerce7 admin to check if tracking is working:

• Live Event Log — every conversion sent to Facebook, with Meta event name, source (wine order, Tock booking, club signup, website, etc.), delivery status, and error details.
• Event sources panel — live counts grouped by source so you can see at a glance whether Tock bookings, club signups, and wine orders are flowing.
• Tracking health checklist — setup progress and live-traffic checks with plain-English guidance when something needs attention.
• Filter Event Log by event type, delivery status, or source — for example, Tock bookings only.
• Simulate events and verify connection — test every event type before relying on live campaign data.

────────────────────────────────────────

WHAT REQUIRES EXTRA SETUP (HONEST EXPECTATIONS)

• Tock Partial sync — bookings stay in Tock; not trackable until Full integration is enabled in Commerce7/Tock admin.
• Website browsing events (PageView, AddToCart, etc.) — optional snippet on your public winery website; not required for orders, club, or reservations.
• Overlapping Meta Event Setup Tool or GTM rules — disable duplicate automatic rules for the same events before enabling website tracking in 1Pixel, or Meta may count events twice from unrelated sources.

────────────────────────────────────────

Support and documentation are available inside the app. Privacy policy and terms are linked from your Commerce7 app settings.