Reddit Outreach Tracking: Threads Are Not Contacts

Use the outreach results tracker for Reddit for records your team supplies. The usability-study example below is a manual ledger, not a Reddit account import or a participant-matching system.

Start with an individual research invitation

Reddit discussions are organized around posts and comment trees, but those structures are not contact populations. One participant can write several answers, return in another thread, or discuss the problem without being invited to your project. For this guide, a fictional accessibility team, Clearpath Research, invites selected participants to discuss a prototype navigation study. Its outreach question concerns those actual individual invitations, not every comment beneath the research topic. Define first contact at the point where the team makes the specific invitation to the selected participant. A broadly visible study announcement does not establish that every reader or commenter became a contacted reference in the ledger.

Current Reddit help describes Chat requests and settings that control who can initiate them. The actual route available depends on the relevant account and recipient settings; a public comment exchange is a different context from an individual Chat conversation. Use the channel that actually supports the interaction rather than promising every participant the same private route. Choosing Reddit in this tracker does not open Chat, inspect a request, retrieve a comment, or identify a participant behind a username. It labels the supplied records. The research team must decide which evidence supports an invitation and a reply, keeping any necessary source context outside the short ledger fields.

Clearpath defines a positive reply as willingness to discuss study participation, neutral as an answer that leaves that willingness unresolved, and negative as a decline. A participant can make a valuable public criticism of the prototype without accepting the invitation. Likewise, a request for an alternative session format can be a genuine neutral response rather than no reply. Keep the distinction between contribution to the discussion and response to the invitation visible. This prevents a busy comment thread from being presented as a large recruited audience and lets the researcher respond to useful information without assigning every engaged participant a favorable commercial or research outcome.

Use contact aliases instead of thread identifiers

Give each selected contact a stable internal alias that your authorized team can resolve when needed. A post identifier describes a discussion, not the individual contact, and using it as a shared reference for several participants would collapse their different outcomes. Conversely, adding a new alias each time the same participant appears in another thread would multiply one contact into several records. The tracker cannot detect either semantic mistake. It enforces one occurrence of an exact reference across the project, not one verified human across Reddit. Retain the necessary source mapping separately and avoid including private research details or message text in the alias itself.

References are trimmed, normalized to NFC, and compared case-sensitively. StudyA and studya therefore remain distinct strings. Do not depend on a guessed native username normalization rule to combine them: this tool neither validates account identity nor resolves renamed, alternate, or shared accounts. Agree on the internal spelling before combining colleagues’ notes. Assign one primary campaign to each reference, such as Navigation study in this example. If the same participant is relevant to a later terminology study, preserve the agreed project ownership rather than duplicating the reference across campaigns. Campaign labels group case variations after normalization, but they do not establish who belongs to which study or which discussion deserves credit.

When a participant asks several questions, continue updating the existing row. A clarified invitation, a promised document handoff, and a later check can change Last touch and the known Touch count without creating additional contacted references. Do not derive touches from raw comment totals: several comments might belong to one exchange under your team’s definition, and other comments might concern the public topic rather than the invitation. Leave an uncertain touch total blank. The ledger preserves unique-contact denominators while allowing activity to accumulate, but the research team still needs a consistent definition of a touch if it intends to compare totals across coordinators or review windows.

Prepare the nine-participant navigation-study ledger

Choose Reddit in Platform, Fictional Clearpath Research as Account label, and Navigation study as the primary campaign for all nine references. Set Cohort start to 2026-09-07, Cohort end to 2026-09-15, and As of date to 2026-09-18. CR01 entered on September 7 and replied positively on September 8. CR02 entered on September 8 and replied positively on September 9. CR03 entered on September 9 and replied positively on September 10. These positive classifications mean willingness to discuss the study, not completed participation. Their individual first-contact dates determine cohort membership even if their public discussion activity began earlier or continued after the invitation.

CR04 entered on September 10 and replied neutrally on September 11, asking about an alternative session format. CR05 entered on September 11 and declined on September 12. CR06, CR07, and CR08 entered on September 12, 13, and 14 respectively, and each has a tracked None reply status. CR09 entered on September 15, but its reply status is Unknown because the coordinator has not reconciled that record. Leave Reply date blank for CR06 through CR09. The resulting distribution is three positive, one neutral, one negative, three with no reply yet, and one unknown. It is nine contacts, regardless of how many public comments their source discussions contained.

