Last updated: 27 May 2026

Smart Segments can ingest data from, and transmit data to, a range of third-party systems on behalf of its customers. This page lists those customer-configurable integrations. Inclusion on this page is for transparency only and does not make any of the listed systems a subprocessor of Smart Segments — please see the Data Processing Addendum (DPA), Sections 5.5 and Annex I, for the full position on data flows and responsibilities.

The current list of Smart Segments’ own subprocessors is published at smartsegments.ai/subprocessors.

Source systems (data ingested into Smart Segments)

Smart Segments ingests booking, ticket, attendance, and related operational data from the customer’s venue management or source platform(s) on the customer’s instructions:

The customer remains the controller of the data held in these source systems and is responsible for its own contractual relationship with the provider.

Marketing, CRM, engagement and customer feedback platforms

Where activated by the customer, Smart Segments transmits configured Customer Data fields (which may include, where applicable, fields relating to minors for birthday or family marketing flows that the customer operates) to the customer’s chosen marketing/CRM/engagement/feedback platform. The customer remains responsible for: (a) the contractual relationship with the platform, including any data processing terms; (b) the lawful basis (including any required consents) for the direct marketing or engagement activity; and (c) the privacy information provided to End Users.

Smart Segments currently supports activation to the following platforms:

Point-of-sale, accounting, invoicing and fiscal compliance systems

Where activated by the customer, Smart Segments transmits configured Customer Data fields to the customer’s chosen point-of-sale, accounting, invoicing, or fiscal compliance system. Depending on the destination system and the applicable national tax law, such fields may include the End User’s national tax or fiscal identification number (for example, the Portuguese Número de Identificação Fiscal (NIF)) for the purpose of issuing legally compliant invoices, receipts, or fiscal records. The customer remains responsible for the contractual relationship with the system and for the lawful basis for that processing.

Smart Segments currently supports activation to the following systems:

Workforce management and other operational systems

Where activated by the customer, Smart Segments transmits configured Customer Data fields to the customer’s chosen workforce management, rostering, business intelligence, customer support, or similar operational system. The customer remains responsible for the contractual relationship and lawful basis.

Smart Segments currently supports activation to:

Conversion tracking / advertising platforms (optional)

Smart Segments offers an optional Conversion Tracking Integration that relays server-side conversion events from the customer’s online checkout (currently the ROLLER platform) to advertising platforms. Where activated, the customer’s chosen advertising platforms receive Customer Data as independent controllers (or, depending on the configured feature, as joint controllers with the customer). The customer must have its own contracts with those platforms and must operate a compliant consent management platform — see Annex I, Section C of the DPA for the full warranty and consent requirements.

Smart Segments currently supports conversion event relay to:

Customer-configured AI and large language models (via MCP)

Smart Segments operates a Model Context Protocol (MCP) endpoint that allows customers to connect a large language model or AI tool of their choice to their own Smart Segments data and query it through that tool.

Smart Segments currently supports connection to:

The customer is responsible for: (a) selecting the LLM/AI provider; (b) entering into its own contracts with that provider, including any data processing or consumer terms; and (c) the lawful basis for the processing carried out through that connection. Data flowing from the customer’s Smart Segments environment to the customer-selected LLM/AI tool flows under the customer’s own commercial and privacy relationship with that provider — not under Smart Segments’ subprocessor list.

This customer-configured use of Claude (or another LLM) via MCP is distinct from Smart Segments’ own internal use of Claude for support and investigation, which is listed on the subprocessors page and described in Annex II, Section 14 of the DPA.

Requesting a new integration

If you would like Smart Segments to build or activate an integration with a system not listed here, please contact jeroen@smartsegments.ai.

Disclaimer

This list is provided for transparency and is non-binding. Smart Segments may add, remove, or modify supported integrations from time to time. Inclusion on this list does not imply that any listed system is fit for the customer’s particular use case, nor that Smart Segments has reviewed or endorsed the privacy, security, or contractual terms of any listed provider; that assessment is the customer’s responsibility.