Merge pull request #889 from IABTechLab/gwh-3191-uid2-ctv-faq-info

add best practices for CTV integrations

Author: genwhittTTD

docs/getting-started/gs-faqs.md

@@ -10,7 +10,15 @@ import ExampleTokenInBidstream from '../snippets/_example-token-in-bidstream.mdx
 
 # Frequently Asked Questions
 
-Frequently asked questions for UID2 are grouped into general categories by audience.
+Frequently asked questions for UID2 in this document are grouped by audience, into the following general categories:
+
+- [FAQs—General](#faqsgeneral)
+- [FAQs for Publishers](#faqs-for-publishers)
+- [FAQs for Advertisers and Data Providers](#faqs-for-advertisers-and-data-providers)
+- [FAQs for DSPs](#faqs-for-dsps)
+
+The following additional FAQ information for publishers is also available:
+- [FAQs for Mobile Integrations](../guides/integration-mobile-overview.md#faqs-for-mobile-integrations)
 
 ## FAQs—General
 

docs/guides/integration-ctv-guide.md

@@ -13,7 +13,7 @@ import PrivateOperatorOption from '../snippets/_private-operator-option.mdx';
 
 # CTV Integration Guide
 
-If you're a CTV publisher, there are several ways that you can integrate with UID2 to generate and refresh identity tokens to be passed into the RTB bidstream in the context of your CTV apps.
+If you're a Connected TV (CTV) publisher, there are several ways that you can integrate with UID2 to generate and refresh identity tokens to be passed into the RTB bidstream in the context of your CTV apps.
 
 ## Key Integration Steps
 At a high level, to integrate with UID2, you'll implement these three key steps: 
@@ -113,3 +113,23 @@ The following table shows supported operating systems, with links to applicable
 | :--- | :--- | :--- |
 | [Apple tvOS](https://developer.apple.com/tvos/) | [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for iOS Reference Guide](../sdks/sdk-ref-ios.md) |
 | [Android TV](https://www.android.com/tv/) | [UID2 Client-Server Integration Guide for Mobile](../guides/integration-mobile-client-server.md) | [SDK for Android Reference Guide](../sdks/sdk-ref-android.md) |
+
+## Best Practices
+
+The following points are best practices for CTV integrations:
+
+- **Rotate tokens in advance**
+
+- CTV ad activity is tied to traffic spikes during ad breaks; generating or refreshing UID2 tokens during these times is not ideal. We recommend that you generate or refresh tokens before these busy times.
+
+  If the token was refreshed before its expiration date, you can use either the new or the old token 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.
+
+- **Rotate tokens only when needed**
+
+  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.
+
+- **Use the same token for multiple ad slots within a pod**
+
+  As long as the UID2 token is valid throughout the pod duration, you can use it for any ad slot within the pod.
+
+Ideally, if you follow these guidelines, there is no need to generate a new UID2 token during an ad break.