Menu
A high Event Match Quality (EMQ) score is no longer a luxury, it’s the bedrock of profitable paid media. In the post-iOS 14 world, where browser-side tracking is crumbling, relying solely on the Meta Pixel is like driving with your headlights off. The key to unlocking maximum return on ad spend (ROAS) and hitting your Max Profitable CAC target? Mastering the Conversions API (CAPI).
This isn’t about simply sending a purchase event. This is about advanced tracking, sending the precise customer identifiers Meta needs to confidently link an on-site conversion back to an ad click. Below is your checklist and guide to the specific customer information parameters, like fbc, fbp, and external_id, required for top-tier EMQ, and a breakdown of how to securely hash them for compliance.
Before diving into the technical details, let’s understand the gravity of the situation. Low EMQ means Meta’s algorithm is blind. It cannot accurately attribute conversions, leading to two massive, profit-killing problems:
For Singapore-based businesses, especially in high-CPC industries like finance or education, tracking fidelity isn’t just a best practice, it’s a survival mechanism. We’ve seen local e-commerce and B2B clients in Singapore jump from sub-60% EMQ to over 90% simply by implementing the advanced parameters discussed here. For a deeper understanding of how tracking impacts your bottom line, consider reading our corner-stone article on Max Profitable CAC.
Connect with our expert team with proven digital marketing strategies that deliver real results.
Connect with us! →Achieving an elite EMQ score requires you to provide Meta with as much information as possible to find the matching user profile. This data falls into two key categories: User Data and Click Data.
This is the Personally Identifiable Information (PII) you collect on your website, typically from a form fill, sign-up, or checkout. To be compliant and secure, this data must be hashed using SHA256 before being sent via CAPI.
Parameter Name | Description | Example (Hashed) | EMQ Impact |
|---|---|---|---|
email | The customer’s primary email address. | 493A…E5C1 | High |
phone | The customer’s full phone number, including country code (e.g., +6591234567 for Singapore). | 6B21…F8D9 | High |
external_id | A unique, non-PII identifier you use to track a customer across your own systems (e.g., CRM ID). | Cust-45678-SG | Crucial |
fn / ln | Customer’s first name and last name. | A1B2…C3D4 | Medium |
zipcode | The postal code (e.g., 519966 in Singapore). | D9E0…A1B2 | Medium |
Actionable Tip: Don’t wait for a purchase. For B2B businesses, send a hashed email and phone number immediately upon a ‘Lead’ or ‘Contact’ form submission. This provides high-fidelity signals early in the funnel, dramatically improving the algorithm’s learning speed. You can also explore The Critical Difference Between Offline Conversions and Conversions API for High-Ticket Services for advanced B2B strategies.
These are identifiers generated by Meta and stored in the user’s browser. They provide a direct, albeit time-limited, link back to the ad click. Unlike PII, these are typically not hashed but sent as plain text.
Parameter Name | Description | Source | EMQ Impact |
|---|---|---|---|
fbp | The Meta Browser ID. A cookie-based identifier for a browser. | Pixel/CAPI Helper | Critical |
fbc | The Meta Click ID. This contains the unique ad click ID. | Pixel/CAPI Helper | Critical |
client_user_agent | The user’s browser, version, and operating system string. | HTTP Request Header | High |
client_ip_address | The user’s IP address. | HTTP Request Header | High |
So, how do you collect this click data reliably and ensure your PII is secure?
Our team consists of seasoned digital marketers, bringing years of hands-on expertise driving results for SMEs and enterprises throughout the APAC region.
from first click to final sale, across Meta, Google, TikTok, YouTube, and your CRM so you can see what’s working and what’s not.
Your videos, landing pages, ads, and data are aligned under one strategy no more juggling vendors.
Budgets shift based on real-time performance, not monthly meetings.
Leads and traffic you already have get optimized for higher ROI and less waste.
Clear reports, honest feedback, and no jargon, even when results aren’t perfect.
Digital Marketing isn’t just about running ads. It’s about turning data into visible growth.
The most reliable way to send these parameters is through a server-side setup, such as using Google Tag Manager (GTM) Server-Side. This setup collects the data on your server, hashes the sensitive PII (like email and phone number) using the required SHA256 algorithm, and then sends the complete, high-fidelity payload to Meta’s CAPI endpoint.
A 2024 study by MarTech Advisor noted that advertisers who implemented a complete CAPI setup, including fbc, fbp, and hashed PII, saw an average 18% improvement in Cost Per Acquisition (CPA). This benchmark provides compelling evidence of the system’s effectiveness.
Many SMEs and even larger firms in Singapore are still making the same critical tracking mistakes:
This flawed tracking strategy means that local ad costs, already high in competitive Singapore markets, are being wasted on under-optimized campaigns. Stop burning cash and start feeding the algorithm the high-quality data it needs.
Conversions API (CAPI) and Event Match Quality
High **Event Match Quality (EMQ)** ensures Meta’s algorithm can accurately attribute conversions to the correct ad. This improves ad delivery, lowers your overall Customer Acquisition Cost (CAC), and helps you stay below your Max Profitable CAC threshold, preventing overspending on ineffective audiences. Achieving $90\%+$ EMQ is critical for scalable profitability.
Hashing PII data using the **SHA256 algorithm** is a mandatory security and compliance step. It converts sensitive customer information into an anonymous, non-reversible string. Meta matches this hashed string to their user database without ever receiving the actual PII, helping to boost your Event Match Quality securely.
No, it is highly unlikely. Given the prevalence of iOS devices and browser tracking restrictions in Singapore, the browser-only Pixel severely under-reports conversions. To achieve $90\%+$ Event Match Quality and accurately track your Max Profitable CAC, you must implement the **Conversions API (CAPI)** with advanced parameters.
For many Singapore SMEs, a **CAPI Partner** (like a reputable agency) provides immediate access to expertise and saves development time, offering a predictable path to a high Event Match Quality. While custom solutions offer total control, the complexity often outweighs the benefit unless you have dedicated in-house development resources.
The most crucial parameters are the user's hashed email, hashed phone number (with country code like +65), and the unique, persistent **external\_id** from your CRM. Additionally, including the Meta-generated **fbc** (click ID) and **fbp** (browser ID) is essential to increase Event Match Quality to the highest tiers.
The **external\_id** is a unique, non-PII identifier you generate (like a CRM ID). It is vital because it provides a persistent link between your internal systems and Meta. When click IDs (fbc/fbp) expire, the external\_id combined with hashed PII maintains a high Event Match Quality, especially for long B2B sales cycles.
**Data normalization** means standardizing PII (e.g., lowercase email, removing dashes from phone numbers) before hashing. If data is not normalized, the resulting hash will be incorrect, and Meta cannot match it. This oversight is a major cause of low Event Match Quality scores for businesses in Singapore.
Your business deserves more. Let ThriveMediaSG help your business Increase Sales through digital marketing.
Conversions API (CAPI) is a server-to-server connection that allows businesses to send web events, such as Purchases or Leads, directly from their own server to Meta (Facebook/Instagram). This is the modern, post-iOS 14 replacement for the traditional browser-based Meta Pixel, which is unreliable due to ad blockers and privacy settings.
CAPI is a direct data pipeline. Instead of relying on the user’s browser, where data can be blocked or lost, the event data is securely collected on the advertiser’s web server and then sent to Meta’s API endpoint.
High-quality data is the fuel for Meta’s bidding algorithms. When CAPI provides a complete, high-fidelity signal of who converted, the algorithm learns faster and optimizes more effectively.
Outcome: The bidding algorithm is smarter, reducing wasted ad spend and ensuring the Customer Acquisition Cost (CAC) remains below the Max Profitable CAC threshold.
Achieving a top-tier EMQ requires a complete data payload. This is done by implementing the Advanced CAPI Matching Framework.
Use CAPI: Always, for every conversion event. It is a mandatory foundation for all paid media on Meta.
Contrarian Insight: Many businesses in Singapore implement CAPI only for ‘Purchase’ events. This is a mistake. You must implement CAPI for all upstream events (e.g., ‘View Content’, ‘Initiate Checkout’) to train the algorithm on the entire user journey. Feeding the Meta Machine with deep data is how you achieve unstoppable ROAS.
Always view the server-side data as the source of truth. The Pixel is merely a fallback, not the primary tracking tool. Deduplication is the critical process of ensuring the same event is not counted twice (once by the Pixel, once by CAPI) by sending a unique event_id with both.
Building Brands Since 2001
©2026. ThriveMediaSG. All Rights Reserved.
