TL;DR: News signals now deliver daily instead of weekly — same schema, same fields, just faster.

What's changing

News signals have moved from a weekly to a daily delivery cadence. During the transition period, weekly and daily deliveries ran in parallel to ensure continuity. The weekly cadence is now fully retired.

Customers receive same-day news signals instead of waiting for the weekly batch, enabling faster response to breaking developments at target accounts.

What stays the same

• Same signal schema and fields
• Same format and structure
• Same filtering and query behavior
• No integration changes required

⚠️ Breaking — new fields added to data and data.evidence[] objects.

Product Review signals now include source URLs and richer evidence metadata for each individual review.

New Fields

Additional Enrichments

Example

{
  "data": {
    "source_page_url": "https://www.g2.com/products/scalepad-backup-radar/reviews",
    "product_name": "ScalePad Backup Radar",
    "switching_intent": {
      "detected": true,
      "signal_phrase": "looking for alternatives",
      "urgency": "medium"
    },
    "competitors_mentioned": ["Veeam", "Datto"],
    "evidence": [
      {
        "quote": "The reporting is limited and we have been exploring other options...",
        "reviewer_name": "IT Director",
        "review_url": "https://www.g2.com/products/scalepad-backup-radar/reviews#review-12710470",
        "star_rating": 2,
        "review_date": "2026-04-29"
      }
    ]
  }
}

Review excerpts in the evidence array are now longer and more detailed.

Effective: May 12, 2026 delivery onward (autobound-product-reviews-v2 bucket).

Action required: If your schema strictly validates the data or evidence[] objects, add handling for the new fields. All new fields are nullable.

⚠️ Breaking — new timestamp fields added, previously-null field now populated.

LinkedIn Comments (contact) signals now include actual posting timestamps. Previously, detected_at (when Autobound ingested the signal, typically 1-3 weeks after posting) was the only time reference.

New & Updated Fields

Example

{
  "data": {
    "comment_posted_at": "2026-04-27T00:03:51.002Z",
    "parent_post": {
      "posted_date": "2026-04-24T00:21:40.232Z"
    }
  }
}

All other fields unchanged. View full schema →

Effective: May 12, 2026 delivery onward (autobound-linkedin-comments-contact-v2 bucket).

Action required: If you filter on posted_date IS NULL or parse posted_date as a date-only string, update your logic. The field is now a full ISO 8601 datetime with milliseconds.

Upstream seniority categories on Hiring Velocity and Hiring Trends signals have been updated. First delivery containing these changes: April 7, 2026 (2026-04-07-00-00-00 folder).

Seniority Categories (Breaking)

Removed: non_manager, owner Added: junior, mid_senior

The full data.seniority[].category enum is now: c_level, director, founder, head, junior, manager, mid_senior, partner, president, vice_president.

A new value not_set may also appear for roles where seniority could not be determined.

Customers filtering or grouping by seniority category should update to the new values.

Title Normalization (Additive)

Two new fields have been added to Hiring Velocity and Hiring Trends signals:

These appear in the data object alongside existing sample_titles. Additive — no existing fields modified.

10 new subtypes have been added to news signals, expanding coverage of corporate events, financials, and risk signals. First delivery containing these subtypes: April 28, 2026 (2026-04-28-00-00-00 folder in autobound-news-v3).

These are additive — existing subtypes and schemas are unchanged. Total news subtypes: 40 (up from 30).

Customers ingesting news signals should update any subtype validation or switch logic to accept the new values. See the News schema page for the full subtype list.

Summary

Our S3 delivery pipeline experienced a 29-day sync outage from February 25 to March 26, 2026. During this period, signal data continued to be produced and delivered to GCS buckets normally, but was not propagated to S3 mirrors. This affected all S3 delivery customers.

All missing data has been fully backfilled as of April 16, 2026. We have also upgraded the sync architecture to prevent recurrence.

What happened

• Feb 25: The GCS→S3 sync scheduler was inadvertently removed during infrastructure maintenance
• Feb 25 – Mar 26: S3 mirrors stopped receiving updates. GCS (primary) was unaffected
• Mar 26: Sync pipeline was restored. New data began flowing to S3 again
• Apr 16: Full backfill of all 121 missing deliveries completed across 36 buckets (242 files)

Impacted buckets (36)

