Second Shift documentation

Second Shift connects to the website you already have. It catches the leads that come through your forms, notifies you the instant one comes in, and tracks them in one dashboard. This documentation covers the install pieces, the platform guides, and the API the dashboard itself uses.

Everything here is the real thing: the same snippets the product hands you in your dashboard, and the same endpoints the dashboard calls. Nothing is documented that does not exist yet.

Your client ID

Every snippet on this site takes one value: your client ID. Find it in your dashboard under Settings, Developer tools. Replace YOUR_CLIENT_ID wherever it appears. That is the only value you ever paste.

A client ID is an identifier, not a password. It is printed in your page source on purpose: anyone can drop a lead in with it, and nobody can read anything back with it. Reading your data always takes your signed-in session. See Authentication in the API reference.

The three pieces

Analytics. One pasted line. The tracker records pageviews, link taps, engagement, page speed, and JavaScript errors, and remembers which page and which campaign a lead came from. No cookies, no stored identifiers, no fingerprinting. Install analytics

Lead forms. An endpoint change, not a plugin. Your form keeps its design and its fields; you change where it posts. An optional snippet adds captcha spam protection, and nothing else. Connect a form

Chat.

PREVIEW

The chat bubble on secondshift.site is our own front desk, live there so you can try it. On client sites it is installed site by site after verification, never flipped on silently. There is no self-serve chat install yet. About chat

Where things live

Install guides cover WordPress, Elementor, Next.js, and plain HTML: the snippets do not change from platform to platform, only where you paste them. The API reference documents authentication, every endpoint these pages rely on, responses, errors, and rate limits, exactly as the live service behaves.