How to build Expansion Signals in BigQuery using Segment data

---

The Architecture: Headless Product Intelligence

To implement Expansion Signals effectively, you need to look beyond raw events. By unifying your data with a CDP and utilizing BigQuery's computational power, you can surface high-intent expansion opportunities automatically.

---

The "Logic Gap": Why Manual Implementation is Hard

1. The Power User Blind Spot: Identifying users who have outgrown their current plan requires tracking dozens of 'Breadth of Use' signals across many BigQuery tables. Manual SQL struggles to maintain this complexity.
2. Lagging Indicators: If your sales team is waiting for a monthly usage report to reach out, they're missing the 'Aha!' moment. Real-time expansion requires a proactive signal layer that monitors BigQuery continuously.
3. The Noise Problem: Not every surge in usage is an expansion opportunity. Filtering out 'noisy' signals in BigQuery requires sophisticated statistical baselining that is complex to write and even harder to debug.

---

Implementation: The BigQuery-Native Code

If you were to build this manually, your dbt model or SQL query in BigQuery might look like this:

/*
   Generic example for Expansion Signals
   Tailored for BigQuery architecture
*/

WITH raw_events AS (
    SELECT
        account_id,
        event_name,
        timestamp
    FROM `bigquery.raw_data.events`
    WHERE event_name IN ('seat_added', 'storage_limit_reached', 'api_usage_spike')
),

calculated_metrics AS (
    -- BigQuery-specific logic for Expansion Signals
    -- e.g., using specific window functions or time-travel
    SELECT
        account_id,
        COUNT(*) as signal_volume,
        DATE_TRUNC('day', timestamp) as metric_date
    FROM raw_events
    GROUP BY 1, 3
)

SELECT * FROM calculated_metrics;

---

The GrowthCues Advantage: Automate the Signal

While the code above provides a starting point, GrowthCues eliminates the need for manual SQL maintenance entirely. Our open-source semantic layer lets you define expansion signals using a simple Milestone Editor, keeping your BigQuery code clean and maintainable.

GrowthCues acts as the Headless Intelligence Layer for your BigQuery. It connects directly to your Segment tables and automatically:

• Calculates Expansion Signals at the account level.
• Detects anomalies and behavioral shifts in real-time.
• Pushes actionable signals back into your warehouse, where you can trigger n8n automations or sync to your CRM.

Deep Dive: Spotting Expansion

Don't leave money on the table. Check out Identify Expansion Opportunities to learn the 4 key signals to watch.

Ready to turn your raw BigQuery data into revenue?

Join the Technical Preview