SHA-256 system tags for outgoing data mappings
Category: Enhancement
Location: Webhooks → Outgoing Webhooks → Create or Edit → Add Tags
Release Date: October 21 2026
What’s new
• Add three automatically derived system tags to outgoing webhook templates and supported RTB mappings:
• caller_id_sha256 — SHA-256 of the normalized caller number, including country code and without a leading plus sign.
• visitor_country_sha256 — SHA-256 of a valid two-letter country code after trimming spaces and converting it to lowercase.
• visitor_id_sha256 — SHA-256 of the visitor ID after trimming surrounding spaces; letter case is preserved.
• Valid values produce 64-character lowercase hexadecimal strings. Missing or invalid source values produce an empty string instead of a hash of empty input.
How to use it
• Open Webhooks → Outgoing Webhooks and create or edit the webhook you want to configure.
• Use Add Tags to select the required SHA-256 system tags and map them to the destination’s expected fields.
• Save the webhook. Where another configuration attaches a webhook, select this existing webhook there rather than recreating it in the attachment form.
• Test your mapping and check both a populated source and an empty-source case before relying on it for customer data delivery.
Impact
• Send consistently normalized hashes without building your own hashing step for these three fields.
• The tags are system-generated, not custom values to override manually. Email hashing, a Meta-specific phone alias and call-record-ID hashing are not included.
• Hashing is not encryption and does not by itself establish consent, destination acceptance or anonymization.
