Connector Framework

Overview

The Connector Framework lets you integrate AEO Optima with external tools and services. Connectors are organized into categories:

• SERP Data Providers — Search engine results APIs for SERP tracking (Serper.dev, DataForSEO)
• Messaging & Alerts — Push notifications to team channels (Slack)
• Analytics & Automation — Dashboards and event-driven workflows (Looker Studio, Zapier/Make)
• E-commerce — Product catalogs and shopping visibility (Shopify)

Each connector is registered per organization, can be enabled or disabled independently, and stores its credentials securely using encrypted storage.

SERP Data Providers

SERP tracking requires a search API connector. These providers are used by the capture pipeline to fetch Google AI Overviews, AI Mode results, and organic search data. Configure your SERP provider in Settings → Connectors, then manage source toggles in Settings → SERP Tracking.

Serper.dev

Google AI Overview and AI Mode SERP tracking via the Serper.dev API.

Required credentials:

• API key

Supported SERP sources:

• Google AI Overview
• Google AI Mode

Use cases:

• Track brand visibility in Google AI Overviews and AI Mode results.
• Monitor organic search positions and AI-generated citations.
• Best value for SERP tracking: 50K searches for $50/mo.

DataForSEO

Full-featured SERP data provider with keyword volumes, backlink data, and domain authority enrichment.

Required credentials:

• API login
• API password

Supported SERP sources:

• Google AI Overview
• Google AI Mode

Use cases:

• Track brand visibility in Google AI Overviews alongside detailed SERP data.
• Enrich citation sources with backlink, keyword volume, and domain authority metrics.
• Cross-reference AI visibility with traditional search rankings.
• Pull detailed SERP feature data for tracked keywords.

Note: Both Serper.dev and DataForSEO implement the same SerpProvider interface, so switching between them requires no changes to your SERP tracking configuration — just add the new connector and disable the old one.

Integration Connectors

Slack

Push alerts, reports, and notifications to Slack channels.

Required credentials:

• Bot token (for direct API access)
• Webhook URL (for incoming webhooks)

Configuration:

• Default channel for notifications

Use cases:

• Receive real-time alerts when visibility drops or anomalies are detected.
• Post weekly digest summaries to a team channel.
• Notify when snapshot captures complete.

Looker Studio

Connect AEO Optima analytics data to Google Looker Studio dashboards.

Required credentials: None (uses data export).

Configuration:

• Data source selection: visibility scores, citations, snapshots, or all data.

Use cases:

• Build custom executive dashboards combining AEO data with other business metrics.
• Create scheduled reports with Looker Studio's built-in distribution.
• Share interactive visibility dashboards with stakeholders who do not use AEO Optima directly.

Zapier / Make

Trigger automations from AEO Optima events via webhooks.

Required credentials: None (uses webhook URL).

Configuration:

• Webhook URL — The Zapier/Make webhook endpoint to receive events.
• Events — Select which event types to forward: snapshot.completed, alert.triggered, visibility.changed, geo_audit.completed, report.generated.

Use cases:

• Automatically create Jira tickets when critical alerts fire.
• Post visibility changes to a Google Sheet for historical tracking.
• Trigger email sequences when GEO audits complete.
• Chain AEO events with hundreds of other tools via Zapier/Make workflows.

Shopify

Sync product catalogs and track AI visibility for e-commerce brands.

Required credentials:

• Shopify access token

Configuration:

• Shop domain (e.g., my-store.myshopify.com)

Use cases:

• Automatically import products as tracking targets.
• Monitor how AI models describe and recommend your products.
• Track shopping-related AI visibility alongside your product catalog.

Setting Up a Connector

1. Navigate to Settings then Connectors in the sidebar.
2. Select the connector type you want to add.
3. Enter the required credentials and configuration fields.
4. Save the connector. It will be registered as active by default.
5. Test the connection using the built-in test function (if available for the connector type).

Managing Connectors

Enable / Disable

Toggle a connector's active status without deleting it. Disabled connectors retain their credentials and configuration for easy re-activation.

Sync Logs

Each connector maintains a log of sync operations showing:

• Sync type (push, pull, test)
• Status (success, failed)
• Records synced
• Error messages (if any)
• Start and completion timestamps

Deleting a Connector

Deleting a connector removes it permanently along with all stored credentials. Sync logs are retained for audit purposes.

Security

• All credentials are encrypted at rest using AES-256 encryption via the credential store.
• Credentials are never exposed in API responses — only existence is confirmed.
• Each connector's credentials are isolated and cannot be accessed by other connectors.
• Deletion of a connector cascades to all its stored credentials.

Plan Requirements

The Connector Framework is available on Pro-SME and above (up to 5 connectors) and Enterprise plans (unlimited). Free and Starter plans do not include connector access.