Mintly Logo
Training
How to Set Up Meta Pixel + Conversions API
Get the Exclusive 28 Page Step-by-Step Setup Playbook (FREE)
First name
Last name
Email
Phone
Include country code for easiest contact.
Primary advertising goal
How did you hear about Mintly?
Having trouble? Retry captcha
By providing your information, you consent to Mintly and our partners contacting you by mail, phone, text, or email, including via an automated telephone dialing system, at the contact details you provide, even if your number is on a state or national Do Not Call list. We do not sell your personal information to other companies, and you can withdraw consent at any time. Consent is not a condition of purchase. By submitting this form, you agree to our Privacy Policy and Terms of Service.
Overview

Module 1: Signals and Tracking (Pixel/CAPI/AEM done right)

“The first step of making progress is tracking progress. If you don’t track, you don’t care.” - Alex Hormozi

Overview:

  • Why Signals Matter

  • Event Map

  • Meta Pixel Setup & Validation

  • CAPI (Conversions API) with Deduplication

  • Privacy, Consent, & Regions

  • Review

  • Actions

    Why Signals Matter:

“What gets measured gets improved”

  • Goal – You want to teach platforms who converts and why, so that ad retrieval/optimization has sauce to cook.

    • Why?
      • Cheaper CAC (Customer Acquisition Cost)
      • Allows you to scale more effectively
      • Helps you understand what is sucking and what is killing it

  • Feedback – Even if you don’t run paid ads, you still want to understand your funnel.

    • Why?
      • Because if you know how much money you make per customer, and you know how much it costs to get that customer, you can figure out what to change.

  • Core concepts:

    • Event = action a user takes
    • Params = details about the event
    • User data = hashed identifiers about a user that boost match rate (aka using data clues to connect back to a real person).
    • Consistency > completeness
      • Track what matters well.

    Event Map:

  • Recommendation – Track what you need, forget about what you don’t

  • Recommended baseline maps:

    • Ecom:
      • PageView → ViewContent → AddToCart → InitiateCheckout → Purchase
    • SaaS:
      • PageView → CompleteRegistration → StartTrial → Subscribe
    • B2B Lead:
      • PageView → Lead (form submit) → Schedule (booked call) → QualifiedLead

    Pixel Setup & Validation:

  • Install: base pixel code sitewide (GTM or direct), fire PageView on load

  • Add events: fire browser events on related actions

    CAPI (Conversions API) with Deduplication:

  • Why this is valuable:

    • Capture server side truths (payments, trials)
    • Improve match rate
      • Aka Meta says “yeah that’s Cindy from Australia with the 2 twins”
    • Survive ad-blockers
    • Stabilize reporting
      • Frontend data can be noisy and can duplicate easily, leading to overreporting of events

  • Deduplication rule:

→ Browser + Server versions of the same action must share the same event_id

  • Meta will de-duplicate for you
    • How to do this:
      • Generate the event_id in browser → include in server payload

GET ACCESS TO THE ENTIRE CODE SETUP FOR FREE

  • Three patterns:
Partner IntegrationGatewayManual Setup
Fastest if you’re on: Shopify WordPress WooCommerce Shopline Wix Google Tag Manager (server-side) Zapier Cafe24 Segment Magento Makeshop Signals Gateway Stape TealiumNgl, I have no idea what this is. Looks confusing and expensive I would avoidThis is what I did. #thegoat A little more complex but if you know how to code it’s chillin + I’ll share some code with ya

  • Meta’s Event Match Quality Score = how rich the data you’re providing, which helps them to target better

    • Higher – is better.
    • Drops – when you aren’t passing as much user data as you could be
      • Or, when you aren’t passing event IDs (technically a param)
    • Find it – in the dataset section under the “Event match quality” column

    Privacy, Consent, & Regions:

  • Collect the data you need for optimization

  • Disclose to people that you want their data

  • Honor it if they opt-out

  • Tactics:

    • Consent banner → toggle non-essential events; allow Purchase events with minimal fields if policy and law permits
    • Respect Limited Data Use/regional processing flags when applicable

Review:

  • Signals are the foundation of optimization. Platforms can’t optimize if they don’t know who converted or why.
  • Consistency beats complexity. A simple, clean setup you trust will outperform a bloated one you don’t.
  • Event maps guide your tracking strategy. Stick to the essentials that map directly to your funnel.
  • Meta’s Pixel Helper is goated for just verifying it’s working.
  • Pixel + CAPI = stability. Pixel alone is fragile (ad blockers, browser issues). CAPI ensures you still capture the truth.
  • Deduplication matters. Without consistent event_ids, you’ll overcount and break reporting. Make the event_id in the frontend.
  • CAPI is super important but lowkey complicated.
    • If you’re watching this on YouTube → click the link in the description
    • If you’re watching this somewhere else → follow & comment for the link
  • Privacy is not optional. Build consent and regional handling into your system from day one.

