Add section to Frequently Asked Questions - Profiles Sync #4657
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What hash function is used for the external_id_hash field by Profile Sync? Zendesk Ticket : https://segment.zendesk.com/agent/tickets/503271
What hash function is used for the external_id_hash field by Profile Sync?
The value of the
external_id_hash
is a hash of theexternal_id_type
andexternal_id_value
, using SHA-1. This field corresponds theprimary_key
for the table.hash ( external_id_type and external_id_value)
For example, in Big Query this is the logic,
TO_HEX(SHA1(concat(external_id_type, external_id_value))) as seg_hash
.Customer (MongoDB) reached out in March wondering what hashing algorithm is used by the Profiles Sync, no docs stated this anywhere though it's obvious that a hashing algorithm is used. Since this page is technical listing Profiles Sync Sample Queries, it's likely other customers would also want this information in order to un-hash (decrypt) their user data.
Merge timing
Related issues (optional)
n/a