Overview

Connections are the foundation of your Marketrix setup. They tell your AI agents where they’ll be helping users and provide the context they need to be effective.

​

What Are Connections?

A connection represents your website, application, or platform where your AI agents will be deployed. Think of it as a bridge between Marketrix and your digital presence.

​

Why You Need Connections

Connections serve several important purposes:

• Context for Agents - Your agents know which website or app they’re helping with
• Security - Only authorized domains can use your agents
• Organization - Keep different projects or websites separate
• Customization - Each connection can have different settings and knowledge

​

Connection Types

Marketrix supports two main types of connections:

​

Website Connections

Best for: Standard websites, landing pages, marketing sites Characteristics:

• Simple setup with just a URL
• Perfect for most websites
• Easy to integrate with widget
• Great for customer support and sales

Examples:

• Company websites
• E-commerce stores
• Marketing landing pages
• Blog sites

​

App Connections

Best for: Web applications, SaaS platforms, complex websites Characteristics:

• More advanced configuration options
• Support for custom authentication
• Better for complex applications
• Can handle multiple environments

Examples:

• SaaS applications
• Web-based tools
• Customer portals
• Internal applications

​

How Connections Work

​

The Connection Flow

1. You create a connection to your website or app
2. Your agents are linked to specific connections
3. Knowledge is organized by connection
4. Integrations are created for each connection
5. Users interact with your agents through the connection

​

Connection Requirements

​

What You Need

To create a connection, you’ll need:

• Website URL - The main URL of your website or app
• Domain Information - Which domains should be allowed to use your agents
• Basic Details - Name and description for your connection

​

Domain Configuration

Allowed Domains specify which websites can use your agents:

• Exact Match: example.com - Only this exact domain
• Subdomain: app.example.com - Only this subdomain
• Multiple Domains: example.com, www.example.com - Both domains
• Wildcard: *.example.com - All subdomains (if supported)

Security Note: Always specify allowed domains to prevent unauthorized use of your agents.

​

Connection Settings

​

Basic Settings

• Name - A descriptive name for your connection
• URL - The main URL of your website or app
• Description - Optional description of what this connection is for
• Status - Active or inactive

​

Advanced Settings

• Authentication - Custom authentication settings (for app connections)
• Rate Limiting - Limits on how often agents can be used
• Custom Headers - Additional headers for API requests
• Environment - Development, staging, or production

​

Best Practices

​

Naming Your Connections

Good Names:

• “Company Website”
• “E-commerce Store”
• “Customer Portal”
• “Marketing Site”

Avoid:

• Generic names like “Connection 1”
• Technical names like “prod-web-001”
• Names that don’t describe the purpose

​

Domain Management

• Be Specific - Only allow domains you actually use
• Include Variations - Add both example.com and www.example.com
• Test Thoroughly - Make sure your domains work correctly
• Update Regularly - Keep domain lists current

​

Organization

• One Connection Per Website - Don’t mix different websites in one connection
• Clear Descriptions - Help team members understand what each connection is for
• Consistent Naming - Use a consistent naming convention across all connections

​

Common Use Cases

​

E-commerce Website

Connection Type: Website Purpose: Customer support and sales assistance Domains: store.example.com, www.store.example.com Use Cases: Product questions, order support, returns

​

SaaS Application

Connection Type: App Purpose: User onboarding and feature help Domains: app.example.com Use Cases: Feature explanations, troubleshooting, account help

​

Marketing Site

Connection Type: Website Purpose: Lead generation and information Domains: example.com, www.example.com Use Cases: Service information, contact assistance, demo requests

​

Customer Portal

Connection Type: App Purpose: Account management and support Domains: portal.example.com Use Cases: Account questions, billing help, technical support

​

Connection Limits

​

Free Plan

• Connections: Up to 3 connections
• Domains: Up to 5 domains per connection
• Agents: Up to 2 agents per connection

​

Pro Plan

• Connections: Up to 10 connections
• Domains: Up to 20 domains per connection
• Agents: Up to 10 agents per connection

​

Enterprise Plan

• Connections: Unlimited connections
• Domains: Unlimited domains per connection
• Agents: Unlimited agents per connection

​

Getting Started

Ready to create your first connection? Here’s what to do next:

​

Troubleshooting

​

Common Issues

Connection Not Working

• Check that your domain is correctly configured
• Verify the URL is accessible
• Ensure allowed domains include all variations

Agent Not Responding

• Confirm the agent is linked to the connection
• Check that the connection is active
• Verify domain permissions

Integration Issues

• Make sure the integration is created for the correct connection
• Check that the connection is properly configured
• Verify domain restrictions

​

Next Steps

Now that you understand connections, you’re ready to:

1. Create your first connection - Set up a connection to your website
2. Add knowledge - Upload documents to train your agents
3. Create an agent - Build an AI assistant for your connection
4. Test in the playground - Make sure everything works correctly

Connections are the foundation of your Marketrix setup. Once you have a connection configured, you can start building powerful AI agents that understand your specific business and help your users effectively.