Tiendanube now turns on Meta's Conversions API: is it enough?

What does Tiendanube's native Meta integration do?

When you connect your Meta portfolio from Tiendanube, you don't have to configure anything else. Their help center puts it this way: "When you connect your portfolio, Meta's Conversions API is activated automatically". And it spells out what travels through that channel today: "only the information for the 'Add to Cart', 'Add Payment Info' and 'Purchase' events is sent", with more events to be added (Tiendanube help center, updated 9/2/2026).

It's a good foundation: the purchase reaches Meta even if the browser blocks the pixel. What the article doesn't detail is which buyer data goes along with each event, and that's where the difference that matters lies. The question is no longer whether Meta finds out about the sale, but what Meta knows about the person who bought.

What is EMQ and why does it matter more than the event?

EMQ (Event Match Quality) is the grade Meta gives each type of event you receive. In Meta's words, it's "a score (out of 10) that indicates how effective the customer information sent from your server may be at matching event instances to a Meta account": a grade from 0 to 10 on how well it can tie that event to a real person. The data points that raise it the most are email, phone, name, IP, and click and browser identifiers (Meta documentation).

Why it matters to you even if you're not technical: an event that arrives without buyer data gets counted, but it teaches nothing. Meta knows someone bought, not who. With that it optimizes worse, builds lookalike audiences on incomplete information, and every sale costs you more. The sale isn't lost. The sale's data is.

If you want the details on each parameter, they're in what EMQ is and match parameters.

What happened when we compared it across 42 Tiendanube stores?

In September 2026 we turned on the Escalafy pixel in Tiendanube stores, running alongside the pixel each store already had, without touching the campaigns. Then we compared the EMQ grade Meta gave each one, event by event.

Method: the 7-day average EMQ Meta shows in Events Manager, comparing only the events both pixels send. We left out the Lead event, which the native pixel normally doesn't send, to keep the comparison even. These are each store's first days: the sample is small and the numbers will move.

Two things to read this table correctly. First, in 2 stores our pixel came out worse: that's why nobody should switch pixels without comparing against their own data first. Second, "higher" isn't the same as "more sales": EMQ is the condition for Meta to optimize better, not the end result. The result is measured in CPA over the following weeks.

Why does Meta receive less buyer data?

Because most of that data is read in the browser, and browsers block it more and more. The four main leaks:

• Ad blockers, which cut off the pixel before it reads anything.
• iOS and the tracking permission, which limit what Meta can match from a phone.
• Cookies that delete themselves: Safari removes third-party cookies and shortens the life of first-party ones.
• Accelerated checkouts, where the buyer pays in one click and the pixel sees little of the journey.

A conversions API sends the event from the server, but with whatever data the store managed to collect. If that data arrived incomplete, the event travels incomplete. We explain it in more detail in why Meta doesn't record all your sales.

How do I check my Tiendanube store's EMQ?

1. Go to Meta Events Manager and choose your store's pixel.
2. Open the Overview tab and click an event, for example Purchase.
3. Look at Event Match Quality. Meta shows you the grade and which parameters it's receiving.
4. Repeat with AddToCart and InitiateCheckout. If any is below 6, Meta is missing data about your buyers at that step.

The full guide, with what to do for each grade, is in how to raise EMQ step by step.

When is the native integration enough?

It's enough if you spend little on Meta, if your EMQ grades are already above 8 on purchase events, or if you don't yet have the volume for the algorithm to really learn. In those cases, improving the signal doesn't move the result enough to justify another cost.

It's not enough when ad spend is a big share of your costs and CPA rises month after month with the same creatives. At that point, the algorithm knowing who buys from you stops being a technical detail.

Is Tiendanube's native integration compatible with Meta's Gateway?

No, and this is new. On October 9, 2026 Tiendanube updated its own help article to warn that the native Conversions API integration is not compatible with Meta's Conversions API Gateway. If you have both active at the same time, the article says, the Gateway "can block or contaminate the data from the native integration, generating empty events."

"Empty events" is exactly the problem this article is about. The event arrives, Meta counts it, and the buyer data Meta needs to know who bought is not inside it. If an agency ever set up a Gateway on top of the native integration, that is the first thing worth checking.

How to check it, per the same article: go to your Meta Business Manager → Events Manager → select your pixel → look at the connected data sources. If "Gateway" shows up as an active source, it has to be disconnected before you go further.

Source: Centro de Atención Nube — How to activate the Facebook Conversions API, last updated October 9, 2026 (accessed October 15, 2026).