Getting started

Sign in

Open the PULSE app. Until you sign in, every route redirects to /login.

The login screen asks the backend which methods are on (GET /auth/config) and shows up to two:

• Sign in with Google appears only when the deployment has a Google OAuth client configured.
• Username and password appears unless the deployment has turned on Google-only sign-in.

Details, including how accounts get their roles, are in Signing in.

Set your business profile

Open System → Settings. Fill in the business name, industry, and timezone. Then set the default content language, the default tone, and your active channels. The app saves these with ConfigService.UpdateConfig. See Business profile.

Connect your accounts (optional)

Open System → Integrations. It has two tabs:

• Accounts: LinkedIn, Instagram, Google Ads, and Google Analytics.
• Data sources: HubSpot and GitHub.

You can run an audit without any of these. Leads sync needs HubSpot. The forecasts need Google Analytics. Publishing to your website needs GitHub. See Connections.

Run a Site Audit

Open Overview → Site Audit. Enter your website URL. You can add a LinkedIn URL and an Instagram handle, and pick the goals you care about. Then choose Run Site Audit.

The diagnosis streams in as it is written. The site must be reachable, because PULSE reads the live page before it writes anything. See Site Audit.

Review what the audit produced

A finished diagnosis fills in the rest of the app, with no extra model calls:

• Content → Approval holds draft posts, one set per recommended channel.
• Content → Campaigns holds one draft campaign linked to the diagnosis.
• Audience → Follow-up holds a 30-day cycle built from the diagnosis’s 4-week plan.
• Audience → Customer 360 holds one profile per audience segment.

Approve or reject the drafts. Nothing leaves PULSE until an administrator has armed publishing. See Publishing controls.