ADVANCED MATCHING

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.

SERVICE SNAPSHOT
Best for

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

What you get

Free 30-minute tracking audit • No obligation

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.

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.

Badly Formatted Data

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

No Identifier After Login

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

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.

HOW IT WORKS

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.

01
Customer Input

Email, phone and name at checkout or form

02
Data Layer

Fields exposed with the conversion event

03
Normalize and Hash

Formatted to spec, then SHA-256 hashed

04
Event Sent

Pixel and CAPI carry the hashed fields

05
Meta Matching

Event linked to a Meta account

WHAT'S INCLUDED

What's Included in Advanced Matching

Clear deliverables, documented and validated before handover.

Match Quality Baseline

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

Customer Data Layer Spec

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

Normalization and Hashing Logic

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

Privacy and Consent Controls

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

Parameter QA

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

Matching Reference

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

IMPLEMENTATION PROCESS

From Audit to Validated Data

How a Advanced Matching project runs, step by step.

01

Audit

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

02

Strategy

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

03

Implementation

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

04

Testing

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

05

Validation

Validate match quality changes per event and document the configuration.

PLATFORMS

Platforms and Tools We Work With

The tools involved in a typical Advanced Matching implementation.

Meta Pixel

Advanced Matching fields

Meta Conversions API

Customer information

Meta Events Manager

Event match quality

Google Tag Manager

Hashing variables

Consent platform

Data sharing rules

FAQ

Advanced Matching FAQ

Straight answers before you book. Still have a question? Talk to us directly.

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.

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.

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.

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.

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.

READY TO FIX YOUR DATA?

Stop Guessing. Start Measuring.

Get a professional review of your tracking setup and discover where your marketing data may be leaking.

Free 30-minute review • No obligation

Scroll to Top