Free tool

Meta Conversions API Event Builder With SHA-256 Hashing

Fill in an event, with its name, time, source, page URL and customer data: the tool normalizes each field the way Meta asks, computes its SHA-256 hash and builds the JSON payload ready to send to the Conversions API. Nothing leaves your browser: the tool prepares the request and never sends it.

Meta rejects the entire request, processing no events, as soon as one event_time in it is more than 7 days old. For a website event, the page URL and the browser user agent are required.

Fictitious example
The event
Hashed customer data

Normalized, then hashed in SHA-256 in your browser, the way Meta asks. An empty field stays out of the JSON.

+
Country code in the + box. A number written with + or 00 keeps its own country code.
Data sent unhashed

Meta asks you never to hash these: IP address, user agent, and the fbc and fbp identifiers from the pixel cookies.

Event value

custom_data: both are required for a Purchase.

Nothing is sent: the tool prepares the request and calls no server.

Request to send

Replace {API_VERSION}, {PIXEL_ID} and {TOKEN} with your API version, your pixel ID and your access token. Meta’s example uses v26.0.
JSON payload
The request body: the data list holds your event. Hashed fields go out as lists, as in Meta’s example.
Each field, normalized then hashed
    Checks

      Sources read on November 6, 2026: Meta, Customer Information Parameters, Meta, Server Event Parameters, Meta, Using the API, Meta, custom_data parameters, Meta, fbp and fbc parameters, Meta, Handling Duplicate Pixel and Conversions API Events and Meta Pixel, standard events.

      Is Your Conversions API Sending The Right Events?

      I set up your tracking with Google Tag Manager, in the browser and on the server: pixel, Conversions API and deduplication, checked event by event.

      20 minutes · No commitment · 100% confidential

      Step 1 Of 2 · Your Project

      Step 2 Of 2 · Your Details

      Who are these campaigns for? *
      What are you looking for in our collaboration? * You can pick several
      Where do your ad campaigns stand today? *
      When would you ideally like to start? *

      How the tool prepares your event

      em = [SHA-256(email trimmed and lowercased)], 64 hexadecimal characters

      Each customer field first goes through the normalization Meta describes, then through SHA-256, computed in your browser. The email loses its surrounding spaces and turns lowercase. The phone number keeps its digits, drops any leading zeros and gets the country code: 020 7946 0958 with code 44 becomes 442079460958. First and last names turn lowercase with no punctuation, accents kept in UTF-8: Valéry becomes valéry. The city also loses its spaces, the date of birth becomes YYYYMMDD, and a US zip code keeps its first 5 digits. To hash a whole list, the SHA-256 hash generator runs the same calculation line by line.

      Meta’s example: John_Smith@gmail.com becomes john_smith@gmail.com, whose hash starts with 62a14e44. The number (650)555-1212, with country code 1, becomes 16505551212, and its hash starts with e323ec62. If the tool returns the same fingerprints, you can compare your own code with it. IP address, user agent, fbc and fbp go out unhashed: Meta asks you never to hash them.

      The JSON follows Meta’s example: hashed fields go out as lists, empty fields stay out, event_time is in Unix seconds, and value travels with currency in custom_data. Before sending anything, check that your pixel fires the same event with the Facebook pixel checker: the same event_id on both sides lets Meta deduplicate.

      What the tool does for you

      • Write your first request: fill in a fictitious purchase, copy the JSON and use it as a template in your code or server container. You start from a structure that follows Meta’s example.
      • Check your hashing: enter the same address as your site and compare the hash with the one your code sends. A gap comes from normalization: spaces, capital letters or a missing country code.
      • Plan server-side tracking: list the fields your server must collect for each event, user agent, URL, fbc and fbp cookies, then the ID shared with the pixel. To go further, see how I set up server-side tracking.

      Frequently asked questions

      Which data needs hashing?

      Meta requires SHA-256 hashing for email, phone, first name, last name, date of birth, gender, city, state, zip code and country, and recommends it for external_id. IP address, user agent and the fbc and fbp identifiers are never hashed. The tool follows this split: the first group goes out as lists of hashes, the second unhashed.

      Which rules does the tool check?

      The event name and time, both required; the 7-day limit, beyond which Meta rejects the entire request (62 days for a physical_store event); the user agent and URL, required for a website event; value and currency, required for a Purchase; the format of fbc, fbp, country and currency; and the presence of an event_id. To deduplicate, Meta matches event_id and event_name with the pixel’s eventID and event received within 48 hours, and favors the browser event when both arrive within 5 minutes of each other.

      Why are test_event_code and data_processing_options missing?

      The tool prepares a plain production event. test_event_code sends events to the test events tool, and data_processing_options sets Limited Data Use (LDU): add them by hand if your integration needs them.

      Is my data sent anywhere?

      No. Normalization and hashing happen in your browser: the tool calls no server, Meta’s or any other, and everything disappears when you close the page. The prefilled example is fictitious.

      Théo Maupilé

      Growth partner

      Positioning, acquisition, innovation: together we build a lasting growth system.

      Théo MaupiléFreelance Paid Media

      Google PartnerSuperMalter

      ◉ Certifications

      Official Google Partner
      & SuperMalter