Twitter Post Company Signal Schema

Source: Jira AN-8784

Last validated: 2026-01-08

signal_type: twitter-post-company bucket: TBD # Not yet in production association: company description: Company Twitter/X posts with engagement metrics and LLM-generated tags refresh: monthly coverage: 2,000,000 companies

Single subtype for company posts

subtypes:

• postedOnTwitter

No top-level signal_category

categories: []

All fields per Jira spec

fields:

Core fields

• path: signal_id type: string (UUID v4) description: Unique identifier for this signal
• path: batch_id type: string (UUID v4) description: Batch identifier for processing
• path: signal_type type: string description: Always "twitter-post-company"
• path: signal_subtype type: string description: Always "postedOnTwitter"
• path: detected_at type: string (ISO 8601) description: Timestamp when signal was detected
• path: association type: string description: Always "company"

Company object (from CSV)

• path: company.name type: string description: Company name
• path: company.domain type: string description: Company website domain
• path: company.linkedin_url type: string description: LinkedIn company URL

Data object - tweet content

• path: data.tweet_text type: string description: Full text of the tweet
• path: data.tags type: string description: LLM-generated topic tags (e.g., "Technology")
• path: data.tweet_url type: string description: URL to the tweet
• path: data.post_date type: string (ISO 8601) description: When the tweet was posted

Engagement metrics

• path: data.engagement_metrics.likes type: integer description: Number of likes
• path: data.engagement_metrics.retweets type: integer description: Number of retweets
• path: data.engagement_metrics.views type: integer description: Number of views

User metadata (company's Twitter account)

• path: data.user_metadata.user_handle type: string description: Twitter handle (e.g., "autobound_ai")
• path: data.user_metadata.user_bio type: string description: Twitter bio
• path: data.user_metadata.user_location type: string description: Listed location
• path: data.user_metadata.followers type: integer description: Follower count
• path: data.user_metadata.following type: integer (nullable) description: Following count
• path: data.user_metadata.verified type: boolean description: Verified status

Schema notes:

- Similar structure to twitter-post-contact but association is "company"

- Tags are LLM-generated from tweet content

- Uses same RapidAPI and tagging system as LinkedIn posts

- Company Twitter handles sourced from 5x5 dataset + SERP enrichment