You can't sell a wine Meta, Google or ChatGPT can't see. You can't sell a wine
Meta
can't see.

Your public pages, the way a customer sees them. We load your homepage and a few wine pages in two separate browsers and record what reaches Meta and Google. We also check the product data Google reads, whether your wine pages and photos load, and whether AI assistants like ChatGPT can read your wines. No login or access needed.

The check starts with just your website. While it runs we ask for an email. Everyone sees the score and the issue titles when the scan finishes. Why each issue matters, the fixes, and a private link that works for 7 days, come after you leave an email. That keeps the scanner from being used anonymously.

Having a pixel and sending the right events are different things. Some Commerce7 sites load the pixel but never tell Meta which wine someone looked at, or leave out the price. The check shows which one you have.

Commerce7 can load your Meta pixel on the storefront, and the pixel reports what happens in the browser. Sending orders from the server, including tasting room and phone sales, takes an app from the Commerce7 App Store. 1Pixel for Meta is ours, and setup is free.

Probably not. The Gateway copies the events your pixel fires in the browser and sends them to Meta from a server, which you run in your own AWS or Google Cloud account or pay a host to run. Because it only sees the browser, orders rung up in the tasting room or taken by phone never reach it. An app that reads orders straight from Commerce7 sends those too, with nothing to host.

Yes. The Google measurement setup ($400, fixed price) covers Google Analytics 4 installed or fixed, ecommerce events from wine view to purchase, and Google Ads conversions with order values. Tested with real Commerce7 orders.

Tracking cleanup, site health fix and wine page SEO & link previews, plus 1Pixel and AI Visibility & Shopping Feed installed and set up, for $449 once. The apps are billed monthly through Commerce7, from $29.99/mo each. Google measurement setup is not included. Bought separately, the same work comes to $950.

When we finish, we run the same check on your site again and send you the result. If an issue we fixed still shows, you get your money back for that fix. That holds as long as we get the access we ask for and nobody else changes that part of the site while we work.

Pick the fix from your report and you get a fixed-price invoice. Work starts when it is paid, and we send a short list of the access we need. If you want to talk it through first, a 20-minute call is $49, and it comes off any fix you book within 30 days. App setup calls are free, since the app subscription covers them.

No. Server-side events still follow your consent and opt-out settings. What changes is that events no longer depend on the browser loading the pixel, so ad blockers and slow pages stop losing them.

No. We block the tracking requests our visit would send, so Meta and Google never count it. We never add to cart or start a checkout.

Every month we run the same check on your site. If a theme update, a plugin or a Commerce7 change breaks tracking or a wine page, we tell you and fix it inside your plan hours.

An intro call, install and authorization, baseline configuration, one test event or sync, and short handoff notes. Custom mapping, multi-step Zaps, backfills, theme work and ongoing support are outside it.

Yes. 7Labs Debug & Branding for Commerce7 is free on WordPress.org. Paid help is there when you want hands-on debugging, branding, launch or storefront work.

It is the floor for a clearly scoped job. We confirm the workflow, access and result you want first. Anything beyond that scope is quoted, or billed at $50/hr once you agree to it.

A plan reserves about two, four or eight hours a month for monitoring, fixes and small improvements. Extra time is billed at $50/hr, and we tell you before we go over.