Formatting Bangladeshi phone numbers for Meta and Google matching

In Bangladesh many buyers check out with a phone number and no email, especially on cash-on-delivery orders. That makes the phone the most valuable identifier you can send to an ad platform, but only if it is formatted exactly the way the platform hashes it. A single stray zero or dash produces a completely different SHA-256 hash, and the match silently fails.

Meta's format

Meta asks for digits only, with the country code, no symbols, letters or leading zeros, and then SHA-256 of that string. A local number 01712345678 becomes 8801712345678.

Google's format

Google's user-provided data uses E.164, which keeps the plus sign: +8801712345678, then SHA-256. The same buyer therefore needs two different hashes, one per platform.

The forms you will actually see in checkout forms

• 01712345678: national format with the trunk 0. Drop the 0 and add 880.
• 01712-345678 or 01712 345678: remove separators first.
• +880 1712 345678 or 00880…: already international. Keep the digits and drop the 00 or +.
• ৮৮০১৭১২৩৪৫৬৭৮ or ০১৭১২৩৪৫৬৭৮: Bengali digits typed on a Bengali keyboard. Convert each to 0–9 before anything else.
• 1712345678: bare national number. Prefix 880.

Email differs too

Meta: trim and lowercase. Google: trim, lowercase, and for gmail.com and googlemail.com addresses also remove the dots before the @. [email protected] and [email protected] are one Google account, so Google expects the dotless form.

Do it once, at the edge

Trakero normalizes every identifier both ways and hashes it the moment an event arrives, before anything is queued or stored. The raw number never reaches a database or a log. You can try the exact rules in your browser on our home page: the demo runs the same code locally and sends nothing.