Search the Help Center
  1. Spotler Activate Help Center
  2. Apps
  3. Connectors

Articles in this section

See more

Connector: Ticketmatic via Spotler Connect

Spotler Connect integration required

This connection requires a licensed integration with Spotler Connect. It is a paid add-on. For more information, please contact your account manager.

This article explains how the integration between TicketMatic and Spotler Activate works, using Spotler Connect as the sync engine. It shows how data is transferred, which fields are included, and how to use the data in Spotler Activate for targeting and personalization.

In this article you will learn more about:

Flow overview

The integration follows a one-way sync pattern:

  • Source: TicketMatic
  • Sync engine: Spotler Connect
  • Destination: Spotler Activate

Spotler Connect reads data from TicketMatic and pushes it into Spotler Activate in structured payloads:

  • Contacts become CRMUpdate events
  • Orders become Purchase events
  • Events become Products in the catalog

Important limitation

No data is written back to TicketMatic.

Contacts sync

Contact records are synced as CRMUpdate events when they change in TicketMatic.

Included fields

  • User ID: TicketMatic contact ID
  • Email, First name, Last name
  • Gender, Birthdate
  • Phone number (first found)
  • Postcode, City, Country (from first address)

Segmentation fields

  • newsletter: "yes" if opted in
  • custom_subscribed: boolean from TicketMatic
  • custom_relaties: relation types as CSV string

Other attributes

  • custom_company, custom_language

Contact ID as fallback

If a contact has no email, the sync still uses the contact ID as the identifier.

Orders sync

Orders are synced as Purchase events when modified in TicketMatic.

Sync criteria

  • Only "completed/paid" orders (status 21002)
  • Orders must be linked to a customer

Included fields

  • userid: contact ID
  • orderid, timestamp, totalvalue
  • Line items as Products:
    • Event ID, price, quantity = 1

Enrichment

  • From contact profile: name, email, city, country
  • Custom metrics:
    • custom_purchased_products: number of tickets
    • custom_distinct_shows: number of unique Event IDs

Event catalog sync

Events are synced periodically as Products.

Core fields

  • ID: TicketMatic Event ID
  • Title, description, subtitle
  • Link to purchase page
  • Image (if available)

Location & timing

  • Location ID/name
  • Start/end times, sales period, publish time

Price & genre

  • Price: max price across all types
  • Genre: from TicketMatic custom field caption

Availability

  • Includes totals for paid, free, reserved, locked, complimentary tickets

Sync frequency

Incremental sync for Contacts and Orders runs frequently to pick up changes without duplication. Catalog sync for Events runs on a scheduled basis to keep availability and sale data up to date.

All syncs are batched and resilient for reliable performance at scale.

Marketing implications

Audience building

Segment based on CRMUpdate fields like newsletter, language, relation type, and location. Use Purchase events to include or exclude customers based on buying behavior. Leverage custom metrics to identify loyal or high-value customers.

Personalization

Use Products (events) in dynamic content. Filter on genre, date range, price, and availability. Include the event link for click-throughs directly to the purchase page.

Lifecycle & triggers

Trigger post-purchase journeys from Purchase events. Use sale dates from the catalog to power last-chance reminders and urgency campaigns.

Edge cases and guardrails

  • Orders without a customer are skipped
  • Contacts without email are still synced
  • Only completed orders are included
  • If multiple addresses/phones exist, the first is used

Summary

  • One-way sync: TicketMatic → Spotler Connect → Spotler Activate
  • Contacts: core profile, location, newsletter, company, segmentation
  • Orders: ticket lines, totals, custom metrics
  • Events: product catalog for personalization and targeting