What we changed

1. Full mirror architecture: S3 now mirrors every folder in every signal bucket, not just the current day. Any historical gap is automatically caught and filled on the next sync run.
2. GCP-native scheduling: The sync trigger has been moved from an external scheduler to GCP Cloud Scheduler, eliminating the single point of failure that caused this outage.
3. Increased capacity: Cloud Run job memory upgraded from 8GB to 16GB to handle large signal files (e.g., website-intelligence at 13.7GB).
4. Backfill manifest: A backfill manifest (backfill-2026-04-16.json) has been uploaded to s3://autobound-s3-manifests/syncs/ documenting all recovered deliveries.

Action required

None. All missing data is now available in your S3 buckets in the same folder structure and file naming convention as regular deliveries. No changes to your ingestion pipeline are needed.

If you notice any remaining gaps, please reach out in your Slack Connect channel.

Product Reviews Schema Update — v2 Migration

We've updated the Product Reviews signal schema as part of the v2 migration. This update brings structural improvements and a significant increase in data coverage.

Schema Changes

New fields added:

Fields removed:

Record Count Increase

The v2 migration includes a +20% increase in record count due to expanded data source coverage and improved entity matching.

Migration Notes

• All v2 fields follow the standardized signal schema documented in Schema Reference
• The headline field replaces insight with a more concise, actionable format
• No breaking changes to existing integration patterns — new fields are additive (except for the two removed fields noted above)

We are expanding the news signal schema with structured second company data and additional enrichment fields.

This is an upcoming change, targeted for early June 2026. We will communicate the exact rollout date in advance. No action is needed until then.

Second company enrichment

News signals for event categories that involve two companies (M&A, partnerships, investments, integrations, litigation, talent movement) now include structured data for the second party. Previously, the second company was only available in the article text.

Two new fields in the data object identify the second company:

Which subtypes include second company data

Additional fields

The following fields are being added to the news signal schema. All fields are nullable and only present when relevant to the signal subtype.

Top-level fields

Company fields

Data fields

Location data object

Each entry in data.location_data contains:

Example

{
  "signal_id": "a1b2c3d4-e5f6-7890-abcd-ef1234567890",
  "signal_type": "news",
  "signal_subtype": "acquires",
  "signal_name": "Acquisition",
  "detected_at": "2026-05-15T14:30:00Z",
  "batch_id": "batch_20260515_001",
  "association": "direct",
  "company": {
    "name": "Acquirer Corp",
    "domain": "acquirercorp.com",
    "linkedin_url": "https://linkedin.com/company/acquirer-corp",
    "industries": ["Technology", "Enterprise Software"],
    "employee_count_low": 1001,
    "employee_count_high": 5000
  },
  "data": {
    "title": "Acquirer Corp Completes Acquisition of Target Inc",
    "summary": "Acquirer Corp has acquired Target Inc for $50M to expand its AI capabilities.",
    "body": "Enterprise software company Acquirer Corp announced today that it has completed the acquisition of Target Inc...",
    "url": "https://techcrunch.com/2026/05/15/acquirer-corp-acquires-target-inc",
    "author": "Sarah Johnson",
    "image_url": "https://techcrunch.com/images/acquirer-target-deal.jpg",
    "published_at": "2026-05-15T10:00:00Z",
    "effective_date": "2026-05-15",
    "amount": 50000000,
    "confidence": 0.95,
    "is_planned": false,
    "location": "San Francisco, California, 94105, United States, Northern America, Americas",
    "location_data": [
      {
        "city": "San Francisco",
        "state": "California",
        "zip_code": "94105",
        "country": "United States",
        "region": "Northern America",
        "continent": "Americas",
        "fuzzy_match": false
      }
    ],
    "related_company_name": "Target Inc",
    "related_company_domain": "targetinc.com"
  }
}

What stays the same

• Signal types without a second party (e.g., Funding, IPO, Launches, Headcount changes) will not include data.related_company_name or data.related_company_domain.
• Delivery schedule and file format are unchanged.
• All fields are nullable and will only be present when relevant to the specific signal subtype.

What to update

If you ingest news signals, add handling for the new data.related_company_name and data.related_company_domain fields on the 11 subtypes listed above, and ensure your schema accommodates the additional data fields documented in this changelog.