Best Practices for Using Hash Data
Hashing is only as accurate as the input it receives. Clean, properly formatted data ensures that your hashes are consistent, platform-compliant, and privacy-safe. Small issues like extra spaces, missing country codes, or inconsistent casing can cause mismatches or failed uploads.
🔐 Tips for using Hash Data:
| Tip | Description |
|---|---|
| Clean Your Inputs | Remove leading/trailing spaces, fix typos, and ensure consistent formats before applying hashing functions. |
| Include Country Codes | Phone numbers must include country codes for proper E.164 formatting. For example, use 14155552671 instead of 4155552671. |
| Be Consistent Across Rows | Consistency is key for matching records in advertising platforms. Double-check that formatting is uniform across your dataset. |
| Freeze When Final | Use the Freeze Results feature to lock in values once you're done. This avoids rehashing and saves credits or API calls. |
| Test a Few Rows First | Before hashing your entire dataset, try a few sample rows and validate the output, especially when preparing for audience uploads. |
| Be Cautious of Sensitive Parameters | The =HASH() function is case-sensitive. Use =HASHEMAIL() for consistent email hashing, as it automatically normalizes casing. |