WooCommerce plugin has been released on WordPress.orgView plugin →

EMQ Enricher: Raise Meta Event Match Quality Server-Side

5 min readUpdated Nov 16, 2026

Meta gives every Conversions API event an Event Match Quality score from 0 to 10: how well it can match the event to a person on Facebook or Instagram. A purchase carries the buyer's email and phone, so it scores high. But a page view, a product view or an add to cart usually carries only the IP address, the browser and the fbp cookie, and scores around 4. Low scores mean fewer events Meta can credit to your ads.

The EMQ Enricher fixes that. The first time a customer's details reach your server (at checkout, sign-up or newsletter), TagLinc remembers them. On every later event from the same visitor, it adds the missing details before the event goes to Meta. It is on the Pro, Business and Enterprise plans.

What Meta gets, before and after

EventWithout the EMQ EnricherWith the EMQ Enricher
Add to cart of a returning customerIP, user agent, fbpIP, user agent, fbp, email, phone, first and last name, city, state, zip, country, fbc
PurchaseEverything the checkout sendsThe same: values the event already has always win

How it works

  • It finds the visitor by any ID the event has: email, phone, external ID, the User ID header, the _fbp cookie or the GA client ID. When one event carries two of them, they are linked, so a later event with only one still finds the visitor.
  • It fills only empty fields. A value the event already has is never replaced.
  • It cleans and hashes the way Meta asks: email lowercased, phone as digits with the country code (a national number gets its country code from the event's country), names without spaces or punctuation, then SHA-256. Values that are already hashed are kept as they are. fbp and fbc stay unhashed, as Meta wants.
  • It builds fbc from a Meta ad click (fbclid in the page address) when there is no _fbc cookie yet, and remembers it.
  • One request per event. The variables of one event share one answer, so the 11 fields cost one quick call.

Privacy

  • Only SHA-256 hashes are stored for email, phone, name, city, state, zip, country and external ID. Never IP addresses or user agents.
  • A visitor is forgotten 90 days after their last event. Clear all on the Power-Up page deletes every visitor at once.
  • Nothing is read or saved when the visitor refused ad data: Google Consent Mode ad_user_data or ad_storage denied. The event then goes out with only its own details. You can turn this check off in the variable, but leave it on in the EU and UK.
  • Requests that Bot Detection marks as bots are left alone.
  • A visitor with only a cookie ID and no customer details is not stored.

Set it up

  1. Open your container, go to Power-Ups and turn on EMQ Enricher. Your container restarts once.
  2. If your container is linked to Google Tag Manager (the GTM setup tab), press Add to GTM. TagLinc adds the template, one variable per field and a Transformation for your Meta tags to a new workspace called TagLinc EMQ setup. Open it in Tag Manager, check it and press Submit to publish. Nothing changes on your site until you publish.
  3. Not linked? Set it up by hand:
    1. Download the TagLinc EMQ Enricher template from the Power-Up page. In your server container open Templates, Variable Templates, New, the three-dot menu, Import.
    2. Make one variable of that type per field. In Return pick the field: em, ph, fn, ln, ct, st, zp, country, external_id, fbp, fbc.
    3. Add a Transformation of the type Augment event. Add one row per field: x-fb-ud-em = {{EMQ em}}, x-fb-ud-ph = {{EMQ ph}}, and so on; use x-fb-ck-fbp and x-fb-ck-fbc for the last two. Meta's Conversions API tag reads these keys first.
    4. Publish.

Check that it works

  1. In Meta Events Manager open your pixel, then Test Events, and put the test code on your Meta Conversions API tag.
  2. In one browser, buy something or sign up with a test email. Then view another product.
  3. The product view now shows Email and Phone under customer information parameters.
  4. On the Power-Up page, Visitors remembered and Events enriched, 24 h start to count.

Event Match Quality in Events Manager is an average over the last 48 hours, so give it two days to move.

Limits by plan

PlanVisitors remembered
FreeNot included
Pro200,000
Business2,000,000
EnterpriseNo limit

When a container is full, visitors it already knows are still enriched and updated; new ones are not added until older ones expire. Enricher visitors do not count against your Data Store limit.

Common questions

Does it replace the Meta tag's own "Event Enhancement"? It goes further. Event Enhancement keeps details in a browser cookie, so it only helps the same browser and is lost when cookies are cleared. The EMQ Enricher keeps them on your server and finds the visitor by email, phone, User ID, fbp or GA client ID, including for orders sent from your store's backend.

Does it work for TikTok or Google Ads? Not yet. It starts with Meta, where Event Match Quality is scored. The same details will come to TikTok and Google Ads enhanced conversions later.

What if TagLinc cannot be reached? The variables return the event's own values, so your Meta tag sends exactly what it would without the EMQ Enricher.

Was this guide helpful?
Thanks, that helps us improve the docs.
Still stuck?

Open a support ticket from your dashboard and include the container name.

Contact support