Skip to content

Commit 6fcfb9c

Browse files
committed
edit from KK
1 parent da428a2 commit 6fcfb9c

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/guides/integration-ctv-guide.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -120,10 +120,10 @@ The following points are best practices for CTV integrations:
120120

121121
- **Rotate tokens well in advance**
122122

123+
You can refresh the UID2 token at any time that's strategic. If the token was refreshed before its expiration date, both new and old tokens are usable for a while, until the old token expires. The TTL (time to live) timestamp is part of the response body returned by the UID2 Operator when the token is generated or refreshed.
124+
123125
Top CTV ad activity is tied to traffic spikes during ad breaks; generating or refreshing UID2 tokens during these times is not ideal. Plan to have tokens generated or refreshed before these busy times.
124126

125-
If the token was refreshed before its expiration date, both new and old tokens are usable for a while, until the old token expires. The TTL (time to live) timestamp is part of the response body returned by the UID2 Operator when the token is generated or refreshed.
126-
127127
- **Rotate tokens only when needed**
128128

129129
The UID2 token is tied to a user's HEM or phone, not to the viewing session or app session. As long as you have a valid UID2 token for the user, there is no need to generate new UID2 for each new viewing session or app session. For example, if the user leaves your app and then opens the app again, there is no need to generate a new UID2 if the existing one is still fresh.

0 commit comments

Comments
 (0)