Removed second level salt references

IABTechLab · Feb 8, 2025 · 2bdbc37 · 2bdbc37
1 parent c017e18
commit 2bdbc37
Showing 1 changed file with 10 additions and 10 deletions.
diff --git a/docs/guides/integration-snowflake.md b/docs/guides/integration-snowflake.md
@@ -149,10 +149,10 @@ If the DII is an email address, the service normalizes the data using the UID2 [
 
 If the DII is a phone number, you must normalize it before sending it to the service, using the UID2 [Phone Number Normalization](../getting-started/gs-normalization-encoding.md#phone-number-normalization) rules.
 
-|Argument|Data Type|Description|
-| :--- | :--- | :--- |
-| `INPUT` | varchar(256) | The DII to map to the UID2 and second-level bucket ID. |
-| `INPUT_TYPE` | varchar(256) | The type of DII to map. Allowed values: `email`, `email_hash`, `phone`, and `phone_hash`.
+| Argument     | Data Type    | Description                                                                               |
+|:-------------|:-------------|:------------------------------------------------------------------------------------------|
+| `INPUT`      | varchar(256) | The DII to map to the UID2 and salt bucket ID.                                            |
+| `INPUT_TYPE` | varchar(256) | The type of DII to map. Allowed values: `email`, `email_hash`, `phone`, and `phone_hash`. |
 
 A successful query returns the following information for the specified DII.
 
@@ -368,14 +368,14 @@ The following table identifies each item in the response, including `NULL` value
 
 The `SALT_BUCKETS` view query returns the date and time when the salt buckets for the raw UID2s were last updated. A salt value is used when generating UID2s. When the salt in the bucket is updated, the previously generated UID2 becomes outdated and doesn’t match the UID2 generated by other parties for the same user.
 
-To determine which UID2s need regeneration, compare the timestamps of when they were generated to the most recent timestamp of the second-level salt bucket update.
+To determine which UID2s need regeneration, compare the timestamps of when they were generated to the most recent timestamp of the salt bucket update.
 
-|Column Name|Data Type|Description|
-| :--- | :--- | :--- |
-| `BUCKET_ID` | TEXT | The ID of the second-level salt bucket. This ID parallels the `BUCKET_ID` returned by the identity map function. Use the `BUCKET_ID` as the key to do a join query between the function call results and results from this view call.  |
-| `LAST_SALT_UPDATE_UTC` | TIMESTAMP_NTZ | The last time the salt in the bucket was updated. This value is expressed in UTC. |
+| Column Name            | Data Type     | Description                                                                                                                                                                                                               |
+|:-----------------------|:--------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `BUCKET_ID`            | TEXT          | The ID of the  salt bucket. This ID parallels the `BUCKET_ID` returned by the identity map function. Use the `BUCKET_ID` as the key to do a join query between the function call results and results from this view call. |
+| `LAST_SALT_UPDATE_UTC` | TIMESTAMP_NTZ | The last time the salt in the bucket was updated. This value is expressed in UTC.                                                                                                                                         |
 
-The following example shows an input table and the query used to find the UID2s in the table that must be regenerated because the second-level salt was updated.
+The following example shows an input table and the query used to find the UID2s in the table that must be regenerated because the salt bucket was updated.
 
 #### Targeted Input Table