Record CR01, CR02, and CR03 as leads on September 8, 9, and 10 under the team’s stated study-eligibility rule. CR04 through CR08 have No lead status, while CR09 remains Unknown. CR01 has a booking recorded on September 12; CR02 through CR07 have No booking, and CR08 plus CR09 remain Unknown for that outcome. Lead rate is three divided by eight known statuses, or 37.5 percent, with 88.89 percent coverage. Booking rate is one divided by seven, or 14.29 percent, with 77.78 percent coverage. A session planned for September 24 does not replace the September 12 recording date or imply that attendance has already occurred.

Explain the three reply percentages with their denominators

Eight of the nine participants have known reply statuses, and five have replied. The reply rate is therefore five divided by eight, or 62.5 percent. Positive reply rate divides the three positive responses by those same eight known-status contacts, giving 37.5 percent. Positive share instead divides three by the five replied contacts, giving 60 percent. Reply coverage is eight divided by nine, or 88.89 percent. State these separately when briefing the researcher. Saying that most replies were positive can be accurate while fewer than half the known-status contacts expressed positive interest, and the unresolved record remains a tracking gap in either description.

CR04’s format question and CR05’s decline both count as replies. They differ in classification and in the useful next step, but neither should be erased from the answered population. CR06 through CR08 are known no-reply-yet observations, while CR09 is not. If reconciliation established None for CR09 at the same cutoff, coverage would reach 100 percent and reply rate would become five divided by nine, or 55.56 percent. That movement reflects a completed status check rather than a measured effect of changing the invitation. Keep correction notes outside the short record so a colleague can distinguish repaired tracking from newly observed answers in a later snapshot.

A positive reply is also not a completed recruitment funnel. Study eligibility can be recorded separately, and a booking does not establish attendance, task completion, or usable research data. The tracker does not require lead and booking outcomes to follow every prior recorded status in a rigid order. A lead without a reply or a booking without a lead can be retained with a review flag rather than forced into an invented sequence. This matters when research records arrive from different responsible owners. Reconcile the unusual combination, but do not fabricate missing stages merely to make the row look conventional or attribute every downstream result to one public discussion.

Keep the discussion window separate from contact maturation

At September 18, the first-contact ages range from eleven calendar days for CR01 to three days for CR09. A public thread may be older than either invitation, but its publication date does not supply the participant’s response window. Use the actual individual First contact date for cohort inclusion. Replies recorded after Cohort end can still belong to the entry cohort when they occur by As of date. The tool is reviewing people contacted in the chosen entry window, not counting only messages posted during those same days. This separation lets a researcher observe later responses without shifting the original invited population to chase favorable results.

The common cutoff still does not make every participant equally mature. A participant invited on September 15 has had fewer calendar days than one invited on September 7. Compare later research cohorts with similar opportunity to answer, and describe any differences in study criteria or invitation context. Campaign filter does not normalize those differences or transform a small ledger into a controlled experiment. A neighboring campaign with a higher reply rate may have older contacts or more complete status tracking. Review the counts, coverage, and age range before discussing what the pattern suggests, and avoid calling a campaign a winner merely because its displayed percentage is larger.

All activity dates must be on or before the declared cutoff, while a planned follow-up may be later. These are day-only calendar records, not message timestamps that the tool converts by timezone. Moving As of date to September 10 would reject the already entered September 12 booking and later replies; it cannot reconstruct the earlier state by temporarily hiding those fields. Save separately dated projects if the study needs a review history. Preserve the earlier snapshot as its own declared record, then update a later version with supported observations. The tracker does not retain an event log or infer when colleagues first knew a participant’s status.

Make the next research task more useful than a generic reminder

Complete the schedule as follows. CR01 is Closed after a September 12 last touch with three touches and no next date. CR02 is Open, last touched September 16 with two touches, and scheduled for September 18 to receive the promised preparation material. CR03 is Paused, last touched September 10 with one touch, with an old September 17 schedule. CR04 is Open, last touched September 14 with two touches, and scheduled for September 16 so the researcher can answer its format question. Those tasks serve different needs. The positive participant needs an agreed handoff, while the neutral participant needs information before it can decide.

