Commerce7 has something every winery running Meta ads should know about: an app dedicated to sending winery-specific conversion data directly to Meta. Many wineries and agencies already use it, but it never hurts to explain why it exists, what it actually does, and why better conversion data matters to your advertising.
What is Facebook conversion tracking?
When you run paid advertising across Facebook and Instagram, Meta can attribute sales and other conversions back to people who interacted with your ads. Traditionally, websites do this using the Meta Pixel: a piece of Javascript that runs in the customer’s browser and sends events such as purchases back to Meta.
That browser-side data is useful, but it doesn’t tell the whole story. Especially for wineries.
Why isn’t the Meta Pixel enough?
The Meta Pixel depends on Javascript successfully running in the customer’s browser. Ad blockers, browser privacy protections, consent choices, Javascript errors, tag configuration problems, and other client-side factors can all prevent events from reaching Meta.
For wineries, browser tracking has an even bigger limitation: a lot of your revenue doesn’t happen on your website.
What about tasting room sales? Inbound orders? Club signups? Reservations? Wineries spend thousands of dollars advertising visits, memberships, experiences, and wine sales, but a browser Pixel alone has no way to understand much of what ultimately happens inside Commerce7.
You can manually upload some of that data to Meta, and that’s certainly better than ignoring it. But manual uploads take time, happen after the fact, and don’t give Meta the same consistent stream of conversion signals that an automated integration can provide.
Incomplete conversion data doesn’t just make your reports less accurate. Meta uses conversion signals to understand which customers are taking valuable actions and to optimize campaigns around those results. The better the data going in, the better information Meta has to work with.
If you’re paying for Meta ads and using Commerce7, your advertising platform should know when those ads help generate ecommerce sales, tasting room revenue, club signups, and reservations.
Why we built Facebook Conversion Tracking for Commerce7
We built this app because we needed it ourselves.
At 5forests, we manage digital marketing and Meta advertising campaigns for wineries. We know first hand how important reliable conversion data is for attribution, audience building, campaign optimization, and understanding actual return on ad spend.
Commerce7 already contained much of the conversion data we wanted Meta to understand. The problem was getting that information back to Meta reliably and automatically.
So we teamed up with our friends at Treefrog Digital to create the Facebook Conversion Tracking app for Commerce7.
How does the app work?
The app uses Meta’s Conversions API to send supported Commerce7 conversion events directly from the server rather than relying exclusively on Javascript running in the customer’s browser.
For purchases, reservations, and club signups, the app also identifies how the Commerce7 conversion happened. Website activity, tasting room and other physical-store activity, inbound activity, and other supported channels are sent to Meta with the appropriate conversion source.
Where available, the app includes customer matching and attribution signals from Commerce7, including hashed customer details and Meta click-identification data associated with the conversion. For supported events that may also be sent by the browser Pixel, consistent event identifiers allow Meta to deduplicate the browser and server events rather than counting the same conversion twice.
What does that mean for your winery’s marketing campaigns?
- More complete ROAS attribution for ecommerce, club, reservation, and tasting room campaigns
- More conversion signals for Meta to use when optimizing campaigns
- Better source data for custom audiences and lookalike audiences
- Less dependence on browser-side tracking alone
- No recurring manual uploads of Commerce7 conversion data
No attribution system is perfect, and Meta will never give you a one-to-one view of every customer’s journey. But giving Meta more complete, reliable conversion data gives both the advertising platform and your marketing team a much better dataset to work with.
Built specifically for Commerce7 and winery marketing
This isn’t a generic Meta Pixel plugin adapted to work with a winery website. Facebook Conversion Tracking was built specifically around Commerce7 and the kinds of conversions that matter to wineries.
It’s also built and supported by teams that work with Commerce7 every day. 5forests brings the winery marketing and advertising experience, while Treefrog Digital brings deep Commerce7 development experience. The app has been running in real winery environments for years, alongside the campaigns and Commerce7 implementations our teams support.
That real-world experience continues to shape how the integration works. We’re interested in sending useful conversion signals to Meta reliably, not simply generating the longest possible list of tracking events.
How do I install the app?
The app can be installed directly from Commerce7. Make sure you select the Facebook Conversion Tracking app by Treefrog Digital and 5forests.
You’ll need to connect the app to your Meta Dataset before events can be sent. Our step-by-step setup instructions walk through the complete process, including creating the required Meta access token and configuring event deduplication.
Once configured, conversion tracking is automatic. You don’t need to export Commerce7 orders or regularly upload customer lists to Meta to keep the integration running.
What can I do with the conversion data?
Getting the data into Meta is only the beginning. You can use the events and parameters provided by the app to build custom conversions, audiences, reports, and other tools inside Meta Ads Manager and Events Manager.
Here are a few examples. Meta’s interface changes regularly, so the screenshots may look slightly different from what you see in your own account. The underlying event data available from the app is documented at the end of this post.
Measure the value of club signups
You can create a custom conversion around the ClubJoin event and assign an estimated value to a new club membership.
How long does a typical member remain in your club? What is their expected shipment value? Using a reasonable customer value estimate can give you a much better understanding of the financial impact of campaigns focused on club acquisition.
Build audiences from club members
The same club conversion data can be used when creating audiences from customers who joined a traditional or subscription club.
Use tasting room purchasers as an audience signal
Physical-store purchase data can also provide a valuable audience source. For example, a winery might use known tasting room purchasers as the source for a lookalike audience when advertising locally.
Report on tasting room revenue
Commerce7 physical-store purchases can be included alongside your website conversions when evaluating advertising performance, helping you better understand campaigns that influence an in-person visit rather than an immediate ecommerce transaction.
Build better advertising reports
We also recommend customizing your Meta Ads reporting around the conversion events that actually matter to the winery. Depending on your campaigns, that might include ecommerce purchases, physical-store revenue, club joins, reservation activity, and ROAS.
Useful for wineries and the agencies that support them
For winery teams managing advertising themselves, the app removes a significant amount of technical setup and ongoing manual data work. Commerce7 conversion data is automatically sent in a format Meta can use.
For agencies, better conversion data makes it easier to evaluate campaigns against the actual outcomes wineries care about. It also removes the need for recurring Commerce7 exports and manual conversion uploads.
And 5forests uses it too
This isn’t just an app we sell. Facebook Conversion Tracking is part of the measurement stack we use when managing Meta advertising for Commerce7 wineries.
Better tracking can’t turn a bad campaign into a good one, but it gives us more complete information about what happens after someone interacts with an ad. That helps us make better decisions about audiences, creative, budgets, optimization, and overall advertising strategy.
If you’re looking for help beyond the app itself, contact 5forests to talk about winery digital marketing, or learn more about our Commerce7 website services.
California privacy and Meta Limited Data Use
The Facebook Conversion Tracking app supports Meta’s Limited Data Use processing for customers who have exercised applicable privacy rights.
Commerce7 includes a Customer Meta setting named “Limited Data Use“. When this is enabled for a customer, our app includes Meta’s Limited Data Use parameters when sending supported conversion data for that customer.
Limited Data Use can form part of a winery’s privacy compliance process, but enabling this feature does not by itself make a winery compliant with the CCPA/CPRA or other privacy laws. Your business remains responsible for determining when Limited Data Use should be applied and for complying with any other applicable privacy requirements.
See Meta’s documentation on Limited Data Use for more information.
Commerce7 events and parameters sent to Meta
For app users who want to extend the data inside Meta, the app includes custom values that can be used in Events Manager, custom conversions, audiences, and reporting.
The examples below show the structure of some of the event data sent by the app and document the custom values available for those events. If you’re unsure how to use these values in Meta Ads Manager or Events Manager, speak with an experienced Meta Ads practitioner before changing campaign optimization or attribution settings.
Reservation events
Commerce7 reservations are sent to Meta as Reservation events. The app identifies how the reservation was created and supplies the appropriate Meta action_source for website, tasting room/POS, and inbound reservations.
Reservation events can include the reservation value, currency, reservation type and option, location, table code, and reservation number. Where available, the app also includes customer matching and attribution data such as hashed contact information, Commerce7 customer ID, browser information, and Meta click-identification data.
"event_name": "Reservation", "event_id": "reservationNumber", "action_source": "website | physical_store | phone_call", "custom_data": { "value": 100.20, "currency": "USD", "content_type": "product", "content_name": "Reservation Name", "order_id": "reservationNumber", "res_name": "Reservation Option", "res_location": "Reservation Location", "table_code": "Table Code" }Club signup events
New Commerce7 club memberships are sent to Meta as ClubJoin events. Like purchases and reservations, the app identifies whether the signup originated from the website, tasting room/POS, or an inbound channel and sends the corresponding Meta action_source.
Club signup events include the club name and club type, along with available customer matching and attribution data. This makes the event useful for measuring club acquisition campaigns, creating custom conversions, and building audiences based on new memberships.
"event_name": "ClubJoin", "event_id": "membershipId", "action_source": "website | physical_store | phone_call", "custom_data": { "content_type": "product", "content_name": "Club Name", "club_type": "Traditional" }Purchase events
Commerce7 orders are sent to Meta as Purchase events. The app automatically identifies the Commerce7 order channel and supplies the appropriate Meta action_source, allowing website, tasting room, inbound, and other supported orders to be represented appropriately inside the same Meta Dataset.
Purchase events include the order value, currency, order number, and product SKUs, quantities, and prices. Where available, the app also supplies customer matching data such as email address, phone number, name, location, date of birth, Commerce7 customer ID, browser information, and the Facebook Click ID associated with the order.
Personally identifiable customer matching fields are normalized and hashed as required before being sent to Meta.
"event_name": "Purchase", "event_id": "orderNumber", "action_source": "website | physical_store | phone_call | system_generated", "custom_data": { "value": 100.20, "currency": "USD", "contents": [ { "id": "SKU", "quantity": 2, "item_price": 5.99 } ], "content_type": "product", "order_id": "orderNumber" }Ready to connect Commerce7 to Meta?
If you’re ready to install the app, start with our Facebook Conversion Tracking for Commerce7 setup instructions. They’ll walk you through the required Meta and Commerce7 configuration step by step.
