NewCheck out Claude MCP for AI Venue Intelligence.Explore AI Venue Intelligence
smartsegments
All resources
AI assistant setup

Connect SmartSegments to Copilot.

Connect SmartSegments through Copilot Studio, confirm the agent can access the right projects, then ask clearer questions about bookings, revenue and guests. Google Ads and Google Analytics performance, along with labour data, depend on your data setup; other sources are available on request.

First, choose the right Copilot

Before you start

This guide covers a Microsoft Copilot Studio agent using the standard harness and its MCP onboarding wizard. The agent can be published to the Teams and Microsoft Copilot channels.

Not GitHub Copilot. This is also not the separate Microsoft 365 custom federated connector / Agent 365 admin registration path.

  • Maker: you need permissions to use the Copilot Studio environment where the agent will be created.[2]
  • End user: the user needs access to Microsoft Copilot to use it there. Their access to data still depends on their Google account and SmartSegments permissions.
  • Data and policy: confirm the expected projects and venues are configured for the user. Copilot Studio / Power Platform environment and admin policies can affect MCP access.[8, 11]

The maker's authoring connection is not a substitute for each user's own OAuth connection. Copilot prompts users when a conversation reaches a tool that needs authentication; users can retry after completing the connection.[3]

01 / Maker setup

Create the agent and add the remote MCP server

Start in the Copilot Studio environment you are authorised to use. Create an agent using the standard harness, then open its Tools page.[1, 2]

  1. Open Tools and start a new tool

    From the agent's Tools page, select Add a tool > New tool > Model Context Protocol. The labels can vary as Copilot Studio changes.[1]
    Illustrated example: A conceptual agent workspace with Tools selected and Add a tool highlighted.
    Illustrated example, not a screenshot. Open the agent Tools page and begin adding a tool.

  2. Select Model Context Protocol

    Choose the MCP option for an existing remote server, not a different connector or registration workflow.

    Illustrated example: A conceptual Add a tool menu with the Model Context Protocol option selected.
    Illustrated example, not a screenshot. Choose the MCP tool path in the standard agent harness.

  3. Enter the exact server details

    Use the server URL exactly as shown. The service requires OAuth.

    Server name
    SmartSegments
    Description
    A short explanation for your agent, for example: “Use SmartSegments to access the venue and project data available to the signed-in user.”
    Server URL
    https://mcp.smartsegments.ai/
    Illustrated example: Conceptual MCP tool form populated with SmartSegments name, exact server URL and OAuth dynamic discovery.
    Illustrated example, not a screenshot. Enter the service details and use OAuth 2.0 with dynamic discovery.

  4. Create the tool

    For authentication choose OAuth 2.0 > Dynamic discovery, then select Create > Next. SmartSegments publishes OAuth discovery metadata, so do not invent client credentials or manually fill endpoint URLs.[1, 9, 10]

  5. Add the tool to the agent

    In the Add tool step, choose Create a new connection or select an existing connection as appropriate for your authoring setup, then select Add to agent. This adds the tool to the agent; end users still complete their own authentication when prompted.[1, 3]

02 / User-specific access

OAuth connection and user sign-in

Microsoft documents OAuth 2.0 as allowing individual users to authenticate. The end-user flow prompts when a conversation reaches a tool that requires authentication; after finishing the connection, the user can retry the request.[3]

A live read on 16 October 2026 confirmed SmartSegments' public OAuth metadata advertises its authorization server and publishes the authorization, token and registration endpoints and scopes. A no-token MCP initialize request returns HTTP 401 with the expected resource-metadata challenge. This is why the wizard should use OAuth discovery; it is not a reason to turn authentication off or manually configure endpoints.[9, 10]

Illustrated example: A flow diagram distinguishing maker authoring from an individual user's Google sign-in and data access.
Illustrated example, not a screenshot. The agent is authored once; each user authenticates with their own authorised account.

  1. Wait for the tool's sign-in prompt

    In a conversation, when SmartSegments needs authentication, follow the prompt to connect. Use the Google account already authorised for your SmartSegments data.

  2. Complete sign-in and retry

    Finish the connection flow, return to the conversation and retry the original request if needed. Do not share credentials, tokens or authorization codes with the agent, the maker or support.

  3. Keep access expectations personal

    A user's connection does not grant access to another person's Google data. What is available depends on that Google account, SmartSegments permissions and configured data, plus the Copilot / Power Platform environment policies.[3, 8, 11]
Illustrated example: A conceptual diagram showing Google account access, SmartSegments configuration and environment policy as boundaries on available data.
Illustrated example, not a screenshot. Results depend on each access layer; an agent cannot reveal unconfigured or inaccessible data.

03 / Test before publishing

Test the connection in Preview

Use Preview in Copilot Studio. Ask the agent to use SmartSegments and list accessible projects and ROLLER venues. Complete OAuth if prompted; if needed, retry after authentication. Inspect tool activity to check whether the tool was called and review its activity when diagnosing a failure.[3, 4]