CR05 is Open, last touched September 12 with one touch, and scheduled for September 18 for an internal roster-correction review after the decline. CR06 is Open, last touched September 12 with one touch, scheduled for September 19. CR07 is Open, last touched September 14 with two touches, scheduled for September 18. CR08 is Closed, last touched September 14 with one touch, without a next date. CR09 is Open with unknown Last touch and Touch count, scheduled for September 17 for reconciliation. On September 18 the queue is CR04, CR09, CR02, CR05, then CR07: five due contacts, comprising two overdue and three due today.

CR05 stays visible despite its negative reply because the row is explicitly Open and scheduled; the tracker flags it for human review without sending anything. A booked contact would likewise remain if it were Open and scheduled, even though CR01 happens to be Closed here. Paused CR03 is excluded because of state, not because of its positive reply or the age of its schedule. CR09’s Days since touch is unavailable rather than zero, and its task should begin with checking the record. A schedule earlier than Last touch receives another flag rather than silent repair. Keep uncontacted prospects outside the contacted due queue even when they have a planned research date.

Protect participant references in the research handoff

Use Summary only when a research lead needs aggregate recruitment status without a participant list. The copied result and report CSV, JSON, PDF, and attachments omit contact references and raw records, preserving scope counts, outcome coverage, age information, and aggregate scheduling instead. That is not a promise of anonymity. A real account label or unusually specific study name can still reveal confidential work, so review those labels before sharing. Avoid campaign wording that embeds participant characteristics or private discussion details. The ledger’s local calculation limits what the tool needs to do with supplied data; it does not control what recipients learn from a downloaded report or later forwarded copy.

Include contact references is suitable for an authorized coordinator who needs the selected participants and their next tasks. Its report detail includes only contacts matching the campaign selection and first-contact cohort, plus their eligible due and flag rows. A terminology-study participant filtered out, an older navigation contact outside the dates, and an uncontacted research shortlist do not appear merely because they remain saved in the project. The PDF can display a limited selection of contact and due rows with counts and a selection note. Complete chosen-scope detail remains in the attached report CSV and JSON, not in an invisible full-project attachment that bypasses the chosen privacy mode.

Keep Save project separate from that sharing decision. Its full editable JSON includes all saved records, including excluded aliases and uncontacted prospects, regardless of the report filter or Summary only setting. It is for authorized reopening with Open project, not a privacy-reduced report. Report downloads are not complete backups or CSV input templates. Save a deliberate project version because the browser tool has no autosaved history, and rerun Analyze outreach after changes to records or review settings. If a participant’s status is corrected after a report was sent, issue an updated review explicitly; the old attachment does not synchronize with the new ledger or remove information from the recipient’s copy.

Return to the evidence before the next study review

Clearpath’s next actions are concrete: resolve CR04’s format question, reconcile CR09, supply CR02’s preparation material, review CR05’s open roster task, and inspect whether CR07’s scheduled check remains appropriate. Those are not five interchangeable recruitment reminders. The researcher should return to the actual conversation or authorized source notes, carry out the approved work, and update the existing reference afterward. The tracker cannot notice a new public reply, decide that two usernames are the same participant, or tell whether another colleague has already handled the request. Keep the internal alias mapping accessible only where necessary, and do not turn the report into a repository of private study responses.

For a combined team file, use the exact CSV template provided by the tracker. Paste CSV needs Replace records before the proposed text becomes the dataset, whereas Open CSV validates a selected file and can replace the rows after the applicable confirmation. Neither route is a Reddit export importer, a CRM merge, or a contact-matching operation. Confirm the reference convention and primary campaign assignment before replacement, then inspect the retained review settings and analyze the saved rows. A perfectly formatted file can still mistake a thread identifier for a participant or a general comment for an invitation response. Human evidence checks remain essential after the parser accepts the data.

The wider account routine is a separate decision. SMTasker supports workflows across nine social platforms and provides Skye and MCP options for supported workspace operations with chosen permissions. That context can help organize approved manual tasks without promising this free ledger can import research contacts, match participants, synchronize Reddit Chat, or send messages. Keep study evidence and recruitment definitions in the systems your team actually uses. The next snapshot should explain completed promises, resolved unknowns, and remaining observation time. A campaign label is an organizing choice, not proof that a thread caused participation or that more reminders would produce additional usable research.

Questions about Reddit Outreach Tracking

Continue with another outreach guide

Review your supplied contact records in the Social Media Outreach Results Tracker, or choose another guide below. Find more practical resources in all free tools.