Threads

📘

Datastreamer selects from available providers automatically based on your Job configuration. You do not need to manage provider accounts or credentials to use this source.

Configuring a Job

When creating a Job for the Threads source, you define what content to collect. Common configuration options include:

• Keywords / query: terms to search for in post content
• Account targets: specific Threads accounts to monitor
• Date range: the time window to collect data from
• Document limit: maximum number of documents per Job run

Refer to the Job creation documentation for full configuration details: Creating Jobs

What is Collected

Each document returned from the Threads source represents a post or reply. Fields are mapped to the Datastreamer unified schema and include content text, author metadata, engagement metrics (likes, replies, reposts), and post date.

Platform-specific fields are available under the threads schema namespace. See the Schema Reference for field details.

Troubleshooting

Job fails or returns no data

• Check that the query or account target is valid and publicly accessible
• Verify the date range contains data
• Review Job logs for specific errors

Unexpectedly high document counts

• Add more specific filters to narrow the query
• Set a document limit on the Job
• Review the DVU pricing page

Provider switch noted in Job logs

• This is expected behavior. If a provider is unavailable, the Job is routed to an alternative automatically. No action is required.

Related

• Sources Overview
• Creating Jobs
• Data Volume Units
• Direct Integrations: use if you need a specific provider directly