We've completed the first weekly delivery for the following signal categories, which were shifted from monthly.

Delivery Summary

Because of an issue with our Jan 29th batch, we decided to remove that delivery and regenerate those signals in this delivery.

Schema Updates

New field: data.filing_date

All SEC filing signals (10-K, 10-Q, 8-K, 6-K) now include a data.filing_date field representing the actual date the filing was submitted to the SEC. This is distinct from detected_at, which indicates when we processed the signal. Use filing_date to understand how fresh the underlying event is.

Example:

{
  "detected_at": "2026-02-03T00:00:00Z",
  "data": {
    "filing_date": "2026-01-30",
    "filing_year": 2025
  }
}

Subtype cleanup: digitalTransformation

The digitalTransformation subtype was producing false positives previously. This issue has been fixed in the current batch.

Date Ranges

Known Limitations

20-F: No new filings this period. There were no new 20-F filings between January 17 and February 3. The 20-F bucket was not updated.

Earnings Transcripts: Limited data. Only 42 signals from 3 companies in this delivery. Earnings transcript availability depends on the earnings calendar; Q4 2025 earnings season is ramping up and volume will increase in coming weeks.

We recently completed a delivery of our Website Intelligence signal that includes some information worth noting.

The latest release is available in gs://autobound-website-intelligence-v1/.

Refresher on Website Intelligence

Website Intelligence detects meaningful changes across company websites to surface buying signals and business priorities. We scan 6 million company websites on a recurring basis, analyzing:

• Text modifications — Changes to messaging, positioning, and product descriptions
• Page additions — New product pages, pricing tiers, compliance certifications, partnerships
• Page removals — Deprecated products and discontinued services

This Delivery

• 2,062,117 signals across 523,145 companies
• 38 standardized subtypes (consolidated from 1,700+ fragmented event types in previous iterations)
• High-value subtypes include: pricingChange, productLaunch, partnershipAnnouncement, executiveChange, geographicExpansion

See the full schema documentation for details.

Known Limitations

Relevance scoring needs tuning. The data.relevance field is generated by an AI model that isn't calibrated as tightly as we'd like. Currently, 71% of signals score between 0.5-0.7, with only 9% scoring above 0.9. We recommend filtering on relevance >= 0.7 for higher-precision use cases. Improved model calibration is planned for the next delivery.

Limited date range. This delivery covers website changes detected between January 2-8, 2026 only. While we've dramatically expanded company and signal coverage, the event date window is narrow. Future deliveries will analyze multiple historical timestamps to provide broader temporal coverage.

❗️

Update (February 2, 2026 — 2:00 PM PT): There is a known issue in the latest SEC filing
delivery. The excerpts field is returning raw XBRL tag identifiers instead of human-readable text from the filings. This has been confirmed in 10-K signals and likely extends to 10-Q, 20-F, 8-K, and 6-K as well. We are currently investigating the full scope — if there is a major quality issue across the batch, we will reprocess and re-upload the affected signals. This will be resolved no later than February 3, 2026.

Signal delivery has been upgraded from a monthly to a weekly cadence across nine existing signals, providing more timely data to downstream consumers. We've also launched a new Work Milestones signal covering job changes, promotions, and work anniversaries.

For full delivery schedules and next delivery dates, see the Delivery docs.

Delivery Cadence: Monthly → Weekly

The following signals have shifted from monthly to weekly delivery. The January 31 delivery was a one-time push to get data in by end of month for partners who required it. Starting February 3, 2026, these signals will begin their regular weekly cadence.

The output format, schema, and bucket structure remain unchanged - only the frequency has increased.

New Signal: Work Milestones

