Docs
Swagger

Dashboard

Domains & branding

Attach hostnames, set a primary domain, run probes, and manage powered-by attribution.

Where in the app
Domains live under Settings → General. Branding / attribution is under Settings → Branding (and related overview widgets).

Domains list

Add every hostname that serves your site with the macrocontent SDK (production, www, staging). Each row tracks whether the domain is active, last probe time, and a short health label such as OK, SDK live, or Fail.

Primary domain

Mark one hostname as the primary domain. That hostname drives overview screenshots, crawlers, and a clearer project home. When you change primary, the dashboard may ask whether to update PUBLIC key allowed origins to match.

  1. Add the hostname

    Settings → General → add domain (for example www.example.com).

  2. Set as primary

    Choose Use as primary domain so overview and checks have a canonical home.

  3. Align SDK origins

    Ensure the PUBLIC key allowlist includes the corresponding https://… origin for browser SDK calls.

Probes / heartbeat

A probe asks macrocontent’s servers to fetch the domain homepage and verify the SDK / Macro presence. You can run a probe from the domains table. Status meanings:

NameTypeDescription
OKstatusLast server probe confirmed Macro / SDK on the homepage.
SDK livestatusActive from real SDK traffic on this domain (heartbeat may still be re-run).
FailstatusProbe failed — check DNS, TLS, homepage reachability, and SDK install.
SDK live
If live traffic already hit the domain, you may see SDK live even when the last server heartbeat failed — use probe again after fixing DNS, TLS, or SDK install.

Branding & powered-by attribution

Free plans show a floating Macro (“powered by”) badge to visitors. You can keep that floating badge, or paste the same attribution snippet once into your layout (sidebar, footer, etc.) and verify it so the floating badge can be turned off. Paid / upgraded plans can remove attribution requirements according to your plan.

  • Copy the HTML snippet from Settings → Branding (attribution badge textarea).
  • Paste it somewhere visible on each domain’s homepage (/ is what probes check).
  • Run Verify for the floating badge and/or embedded snippet. All active domains must pass before you can disable the floating badge when the plan requires attribution.
SDK contract
The badge / snippet is part of the SDK powered-by contract. Don’t strip Macro attribution markup in a way that breaks verification if your plan still requires it.

Do

  • Keep primary domain DNS and TLS healthy so probes and screenshots succeed.
  • Verify attribution on every active domain after layout changes.
  • Update PUBLIC origins when you add a new production hostname.

Don’t

  • Don’t mark a temporary tunnel URL as primary for a production project.
  • Don’t hide the floating badge without a verified embedded snippet (when required).

Automation

GET/management/domainsmt_

List domains (settings.domains:read).

Domain write operations require settings.domains:write. See Management API.