Share links
Viewers can share links to content (Stories, Moments, and Videos) using the device's native share menu (Messages, social apps, and similar). Sharing between viewers drives app engagement, and each link deep-links recipients into the app when they open it. If the app isn't installed on the recipient's device, they are prompted to download it.
What sharing is
Sharing means sending a URL and the text your integration defines through the device share menu, targeting a specific content item. The link and accompanying text are generated by the SDK using your definitions.
Opening a shared link
When a recipient taps the link, they are taken directly to the specific content within your app. If the app isn't installed on their device, a landing page is displayed inviting them to install your app, after which they are deep-linked to the shared content.
The exact content that displays depends on the content type as follows:
- Stories: The Story on the specific card that was shared.
- Moments: The Moment that was shared.
- Videos: The Video that was shared.
After the recipient views the content, they can continue to browse the app as usual.
When the link might not show content
- If the status is draft or the content has been deleted, no content is displayed. In this case, deep linking opens the app and terminates without displaying a specific content item.
- Deep links aren't dependent on labels or label schedules. This means, for example, that in-game content can be shared, and the link can be opened after the game, provided the content hasn't been deleted and the status is active.
Implementation considerations and prerequisites
Prerequisites checklist
- Choose a hosting option for the landing page and link (see Hosting the landing page and link).
- Implement universal link handling in your app.
- Android: Methods and parameters (universal link handling).
- iOS: Methods and parameters (universal link handling).
- Complete the Information required for linking section.
Hosting the landing page and link
The landing page and domain in the link depend on the hosting option you select, as set out in the table. Consider and prepare for the option that suits you.
| Topic | Hosted by WSC Sports | Hosted by you |
|---|---|---|
| Share URL | WSC Sports provides the domain name. Typical format: To implement this option: | Use your domain and brand. |
| Landing page | WSC Sports hosts and serves a landing page branded for you. See Figma. | You own and host the landing page and the app-not-installed flow. See Figma. |
| Sharing link | WSC Sports generates the sharing link. | You generate the link and populate it with the content ID path WSC Sports provides. |
Information required for linking
| Item | Response |
|---|---|
| App name | |
| Text for links. You can specify different text for each content type. You can specify placeholders from the content item title, subtitle, and metadata. | |
| App link to Google Play Store | |
| App link to Apple App Store | |
| Logo file link | |
| Story thumbnail to use. Specify 1:1 or 2:3 | |
| Font color in hex code | |
| Icon (.ico) file link | |
| Desktop background file - link to file | |
| Mobile background file - link to file | |
| CTA text | |
| CTA font color hex code | |
| CTA background hex code | |
| Main title | |
| Subtitle |
Related topics
Updated 25 days ago