Help users discover relevant community conversations through configured topics, using the SDK or the Discovery Widget.
Topic-based content discovery helps brands and community teams bring relevant conversations to the pages people already visit. Instead of relying on users to search for a community, surface posts about a topic on your homepage, category pages, or other browsing surfaces. Post previews help people understand what your community offers and decide which conversations to explore.Your team configures a topic in the social.plus Console. The SDK uses its topic ID to fetch an ordered selection of community posts, called a pool. Build your own presentation with these posts, or use the UIKit’s Discovery Widget for a ready-made carousel.
The SDK supports topic-based content discovery on TypeScript, iOS, and Android. Flutter and React Native are not supported.
Topic relevance: how closely a post matches the configured topic. This is the main signal.
Engagement: activity on a post, such as reactions and comments, helps identify relevant conversations people are participating in.
Freshness: newer posts help keep the selection timely.
Selection is based on the configured topic rather than a reader’s personal interests or engagement history. Topic configuration and eligibility rules determine which posts can appear. Viewer-specific restrictions, such as blocked authors, can further affect the returned selection.The SDK returns posts in recommendation order. Preserve that order when presenting the recommended selection.
Configure a topic in the social.plus Console and obtain its topic ID. Initialize the SDK and establish a user session or a visitor session before fetching posts.Topic configuration is managed in the Console. This page covers reading its recommendations and reporting interactions from your app.
getPool returns the topic and its ordered posts in a single request. It is not a live collection and does not support pagination. Call it again when your app needs a new selection.
import { CuratedContentRepository } from '@amityco/ts-sdk';const pool = await CuratedContentRepository.getPool('your-topic-id', 10);const topicName = pool.topic.topicName;const posts = pool.posts;
let repository = AmityCuratedContentRepository()let pool = try await repository.getPool(topicId: "your-topic-id", limit: 10)let topicName = pool.topic.topicNamelet posts = pool.posts
val repository = AmityCoreClient.newCuratedContentRepository()repository.getPool(topicId = "your-topic-id", limit = 10) .subscribeOn(Schedulers.io()) .observeOn(AndroidSchedulers.mainThread()) .subscribe({ pool -> val topicName = pool.topic.topicName val posts = pool.posts }, { error -> // Handle the failed request in your app. })
The returned posts are standard post objects that you can render in your own UI. Results may contain fewer posts than requested, including an empty list. An empty list is a successful response; omit the discovery surface when there is no content to display.
When building your own discovery surface, use the topic’s analytics handle to measure what readers see and open. Report views when the surface or card becomes visible, rather than when an off-screen element is mounted.
val topic = pool.topictopic.analytics().markAsViewed()topic.analytics().markPostAsViewed(post.getPostId())topic.analytics().markPostClick(post.getPostId())
Report the surface impression and each post impression once per page load. Report a click when the reader selects a card, and let navigation proceed without waiting for analytics.The Discovery Widget reports these interactions automatically, so you do not need to report them again for that component.
