---
name: ltx-marketing-daily-report
description: "Generate LTX Studio marketing & sales daily report with lead gen, spend, PELs/PQLs, sales metrics, and top org usage vs 7-day averages. Use when: daily marketing standup, GTM review, or when asked for 'marketing numbers' or 'lead performance'."
tags: [reporting, daily-metrics, ltxstudio, marketing, sales]
compatibility:
  - bq CLI installed and authenticated
  - GCP project access (ltx-dwh-explore for query execution)
metadata:
  author: dbeer
  version: "2.0"
  created: "2026-03-13"
---

# LTX Marketing & Sales Daily Report

## Overview

Daily snapshot of LTX Studio go-to-market performance: marketing spend and lead generation, sales activity (reach-outs, meetings), top enterprise org usage, new activations, and credit limit summary.

**Slack channel:** `#ltx-marketing-auto-report`

## Instructions

### Step 1: Run the Query

```bash
bq --project_id=ltx-dwh-explore query --use_legacy_sql=false --format=pretty "$(cat queries/marketing_sales_daily_report.sql)"
```

The query returns marketing & sales metrics including:

1. **Marketing Metrics** — Daily spend, leads, PELs, PQLs vs 7-day avg
2. **Sales Metrics** — Reach-outs, meetings (AE + BDR/SDR) vs 7-day avg
3. **New Activations** — Count of new users yesterday
4. **Credit Limits** — Accounts near 80%+ usage

**Key tables:**
- `ltx-dwh-prod-processed.marketing.sf_perf_marketing_agg_w_spend` (marketing spend & leads)
- `ltx-dwh-prod-processed.marketing.final_sf_lead_opportunity` (sales metrics)

See `shared/bq-schema.md` for full table schemas.

### Step 2: Format Output

Format per `references/report-template.md`.

### Step 3: Highlight Anomalies

Flag any metric deviating >50% from 7-day average.

## Context & References

### Shared Knowledge (Read First)
- **`shared/bq-schema.md`** — Table schemas, columns, joins, segmentation CTEs
- **`shared/metric-standards.md`** — Standardized metric definitions with SQL
- **`shared/product-context.md`** — LTX Studio overview, user types, business model

## Constraints

### DO NOT
- Run queries without `--project_id=ltx-dwh-explore`
- Use `is_enterprise_user` flag — use org-based enterprise logic
- Skip partition pruning (use `date(action_ts) >= ...`)

### DO
- Filter `ltx_studio = true` on sales funnel table
- Exclude `is_lt_team = false` on all user-level queries
- Use `SAFE_DIVIDE` for all percentage calculations
- Use enterprise segmentation CTE for top orgs (see `shared/bq-schema.md`)

## Examples

```
User: "Marketing daily report"
User: "How did leads perform yesterday?"
User: "Marketing performance vs last week"
User: "Run the GTM report"
```