How PACE gets this client's content in front of their audience. Changing it never touches generated content — it only changes where it's served.
Where PACE's contact / CTA / providers info sits on blog posts and pages. Use Footer bar when the client's own site already has a sidebar (e.g. WordPress) so PACE content complements it instead of competing.
Every page PACE delivers into the client's site ends with their quote or appointment button, the same block their articles carry, tagged utm_source=pacepro when it leaves their site so their lead reporting sees which page it started on. Turn it off for a client whose theme already carries that call to action. Changing it rebuilds the account's live pages.
A standing card in the brand colour on every page PACE hosts (subdomain or edge), under the contact card: a heading, a sentence, a phone number as a tap-to-call link, and optionally a link with its button label. St. Bernards carries "Call the Healthline" on every page of its own site. Saving rebuilds the account's pages; clearing every field removes the card.
Every quote or appointment link PACE publishes for this account leaves tagged utm_source=pacepro. Set a name here when the client reports on several properties side by side (Trimlight: pacepro_etn, pacepro_hv, pacepro_chatt) and it becomes utm_campaign exactly as typed; the kind of page moves to utm_term. Blank keeps the standard (service-areas, services, blog). Saving rebuilds the account's pages.
Emails whoever manages the client's site everything they need for the current delivery mode (WordPress plugin + keys, or the DNS records) PLUS the Google Analytics + Search Console access steps, in one message.
A real first name opens the email "Hi Jacob,"; anything else opens "Hello,". The company is named only where it helps ("forward this step to your DealerOn rep"). An email that still carries a placeholder is refused, never sent.
PACE publishes into the client's existing WordPress as native posts/pages via the PACE Content Bridge plugin. Recommended path: pairing, no secret is ever emailed or pasted, the plugin generates its own key and connects itself.
Generate a one-time pairing code, then give the client their license key + code. In WordPress → Settings → PACE Bridge → Pair with PACE, they enter both and click Generate secret & pair. The endpoint + secret land here automatically. Or just use Send full setup above, which emails the code with the steps.
Rebuilt (default): PACE's own header and footer, styled from the brand extraction (colours, fonts, logo, nav links). Captured: the client's actual header and footer taken from a page on their site, with their stylesheet, so a page on their own domain (edge) matches their site exactly. Captured chrome is re-checked weekly; a change rebuilds their pages.
For a dealership whose website runs on DealerOn. DealerOn issues PACE its own API key (a client id and secret) for this dealer, with the blog permission (dealeron.blogs) and ideally media and pages. Paste it here and Test: PACE asks DealerOn's sign-in service for each permission and shows which were granted. The test changes nothing on their site. The secret is sealed and never shown again.
One credential per practice (how USOP's warehouse team works). A key issued here reads only this practice's data. Hand it over with a verified link: the recipient confirms their email, enters a code, and the key is created and shown once. Nothing travels in an email.
For clients not on WordPress. Their edge (Akamai, Cloudflare, nginx, Netlify, Vercel) rewrites a subfolder of their own domain to PACE, the best placement for search. Set the subfolder, save, then hand them the matching config below.