Adobe Experience Platform: streaming validation fails on hashed emails
Learn how to resolve the Adobe Experience Platform issue when streaming validation fails on hashed emails. You need to verify schema requirements, check data transformation rules and configuration, and implement hashing mechanisms.
Description description
Environment
- Product: Adobe Experience Platform (AEP)
- Component: Data Collection / Adobe Launch
- Dataset: Web SDK
Issue
When streaming data into the Web SDK dataset, batches fail to load due to an error with the hashed_email field. The hashed_email column is mandatory and requires a minimum length of 64 characters. However, some streaming batches contain email addresses in this column that do not meet the required length, resulting in validation errors.
Error message example: The message cannot be validated: [ #/path/to/hashed_email: expected minLength: 64, actual: 25]
Resolution resolution
To resolve this issue:
- Ensure that the schema associated with your dataset specifies that the
hashed_emailshould be a SHA256 hashed value. Review SHA256 Hashing Support for setCustomerIDs for more details. - Review any rules or data elements within your Tag property configuration to ensure they correctly hash email addresses before sending them to AEP. Review Build tag rules for more details.
- If not already implemented, add code within your web implementation (For example: JavaScript) to automatically hash email addresses using SHA256 before they are sent as part of the streaming batch. Failing to do so may result in the data (“email” in this case) being sent in clear text. Review SHA256 Hashing Support for setCustomerIDs for more details.
- Use debugging tools such as console logging on relevant web pages where data collection occurs to verify that all events and data elements fire correctly and include properly hashed values for emails. Review Debugging in the Web SDK Guide.
- After making necessary adjustments, validate by re-streaming sample batches ensuring no validation errors occur related to
hashed_email. For steps, Stream data to Experience Platform with Web SDK.
By following these steps, you can ensure compliance with schema requirements and prevent future batch failures due to invalid email token lengths.
For further assistance or if issues persist after implementing these changes, please contact Adobe Support for additional troubleshooting guidance.