Illustrated example: A conceptual agent Preview chat beside an activity panel showing a SmartSegments tool call.
Illustrated example, not a screenshot. Test the conversation and inspect tool activity when a result is unexpected.
Confirm accessible projects and venues
Use SmartSegments to list the projects and ROLLER venues I can access. Show their names and IDs, then ask me which venue to analyse.

A useful test returns the projects and venues available to the signed-in user. If the answer is empty or incomplete, do not assume the agent has additional data; check permissions and configuration in Troubleshooting.

04 / Publish and share

Publish so users can reach it in Microsoft Copilot

  1. Publish the agent

    Select Publish > Publish. Connect a channel only after at least one publish.[5]

  2. Add the Teams and Microsoft Copilot channel

    Open the channel setup and connect the Teams and Microsoft Copilot channel. Make sure Make agent available in Microsoft Copilot is selected, then select Add channel.[5, 6]

  3. Share with permitted users

    Share the installation link with users who are permitted to use the agent. An organization-wide app store listing may require administrator approval. Users need access to Microsoft Copilot and each user completes their own OAuth connection when the tool requests it.[3, 6, 7]

  4. Set expectations

    Tell users which Google account to use and that accessible data follows their own Google and SmartSegments permissions. Availability and rollout can also be affected by Copilot Studio / Power Platform environment configuration and administrator policies.
Illustrated example: A conceptual three-stage path from publishing to adding the Microsoft Copilot channel and sharing an installation link.
Illustrated example, not a screenshot. Publish first, enable the Microsoft Copilot option, then share with permitted users.

05 / Ask grounded questions

Sample venue analytics prompts

Replace bracketed text with the venue, project or property ID that SmartSegments returns. The available answers depend on configured data and your permissions; ask the agent to flag incomplete data and state metric definitions rather than estimate unavailable values.

Monthly revenue and bookings
For [venue], compare bookings and revenue for the last full calendar month with the month before. Show totals, percentage changes and the main drivers.
Top products
For [venue], rank the top 10 products by revenue over the last 90 complete days. Include booking counts and each product's share of revenue.
Party bookings and revenue
For [venue], analyse party bookings and revenue over the last 90 complete days. Show average spend per party booking and the strongest packages, then suggest three ways to grow party revenue. Flag any missing data.
Discover GA4 properties
Use SmartSegments to list the Google Analytics 4 (GA4) properties I can access, including their names and property IDs.
Compare marketing channels
For [GA4 property ID], compare sessions, key events and purchase revenue by session source/medium for the last full calendar month. Highlight the strongest channels and flag unavailable metrics.
Peak and quiet visit times
For [venue], break down visits and revenue by day of week and session start hour over the last 90 complete days. Identify peak and quiet periods. Use visit dates and session times where available, and explain how revenue is allocated.
New and returning guests
For [venue], compare revenue share and average spend per booking for new and returning guests last quarter. Define returning guests and the history used to identify them. If customer history is insufficient, explain the limitation.

06 / Help and reference

Troubleshooting

Use the error text and the step where it occurred to narrow down the issue. Do not send passwords, OAuth tokens, authorization codes or client secrets.

Common Copilot Studio and SmartSegments connection problems and actions
What you seeWhat to do
The MCP option or Add a tool is unavailableConfirm you are authoring a Copilot Studio agent in the intended environment and that your account has maker permissions there. Ask the environment administrator if the page or action is unavailable.[1, 2]
Dynamic discovery fails or sign-in cannot startStop and contact your SmartSegments administrator or support with the exact non-secret error and step reached. Keep OAuth 2.0 > Dynamic discovery; do not select None, bypass sign-in, invent client credentials or manually enter endpoints. SmartSegments discovery metadata provides the OAuth configuration for this server.[1, 9, 10]
A conversation asks me to connectThat is the expected per-user flow when a conversation reaches a tool that requires authentication. Complete the sign-in using the Google account already authorised for your SmartSegments data, then retry the tool request.[3]
Authentication completed but the retry still failsRetry once after completing the connection. If the problem continues, contact your SmartSegments administrator/support and your Copilot Studio environment administrator. Share the visible error and approximate time, never tokens or secrets.[3, 8]
The tool is blocked or missing under policyAsk the Power Platform environment administrator to review applicable data policies for MCP access. Do not try to bypass a policy by changing authentication or using another connection path.[8]
Preview returns no projects or venue dataConfirm the signed-in Google account is already authorised for the relevant SmartSegments data and that the user's SmartSegments permissions include the projects or venues. Ask the administrator/support to check data configuration. An agent cannot return data that has not been configured or made accessible.[11]
The agent gives a general answer instead of calling the toolIn Preview, ask explicitly to use SmartSegments and inspect the tool activity to see whether the MCP tool ran. Check that it was added to the agent and that the request is within the user's access. Preview does not establish that other users have connected their own accounts.[1, 4]
A result differs from another reportCompare the same venue, dates, timezone and currency. Check booking versus visit date, metric definitions, tax, refunds, cancellations and data freshness. Ask the agent to state unavailable or incomplete data rather than estimate it.