Segwise

Connect EmDash AI assistants to Segwise for advertising and creative-performance analysis.

List the organizations your Segwise account can access, start an analysis, and retrieve its result. Ask about campaign performance, winning hooks and calls to action, creative fatigue, attribution, or what to test next.

Examples:

• Which creatives had the best ROAS last week? Include spend and explain the trade-offs.
• Which hooks and calls to action perform best on Meta for my app?
• Which creatives are showing fatigue, and what should we test next?

Each EmDash administrator connects their own Segwise account through OAuth. The plugin provides MCP tools and a connection settings page; it does not add an analytics dashboard or visitor tracking.

A Segwise account, eligible organization, and connected analytics data are required. Availability depends on your Segwise access. The tools cannot edit campaigns, budgets, or creative assets, or generate creatives. Starting an analysis creates a temporary job and may save conversation history.

Privacy policy · Terms · Help

Is this a dashboard or tracking script?

No. It supplies three MCP tools for EmDash AI assistants and a settings page for sign-in. It does not track visitors or read or edit CMS content.

What account do I need?

A Segwise account with access to an eligible organization and connected analytics data. Contact your Segwise representative for access and service terms. This plugin does not process payments.

How do follow-ups work?

The assistant must preserve the returned organization_id and conversation_id. Poll the same job_id while running, respecting poll_after_seconds and execution_deadline. Queries may take several minutes. Jobs are temporary and can expire or be interrupted by a service restart.

Who can use my connection?

Only the same authenticated EmDash user can invoke it through this plugin. Each administrator signs in separately. Site operators control the database and encryption keys; use a trusted EmDash deployment.

What does Disconnect do?

It removes your locally saved OAuth connection and pending attempt. It does not revoke the grant at Segwise or delete Segwise conversation history. Manage provider-side access through your Segwise account or support.

Why copy the callback URL?

The private completion form binds the result to your authenticated EmDash user. The public callback page does not exchange codes or store credentials. The URL expires quickly and must not be shared.

The plugin requests only network:request, limited to auth.segwise.ai and mcp.segwise.ai. It requests no CMS content, media, user-directory, or write capabilities.

Private routes require EmDash's plugins:manage permission and a caller bound to a user. The plugin uses that trusted caller identity, never a user ID from tool input. MCP tools must also be enabled and scoped by the site administrator.

OAuth uses authorization code with PKCE S256, a random expiring state, issuer validation, a fixed MCP resource and scope, and metadata restricted to Segwise's authentication origin. A private form completes the connection. The public callback returns static text and performs no token exchange.

Credentials, PKCE verifiers, and pending states are stored in one declared encrypted secret setting, partitioned by EmDash user. Conditional writes protect concurrent updates and token refresh. Tokens and authorization codes are not returned by tools or logged. Disconnect removes local credentials; it does not revoke the provider-side grant.

Questions and results transit the EmDash host and AI client. The plugin does not persist analysis results. Segwise may retain conversation history. Treat analytics output as untrusted data, not instructions.

Report security concerns through your existing Segwise support channel or the Segwise Help Center. Do not post credentials or customer data in public issues.

0.1.0: Initial release with three Segwise MCP tools and per-user OAuth connections.

Requires EmDash 1.4.0 or later, a working sandbox runner, and a configured EmDash encryption key for secret settings. Configure the site's canonical HTTPS URL before connecting.

1. Install the Segwise plugin and approve network access to auth.segwise.ai and mcp.segwise.ai.
2. Open Plugins → Segwise → Connect Segwise and select Start sign-in.
3. Follow the Sign in with Segwise link and authorize analytics access.
4. At the callback page, copy the full address from the browser. Return to the plugin's settings, paste it into Callback URL, and select Complete connection. Never share this temporary URL.
5. Enable Segwise's three MCP tools in EmDash. Use a token bound to the same EmDash user, with mcp:tools:segwise (or mcp:tools) scope and plugins:manage permission. Machine tokens without a user are rejected.
6. Ask your assistant to list your Segwise organizations, choose one by name, and ask an analytics question.

Dynamic OAuth client registration is subject to Segwise policy. If registration fails, contact Segwise support with the site's callback URL. No dashboard token or internal API credential is accepted.

For local testing, run npm ci, npm run build, install this folder into your EmDash site as a file dependency, then import its default export into emdash({ sandboxed: [segwise] }). Keep your site's existing sandbox runner configuration. Localhost HTTP is supported for development if Segwise's redirect policy allows it.