We launched a brand new signal: Work Milestones (gs://autobound-work-milestones/). This signal consolidates three career event subtypes under a single workMilestone signal type:

• jobChange — Contact moved to a different company
• promotion — Contact changed roles within the same company
• workAnniversary — Contact hit a tenure milestone at their current company

This signal is also on a weekly delivery cadence, starting February 3, 2026.

Access details:

• Bucket: gs://autobound-work-milestones/
• First run: gs://autobound-work-milestones/2026-01-30-16-07-00/
• Files:
  • output.jsonl (54.4 GB)
  • output.parquet (7.8 GB)
• Auth: Authenticate via gcloud auth login with access to the autobound-signal-delivery project

Why the first delivery is unusually large (~54 GB)

The first run produced a significantly larger file than future deliveries will. This is expected behavior.

The delivery window is based on detected_at (when our system identified the event), not event_date (when the career event actually occurred). Since this is the first run under a new process, every historically detected signal was included in a single backlog delivery — even if the underlying career events happened months or years ago.

Going forward, each weekly delivery will only include signals where detected_at falls within the past week, resulting in much smaller files.

We're shifting the following signals to weekly delivery to provide more timely data updates:

Signals Now on Weekly Cadence

What This Means

• Previous cadence: Varied (some monthly, some bi-weekly)
• New cadence: Weekly delivery every Friday
• Next delivery: January 31, 2026

No Action Required

Your existing bucket access and authentication remain unchanged. Simply pull from the same bucket URIs as before — you'll now see new timestamped folders appearing weekly.

Questions?

Contact us at [email protected] if you have any questions about this change.

We've migrated 15 signal categories to new GCS bucket URIs with corrected, standardized schemas. The new buckets use a -v1, -v2, or -v3 suffix.

What's Changing

Why We Made This Change

As part of a broader delivery infrastructure cleanup, we've migrated these signal categories to new buckets with corrected and standardized schemas that align with our Signal Schema documentation. This ensures consistent field naming, data types, and structure across all signal categories.

📘

One-Time Migration: This cleanup is a one-time effort to standardize our delivery infrastructure. We do not anticipate additional bucket URI changes going forward. Once you've updated to the new URIs, your integration should remain stable.

Deprecation Timeline

⚠️

Action Required: Update your data pipelines to use the new bucket URIs before February 2026.

Historical Data Note

Due to the new delivery mechanism, historical data in the new buckets may not extend the full 3-6 months initially. If you require historical backfill for specific signal categories, please contact us at [email protected].

Buckets Not Affected

The following buckets remain at their current URIs with no changes:

• gs://autobound-8k/ — SEC 8-K current reports
• gs://autobound-company-database/ — Company database
• gs://autobound-contact-database/ — Contact database
• gs://autobound-earnings-transcripts/ — Earnings call transcripts
• gs://autobound-financials/ — Financial data
• gs://autobound-hiring-trends/ — Hiring trends
• gs://autobound-intent/ — Intent signals
• gs://autobound-manifests/ — Data manifests
• gs://autobound-patents/ — Patent filings
• gs://autobound-seo-traffic/ — SEO & traffic signals
• gs://autobound-tech-used/ — Technology stack
• gs://autobound-twitter-company-posts/ — Twitter/X posts (company-level)
• gs://autobound-work-milestones/ — Work milestones
• gs://autobound-x-company/ — Twitter/X posts (company-level)
• gs://autobound-x-contact/ — Twitter/X posts (contact-level)
• gs://autobound-youtube-company/ — YouTube activity (company-level)
• gs://autobound-youtube-contact/ — YouTube activity (contact-level)

Migration Checklist

Use this checklist to ensure a smooth migration:

• Identify which of the 15 migrated signal types you currently use
• Update bucket URIs in your data pipeline configuration
• Test access to new buckets with your service account credentials
• Verify data schema compatibility with your downstream systems
• Update any monitoring or alerting that references old bucket names
• Complete migration before February 2026 deprecation date

Questions?

If you have questions about this migration or need assistance updating your pipelines, contact us at [email protected].

We've made the following updates to the Earnings Transcript signal schema to improve signal quality and provide richer context for sales outreach.

New Fields Added: Speaker Attribution

We've added speaker attribution to help you reference who said what in your outreach. Instead of just having quotes, you now know if it was the CEO, CFO, or another executive—making your outreach more credible and personalized.

Example usage:

"In your Q3 earnings call, your CEO Michael O'Sullivan mentioned you're 'aggressively going after' the performance gap with competitors. We help retailers close that gap—worth a quick chat?"

Format Changes

Migration Notes

• evidence_speakers: This is an additive, non-breaking change. The new field provides speaker attribution for quotes in the evidence array. The evidence field itself remains unchanged as array[string]. If you don't need speaker info, you can ignore this field.

• earnings_date: This is a breaking change if you're parsing dates with strict ISO 8601 parsers. Update your date parsing logic to handle the new YYYY-MM-DD HH:MM:SS format (no T separator, no timezone suffix).

Affected Data

• All historical earnings transcript data (2025-01 through 2026-01) has been regenerated with the new schema
• Data delivered prior to January 11, 2026 uses the old schema (no evidence_speakers, ISO 8601 dates)
• Action required: If you received earnings transcript data before January 11, 2026, contact your account manager to request a re-sync to get the updated schema

Questions?

Contact [email protected] if you have questions about this update or need assistance with migration.

We've expanded our content moderation scoring to include product review signals, ensuring brand-safe data for customer-facing use cases.

Affected Signals

• G2 Reviews
• Glassdoor Reviews
• Reddit, LinkedIn, Twitter/X, YouTube (already supported)

How to Use

Filter by moderation_score (0.0–1.0, higher = safer):

{
  "signal_type": "g2-review",
  "data": {
    "moderation_score": 0.95,
    "review_text": "Great product for enterprise teams...",
    ...
  }
}

Recommended Thresholds

Manifest files are now being generated for all signal data drops, enabling event-driven data pipelines.

How It Works

After each data push to your S3/GCS bucket, we generate a manifest file in the /manifest folder:

/manifest/2026-01-14_success.json

This allows you to:

• Trigger pipelines only when new data arrives
• Avoid polling or scheduled jobs
• Confirm successful delivery before processing
  

Schema

{
  "timestamp": "2026-01-14T00:00:00Z",
  "status": "success",
  "signals_delivered": ["10-k", "news", "hiring-velocity"],
  "record_counts": {
    "10-k": 1247,
    "news": 8934,
    "hiring-velocity": 3421
  }
}

We've increased the refresh frequency for all SEC filing signals from quarterly to monthly, ensuring you get financial insights closer to when they're filed.

Affected Signals

Why It Matters

SEC filings contain high-value signals — leadership changes, acquisitions, risk factors, strategic initiatives — but they go stale fast. With monthly refresh:

• Catch CFO/CEO changes within weeks, not months
• Surface M&A activity before your competitors
• React to risk disclosures while they're still relevant

What's Next

We're targeting weekly refresh for all SEC filings by February 2026. See our Roadmap for details.

→ View 10-K Schema
→ View Earnings Transcript Schema

We’ve added support for Commented on LinkedIn Post as both an insight and a signal.

• As an insight: Captures when a prospect comments on a LinkedIn post, including the full comment text, sentiment, engagement metrics, and tags. It also includes details about the parent post (content, author, tags, and engagement), giving sellers both the prospect’s perspective and the broader context of the discussion.

• As a signal: Can now be used to automatically trigger campaign enrollment when prospects engage meaningfully in LinkedIn conversations. This allows GTM teams to take action the moment a prospect expresses opinions, challenges, or interests tied to their value proposition.

By combining both sides of the interaction—the comment and the post itself—you can pinpoint not only what your prospect cares about but also the broader conversation they’re joining.

Learn more in the full docs: Commented on LinkedIn Post API