# How to Find Direct Replies to Your Comment on a Known Snapchat Spotlight

Start with the known public Spotlight and check the visible conversation yourself. To find direct replies in an exported file, use the exact verified ID of your own comment. An ID is a value that identifies one record. Accept a reply only when its `parentCommentId` matches your comment’s `commentId` on that same Spotlight. Keep replies to those replies separate. If you cannot confirm the post or your comment ID, leave the lookup unresolved. This method cannot recover an unknown video from a broken notification.

A direct reply answers your exact comment. A deeper reply answers another reply below it. Both can matter when you read a conversation, but they are different results.

This guide shows how to make a checked table of direct replies. The collection tool supplies public records. You must check the post, confirm your comment, and decide which records belong in the table.

## 1. Confirm the Spotlight and your own comment

The reader’s question is practical: how can you find replies to a comment you left on Snapchat Spotlight? A supplied [public reader question, retrieved August 11, 2026; one question only](https://www.reddit.com/r/SnapchatHelp/comments/1b5rwle/how_to_see_who_replied_to_your_comment_snapchat) asks this directly. It does not establish how many users have the same problem.

If you can open the known Spotlight and find your comment, start there. Read the relevant public exchange. A manual check is useful when you want to understand a reply or decide whether to respond. You do not need an export just to read an exchange that you can already locate.

For a checked export, confirm these prerequisites before collection:

1. Save the public Spotlight URL, which is its web address.
2. Save the exact ID of your comment.
3. Keep evidence that connects that comment to the intended Spotlight.
4. Keep evidence that the comment belongs to your account.

Use an existing verified record if you have one. This guide does not establish a way to obtain an unknown comment ID from a notification. It also does not provide instructions for an undocumented Snapchat screen.

Similar wording is not enough to identify your comment. A display name alone is not enough either. If the saved evidence does not establish the identity, stop the target lookup. More rows cannot fix an unconfirmed target.

Public comment records also differ from owner-only records. The documented tool collects exposed public comments and replies. Its contract does not provide private messages or notifications. Do not treat a public export as a copy of your account’s private activity. [Public Actor contract, checked October 25, 2026; documented fields only](https://api.apify.com/v2/acts/chronometrica~snapchat-comments-scraper/builds/default).

## 2. Set up one small public collection if needed

An Actor is a hosted data collection program. The Chronometrica Snapchat Comments Scraper accepts known public Spotlight URLs. Its `includeReplies` setting requests public replies as separate paid rows. The setting defaults to `false`, so set it to `true` for this method. [Public input contract, checked October 25, 2026; no runtime test](https://api.apify.com/v2/acts/chronometrica~snapchat-comments-scraper/builds/default).

Use this supplied input shape:

```json
{
  "includeReplies": true,
  "startUrls": [
    "https://www.snapchat.com/@mrbeast/spotlight/W7_EDlXWTBiXAEEniNoMPwAAYbHZzZmtrYm1jAZhMOQmTAZhMOQfqAAAAAQ"
  ]
}
```

2. Set up one small public collection if needed

Replace the sample address with your known public Spotlight URL. The sample shows a valid input format. It does not identify your post or establish that your comment appears there. No collection was run for this guide.

Start with one post. The checked public input schema has no per-post row-cap input. A schema defines the accepted fields and their types. A row cap would set a maximum number of records for a post. Do not add an input field that the schema does not document.

Before a proposed run, inspect the available spending controls. Keep the exact input with any exported records. This preserves what you requested without implying that you received every available reply.

A Task is a saved input preset. The public [Snapchat Spotlight Comments and Replies Task, checked October 25, 2026; page presence only](https://apify.com/chronometrica/snapchat-comments-scraper/examples/snapchat-spotlight-comments-and-replies) exists. Its saved settings were not checked through an authenticated account, and it was not run. Check its inputs before use.

## 3. Save the fields needed to check each reply

A row is one record in the exported file. Save the original rows before you classify them. Keep enough information to connect each row to the requested post and its exact parent comment.

A parent comment is the specific comment that a reply responds to. Depth describes a comment’s level in a conversation. Depth gives context, but the parent ID determines whether a reply directly answers your target.

The current output contract documents the following fields. Their presence in the contract does not prove that a particular live collection will provide complete context. [Public output contract, checked October 25, 2026; documented output only](https://api.apify.com/v2/acts/chronometrica~snapchat-comments-scraper/builds/default).

| Field | What to preserve and check |
| --- | --- |
| `inputUrl` | The address supplied for collection. |
| `postUrl` | The returned public post address. |
| `snapId` | The returned Spotlight ID. Check it against the intended post. |
| `commentId` | The comment ID used to identify each distinct comment. |
| `parentCommentId` | The exact parent ID used for the direct-reply decision. |
| `depth` | The recorded conversation level. Keep it as context. |
| `text` | The comment text used for manual reading. |
| `authorId` | The author ID, when available. Preserve a missing value. |
| `publishedAt` | The comment publication time, when available. |
| `observedAt` | The time the record was observed. |
| `status` | The returned record status. Keep its original value. |
| `statusReason` | The returned status explanation, when available. |
| `replyCount` | A reply count. It does not supply the reply records. |
| `postCommentCount` | A post comment count, when available. It does not prove export completeness. |

Publication time and observation time answer different questions. The first concerns when the comment was posted. The second concerns when the record was seen. Do not replace a missing publication time with the observation time.

Keep missing values distinct from zero. A missing parent ID means that the parent relationship is not established. It does not mean that the comment has no parent. A missing count is unknown. A recorded zero is a numerical value.

You can add your own columns for the target ID, decision, reason, and source reference. Label them as your review fields. They are not native Actor output fields. A source reference should identify the original export row and preserve its public post link. Do not invent a direct comment URL.

## 4. Build one index of known comment IDs

An index is a lookup table. For this task, it connects each known `commentId` to its saved record. Keep repeated sightings in a separate observation log. An observation is one sighting of a record in an imported file.

Follow these steps:

1. Check that the returned post identity matches the intended Spotlight.
2. Record each distinct comment ID once in the index.
3. Keep each imported sighting in the observation log.
4. Connect repeated sightings to the existing index entry.
5. Preserve the saved, verified target comment and its identity evidence.
6. Hold any record whose required identity or parent relationship remains unproved.

Do not count repeated sightings as extra replies. If the same reply appears twice in a file, it remains one unique comment ID.

Your target comment might be absent from a later export that covers only part of the public conversation. That absence does not disprove its saved identity. Keep the earlier verified record and its evidence. The essential question is whether the target identity remains confirmed.

For a broader example of keeping requested posts, unique rows, and imported observations separate, see the [TikTok comment dataset guide](/en/articles/chronometrica-vs-clockworks-tiktok-comment-datasets/). Its product settings concern TikTok. Do not copy those settings into this Snapchat input.

## 5. Accept replies by exact parent identity

Apply the same decision to every candidate record. First check the Spotlight. Then check the parent ID. Finally, check that the accepted comment ID is unique in your result.

| Evidence in the checked record | Your review decision |
| --- | --- |
| Intended Spotlight confirmed and parent equals your verified comment ID | Accept as a direct reply. |
| Parent equals an accepted reply’s ID | Keep as deeper context. |
| Parent identifies a different branch | Keep separate from the target replies. |
| Parent is missing or unproved | Keep unresolved. |
| Spotlight identity does not match | Exclude from this target lookup. |
| Your target comment identity is unconfirmed | Hold the whole target lookup. |

These are reader review decisions. They are not documented values for the Actor’s `status` field.

Do not filter only for depth one. Your own comment can already be a nested reply. In that case, a direct reply to you can have a greater depth. The exact parent relationship still identifies it correctly.

Do not infer a parent from row order, similar wording, or a nearby display name. A spreadsheet can place unrelated records next to each other. That position does not establish a conversation link.

The [Facebook unanswered-question guide](/en/articles/facebook-unanswered-comment-questions/) shows why exact comment relationships matter when a question sits inside a thread. Its brand-answer review process serves a different task. Here, you only decide which observed records directly reply to your verified comment.

A structural match also does not establish meaning. Read the text and relevant public context before deciding how to respond. This method identifies the relationship between records. It does not automatically interpret or post replies.

## 6. Work through an original fictional example

Original fiction. This example uses invented IDs. It contains no actual Snapchat collection or private account data. It illustrates your review table, not verified runtime output.

Assume the known Spotlight is S1. Your confirmed comment is T2. Its parent is ROOT, and its depth is one. ROOT is an invented comment ID in this example.

All rows below concern S1. Their post identity has been checked within the fictional exercise.

| Comment ID | Parent ID | Depth | Review decision | Reason |
| --- | --- | --- | --- | --- |
| T2 | ROOT | 1 | Verified target | Saved evidence confirms your comment. |
| R1 | T2 | 2 | Direct reply | Its parent is the target T2. |
| R2 | T2 | 2 | Direct reply | Its parent is the target T2. |
| D1 | R1 | 3 | Deeper context | It replies to R1. |
| O1 | ROOT | 1 | Other branch | It shares T2’s parent but does not reply to T2. |
| M1 | Missing | Missing | Unresolved | Its parent relationship is unproved. |

The missing depth for M1 describes an incomplete review record in this fiction. It is not a claim that the current output schema accepts a null depth. That schema defines `depth` as an integer.

R1 and R2 pass because their parent is T2. Their depth of two does not prevent them from being direct replies. D1 belongs below R1, so it provides deeper context. O1 belongs to another branch.

A depth-one filter would miss both direct replies. It would also include O1, which does not answer T2. This is why parent identity controls acceptance.

Now suppose the imported file contains one extra copy of R1. Show both totals:

7 imported observations − 1 repeated observation = 6 unique comment IDs.

Classify the six unique IDs:

1 target + 2 direct replies + 1 deeper reply + 1 other-branch row + 1 unresolved row = 6 unique comment IDs.

The direct-reply result is two unique comment IDs: R1 and R2. It is not a count of two people. This exercise does not establish distinct author identities.

Deliver R1 and R2 with references to their source rows and the known Spotlight. Keep D1 as deeper context. Keep O1 separate. Keep M1 unresolved. If T2’s identity cannot be confirmed, hold the entire lookup.

## 7. Check the result and state its limits

Before you accept the table, complete these checks:

1. Confirm that the target ID still matches the saved identity evidence.
2. Confirm the intended Spotlight for every accepted reply.
3. Confirm that every accepted `parentCommentId` equals the target ID.
4. Confirm that each accepted `commentId` appears once in the result.
5. Confirm that each accepted reply has a source-row reference.
6. Import the same saved export again and confirm that it adds no new comment identity.
7. Keep deeper context, other branches, and unresolved rows separate.

The repeat import checks your handling of the same file. It is a proposed verification step, not a test performed for this guide. It does not show that a fresh live collection would return the same records.

If no unique reply passes the checks, report “zero accepted direct replies in this checked file.” Do not report that nobody replied. Public visibility does not guarantee a complete reply set.

If a required parent value is missing, keep that row unresolved. If the target itself is unconfirmed, report that the lookup is unresolved. These states differ from an observed count of zero.

Your delivery note should name the known Spotlight, verified target ID, observation times, imported observation count, and accepted unique direct-reply count. State the unresolved records and public-visibility limits. A reply-count field cannot replace this checked list of actual reply records.

## Choose the next action from the checked result

If you have accepted direct replies, open the known public conversation and read them in context. Use the saved table to locate the relevant records. Make any response decision yourself.

If required evidence is missing, keep the lookup unresolved. Do not substitute a similar comment or another Spotlight. A further collection is useful only when the post and target identity are already confirmed.

For a proposed public export, use the [Chronometrica Snapchat Comments Scraper](https://apify.com/chronometrica/snapchat-comments-scraper) with one known Spotlight and replies enabled. Check the returned identities and parent links before you expand. The documented fit is public record collection. The direct-reply table remains your checked result.

## Sources

- [Chronometrica Snapchat Comments Scraper default build 1.0.36 — checked October 25, 2026; static public input, output, and README evidence; no paid run or runtime verification](https://api.apify.com/v2/acts/chronometrica~snapchat-comments-scraper/builds/default)
- [Snapchat Spotlight Comments and Replies Task — checked October 25, 2026; public page presence only; saved settings not authenticated and Task not run](https://apify.com/chronometrica/snapchat-comments-scraper/examples/snapchat-spotlight-comments-and-replies)
- [Public question about replies to a Spotlight comment — retrieved August 11, 2026; one question record; no demand or volume estimate](https://www.reddit.com/r/SnapchatHelp/comments/1b5rwle/how_to_see_who_replied_to_your_comment_snapchat)