Symptom
Meta Events Manager shows low Event Match Quality (EMQ) score, typically 3/10 or below.
Understanding Event Match Quality
EMQ measures how well Meta can match your events to Facebook/Instagram users:
| Score | Quality | Meaning |
| 8-10 | Excellent | Most events matched to users |
|---|---|---|
| 6-7 | Good | Majority of events matched |
| 4-5 | Fair | Some matching, room to improve |
| 1-3 | Poor | Few events matched to users |
Higher EMQ = Better ad optimization = Lower cost per acquisition.
Factors Affecting Match Rate
1. Customer Data Available
Meta needs user identifiers to match events:
| Data Point | Match Impact |
| High | |
|---|---|
| Phone | High |
| First Name + Last Name | Medium |
| City + State + Zip | Low |
| IP Address | Low |
| User Agent | Low |
2. Browser vs Server Events
| Source | Typical EMQ |
| Browser pixel only | 2-4/10 |
|---|---|
| Server CAPI only | 5-7/10 |
| Browser + CAPI | 7-9/10 |
3. iOS Users
Apple’s App Tracking Transparency reduces browser-side matching for iOS users.
How to Improve Match Rate
Solution 1: Enable Server-Side CAPI (Recommended)
The biggest improvement comes from server-side tracking:
- Upgrade to TrackShift Pro if not already
- Go to Integrations → Meta
- Enter your Pixel ID and Access Token
- Click Save and Test Connection
CAPI sends richer customer data (email, phone) with proper hashing.
Solution 2: Ensure Customer Data is Captured
Verify your checkout collects:
- Email (required for checkout anyway)
- Phone number (make it required or prominent)
In Shopify Admin:
- Go to Settings → Checkout
- Under “Customer contact method” ensure email is required
- Consider adding phone as required field
Solution 3: Verify Data is Being Sent
Check that TrackShift sends customer data:
- Open Developer Tools (F12)
- Go to Network tab
- Complete a test purchase
- Filter by “telemetry”
- Look for the purchase event payload
- Verify
emailandphonefields are present (hashed)
Solution 4: Check Hashing Format
Meta requires SHA256 lowercase hashing:
Correct format:
em: "e99a18c428cb38d5f260853678922e03..." // 64 chars
ph: "8d969eef6ecad3c29a3a629280e686cf..." // 64 chars
Wrong format:
em: "john@email.com" // Unhashed
em: "E99A18C428CB38D5F260..." // Uppercase
TrackShift handles hashing automatically. If you see unhashed data, contact support.
Solution 5: Enable Advanced Matching in Meta
- Go to Events Manager → Settings
- Find Automatic Advanced Matching
- Ensure it’s ON
- Enable all data points
Solution 6: Wait for Data Accumulation
EMQ requires sufficient data to calculate:
- New setups may show lower scores initially
- Wait 1-2 weeks with steady traffic
- Score should improve as more events accumulate
Expected Timeline for Improvement
| Action | EMQ Improvement | Timeline |
| Enable CAPI | +2-3 points | Immediate |
|---|---|---|
| Add phone to checkout | +1-2 points | 1-2 weeks |
| Accumulate more data | +1-2 points | 2-4 weeks |
Checking Your Progress
- Go to Meta Events Manager
- Click your Pixel
- Go to Overview tab
- Look at Event Match Quality section
- Click “View Details” for per-event breakdown
Focus on purchase events first, as they’re most important for optimization.
—