Meta Advantage+ uses artificial intelligence to find buyers. But that AI needs data: the email, phone number, name, and location of every person who bought from your store. If your EMQ is low — below 7 out of 10 — that data is missing from most events, and Meta's AI is working from a blurry picture of who your buyers actually are. Weaker audiences, worse performance, higher CPA.
What is Meta Advantage+ and why does it depend on your data?
Meta Advantage+ is Meta's suite of automation technologies for ad campaigns: Advantage+ Shopping Campaigns (ASC), Advantage+ Audience (the former broad targeting), and Advantage+ Creative, among others. The promise: Meta automatically decides who to show your ad to, when, and in what format, using its AI model.
What that AI does is look for patterns in the events you send it. Every time someone buys from your store, the pixel sends a Purchase event to Meta. If that event includes the buyer's email, phone number, name, city, and postal code, Meta can identify that person in its database with high confidence and find other people like them. More quality data → better model → more conversions at the same cost or less.
The problem is that most ecommerce pixels on Tiendanube and Shopify don't send that data. The event arrives, but without email, without phone, without name. Meta counts the purchase, but it doesn't know who bought.
How does EMQ affect Advantage+ performance?
EMQ (Event Match Quality) is Meta's quality score measuring how much buyer identification data each event includes. It runs from 0 to 10. The relationship with Advantage+ is direct:
| EMQ | Data reaching Meta | What Advantage+ can do |
|---|---|---|
| 8–10 | Email, phone, name, city, postal code | Identifies the buyer, builds precise lookalikes, optimizes well |
| 5–7 | Only some data (e.g., email only) | Partial identification, less precise lookalikes, degraded optimization |
| 0–4 | Little or nothing (IP or user agent only) | Cannot identify the buyer, generic audiences, higher CPA |
Most ecommerce stores in LATAM have an EMQ between 4 and 6. That means Meta is building its Advantage+ audiences with half the data it needs.
The correct framing for the data loss: Meta does count your sales. If you had 100 orders yesterday, Meta probably saw 90–95 of them. The real problem is that of those 95 purchases Meta sees, in 50 or 60 of them it doesn't know who the buyer is because the event arrived without an email or phone number. Meta tallies the sales but can't attribute them or find look-alikes from them. That destroys lookalike audiences and degrades Advantage+.
Why is that identification data missing from pixel events?
The standard Meta pixel (installed via code or through the native Tiendanube/Shopify integration) captures browsing events: PageView, ViewContent, AddToCart. But to capture buyer identification data, it needs access to the user's session at the moment of Purchase.
In many Tiendanube and Shopify checkouts, when the Purchase event fires, the pixel doesn't have access to the buyer's email and phone because that data lives on the server layer, not in the browser. The pixel sees that a purchase happened, but not by whom.
The solution is Meta's Conversions API (CAPI): send events from the server, where all the order data is always available, with the full identification parameters (email, phone, name, city, postal code). When CAPI sends the Purchase with those hashed fields, the EMQ rises to 8–10.
What improves when EMQ goes up?
With a high EMQ (8+), Advantage+ can:
- Build better lookalikes: it knows exactly who bought and finds similar people on Facebook and Instagram. With incomplete data, it's searching for "people who clicked on a pixel without knowing who they are."
- Attribute conversions correctly: it can connect a click to a purchase even when ad blockers are present or when browsing happened across devices.
- Optimize Advantage+ budgets faster: the algorithm learns who converts more quickly when it can identify real buyers. Fewer wasted iterations, shorter learning phase.
- Re-engage previous buyers: Advantage+ retargeting is more precise when prior events included full identification data.
How Escalafy's pixel improves EMQ for Advantage+
Escalafy's server-side pixel sends every purchase event to Meta with full identification parameters: hashed email, hashed phone, name, city, and postal code. The data comes from the actual order in Tiendanube or Shopify, where it is always available — not from the buyer's browser, which may be blocking the pixel.
The result is a consistently high EMQ, and an Advantage+ that works from real data instead of guesses. To see how to improve it step by step, read the guide on improving EMQ.
The difference versus other tracking pixels: Escalafy doesn't just improve Meta's signal — it already knows the cost of each product, the commissions, the shipping, and the installment fees for each order. So the event it sends to Meta isn't just "there was a purchase" but "there was a purchase with this real profit." That closes the loop between advertising and profitability.
Frequently asked questions about Meta Advantage+ and data quality
Does Meta Advantage+ work without a high EMQ?
It works, but with degraded performance. With a low EMQ, Advantage+ uses weaker signals to optimize — primarily browsing behavior and demographic patterns — instead of real identity data. Many advertisers who "tried Advantage+ and it didn't work" had a low EMQ without realizing it.
What's a good EMQ for Meta Advantage+?
Meta recommends an EMQ of 7 or higher for optimal performance. 8–10 is the range where Advantage+ can identify buyers with high confidence. Check your current EMQ in Meta Events Manager under "Event match quality."
Does implementing CAPI improve Advantage+ immediately?
The EMQ improvement is immediate — new events arrive with complete data right away. The impact on Advantage+ takes a few weeks to show up because the algorithm needs enough events at the new EMQ to recalibrate its model. Measurable CPA improvements are typically visible between weeks 2 and 6 after a correct CAPI implementation.
Doesn't the native Meta integration with Tiendanube or Shopify handle this?
Partially. The native integration sends events with some identification parameters, but email and phone coverage varies by checkout configuration. Many stores with the native integration have an EMQ of 5–7, not 8–10. To maximize EMQ you need CAPI with all the identification parameters from the complete order.
Keep reading
What Escalafy does for your store
Connect your channels and see the truth behind your numbers. No Excel, in real time.
