Before You Touch Anything: The 4 Prerequisites for Conversions API Setup
Now that you understand both the opportunity and the constraints, let's get into the actual work. But don't skip ahead — this prep stage is where most setups go off the rails.
The Meta Conversion API for your liquor store requires four distinct prerequisites before you send a single event: creating a business in Business Manager, creating a Meta App, creating a Meta Pixel, and configuring your server connection. Let's walk through the first three here.
Setting Up Your Business Manager and Facebook App
If you've ever run a Facebook ad for your store, you probably already have a Business Manager account. Log into business.facebook.com ↗ and verify it's active. If not, creating one takes about five minutes — name, address, business details.
The critical step most retailers skip? Domain verification. This is especially important for alcohol ecommerce. A verified domain signals to Meta that you're a legitimate business, not a fly-by-night operation. You'll add a DNS record or upload an HTML file to your website. Your web host can help if that sounds foreign.
Next: creating a Meta App through the developer portal ↗. This sounds intimidating. It's not. You're essentially filling out a form — app name, contact email, business association. You won't write code here. Think of it as registering your store's "digital ID" so Meta's servers can talk to yours.
Good news: if you're already tracking online orders with a Facebook Pixel on your ecommerce site, you don't need a new one. CAPI works alongside your existing pixel, not as a replacement. Meta calls this "redundant event tracking" — both the browser-side pixel and server-side API send the same events, and Meta deduplicates them automatically to improve data accuracy.
No pixel yet? Create one in Events Manager, grab the base code, and install it on your site. Most platforms like Shopify or WooCommerce make this a simple paste-and-save.
Preparing Your Server Connection
This is where CAPI diverges from standard pixel tracking. Instead of relying solely on a customer's browser, you'll configure your server to send event data directly to Meta. The method depends on your platform — direct integration, partner integration, or manual API calls. We'll cover the specifics in the next section, but for now, confirm you have admin access to your ecommerce backend. You'll need it.
Prerequisites handled? Good. You have three paths forward, and the right one depends on your technical comfort level, your ecommerce platform, and how much you want to spend.
Option 1: Manual Setup Through Events Manager
This is the most hands-on approach, and it's worth understanding even if you ultimately choose a different method.
Here's the path: Events Manager → Add Events → Add new integration → Conversions API → Set up manually.
The workflow walks you through selecting which events you want to track server-side. For a liquor store's online orders, configure these events at minimum:
- Purchase — the money event. This is what Meta optimizes your ad spend around.
- Add to Cart — signals buying intent, critical for retargeting.
- Initiate Checkout — identifies where customers drop off.
- View Content — tells Meta which products attract attention.
- Age Verification Completed — a custom event unique to alcohol ecommerce that helps you track where age-gating causes friction.
You'll also set up customer information parameters (email, phone, location) that Meta uses for matching. The manual method requires a developer to handle the actual API calls from your server — so unless you have technical help on staff, keep reading.
Option 2: Server-Side Google Tag Manager (Recommended for Most Stores)
For most independent retailers, server-side Google Tag Manager (sGTM) is the sweet spot.
Here's why: sGTM sits between your store and Meta, routing event data through a server container you host on Google Cloud. You control exactly what customer data gets shared — which matters when you're operating in a restricted advertising category.
Platform shortcut: If you're on Shopify, WooCommerce, or BigCommerce — and most liquor stores doing ecommerce are — check for native CAPI integrations first. Shopify has a built-in Meta channel app. WooCommerce has plugins like PixelYourSite. BigCommerce offers a Meta integration through its app marketplace. These can handle the heavy lifting without a full sGTM deployment.
Option 3: The Conversions API Gateway (And Why You Might Skip It)
Meta offers its own Conversions API Gateway as a managed setup alternative. In theory, it simplifies deployment. In practice, most experts steer clients away from it.
The Gateway introduces ongoing hosting costs and infrastructure complexity that rarely justify themselves for an independent liquor store. You're paying for enterprise-grade plumbing when a plugin or sGTM setup does the job at a fraction of the cost and maintenance burden.
The bottom line: If you're running a single-location or small-chain liquor store, the Gateway adds overhead without proportional benefit. Save it for the national distributors with dedicated IT teams.
