diff --git a/docs/endpoints/post-identity-map.md b/docs/endpoints/post-identity-map.md index ca57b90f7..a55a44ba2 100644 --- a/docs/endpoints/post-identity-map.md +++ b/docs/endpoints/post-identity-map.md @@ -145,12 +145,12 @@ Response: { "u": "AdvIvSiaum0P5s3X/7X8h8sz+OhF2IG8DNbEnkWSbYM=", "p": "EObwtHBUqDNZR33LNSMdtt5cafsYFuGmuY4ZLenlue4=", - "r": 1735689600000 + "r": 1735689600 }, { "u": "IbW4n6LIvtDj/8fCESlU0QG9K/fH63UdcTkJpAG8fIQ=", "p": null, - "r": 1735862400000 + "r": 1735862400 }, { "e": "invalid identifier" }, { "e": "optout" } @@ -181,7 +181,7 @@ For successfully mapped DII, the mapped object includes the properties shown in |:---------|:-----------|:--------------------------------------------------------------------------------------------------------------------------------------| | `u` | string | The raw UID2 corresponding to the email or phone number provided in the request. | | `p` | string | One of the following: | -| `r` | number | The Unix timestamp (in milliseconds) that indicates when the raw UID2 might be refreshed. The raw UID2 is valid until this timestamp. | +| `r` | number | The Unix timestamp (in seconds) that indicates when the raw UID2 might be refreshed. The raw UID2 is valid until this timestamp. | :::note The raw UID2 does not change before the refresh timestamp. After the refresh timestamp, remapping the DII returns a new refresh timestamp, but the raw UID2 might or might not change. It is possible for the raw UID2 to remain unchanged for multiple refresh intervals. @@ -295,7 +295,7 @@ The following example shows an implementation of the v3 approach for checking re import time def is_refresh_needed(mapping): - now = int(time.time() * 1000) # Convert to milliseconds + now = int(time.time()) # Current time in seconds return now >= mapping['refresh_from'] # Check individual mappings for refresh needs diff --git a/docs/guides/integration-snowflake.md b/docs/guides/integration-snowflake.md index f7b42a5b8..6078093e9 100644 --- a/docs/guides/integration-snowflake.md +++ b/docs/guides/integration-snowflake.md @@ -179,7 +179,7 @@ A successful query returns the following information for the specified DII. |:---------------|:----------|:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `UID` | TEXT | The value is one of the following: | | `PREV_UID` | TEXT | The value is one of the following: | -| `REFRESH_FROM` | TIMESTAMP | The value is one of the following: | +| `REFRESH_FROM` | NUMBER | The value is one of the following: | | `UNMAPPED` | TEXT | The value is one of the following: | #### Values for the UNMAPPED Column @@ -401,7 +401,7 @@ To determine which UID2s need regeneration, compare the current time to the `REF | Column Name | Data Type | Description | |:------------------|:--------------|:--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | `UID` | TEXT | The UID2 associated with the DII. This is the current UID2 value returned by the identity mapping function. | -| `REFRESH_FROM` | TIMESTAMP | The timestamp (in epoch seconds) indicating when this UID2 should be refreshed. Compare this value to the current time to determine if regeneration is needed. | +| `REFRESH_FROM` | NUMBER | The timestamp (in epoch seconds) indicating when this UID2 should be refreshed. Compare this value to the current time to determine if regeneration is needed. | The following example shows an input table and the query used to find the UID2s in the table that must be regenerated because their refresh time has been reached.