00signal.com
Marketing edge
Static site, docs bundle, launch pages, connector catalog, and public product story. Deployed from the marketing workflow to GCS today, with S3 still available as an optional parallel target.
Canonical Domain Plan Active
Observe behavior. Trigger workflows. Measure what changed.
00signal turns user behavior into a live operating loop. The public story lives on 00signal.com, operators work from app.00signal.com, and ingestion, commands, rules, and analytics flow through api.00signal.com.
GCS marketing deploy live
Cloud Run deploy wired
12-source roadmap for marketing and ecommerce data
3
canonical surfaces
1
workflow control plane
12
priority source targets
Closed
behavior to outcome loop
Public topology
One product, three clear hostnames.
Keep the story, the operator app, and the ingest surface separate so auth, cache, and workflow traffic stay sane.
00signal.com
app.00signal.com
api.00signal.com
00signal.com - marketing site and docs app.00signal.com - dashboard and operator controls api.00signal.com - ingest, commands, rules, analytics
Live loop
Behavior becomes an intervention in four moves.
01
Capture
web, next.js, wordpress, shopify, mobile wrappers
02
Decide
rules, identity, behavior signals, cooldowns
03
Act
commands, overlays, modals, operator alerts
04
Measure
delivered, shown, clicked, completed, failed
Platform split
Clean separation beats one overloaded origin.
The domain plan is part of the product design. Marketing stays fast and cacheable, operators stay authenticated, and the API stays explicit for SDKs, connectors, and the CLI.
app.00signal.com
Operator app
Pulse dashboard, live sessions, workflow rules, rule performance, and identity drilldown. This should stay isolated from public marketing traffic and future customer auth scope.
api.00signal.com
Runtime core
Ingest, command delivery, analytics APIs, connector routes, workflow rules, and transport discovery. This is the canonical base URL for the API docs and CLI now.
Connector plane
Capture surfaces, operator surfaces, and data sinks on one contract.
Every integration feeds the same identity, command, and outcome model. The current source wave focuses on six marketing and ecommerce systems first, then expands in the next six without changing the operator story.
Capture surfaces
Where behavior starts
Next.js
WordPress
WooCommerce
Shopify
Chrome extension
- Web SDK injection and route tracking
- Server-side forwarding for commerce and CMS hooks
- Behavior signals that can trigger workflows immediately
Operator surfaces
Where humans stay in the loop
Slack
Microsoft Teams
ButtrBase identity
- Approval, escalation, and acknowledgement flows
- Identity enrichment by org, team, role, and app
- Rule performance and command outcomes tied back to sessions
Data and automation
Where the signal moves next
Segment
RudderStack
Zapier
n8n
BigQuery
Snowflake
- Connector-safe JSON ingest family under one security model
- Workflow-aware exports and warehouse replay correlation
- CLI and API docs that now point to the real production host plan
Wave 01 · build next
First six marketing and ecommerce sources
These are the highest-leverage systems for stitching storefront behavior, payments, attribution, and lifecycle messaging back into the same workflow engine.
Shopify
Storefront behavior, checkout recovery, and order lifecycle hooks.
WooCommerce
WordPress-native carts, orders, and customer activity already fit the loop.
Stripe
Payment intent, subscription, refund, and billing outcomes complete revenue attribution.
Google Analytics
Campaign and funnel context should sit beside behavior-triggered workflow outcomes.
Meta
Ad click and conversion signals should connect directly to journey replay and recovery flows.
Klaviyo
Email and SMS events let workflows follow the user after an abandoned or recovered session.
Wave 02 · queue after
Second six for CRM, CDP, and warehouse expansion
Once the first six are stable, this wave broadens marketing ops, warehouse reporting, and cross-system audience sync without changing the ingest contract.
HubSpot
Lifecycle stage, owner, and lead status should shape rule targeting and follow-up.
Segment
Mirror track, identify, and group traffic into one shared event model.
BigCommerce
Extend the commerce story beyond Shopify and WordPress-based stores.
Mailchimp
Campaign sends, opens, and audience states round out the retention layer.
BigQuery
Modeled behavior and workflow outcomes should export cleanly into analyst tooling.
Snowflake
Cross-team reporting belongs in the warehouse without losing command and outcome lineage.
Loop design
The product wins when the loop is obvious.
This is not just analytics, and it is not just messaging automation. The value comes from keeping behavior, decisioning, workflows, and outcomes in one measurable loop.
01
Observe
Clicks, routes, identity, commerce events, and visual state all land in the same event envelope.
02
Decide
Rules evaluate signals like rage clicks, hesitation, validation loops, and team- or org-specific targeting.
03
Intervene
Commands can show a modal, request a snapshot, deliver an operator card, or recover a stuck checkout in real time.
04
Learn
Delivered, shown, clicked, dismissed, completed, and failed outcomes all feed back into the same analytics plane.
Production topology
Ship the domain split directly into the docs and env defaults.
The repo now treats https://api.00signal.com as the canonical production base URL for the CLI and API docs, while localhost remains the explicit local dev override.
Host map
Route the right traffic to the right surface.
00signal.com -> marketing bundle -> docs bundle app.00signal.com -> pulse dashboard -> operator workflows api.00signal.com -> ingest -> commands -> analytics -> connectors -> rule engine
- Keep the marketing edge cacheable and static.
- Keep operator auth and dashboard traffic off the apex.
- Keep connectors and SDKs pointed at a single public API hostname.
Env shape
Make production explicit, not implied.
SIGNAL_BASE_URL=https://api.00signal.com NEXT_PUBLIC_00SIGNAL_ENDPOINT=https://api.00signal.com 00SIGNAL_ENDPOINT=https://api.00signal.com ANALYTICS_SERVER_URL=https://api.00signal.com # local dev override SIGNAL_BASE_URL=http://localhost:8080
- The marketing workflow now deploys the static bundle to GCS.
- The Cloud Run workflow remains the runtime path for the backend.
- Cloud CDN invalidation can be added later with `MARKETING_GCS_URL_MAP`.
Operator docs
Everything that matters is bundled with the site.
The static marketing bundle ships the deploy playbook, domain plan, API reference, CLI guide, connector docs, tutorial roadmap, and checked-in examples so the public site stays synchronized with the repo.
Deploy and domains
Production rollout docs
Runtime surface
API and CLI
Connectors
Surfaces that feed the loop
Tutorial roadmap
Six connectors at a time, with public docs to match
The public site now has a dedicated plan for how source integrations become quickstarts, deep tutorials, example payloads, and launch checklists.
Wave 01 tutorial set
What the first public connector tutorials need to teach
- Shopify checkout recovery with live workflow outcomes
- WooCommerce and Stripe revenue tracking with refund feedback
- Google Analytics and Meta campaign context attached to real sessions
- Klaviyo follow-up loops tied back to the same user journey
Next step