● Meta / Facebook Tracking

Meta Advanced Matching for Stronger Event Matching

We configure Meta Advanced Matching so your pixel and server events carry hashed customer details such as email, phone and name. This helps Meta connect conversions to ad viewers. Suited to advertisers whose events fire correctly but show weak event match quality.

Advanced MatchingIllustrative
  1. Customer Input
  2. Data Layer
  3. Normalize and Hash
  4. Event Sent
  5. Meta Matching
What this covers
  • Manual Advanced Matching on the pixel
  • Normalized, hashed customer fields
  • External ID for logged in users
  • Match quality reviewed per event
Platforms
Meta PixelMeta Conversions APIMeta Events ManagerGoogle Tag ManagerConsent platform
Best for

Advertisers whose Meta events fire correctly but show low event match quality

01 The problem

Events That Fire but Do Not Match Anyone

An event without customer information is hard for Meta to link to a person. Automatic matching catches some fields, but it often misses data from checkouts, forms and logged in sessions.

  1. 01

    Automatic Matching Misses Fields

    Automatic Advanced Matching reads visible form fields, so it can miss data on custom checkouts, embedded forms and multi-step flows.

  2. 02

    Badly Formatted Data

    Phone numbers without country codes, emails with capital letters or spaces, and unhashed values reduce or block matching.

  3. 03

    No Identifier After Login

    Returning customers who are logged in are not identified with an external ID, so repeat purchases match less reliably.

02 What we implement

What We Add to Your Meta Events

We pull customer details from the data layer at the moments they are known, format them the way Meta specifies and attach them to both browser and server events.

  • 01

    Manual Advanced Matching

    Customer fields passed to the pixel init or event call instead of relying on automatic detection alone.

  • 02

    Customer Data Layer Variables

    Email, phone, name, city, state, zip and country exposed in the data layer after checkout or form submit.

  • 03

    Normalization Rules

    Lowercasing, trimming, removing symbols and adding country codes to phone numbers before hashing.

  • 04

    SHA-256 Hashing

    Values hashed in GTM or on the server so plain text customer data is not sent to Meta.

  • 05

    External ID Mapping

    A stable customer or CRM ID sent as external_id on both pixel and CAPI events.

  • 06

    Consent Rules for Customer Data

    Customer fields only attached when your consent setup allows it.

03 Live data flow

How Customer Data Improves an Event Match

Customer details captured on your site are cleaned, hashed and attached to the event, giving Meta more signals to match the conversion to an account.

Advanced Matching data flowIllustrative
  1. 01Customer InputEmail, phone and name at checkout or form
  2. 02Data LayerFields exposed with the conversion event
  3. 03Normalize and HashFormatted to spec, then SHA-256 hashed
  4. 04Event SentPixel and CAPI carry the hashed fields
  5. 05Meta MatchingEvent linked to a Meta account
04 How it works

From audit to validated data.

How Advanced Matching projects run. Nothing goes live until it has been tested.

  1. 01

    Audit

    Audit current customer parameters and event match quality in Events Manager.

  2. 02

    Strategy

    Decide which customer fields to send, where they come from and consent rules.

  3. 03

    Implementation

    Implement data layer fields, normalization, hashing and external ID mapping.

  4. 04

    Testing

    Test hashed parameters on pixel and CAPI events in the Test Events tool.

  5. 05

    Validation

    Validate match quality changes per event and document the configuration.

05 Deliverables

What's Included in Advanced Matching

Everything is documented and handed over, so your team knows exactly what was built and why.

  • 01

    Match Quality Baseline

    We record current event match quality and which customer parameters each event sends today.

  • 02

    Customer Data Layer Spec

    A specification for your developers or platform showing which fields to expose and when.

  • 03

    Normalization and Hashing Logic

    GTM variables or server code that format and hash every field to Meta's requirements.

  • 04

    Privacy and Consent Controls

    Customer data tied to consent status and limited to fields you collect lawfully.

  • 05

    Parameter QA

    Each event inspected in Test Events to confirm the expected hashed parameters are present.

  • 06

    Matching Reference

    Documentation of fields, formats, sources and consent rules for future maintenance.

Platforms

The tools involved in a typical Advanced Matching implementation.

  • Meta PixelAdvanced Matching fields
  • Meta Conversions APICustomer information
  • Meta Events ManagerEvent match quality
  • Google Tag ManagerHashing variables
  • Consent platformData sharing rules
06 QA and testing

Tested before anything goes live.

Test hashed parameters on pixel and CAPI events in the Test Events tool.. Validate match quality changes per event and document the configuration..

QA checklistAdvanced Matching
  • Meta Pixel HelperBrowser events fire with the right parameterschecked
  • Test EventsServer events received and matched in Events Managerchecked
  • DeduplicationBrowser and server events share event_id and count oncechecked
  • Match qualityEvent Match Quality reviewed for each eventchecked

Each check is repeated after launch on live traffic.

07 FAQ

Advanced Matching FAQ

Something else? Talk to GrowthUper

What is the difference between automatic and manual Advanced Matching?

Automatic matching lets the pixel read form fields it detects on the page. Manual matching means you pass customer values to the pixel directly from your own data. Manual matching is more dependable on custom checkouts, embedded forms and single page apps, so we usually set it up alongside automatic matching.

Which customer fields does Meta accept?

Meta accepts email, phone, first name, last name, date of birth, gender, city, state, zip code, country and external ID, plus technical fields like fbp, fbc, IP address and user agent on server events. We send the fields you actually collect and are allowed to share.

Is sending hashed customer data compliant?

Hashing protects the raw values in transit, but compliance also depends on your privacy policy, consent setup and the regions you serve. We connect the data to your consent tool and follow the guidance of your legal team.

Does Advanced Matching need the Conversions API?

No. Advanced Matching works on the pixel alone. Adding the same fields to Conversions API events usually gives Meta a more complete picture, so we apply the same field logic to both when you run CAPI.

How will we know if matching improved?

Events Manager shows event match quality per event and lists which customer parameters are received. We record these before the work and review them after, so you can see what changed without relying on estimates.

→ Next step

Get Advanced Matching right the first time.

Build a tracking and measurement system you can trust.

Get Free Tracking Audit Talk to GrowthUper Free 30-minute review · No obligation
Scroll to Top