Gwh apidocs 3595 clarify token update info

docs/endpoints/post-token-generate.md

@@ -129,7 +129,7 @@ The response body includes the properties shown in the following table.
 | `advertising_token` | string | An encrypted advertising (UID2) token for the user. |
 | `refresh_token` | string | An encrypted token that can be exchanged with the UID2 Service for the latest set of identity tokens. |
 | `identity_expires` | number | The <a href="../ref-info/glossary-uid#gl-unix-time">Unix</a> timestamp (in milliseconds) that indicates when the advertising token expires. |
-| `refresh_from` | number | The Unix timestamp (in milliseconds) that indicates when the SDK for JavaScript (see [SDK for JavaScript Reference Guide](../sdks/sdk-ref-javascript.md)) will start refreshing the UID2 token.<br/>TIP: If you are not using the SDK, consider refreshing the UID2 token from this timestamp, too. |
+| `refresh_from` | number | The Unix timestamp (in milliseconds) that indicates the point at which you should consider refreshing the UID2 token. |
 | `refresh_expires` | number | The Unix timestamp (in milliseconds) that indicates when the refresh token expires. |
 | `refresh_response_key` | string | A key to be used in a [POST&nbsp;/token/refresh](post-token-refresh.md) request for response decryption. |
 

docs/guides/integration-ctv-guide.md

@@ -20,7 +20,9 @@ If you're a Connected TV (CTV) publisher, there are several ways that you can in
 At a high level, to integrate with UID2, you'll implement these three key steps: 
 
 1. Generate the UID2 token.
-1. Refresh the UID2 token as needed.
+1. Refresh or regenerate the UID2 token frequently to ensure the token stays current.
+
+   For details, see [Keeping the Token Current](../ref-info/ref-tokens.md#keeping-the-token-current) and [Recommended Token Refresh Frequency](../ref-info/ref-tokens.md#recommended-token-refresh-frequency).
 1. Pass the UID2 token into the bidstream.
 
 To determine how you'll implement these steps, choose from the [CTV Integration Options](#ctv-integration-options).

docs/guides/integration-options-publisher-all.md

@@ -11,4 +11,4 @@ import SnptPublisherImplementationResources from '../snippets/_snpt-publisher-im
 
 # Publisher Integration Resources
 
-<SnptPublisherImplementationResources/>
+<SnptPublisherImplementationResources />

docs/ref-info/ref-tokens.md

@@ -20,13 +20,12 @@ Here are some key points about UID2 tokens:
 
 - The UID2 token is a unique value: no two UID2 tokens are the same.
 - UID2 tokens are case sensitive.
+- Publishers send UID2 tokens in the bidstream.
 - The token value is an <a href="glossary-uid#gl-opaque">opaque</a> string: do not make any assumptions about the format or length of the string.
 - UID2 tokens representing different instances of user activity, on browsers, CTV, and electronic devices such as phones and tablets, can still be matched to the same raw UID2.
 - The token generation logic checks for user opt-out. If the user has opted out of UID2, no UID2 token is generated. For details, see [User Opt-Out](../getting-started/gs-opt-out.md).
 - The token has a limited life, but can be refreshed using the refresh token.
 - You can refresh many times, to get a new UID2 token and corresponding new refresh token, as long as the current UID2 token is always refreshed before the current refresh token expires.
-- If the token has expired, or as an alternative to refreshing an existing token, you can generate a new UID2 token from the original hashed or unhashed email address or phone number.
-- Publishers send UID2 tokens in the bidstream.
 - Refreshing a UID2 token does not invalidate/expire the original or previous UID2 token. You can still use the earlier token until it expires.
 
 For more information, see [How the UID2 Token Is Created](ref-how-uid-is-created.md).
@@ -48,6 +47,14 @@ Here are some key points about refresh tokens:
 - In most cases, you can refresh tokens on the client side, even if the token was generated on the server side. For details about refresh functionality for the various SDKs, see [SDK Functionality](../sdks/summary-sdks.md#sdk-functionality) (*Refresh UID2 Token* column).
 - When the UID2 <Link href="../ref-info/glossary-uid#gl-operator-service">Operator Service</Link> receives the refresh token with a request for a new UID2 token, it checks for user opt-out. If the user has opted out of UID2, no new UID2 token is generated. For details, see [User Opt-Out](../getting-started/gs-opt-out.md).
 
+### Keeping the Token Current
+
+It's very important to keep your UID2 tokens current (not expired). You get the advantages of UID2 only if the token is current.
+
+There are two options for keeping your UID2 tokens current:
+- Refresh frequently, using the [POST&nbsp;/token/refresh](../endpoints/post-token-refresh.md) endpoint or the token refresh feature of many UID2 SDKs. For details, see [Recommended Token Refresh Frequency](#recommended-token-refresh-frequency).
+- As an alternative to refreshing an existing token, generate a new token each time, using the [POST&nbsp;/token/generate](../endpoints/post-token-generate.md) endpoint or the token generate feature of many UID2 SDKs.
+
 ### Recommended Token Refresh Frequency
 
 Currently, the recommended refresh interval is hourly. An hourly interval helps ensure that the token doesn't get close to being expired, and is ready to be sent to the bidstream. In addition, since user opt-out is checked before a new token is generated, this helps ensure that user opt-out preferences are implemented promptly.

i18n/ja/docusaurus-plugin-content-docs/current/guides/integration-options-publisher-all.md

@@ -11,4 +11,4 @@ import SnptPublisherImplementationResources from '../snippets/_snpt-publisher-im
 
 # Publisher Integration Resources
 
-<SnptPublisherImplementationResources/>
+<SnptPublisherImplementationResources />