Connectors overview

Connectors link your advertising platforms and the tools your team works in to Concord. They are grouped by category on the Connectors page.

​

Advertising platforms

​

Workspace tools

HubSpot is coming soon.

​

Measurement

AppsFlyer brings your attribution data into the conversation, so Concord can read install and in-app event data alongside platform delivery.

​

Your own MCP servers

Any workspace can add a Custom MCP connector pointing at an MCP server you run or subscribe to, and its tools become available to Concord in your conversations. Authentication covers what enterprise authorization servers actually offer: no auth, a bearer token, or OAuth. For OAuth, Concord registers itself dynamically when the server supports it, and otherwise takes a client id and secret you pre-registered with your provider, which is what Entra ID, Okta, Auth0, Cognito, and Salesforce require.

​

Bring Concord into your own tools

Concord is also available as an MCP server, so Claude, Cursor, or an agent you build can talk to the Concord agent directly. See the Concord MCP server page.

​

Partnership status

Concord is a Meta Tech Certified Provider and a Google Tech Partner. Both are partnership statuses granted by those platforms — they are not security certifications, compliance audits, or endorsements of campaign results.

​

How much of each platform is covered

Connectivity is not the same as full feature coverage. Each connector page lists what Concord supports and what has to be done in the platform’s own interface, and Platform coverage is the summary.

​

Connections are per user

Each member connects the platforms and accounts they are individually authorized to access. Concord never holds broader platform access than the person who granted it. An admin then decides which of those advertisers and accounts the workspace activates, through scope. Only entities in scope are visible to Concord.

​

Managing a connection

Each connector has its own detail page. Open it to see the connected account, review what is in scope, and reconnect or disconnect. Connection status

• Active — healthy, synchronizing normally
• Error — needs attention, usually a re-authentication
• Disconnected — no active connection

​

Security

Connections use OAuth. Only the permissions Concord requests are granted, and you can disconnect a connector at any time.