ContentPulse

What it does in ClientPulse: Surfaces content-ops health signals (publishing velocity, approval latency, voice freshness, engagement velocity, platform composition) per client so the same client-health score reflects how the marketing work is actually going, not just CRM and finance.

Status: Available — Aurora-internal source. Auto-wired when both products belong to the same Aurora agency.

Tier: Included on every ClientPulse plan; ContentPulse is licensed separately at https://contentpulse.helloaurora.ai/pricing.

Per-user: No — wired at the agency level.

Why there's no "Connect" button

ContentPulse is Aurora's marketing-content workflow product. When an agency uses both ClientPulse and ContentPulse, ContentPulse pushes signals into ClientPulse's client_signals pipeline automatically via a signed server-to-server call — there's no OAuth handshake to authorise, no API key to paste. The "Connect" button you see on every other integration card doesn't apply here because the wiring is already done at the platform level.

This is the same model used by all Aurora-internal signal sources (e.g. in-app micro-NPS): not a third-party OAuth integration, just a cross-product API contract.

How the wiring works (technical detail, optional read)

• Both products share the same agencies.id UUID in the Aurora-Core Supabase.
• ContentPulse computes seven signal kinds nightly: content_velocity, approval_latency, pause_resume, voice_freshness, ingestion_rate, engagement_velocity, platform_composition.
• Each signal is HMAC-signed with the agency's shared secret + POSTed to ClientPulse's /api/sal/ingest endpoint.
• ClientPulse verifies the signature, resolves the agency, and writes a row into client_signals — the same table HubSpot, Asana, etc. write into.
• The signal flows into the per-client health score and the Monday Brief just like every other source.

You don't need to do any of this manually — it happens for any agency whose user has signed in to both products with the same email.

How to tell if it's working

In ClientPulse:

1. Open https://clientpulse.helloaurora.ai/dashboard/integrations/sources.
2. Find the ContentPulse card.
3. If the card shows under Emitting signals — last signal 24h ago / 7-day count > 0 for your agency, the wiring is live.
4. If the card shows under Available — Not connected via OAuth (with this page linked), one of two things:
   - Your agency isn't using ContentPulse yet. Sign up at https://contentpulse.helloaurora.ai.

   - Your ContentPulse and ClientPulse sign-in emails don't match. Use the same email for both.

If something's wrong

• No signals after 24h with both products live: ping us at hello@helloaurora.ai with your agency name. We can confirm both products see the same agency_id and re-run the catch-up sync.
• Wrong agency mapping (signals showing in the wrong agency): also a hello@helloaurora.ai ticket. We don't expose a self-serve re-map yet because the cross-product link is irreversible without us.

What you can do once it's connected

• See content-velocity drop alerts in your Monday Brief ("Acme posted 3 pieces last week vs. their 8-piece baseline").
• See approval-latency spikes on a client's health card ("Acme is taking 6 days to approve drafts vs. their 1.5-day median").
• The seven content-ops kinds feed the Engagement and Delivery dimensions of the client health score — visible on every client detail page under "Why this score?"