Integrations
⏱ ~3 min read · catalog + configuration overview — per-integration setup guides link out from each section.
In short. SGEN connects to external services through a curated set of first-party integrations — Google Search Console, Google Business Profile, Google Analytics 4, ClickUp, email/SMTP providers, and payment gateways. Each is configured inside the admin, governed by the platform's release cadence, and monitored alongside the rest of the platform. No plugin juggling, no separate vendor update cycle. Find the integration you need in the catalog below, then follow its reference page for setup.
On this page: The catalog · Why first-party · Configure an integration · Authentication patterns · Troubleshooting · Related reading
The catalog
The shipped integrations group by function:
| Category | Integration | What it does in SGEN |
|---|---|---|
| Search | Google Search Console | Verification, sitemap submission, indexing status surfaced inside the admin |
| Search | Google Business Profile | Business listing data tied to local SEO and location surfaces |
| Analytics | Google Analytics 4 | Traffic measurement and event tracking alongside SGEN's built-in analytics |
| Workflow | ClickUp | Task and ticket sync for support and operations workflows |
| Email and SMTP providers | Transactional email delivery for form submissions, notifications, and password recovery | |
| Commerce | Payment gateways | Stripe, PayPal, and other processors for the Ecommerce module |
The catalog grows with platform releases. Per-integration reference pages: Google Search Console · Google Analytics 4 · ClickUp · Email and SMTP · Payment gateways.
Why first-party
A third-party plugin integration is a black-box dependency: separate vendor, separate update cycle, independent failure mode. A first-party integration follows the platform's release cadence and audit logging — when the platform is healthy, the integration is healthy; when something breaks, the platform's monitoring catches it.
The trade-off: the catalog is curated, not exhaustive. Operators who need a connection outside the catalog can use the Custom Codes module as a fallback.
Configure an integration
Open the admin → Settings → Integrations. Each integration has its own configuration surface; authentication, scope, and operational state all live there.
For the common tracking integrations, paste the ID from your external service account:
| Integration | ID format | Where to find it |
|---|---|---|
| Google Analytics 4 | G-XXXXXXXXXX (Measurement ID) | GA4 Admin → Data Streams → stream → Measurement ID |
| Meta Pixel | 15-digit number | Meta Events Manager |
| Hotjar | 7-digit number | Hotjar → Settings → Sites & Organizations → Site ID |
| Intercom | 8-character string | Intercom → Settings → Installation → Workspace ID |
Click Save — a green banner "Integration configuration has been successfully updated!" confirms the commit. Verify in an incognito window after saving.
To remove an integration: clear its ID field and click Save.
Configuration is per-site and persists until you change it. Multi-site teams configure each site independently; token issues on one site don't affect others.
Authentication patterns
| Pattern | Used by | How it works |
|---|---|---|
| OAuth | Google integrations | Click Connect → authorize on Google → redirected back. Tokens stored encrypted; platform handles refresh automatically. |
| API key | Analytics tracking, third-party services | Paste key into the configuration field. Stored encrypted, not displayed in plain text after save. |
| SMTP credentials | Email / SMTP | Host, port, username, password configured once. Platform owns the connection. |
| Webhook URL | Some integrations | SGEN generates a URL; you paste it into the external service's webhook settings. |
How integrations sit in the platform
Integrations extend platform reach to external services. SG-Modules covers internal workflows (forms, popups, redirects); Integrations covers outbound connections (analytics, search reporting, payments). The two layers compose — a form submission can trigger email/SMTP delivery and fire a GA4 event in the same workflow.
Troubleshooting
Integration isn't authenticating. Most often an expired token or revoked OAuth. Re-authenticate from the integration's configuration surface.
Data isn't flowing. Check the integration's operational state in the admin — the surface shows whether data is being sent and whether the receiving service is acknowledging.
Feature isn't supported. Check sibling integrations first; if genuinely unsupported, Custom Codes is the fallback.
Multiple Google integrations seem to overlap. They cover different workflows even when they share authentication. Configure each for its specific role.
Integration was deprecated. The platform notifies operators in advance. The notice covers what to migrate to and the timeline.
Related reading
- Integrations overview — deeper introduction
- SG-Modules — the internal-workflow layer
- SG-Admin Overview — the operator surface where integrations are configured
- Google Search Console · Google Analytics 4 · ClickUp · Email and SMTP · Payment gateways