Viewer actions
Viewer actions cover activity that persists across sessions or devices, and in-player capabilities such as engagement elements, sharing, and follows. For the viewer ID your app supplies, see Viewer ID under Requirements and policies.
For free text search as a content query path, see Free text search under Data sources.
Who owns what
Use this table to see who decides, implements, or configures each viewer-action topic.
| Topic | App (product / backend) | Developer | Content manager | WSC Sports |
|---|---|---|---|---|
| Viewer ID (Requirements) | Choose the account key strategy and when to send an ID (logged-in only) | Meet the Viewer ID specifications; pass externalUserId on init and on login, logout, and account switch | Not involved | Does not create or assign viewer IDs |
| Privacy and tracking | Set privacy policy and tracking mode for the app | Apply tracking modes in the SDK | Not involved | Advises on product behavior; legal compliance stays with you |
| Cross-device activity sync | Decide whether sync is required for your product | Pass a stable viewer ID on every platform that should sync | Not involved | Enables sync on the backend when you request it |
| Engagements (CTAs, polls, quizzes) | Own deeplink destinations and web link targets used by CTAs | Style and handle engagement callbacks in the player where needed | Create and place CTAs and interactions in CMS / Story Manager | May help with content tooling setup |
| Share links | Choose landing-page hosting and app install paths | Implement universal / app link handling | Not required for share to work once hosting and links are set | Can host the landing page if you use the WSC Sports option |
| Follow button | Store follow lists as the source of truth | Wire follow UI, callbacks, and setFollowedEntities | Tag entities on uploaded Moments so the button has a subject | Maps follow images and enables follow for automated content |
Updated 24 days ago
Did this page help you?