Action Steps:

  1. Define your funnel events – pick 3–5 critical milestones from your event map.

  2. Implement the Pixel base code – sitewide with PageView firing on load.

  3. Layer in browser events – for each funnel action.

  4. Set up CAPI – mirror the same funnel events server-side, attach a shared event_id.

  5. Check Event Match Quality – improve by passing as much hashed user data as possible.

  6. Test & validate – use Meta’s Pixel Helper, Event Manager diagnostics, and your own server logs.

  7. Enable consent management – ensure compliance in all regions you operate.

  8. Audit monthly – check match scores, event firing, and deduplication health to catch drift.

Transcript
Hey guys—before we get into the video, if you’re a developer I have something for you for free. If you’re going to implement Meta’s Conversions API directly in your code, I created a 30-page, step-by-step guide that explains how to set it up for both your front end and your back end. It integrates with Stripe, and it doesn’t just cover Meta—it also shows you how to get set up with Google Tag Manager, TikTok, and a tool called PostHog. That way, you can have all of your analytics dialed in from day one without the stress I went through. If you want that for free and you’re watching on YouTube, click the link in the description. If you’re watching this anywhere else, comment “meta” and I’ll send it straight to your DMs. Now, let’s get into the video. Hello and welcome to this training. As you can see by the title, today we’re talking about setting up your Meta Pixel and making sure your tracking is on point so that, when you go to advertise, you achieve the lowest customer acquisition cost possible and run campaigns as effectively as possible. We’ll cover why this data matters, how to set up and debug the Pixel, how to make sure everything’s working properly, how to configure the Conversions API—which a lot of people find confusing—then touch on privacy, consent, and regional considerations. We’ll finish with a review and concrete action steps so you can implement this on your website. Let’s start with why signals matter. What gets measured gets improved. Our goal is to teach platforms who converts on our site and why they convert, so that when we run ads everything is as optimized as possible and Meta has as much “sauce” as it can to cook. Doing this lowers your CAC, makes scaling more effective, and helps you see what’s underperforming and what’s crushing it. Even if you don’t run paid ads yet, this is still very important. If you don’t know how much money you make per customer and how much it costs to get that customer, you can’t figure out what to change. You may consider paid ads in the future, so the more data you can give to Meta, Google, and TikTok now, the better your future performance will be. Core concepts for today are events, parameters, and user data. An event is something someone does on your website. Parameters are the details about that event—when it happened, on which page, what button they clicked, and so on. User data (hashed) provides non-plain-text information about who and where the user is—city or state, the Facebook account they’re tied to, or their email address. These are the data points you want to feed to Meta when you share information from your site. The number one rule: consistency beats completeness. Send as much high-quality data as you can for the events that matter, but you don’t need to track every possible event. Focus on the core events for your business. Now, here’s how to set up the Meta Pixel step by step. Go to Meta for Business—search for Meta Business Manager, since Meta has a bunch of pages—and open Events Manager under “All tools.” This is where you’ll set up your Pixel and everything you need to track users coming to your site. If you’re new, you probably won’t see any data yet. Click “Connect data” and create a dataset—this is where your tracking data will live. Choose “Website” (or “App” if that’s you), name it, and create your Pixel. You can set it up manually or with a partner integration. If you’re on Shopify or a similar platform, the partner integration is great. I personally code things manually, so I choose the manual setup. Turn on Automatic Advanced Matching so Meta can recognize returning users and help with retargeting. Place the Pixel base code in your site’s `<head>`. If you’re unsure where that is, ask ChatGPT for your specific framework—it’ll point you to the right place. I highly recommend installing the Meta Pixel Helper Chrome extension. It lets you verify the Pixel is live and that events are firing. First, use the “Troubleshoot Pixel” option in Events Manager. Enter your URL, and Meta will open a special view of your site so you can click around, trigger events, and confirm they’re being captured. You’ll also see a testing code for server events—use this when you’re in development so you don’t pollute your real data. Pass the test code along with your events; Meta will treat them as test traffic. Back in your dataset, click “Add events.” You can add events directly from the Pixel using the Pixel Helper—go to your site, click buttons, and set events on those interactions. A heads-up: dynamic buttons can be tricky, and if multiple pricing cards share the same CTA text, Meta may struggle to infer which specific price a click relates to because it’s tracking the button, not the card. Keep that in mind as you plan your event structure. You’ll also see options to use the Conversions API (CAPI). You’ll typically get three choices: a partner integration (great if you’re on Shopify, etc.), the Conversions API Gateway (I find it confusing and potentially costly, so I don’t use it), and manual setup. If you have a custom website and codebase, I recommend the manual setup. It’s a bit complicated at first, but I’ll share the code in my free guide so you can see how I implemented it and replicate the approach. What should you track? For e-commerce, track PageView, ViewContent, AddToCart, InitiateCheckout, and Purchase. For SaaS (like mine), keep it simpler: PageView, CompleteRegistration (sign-ups), StartTrial (if applicable), and Subscribe (paid). Capturing these server-side “truths” for payments and trials is critical. Next, improve your match rate by sending Meta as many user identifiers as possible (hashed): name, email, phone, city, state, etc., to better match actions to people. Another reason to use server-side events is ad blockers—client-side tracking can be blocked, but server-side events will still persist for your most important metrics. Server-side also stabilizes your reporting; the front end can over-report due to reloads or double fires, while server-side helps you keep clean, accurate numbers. One of the most important concepts is deduplication. If an important event happens on the front end (e.g., someone clicks “Pay”) and a corresponding event happens on the back end (the payment is confirmed), you want to send both events to Meta with the same `event_id`. That tells Meta these two records are the same real-world action, just with richer data, and Meta will deduplicate them for you. Generate the `event_id` in the browser and pass it through to your server so both client and server events share it. It’s a lot to explain in a single video, so I put together a free PDF outlining how our codebase handles Meta, TikTok, and Google tracking, so you can track ads and user interactions across your whole site and share them with each platform. Click the link in the description to access it for free. Let’s continue with the Conversions API setup. In your dataset, click “Conversions API,” choose the manual setup with Meta Pixel + CAPI, and pick the events you want (I chose the SaaS Core Four). Then walk through all the parameters and user data you plan to send. I like to include as much as possible—even if I don’t collect a field yet—so I’m prepared when I add it later. Review everything, then move to implementing the code in your codebase. If you want to skip the headache or get a big head start, grab the free guide or comment so I can send it to you. Once events start coming in, the number one thing to watch is Meta’s Event Match Quality score (1–10). It reflects how good Meta thinks your data is. If you’re not sending enough identifiers—name, city, state, phone, email—your score will drop and Meta will nudge you to add them. Early-funnel events will naturally have less data (an anonymous visitor won’t have given you their email yet), but for high-priority events—payments, trials, subscriptions—you will have collected user information. Make sure you send those identifiers so those critical events get the highest match quality possible. Those are the actions you’ll optimize for when you run ads. A quick word on privacy, consent, and regions. Collect only what you need for optimization and funnel improvement. Disclose your data collection and honor opt-outs. I recommend using a premade cookie-consent tool so you don’t have to wrangle the legal implementation yourself. I use CookieYes—they don’t sponsor me, but setup was easy. I delay any advertising-related tracking until a user opts in. Design your banner so opting in is easy; if someone wants to opt out, let them manage settings. You’re not required to include a prominent “Reject all” button, and it can reduce opt-in rates significantly. Make opting in straightforward and let users dig into settings if they want to disable advertising cookies. Let’s review. Signals are the foundation of optimization—if you can’t track it, you can’t improve it. Consistency beats complexity: you don’t need to track everything, but you must track the few events that truly matter, and track them very well. Your event map should guide your tracking strategy: understand the core steps in your funnel, implement events that capture those steps, and then optimize them to move more people toward purchase. The Meta Pixel Helper is “goated”—it’s a bit of a pain to set up initially, but once it’s running it confirms your implementation is working. Pixel + Conversions API gives you maximum stability: relying solely on the front end exposes you to ad blockers and client-side quirks, while server-side is your most reliable source of truth. Combine both for the richest data to feed Meta’s algorithm. Deduplication matters—always send event IDs so you don’t over-report. Accurate data leads to better decisions. CAPI is super important but admittedly complicated—again, grab the free guide if you want the step-by-step. Finally, privacy isn’t optional. If people want to opt out, respect it and build it into your system so you’re protected later. Action steps: First, define your funnel. Use Meta’s recommended events for your business type and identify the handful of actions that truly matter up to purchase. Second, implement the Pixel base code in your site’s head and verify it with Pixel Helper. Third, configure your events and confirm they’re firing correctly. Fourth, set up the Conversions API—using my guide or a partner integration—so you’re capturing crucial server-side events. Fifth, test and validate thoroughly. It’s tempting to skip testing because setup is a hassle, but don’t—make sure everything works as intended. Sixth, ensure regional compliance: enable consent management and respect opt-outs. Finally, audit regularly. Even after recording this video, I realized a few events in my funnel could be optimized and enriched with better data—so that’s what I’m off to do now. I’ll see you in the next video. Go make some money—and follow for more.