Onboarding Guide

Welcome to Autobound Signal Data! This guide covers technical setup and working with our team.

• Roadmap — Upcoming features & improvements
• Changelog — Release notes & updates

Onboarding Timeline

Onboarding Checklist

Team Setup

Technical Setup

Go-Live

Who Should Be Involved

Kickoff attendees: Data Engineer + Product Manager recommended.

Working with Autobound

Slack Connect

Your shared channel is for:

• Quick questions (response within 4 hours)
• Data quality issues
• Schema clarifications

Success Sessions

30-minute check-ins, 2-3x per month for the first 1-2 months:

• Review pipeline progress
• Troubleshoot integration issues
• Optimize match rates
• Share best practices

After go-live, we move to monthly or as-needed.

Core Milestones

Week 1: Access & Kickoff

• Kickoff call completed
• Credentials received and tested
• Slack Connect active

Week 2: First Data Pull

• Downloaded data from at least one bucket
• Validated schema fields
• Initial pipeline created

Week 4: Review & Optimize

• Match rate calculated
• Signal taxonomy defined for your use case
• 30-day review scheduled

Technical Setup Details

Authentication

# Activate service account
gcloud auth activate-service-account --key-file=~/credentials/autobound-key.json

# Verify access by downloading from one of your licensed buckets (see Delivery page for exact URIs)
gcloud storage cp gs://autobound-10k-v1/2026-01-15T00-00-00Z/output.parquet ./test-download.parquet

💡

Note: Bucket listing is not supported. Use the exact bucket URIs from the Delivery page to verify access.

Bucket Structure

Each signal type has its own dedicated bucket with timestamped folders:

gs://autobound-{signal-type}/
├── 2026-01-05T12-00-00Z/    ← Most recent
│   ├── output.jsonl
│   └── output.parquet

Always pull from the most recent folder. See Delivery docs for details.

Available Buckets

→ Delivery — All Bucket URIs: the complete, up-to-date list of bucket URIs, file formats, and refresh cadence.

⚠️

Important: Bucket listing is not supported. Always use the exact bucket URIs from the Delivery page to access your licensed signal types.

Download Data

# Download from a specific bucket (replace with your licensed bucket and timestamp from the Delivery page)
gcloud storage cp gs://autobound-{signal-type}-{version}/2026-01-05T12-00-00Z/output.parquet ./

💡

Tip: Your account manager will provide the specific bucket URLs and timestamps for your licensed data.

Schema Overview

{
  "signal_id": "uuid",
  "signal_type": "10k",
  "signal_subtype": "aiInvestment",
  "detected_at": "2026-01-05T12:00:00Z",
  "company": {
    "name": "Acme Corp",
    "domain": "acme.com"
  },
  "data": {
    "summary": "...",
    "relevance": 0.85
  }
}

→ Schema Overview — high-level schema structure.

💡

Full field reference: For complete field definitions, see the individual signal pages under Company Insights or Contact Insights.

Matching Signals

→ Entity Resolution — best practices for matching.

Key Documentation