From 810f80b03032494ed750f8185066bb2ad364668f Mon Sep 17 00:00:00 2001 From: stayseesong Date: Tue, 1 Apr 2025 00:02:02 -0700 Subject: [PATCH 1/3] [netlify-build] --- src/connections/destinations/index.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/src/connections/destinations/index.md b/src/connections/destinations/index.md index 04c8485b98..f96e0d5ef8 100644 --- a/src/connections/destinations/index.md +++ b/src/connections/destinations/index.md @@ -220,6 +220,18 @@ The following destinations support bulk batching: > info "You must manually configure bulk batches for Actions destinations" > To support bulk batching for the Actions Webhook destination, you must set `enable-batching: true` and `batch_size: >= 1000`. +### Smart hashing +Segment automatically hashes personally identifiable information (PII). This simplifies implementation for teams with data privacy requirements and eliminates issues with double-hashing that can result in failed matching at destinations. + +These are the 2 types of data that Segment handles for hashing: +* **Plain text data:** When you send plain text values to destinations that require hashed values, Segment automatically normalizes and hashes these values. +* **Pre-hashed data:** If you already hash your data before sending it to Segment, Segment is able to detect that the data is hashed, and will pass your pre-hashed data directly to the destination, avoiding double-hashing. + +> info "" +> When pre-hashing data yourself, ensure you follow each destination's specific hashing requirements. Fields that support automatic hashing detection will have a tooltip indicating *"If not hashed, Segment will hash this value."* + +For destination-specific hashing requirements, refer to the destination's API documentation. + ## IP Allowlisting IP Allowlisting uses a NAT gateway to route traffic from Segment's servers to your destination through a limited range of IP addresses, which can prevent malicious actors from establishing TCP and UDP connections with your integrations. From c8a957a93b538896fe7e61d144196a9a21915908 Mon Sep 17 00:00:00 2001 From: stayseesong Date: Wed, 2 Apr 2025 10:05:30 -0700 Subject: [PATCH 2/3] smart hashing to hashing --- src/connections/destinations/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/connections/destinations/index.md b/src/connections/destinations/index.md index f96e0d5ef8..afd1b47765 100644 --- a/src/connections/destinations/index.md +++ b/src/connections/destinations/index.md @@ -220,7 +220,7 @@ The following destinations support bulk batching: > info "You must manually configure bulk batches for Actions destinations" > To support bulk batching for the Actions Webhook destination, you must set `enable-batching: true` and `batch_size: >= 1000`. -### Smart hashing +### Hashing Segment automatically hashes personally identifiable information (PII). This simplifies implementation for teams with data privacy requirements and eliminates issues with double-hashing that can result in failed matching at destinations. These are the 2 types of data that Segment handles for hashing: From 06ed9b0d28a16fd8088dc860747b773aafc61952 Mon Sep 17 00:00:00 2001 From: stayseesong <83784848+stayseesong@users.noreply.github.com> Date: Wed, 2 Apr 2025 10:29:15 -0700 Subject: [PATCH 3/3] Apply suggestions from code review Co-authored-by: pwseg <86626706+pwseg@users.noreply.github.com> --- src/connections/destinations/index.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/connections/destinations/index.md b/src/connections/destinations/index.md index afd1b47765..fea7094e95 100644 --- a/src/connections/destinations/index.md +++ b/src/connections/destinations/index.md @@ -223,12 +223,12 @@ The following destinations support bulk batching: ### Hashing Segment automatically hashes personally identifiable information (PII). This simplifies implementation for teams with data privacy requirements and eliminates issues with double-hashing that can result in failed matching at destinations. -These are the 2 types of data that Segment handles for hashing: +Segment supports these 2 types of data for hashing: * **Plain text data:** When you send plain text values to destinations that require hashed values, Segment automatically normalizes and hashes these values. * **Pre-hashed data:** If you already hash your data before sending it to Segment, Segment is able to detect that the data is hashed, and will pass your pre-hashed data directly to the destination, avoiding double-hashing. > info "" -> When pre-hashing data yourself, ensure you follow each destination's specific hashing requirements. Fields that support automatic hashing detection will have a tooltip indicating *"If not hashed, Segment will hash this value."* +> If you choose to hash data yourself, ensure you follow each destination's specific hashing requirements. Fields that support automatic hashing detection will display a tooltip indicating *"If not hashed, Segment will hash this value."* For destination-specific hashing requirements, refer to the destination's API documentation.