If you're running Facebook ads for clients, you've probably felt the sting of iOS privacy changes and browser-based tracking limitations. Conversions that used to show up cleanly in Ads Manager are now under-reported, attributed incorrectly, or missing entirely. Your campaigns look less effective than they actually are, and your clients start asking uncomfortable questions.
The fix is Meta's Conversions API, commonly called CAPI. It's a server-side tracking solution that sends conversion data directly from your client's server to Meta, bypassing browser restrictions altogether. No more relying on a pixel that a user's browser might block, ignore, or corrupt with cookie limitations.
The problem most agency owners and freelancers have faced is that CAPI historically required developer resources to implement. Digging into server code, managing tokens, and configuring event deduplication isn't exactly what you signed up for when you started running ads for clients.
Here's the good news: you no longer need a developer to get this done. With the right tools and a clear process, you can complete a CAPI setup without coding for your clients in minutes, not days. Every step in this guide is done through UI-based tools, native platform integrations, and dashboards you can navigate without touching a single line of code.
By the end, you'll have a fully functioning server-side tracking setup that improves data quality, strengthens ad performance, and gives your clients more accurate reporting. Whether you're managing one client or twenty, this process is repeatable and scalable. Let's get into it.
Step 1: Understand What You're Setting Up (and Why It Matters)
Before you touch any settings, it helps to understand exactly what CAPI does and why it's worth your time. This isn't just technical background — understanding the mechanics will help you troubleshoot faster and explain the value to clients more confidently.
Browser pixel vs. server-side CAPI: The traditional Meta pixel fires from inside a user's browser when they take an action on a website. The problem is that browsers are increasingly hostile to this kind of tracking. Ad blockers, iOS App Tracking Transparency restrictions, and cookie deprecation all interfere with pixel signals before they ever reach Meta. The result is incomplete conversion data.
CAPI works differently. Instead of relying on the browser, it sends conversion signals directly from your client's web server to Meta's servers. The data travels server-to-server, completely bypassing whatever is happening in the user's browser. Ad blockers can't touch it. iOS restrictions don't affect it.
Why this improves your campaigns: Meta uses conversion signals to optimize ad delivery. When those signals are incomplete or missing, the algorithm has less to work with. Better data means better optimization, which typically translates to more efficient ad spend and stronger results for your clients.
Which clients benefit most: CAPI is valuable across client types, but it's especially impactful for e-commerce clients where purchase events are the primary optimization signal, lead generation businesses where form submissions drive campaign decisions, and service businesses running retargeting campaigns based on page visit behavior. If your client is spending meaningfully on Meta ads, CAPI is worth setting up.
Event deduplication — the concept you need to understand: When you run CAPI alongside the browser pixel (which you should — they work together, not as replacements), the same conversion event can arrive at Meta twice: once from the browser and once from the server. Without deduplication, Meta counts both and your event totals become inflated and unreliable.
Meta handles this through a parameter called event_id. When both the pixel and CAPI send the same event with a matching event_id, Meta recognizes it as a duplicate and counts it only once. Most no-code integrations handle this automatically, but you'll want to confirm it's active before calling the setup complete.
One more thing to clear up: CAPI is not just for large businesses with development teams. The no-code paths available today make it accessible to any agency, regardless of technical resources.
Step 2: Gather What You Need Before You Start
A few minutes of preparation here will save you from getting stuck halfway through the setup. Here's exactly what you need to have in hand before you begin.
Meta Business Manager admin access: You need admin-level access to the client's Meta Business Manager account, specifically to the ad account and Events Manager. Partner access through your agency's Business Manager works, as long as you have the correct permission level. If you're working through a client's account, confirm this before starting.
Your client's Meta Pixel ID: This is a numeric identifier tied to the pixel installed on your client's website. You'll find it in Meta Events Manager. Log in to business.facebook.com, navigate to Events Manager from the left sidebar, and select the correct pixel from the data sources list. The Pixel ID appears at the top of the overview page. Copy it and keep it somewhere accessible.
A CAPI Access Token: This is a credential that authorizes your server-side integration to send data to Meta on behalf of the pixel. You'll generate this in the next step directly inside Events Manager — no developer tools required. For now, just know you'll need it and where it comes from.
Platform confirmation: Identify what platform your client's website runs on. The no-code CAPI setup paths vary by platform, and knowing this upfront saves time. The most common supported platforms include Shopify, WordPress with WooCommerce, Wix, and Squarespace. Each has a native or plugin-based integration that handles CAPI without code. If your client is on a less common platform, ClientPlug's built-in CAPI setup flow covers that scenario.
Your pre-flight checklist:
Admin access to client's Meta Business Manager: Confirmed before proceeding.
Pixel ID located in Events Manager: Copied and ready to use.
Access Token: Will be generated in Step 3.
Client's website platform identified: Shopify, WordPress, Wix, or other.
If you're using ClientPlug to manage this client's account, connecting it to their Meta ad account at this stage simplifies token management and gives you a centralized place to monitor event health alongside campaign performance. It's worth doing before you move forward if you haven't already.
Step 3: Generate Your CAPI Access Token in Meta Events Manager
This is the step that used to require a developer. It no longer does. Meta built the token generation process directly into the Events Manager UI, and it takes about two minutes.
Start by navigating to Meta Events Manager at business.facebook.com/events_manager. Make sure you're logged in under the correct Business Manager account for this client. This is worth double-checking before you proceed — generating a token under the wrong ad account is a common mistake that causes problems later.
In the left panel, you'll see your data sources listed. Select the pixel associated with your client's website. If you're managing multiple clients, the pixel names can look similar, so verify by checking the Pixel ID against what you copied in Step 2.
Once you're on the correct pixel's overview page, click the Settings tab at the top of the screen. Scroll down until you reach the section labeled Conversions API. Inside this section, you'll see a button that reads Generate Access Token. Click it.
Meta will display a token string — a long alphanumeric sequence. This is your CAPI Access Token. Copy it immediately and store it somewhere secure. Think of it the way you'd treat a password: it grants the ability to send conversion data to this pixel, so it shouldn't be shared casually or stored in plain text in a shared document.
What this token can and cannot do: The token authorizes server-side event sending for the specific pixel it was generated under. It doesn't grant access to your ad account settings, billing, or campaign management. It's scoped specifically to event transmission, which keeps the risk profile low.
One important pitfall to avoid: If you navigate away from the token display without copying it, you'll need to generate a new one. Meta doesn't show the same token again after you leave the page. This isn't a problem — you can generate a new token anytime — but it's an unnecessary extra step. Copy it before clicking away.
Success indicator for this step: You have a token string copied and stored. You know which pixel it belongs to. You're ready to connect it to your client's platform.
Step 4: Connect CAPI Through Your Client's Platform
This is where the actual integration happens. The path you take depends on your client's website platform. All of the options below are no-code — you're working through dashboards and plugin settings, not touching any server files.
Shopify (primary example): Shopify has a native Meta integration that includes CAPI built in. From the Shopify admin, go to Settings, then Apps and sales channels, and select the Facebook and Instagram sales channel. Inside the channel settings, navigate to the Data sharing section. You'll see a Conversions API toggle. Enable it and select your data sharing level. Shopify handles the event_id deduplication automatically when this is active, which is one of the reasons it's the smoothest CAPI path available.
WordPress and WooCommerce: Install the official Meta Pixel plugin from the WordPress plugin directory. Once installed and activated, go to the plugin settings and connect your Meta Business account. Enter your Pixel ID and paste the Access Token you generated in Step 3. Look for the CAPI toggle within the plugin settings and enable it. The plugin manages deduplication between the browser pixel and the server-side events.
Wix: From the Wix dashboard, navigate to Marketing and SEO, then Facebook Pixel or the Meta Business integration section. Wix's native integration includes a CAPI option. Connect your Meta Business account, enter your Pixel ID, and enable the server-side events toggle. Wix handles the technical heavy lifting once the integration is active.
Non-standard platforms or multi-client management: If your client's site runs on a platform that doesn't have a native CAPI integration, or if you're looking for a more centralized way to manage CAPI setup across multiple clients, ClientPlug's built-in CAPI setup flow is the fastest path. Enter the Pixel ID, paste the Access Token, select which events you want to send via CAPI (Purchase, Lead, ViewContent, AddToCart — match what your pixel is already firing), and the connection is established. No platform-specific navigation required.
Selecting the right events: Regardless of which platform path you take, you'll typically be asked to choose which conversion events to send via CAPI. As a general rule, send the same events through CAPI that your pixel is already tracking. This ensures complete deduplication and consistent data across both channels.
Critical pitfall: Enabling CAPI without confirming deduplication is active will inflate your event counts. Before moving on, verify in your platform's settings that deduplication is enabled. On Shopify and the Meta Pixel WordPress plugin, this is automatic. On other platforms, look for a specific deduplication or event_id setting and confirm it's turned on.
Success indicator: Return to Meta Events Manager and check your pixel's overview. The CAPI connection should show an Active status. If it shows as active, you're ready to verify the setup is actually working.
Step 5: Verify the Setup Is Working Correctly
An active status in Events Manager tells you the connection exists. The Test Events tool tells you it's actually working. Don't skip this step — it's the difference between thinking CAPI is running and knowing it is.
From Meta Events Manager, select your client's pixel and click on the Test Events tab. You'll see a field where you can enter your client's website URL. Enter it and click Open Website. This opens the site in a new tab while Events Manager listens for incoming events.
Now trigger the events you configured. Visit a product page to fire a ViewContent event. Add something to the cart to trigger AddToCart. If you set up a test lead form, submit it to fire a Lead event. Return to the Test Events tab and watch for the events to appear in real time.
What you're looking for: When CAPI and the browser pixel are both active, you should see each event appear twice in the test events feed — once from the browser (labeled as coming from the pixel) and once from the server (labeled as coming from CAPI). This is expected and correct. The deduplication logic then reduces these to a single counted event. If you see both sources firing and the final event count is not doubled, deduplication is working.
Checking Event Match Quality: After your test events fire, navigate to the Overview tab of your pixel in Events Manager. Look for the Event Match Quality (EMQ) score, which Meta displays as a number out of 10. This score reflects how well Meta can match the conversion events you're sending to actual Meta user accounts. A higher score generally correlates with better ad delivery and optimization performance.
If your EMQ score is lower than you'd like, the most effective way to improve it is to pass more customer data parameters with each event. This includes hashed email addresses, phone numbers, and names where your client's privacy policy and applicable regulations permit. Many platform integrations allow you to configure which customer data fields are included in the CAPI payload.
If events aren't appearing: Start with the basics. Confirm the Pixel ID entered in your platform integration matches exactly what's in Events Manager. Check that the Access Token was saved correctly in the platform settings — it's easy to accidentally copy an incomplete token. Verify the plugin or integration was saved after you made changes. If issues persist, the Diagnostics tab in Events Manager will surface specific error messages that point to the root cause.
Success indicator: Events are firing from both the pixel and CAPI, deduplication is active and reducing the count correctly, and an EMQ score is visible. Your CAPI setup is live and functioning.
Step 6: Monitor Performance and Scale Across Clients
Once your CAPI setup is verified and running, it operates largely in the background. But "set and forget" is a mindset that will cause problems over time. A small monitoring routine protects the data quality you just worked to establish.
What to watch in Events Manager: Check in on your client's pixel periodically and look at a few key indicators. Event volume trends should be relatively consistent week over week — a sudden drop often signals a broken connection, an expired token, or a website change that disrupted the integration. EMQ scores can also shift if the customer data being passed changes. And the Diagnostics tab will flag any new errors that need attention.
Access tokens can expire or be revoked: This is one of the most common reasons CAPI setups quietly stop working. Tokens can be invalidated when Business Manager permissions change, when a team member who generated the token loses access, or in some cases after extended periods of inactivity. Build a monthly check into your workflow where you confirm the CAPI connection is still showing as active and events are still flowing. It takes two minutes and prevents a situation where your client's tracking has been broken for weeks without anyone noticing.
When to revisit the full setup: Three situations typically require going back through the configuration. First, if your client migrates to a new website platform. Second, if they make significant structural changes to their site that affect where conversion events fire. Third, when Meta releases new CAPI features or updates their integration requirements — this happens periodically and is worth staying aware of.
Scaling across your client roster: The most efficient way to handle CAPI for multiple clients is to document your process as an internal SOP. Write down the exact steps, the platforms you've encountered, and any client-specific notes. This means any team member can handle a new CAPI setup without starting from scratch, and onboarding new clients becomes a predictable, repeatable process rather than a one-off project.
ClientPlug's dashboard is built for exactly this kind of multi-client management. Instead of logging into each client's Events Manager separately to check CAPI event health, you can view event status alongside campaign performance and client data from a single interface. When CAPI is improving your underlying conversion data, the automated white-label reports you send clients also become more accurate and defensible — which strengthens your client relationships and makes your reporting conversations easier.
Your CAPI Setup Checklist
Before you close out this setup, run through the following checklist. Every item here was completed through UI-based tools, platform dashboards, and plugin settings. No code required at any point.
Admin access confirmed: You have the correct permission level in the client's Meta Business Manager.
Pixel ID located: Found in Events Manager and copied accurately.
Access Token generated: Created inside Meta Events Manager under the correct pixel's Settings tab.
Platform integration connected: CAPI enabled through Shopify, WordPress/WooCommerce, Wix, or ClientPlug's built-in setup flow.
Events selected and matched: CAPI is sending the same events your browser pixel fires.
Deduplication active: Confirmed through platform settings and verified in the Test Events feed.
Test events verified: Both pixel and CAPI events appeared in the Test Events tool.
EMQ score checked: Event Match Quality score is visible in Events Manager.
Monitoring cadence set: A recurring check is built into your workflow to catch token expiration or connection issues.
Server-side tracking is becoming the standard for agencies that want to deliver reliable performance and accurate reporting. Browser-based tracking alone is increasingly insufficient, and the gap between agencies that have made this shift and those that haven't will only grow as privacy restrictions continue to tighten.
The good news is that the barrier to entry is lower than it's ever been. Everything in this guide is accessible to any agency owner or freelancer, regardless of technical background.
If you're managing multiple clients and want the fastest path to getting CAPI set up and monitored from one place, ClientPlug is built for that workflow. One dashboard, one setup flow, and your CAPI connections sit alongside your campaign data, payment tracking, and client reports. Learn more about our services and set up CAPI for your first client in under ten minutes.