Smeetz

Your bookings know more about your guests than your marketing uses

Smeetz sells your tickets and bookings reliably. What happens next is the same break in most venues: the booking data stays in the booking system, and marketing works from an address list someone exported six months ago.

Yet every booking holds exactly what good communication is made of. Who came. When. How often. For which offer. At what price. Through which sales channel.

The Smeetz integration with Caymland M4 brings this data across automatically, matches it to the right guest and makes it usable right away.

What the integration gives you

• One guest profile instead of one booking row. All of a person's visits sit together, even when they booked over years and through different channels.
• Audiences built on real behaviour. Everyone who came twice, but not this year. Everyone who always buys family tickets. Everyone who only comes in winter.
• No more exports. No list that is out of date from the day it was created.
• Clean data from the start. Existing guests are recognised instead of created twice.
• Reported alongside everything else. Bookings appear in the same reports as your campaigns and channels.

Which data is transferred

About the guest:

Country values are brought into one consistent spelling on the way in, so that "Switzerland", "CH" and "Suisse" do not end up as three different countries in your reports.

About the booking:

That booking date and visit date are kept separately is the single most useful point in this list. Only then can reminders before the visit and follow-ups after it be triggered cleanly, and only then does the report on how far ahead your guests book add up.

How the sync works

Direction: from Smeetz to Caymland M4. The integration reads your booking data and does not write back to Smeetz. Your booking system remains the system of record for sales, and marketing cannot change anything there.

Timing: The sync runs automatically on a schedule in the background, at the frequency that suits your operation. New bookings are in the system without anyone starting an import.

Matching: For every booking, the integration checks whether the guest is already known. If so, the profile is extended. If not, the guest is created. No duplicates are created, not even for regulars with many bookings over the years.

Origin stays visible. Every contact created this way carries a note that it came from Smeetz. When someone asks "where did this record actually come from", you have an answer instead of a guess.

Multiple accounts. If you run several sites, businesses or Smeetz logins, they can be connected side by side, each with its own credentials and activated individually. Bookings carry their account with them, so you can report across the whole business as well as per site.

What you can do with it

The import is not the point. This is the point:

Audiences that maintain themselves. "Everyone who came twice last season and not yet this year." "Everyone with family tickets." "Everyone who booked online rather than at the desk." These groups keep themselves current after every sync.

Communication around the visit. Confirmation after booking, reminder the day before, feedback request the day after, a fitting follow-up offer two weeks later. Triggered by the visit date, not by a list.

Win-back before it is too late. Guests who used to come regularly and have been missing for a season become visible while they can still be reached.

Scoring on real value. Points and stages can follow actual booking behaviour rather than who opened an email.

Reports with substance. Revenue by sales channel, booking lead time, share of returning guests, development per site. As a report that lands in your inbox every week by itself.

Related features: Segmentation & Automation, Contacts (CRM), Dashboards & Reporting.

Consent and data protection

Booking data is customer data, and the transfer decides whether your communication afterwards stands on safe ground.

Consent comes across. Smeetz records for every guest whether they agreed to be contacted. This flag is transferred and takes effect in Caymland M4.

It also lifts blocks, and you need to know this: If Smeetz reports a guest as contactable, existing marketing blocks on that contact are lifted. The one exception is the blocklist, which always stays in place. This is deliberate, so that a consent freshly given during booking does not fail on an old unsubscribe. It also means the consent logic in your Smeetz account has to be set up cleanly. We go through it together during setup.

Everything else applies as it does throughout Caymland M4: All data about a person sits in one profile, can be viewed, exported and deleted, every change is logged, and operation in Switzerland or in the EU is possible.

Requirements

On the Smeetz side:

• A Smeetz account with API access
• An API key and the two endpoint addresses for the general and the sales part of the API. You receive these from Smeetz
• With several sites, the credentials for each account

On the Caymland M4 side:

• Enable the Smeetz integration and store the credentials. The key is stored encrypted
• Define once which Smeetz field maps to which field in Caymland M4. You create your own fields yourself, without a developer
• Set the sync schedule

Setup is a matter of one appointment, not a project.

What it looks like day to day

The leisure venue. The day after their visit, guests receive a short feedback request. Whoever answers positively is offered the season pass four weeks later. Whoever has not been for two seasons gets a welcome-back offer in spring. All triggered by booking data, without anyone maintaining a list.

The group with several sites. Each site has its own Smeetz account. Management sees the development overall and per site in the same report, instead of adding up three exports.

The seasonal business. The lead-time report shows that families book three weeks ahead on average, while individual visitors book at short notice. Next season's communication plan follows from that.