Follow the topics attached to your Spotlight clips
Snapchat Spotlight Topic Tracking for Supplied Clips
Track Spotlight topics alongside the clips that carried them. A topic-set review can organize your supplied observations, but it cannot identify which caption term delivered a view or predict the next clip.
Choose Snapchat Spotlight in the Spotlight topic tracking analyzer. This guide concerns public Spotlight caption and topic records, not Topic Chats, private messages, or Story performance.
Define a Spotlight record without mixing Snapchat surfaces
A ceramics creator may publish a quick forming demonstration to Spotlight, share a studio update elsewhere, and answer questions in a conversation on the same day. Those activities do not form one interchangeable measurement unit. For this review, each row represents one Spotlight post and the topic tokens recorded from its caption or topic setup. Snapchat’s own submission guidance includes adding topics to a Spotlight submission, but this analyzer does not submit content, inspect your account, or decide which label a viewer encountered. Start with a specific inventory of Spotlight posts so unrelated content surfaces cannot silently enter the comparison.
Keep the original caption in your own publishing record and enter only the relevant topic-token list here. For example, #ClayProcess #Handbuilding records two complete members. The analyzer does not extract those members from a sentence about shaping a bowl, interpret spoken words, inspect on-screen text, or infer a topic from the footage. An editorial phrase such as Process clip belongs in Format, not in a tag list as two accidental tokens. Content topic is another local organizing label, such as Technique or Studio visit, which you can later use to narrow the observations without changing the recorded caption topics.
This scope excludes Topic Chats and Stories, including public Stories, even when an interface presents their statistics nearby. A Story viewer count cannot fill a Spotlight view field simply because both numbers concern the same account. A chat message count is not a clip engagement count either. Establish the surface before copying a number and retain its native meaning in your collection log. The benefit is practical: when the review later shows a difference, the team can investigate a difference among Spotlight posts instead of discovering that a mixture of surfaces made the comparison incoherent from the beginning.
Collect clip observations at a repeatable age
Imagine Mintline Ceramics maintaining a Spotlight log for its small handbuilding studio. The team chooses one account, Organic traffic, Views per post, and a declared age of 72 hours after each publication. A calendar reminder outside the analyzer prompts the collection. The shared age is a rule the team follows, not an adjustment the software applies. Entering 72 does not age a new clip, strip later views from an older clip, or verify that screenshots were taken on time. If a snapshot was missed, mark the problem in the working log and avoid presenting a different-age observation as an equivalent one.
Use one ID per Spotlight post and keep that ID stable when correcting a count or its topic list. A second snapshot of the same clip should not become a second post under a new identifier. That would overrepresent one creative in the median and inflate topic usage. Record enough editorial context to distinguish a close-up process demonstration from a tour showing the whole studio. Both may be videos, but their viewing motivations differ. A short, consistent Format label gives you a way to isolate that difference later without pretending that the analyzer watched the clips and classified their content for you.
Snapchat distinguishes Spotlight views from unique viewers and provides additional clip insights. Use the specific measure you actually recorded rather than treating those labels as synonyms. This tool’s count objectives do not include watch-time seconds or average view rate, so do not place those values in Views or Engagements just to fit the form. If a count is unavailable, leave it empty. If you choose a generic rate objective, only supply a denominator whose meaning you can defend consistently across the selected posts. The platform selector describes the context; it neither unlocks a native metric nor converts a differently defined counter.
Preserve exact topic membership through data preparation
For Spotlight, enter a list of complete topic tokens separated by whitespace, commas, or semicolons. A leading hash mark is optional for local matching, and compatible Unicode forms and capitalization are normalized into comparison keys. Thus #Handbuilding #ClayProcess and #clayprocess #HANDBUILDING form the same set even though their order and case differ. Repeating #ClayProcess inside one source list counts once for that post. These conventions avoid accidental fragmentation of an inventory. They do not certify a topic’s native availability, check publication eligibility, or make a statement about what Snapchat’s recommendation system does with the topic.
Actual membership changes stay visible. #ClayProcess #PotteryTools is not the same set as #ClayProcess #Handbuilding, and adding #StudioTour to the latter creates a third set. A blank list is a deliberate no-topic-token observation and appears under No hashtags in the shared results vocabulary. Do not fill that blank with an invented #NoTopic marker. That marker would be analyzed as a real member and could create misleading frequency and overlap entries. Verify the source before treating an unknown topic list as an intentional blank; otherwise missing editorial records would be mislabeled as a clean control condition.
The parser refuses punctuation-containing fragments rather than silently repairing them. A phrase copied as Clay process is two list tokens in this context, not one native multiword topic, and a sentence with punctuation can make the whole row invalid. Prepare intentional hashtag-style tokens such as #ClayProcess instead. Threads uses a different single-label convention, so do not transfer its space-preserving behavior into this Spotlight field. The project retains the entered spelling and order while grouping uses canonical keys. That separation lets you inspect original records later without losing the stable set identity needed to compare repeated combinations.
Recreate the fictional ceramics topic-set review
Enter four Technique posts in Process clip format with #ClayProcess #Handbuilding and views of 1,200, 1,600, 2,000, and 2,400. Add three Technique / Process clip observations with #ClayProcess #PotteryTools and views of 900, 1,100, and an empty value. Record two Technique / Process clip posts without topic tokens and views of 1,000 and 1,400. Finish with three Studio visit posts in Tour clip format using #ClayProcess #Handbuilding #StudioTour and views of 5,000, 6,500, and 8,000. All other count fields stay empty for this exercise. These are invented demonstration observations, not typical results for ceramics creators.
With all rows selected, the review contains twelve posts, eleven eligible views, one missing value, four exact sets, and four unique tokens. Two posts are untagged. The baseline median is 1,600 and the mean is approximately 2,827.27. The tour set has a median of 6,500 from three known observations. The handbuilding pair has a median and mean of 1,800 from four. No hashtags has a median of 1,200 from two. The tools pair has a median of 1,000 from two eligible posts and retains one missing view value alongside them. The larger tour numbers pull the overall mean above the median.
Using three as the minimum eligible-post threshold, the tour set and handbuilding pair meet the review threshold. The tools pair does not meet it merely because three posts were entered; only two have eligible views. The no-topic-token group also remains below the threshold. Their median indices against the 1,600 baseline are 406.25 for the tour set, 112.5 for the handbuilding pair, 75 for No hashtags, and 62.5 for the tools pair. Index 406.25 is a descriptive multiple of this baseline, not a promised growth rate. It does not show that the extra #StudioTour token generated the tour clips’ larger counts.
Keep the clip context attached
Review your Spotlight topic sets
Compare supplied clip observations at one declared age, then filter process clips separately from studio visits before planning the next batch.
Separate the creative difference from the topic-set difference
The tour set looks strongest in the broad table, but its clips show a different experience. A studio tour may reveal equipment, shelves, and a finished collection, while a process clip focuses on forming a rim. The set change is accompanied by a change in subject and format. Selecting Technique and Process clip removes that obvious mismatch from the immediate review. The narrower sample contains nine posts, eight eligible values, and one missing value. Its median becomes 1,300 and its mean 1,450. The excluded tours are still stored; filtering changes the analytical population rather than rewriting the observation file.
The handbuilding pair’s median remains 1,800, the no-topic-token median stays 1,200, and the tools pair stays 1,000. Against the new baseline, their indices are approximately 138.46, 92.31, and 76.92. Nothing improved when the filters changed. Those new values express the same group medians relative to a different selected sample. Include the filter names when discussing an index or saving a report for a colleague. Otherwise, someone comparing 112.5 with 138.46 could mistakenly describe an improvement over time when the only difference was excluding a set of higher-view tour observations.
Even the filtered sample contains creative variation that the labels do not capture. A tool demonstration might open with a reveal, include a different sound, last longer, or show a more visually striking result than a forming demonstration. Keep those differences in an external creative log instead of assuming a shared Format makes clips equivalent. The analyzer does not evaluate footage, sound choice, watch-through behavior, or recommendation eligibility. A useful follow-up specifies which creative features will stay comparable and which topic membership changes. The topic and hashtag testing plan helps define the collection question before the next batch exists.
Use frequency, co-use, and overlap for different decisions
Topic frequency helps audit the studio’s own usage. In the complete sample, #ClayProcess appears on ten of twelve posts, about 83.33 percent, spread across three exact sets. It has nine eligible and one missing view observation. #Handbuilding appears on seven posts, about 58.33 percent, across two sets. #PotteryTools and #StudioTour each appear on three posts, or 25 percent; the tools token includes the missing observation. These shares are based on selected posts, including those without an eligible objective. They are not estimates of Snapchat-wide topic popularity, audience demand, topic-page traffic, or the share of views earned through those labels.
Co-use records how often two topic tokens were supplied together. The clay-process and handbuilding pair appears on seven posts. The clay-process/tools, clay-process/tour, and handbuilding/tour pairs each appear on three. A clip with three members contributes to three pairs, so the pair totals can exceed the number of posts when added together. This is a description of shared membership, not duplicated delivery or overlapping people. It can reveal that the studio nearly always uses a term alongside another term, which makes their separate associations hard to inspect. The interface bounds the visible pair list at twenty while the report retains all calculated pairs.
Overlap compares distinct nonempty sets rather than posts. The handbuilding pair shares two of three union members with the tour set, producing approximately 66.67 percent overlap. It shares one of three with the tools pair, producing about 33.33 percent. The tour and tools sets share one of four, giving 25 percent. All three possible nonempty set pairs are positive here. Larger projects show only the top ten positive overlaps after all pairs are evaluated. The set overlap guide explains why this token calculation cannot measure similarity of footage, viewer interests, or the audience reached by two clips.
Keep missing observations and full exports visible in the workflow
The missing tools-clip view value should stay missing until a defensible measurement is available. Replacing it with zero would lower the group’s statistics and create a false claim about observed performance. Deleting the whole post would erase evidence that the topics were used. Keeping the row preserves usage while the eligibility count states what the performance summary can actually use. If every selected post lacks the objective, analysis cannot produce a baseline and asks for an eligible observation. If a group has no known objective values but other groups do, that unknown group remains visible with unavailable statistics rather than being treated as a zero-performing set.
Use the nine-column observation template when importing a prepared CSV, and keep each topic-token list in its tags cell. The headers are post_id, topic, format, tags, views, reach, impressions, engagements, and clicks. Empty count cells represent unknowns; numeric cells must be plain whole numbers. A report CSV has a different purpose and is not the observation template. Save the project JSON to reopen the editable dataset and settings. Before saving or analyzing, apply or clear any editor entry or pasted-CSV draft so the file and review reflect committed rows rather than a mixture of saved observations and unfinished material.
Exports require a separate privacy check. Copy results, report CSV, and the PDF review include all raw project rows, even the tour clips outside a Technique filter, together with account labels and next-test notes. The PDF’s bounded visible summary does not remove its complete project JSON and report CSV attachments. An internal release date, private production ID, or campaign note can therefore travel with a short-looking report. Remove unnecessary details at the source before sharing. The analyzer processes supplied data locally without a Snapchat login, but exported files remain your responsibility and do not receive an automatic summary-only anonymization mode.
Make the next batch a clear creative learning decision
Mintline can finish with a modest, actionable question: among comparable Technique / Process clip posts observed at 72 hours, how do the handbuilding pair, tools pair, and deliberate no-topic-token observations compare in the next planned batch? Keep the opening style, broad duration range, and collection practice documented so later differences can be examined. Do not call this a controlled experiment just because one visible field changed. Organic delivery, creative appeal, timing, and the people who encounter each clip can differ. The next review improves the studio’s descriptive record; it does not isolate the causal contribution of a topic token.
Retain useful creative judgments outside the numeric ranking. A lower-view tools demonstration might answer a recurring customer question or support a planned workshop better than a widely viewed tour. If the business goal changes, choose an appropriate consistently measured objective and rebuild the analysis rather than forcing the views table to answer a different question. A high index, repeated co-use, or a three-post threshold is not evidence of topic-attributed reach. Equally, no positive overlap between two sets would not prove that their audiences differ. These limitations help the team use the numbers precisely while preserving room for informed editorial decisions.
For work around the account, explore SMTasker for its supported Snapchat Add Friends workflow, sources, limits, and scheduling controls. Skye can assist with checking supported workspace settings, and an external assistant can use available MCP permissions for supported actions. Those capabilities are separate from Spotlight publishing, native clip analytics, or importing this topic review; this guide does not promise any of those connections. Keep Spotlight collection in the studio’s own measurement routine and use operational tools for the tasks they actually support. Return to the free tools directory when another part of the creative workflow needs a separate utility.
Questions about Spotlight Topic Tracking
Can I combine Spotlight clips with Stories or Topic Chats here?
No. This context is for Spotlight caption and topic records. Story metrics and chat activity describe different surfaces and should not be entered as equivalent Spotlight observations.
Does the analyzer extract topics from my full Spotlight caption?
No. Supply an intentional list of complete topic tokens such as #ClayProcess #Handbuilding. It does not inspect the caption, footage, sound, or account to discover topics automatically.
Why is the tour set not the obvious choice for every process clip?
Its median of 6,500 comes from three fictional Studio visit / Tour clip observations. Creative and context differ from Technique / Process clip, so the extra topic cannot be credited with the views. Filter comparable clips and plan a narrower follow-up.
Continue with another tag-set guide
Review your supplied post observations in the Hashtag Set Performance Analyzer, or choose another guide below. Find more practical resources in all free tools.
Use the right workflow for the account task
Organize supported Snapchat account work
Explore SMTasker Add Friends settings and Skye-assisted checks while keeping Spotlight topic measurement in your own collection process.