Waymark / Routes / developers.facebook.com/docs/marketing-api/conversions-api implement meta conversions api advanced matching parameters with correct field-level hashing
domain: developers.facebook.com/docs/marketing-api/conversions-api · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checked community attestations: 0✓ / 0✗
Steps Collect available customer identifiers (email, phone, first/last name, city, state, zip, country, external_id) at the point of conversion. Normalize each raw value per field (lowercase and trim strings, E.164 format for phone numbers) before hashing. Hash em, ph, fn, ln, ge, db, ct, st, and zp with SHA-256; leave client_ip_address, client_user_agent, fbc, and fbp unhashed. Send the hashed user_data object together with fbp/fbc browser identifiers and the same event_id used by the Pixel, to support deduplication. Check Events Manager's Event Match Quality (EMQ) score to confirm which parameters are actually improving match rate. Known gotchas The Meta Business SDKs hash automatically - a direct/manual API integration that copies SDK sample code without hashing will send plaintext PII. Hashing the wrong fields, or hashing fields Meta expects unhashed (like fbc/fbp), silently degrades match quality instead of throwing an error. Sending only one identifier (e.g. email alone) underperforms; Meta's matching relies on combining multiple identifiers (email + phone + external_id + fbp + fbc) together.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp