Connect Campsites.co.uk to Campiamo
Set up two-way iCal calendar sync between Campsites.co.uk and Campiamo, so dates booked on either side are blocked on the other and you cannot be double booked.
Last updated September 29, 2026
Campsites.co.uk and Campiamo exchange calendars using iCal. Each side publishes a calendar link and reads the other's on a schedule: a Campsites.co.uk booking blocks the dates in Campiamo (and on your website, widget and other channels), and your Campiamo bookings block the dates on Campsites.co.uk.
If calendar sync is new to you, read how channel sync works first. If you also list on Pitchup, that is a separate and fuller connection: Pitchup bookings arrive in Campiamo complete with guest details, while calendar sync carries dates only.
Before you start: pools of identical pitches
Calendar sync carries no numbers. A date is busy or free, never "14 of 20 pitches left". Link a Campsites.co.uk pitch type to a 20-pitch grass field in Campiamo and the first booking on either side closes all 20 for that night.
Calendar sync therefore works best for single units: one glamping pod, one named hardstanding, one shepherd's hut. For a field of identical pitches, either list a smaller allocation on Campsites.co.uk and give it a matching pitch type in Campiamo, or leave that field off calendar sync and manage it by hand. The trade-offs are spelled out in the Booking.com guide's unit-count section, which applies here word for word.
Step 1: Create the connection in Campiamo
- Go to Channels in the dashboard sidebar.
- Find Campsites.co.uk and choose Connect.
- Pick the pitch type this listing corresponds to.
Keep the dialog open while you fetch the Campsites.co.uk link.
Step 2: Copy your Campsites.co.uk calendar link
Sign in to your Campsites.co.uk owner account and open the calendar or availability settings for the pitch type you are connecting. Look for calendar sync or iCal, and copy the export link. It usually ends in .ics, sometimes followed by a long code that is part of the link.
If you cannot find calendar sync in your account, contact Campsites.co.uk support and ask them to enable iCal sync for your listing. Tell them you need an export link to give to your booking system and somewhere to paste an import link from it.
Step 3: Finish the connection in Campiamo
Paste the link into the Calendar link from Campsites.co.uk field and save. Campiamo checks the link immediately. A signed-in page or a broken link is refused with an explanation, rather than accepted and left to fail quietly.
Once saved, Campiamo shows your calendar link. Copy it.
Step 4: Import your Campiamo calendar into Campsites.co.uk
Back in the same calendar sync screen on Campsites.co.uk, add an import calendar, paste your Campiamo link, and name it "Campiamo". Both directions are now connected.
What syncs, and how quickly
Campiamo → Campsites.co.uk: all unavailable dates for the pitch type, which means bookings, manual blocks, closed season and availability windows, published 365 days ahead. Campsites.co.uk chooses how often it re-reads your calendar.
Campsites.co.uk → Campiamo: read every 15 minutes; busy dates become blocks marked "Booked on Campsites.co.uk". No booking or guest is invented. The guest's details and payment live in your Campsites.co.uk account. Cancellations release the blocks on the next sync, and Sync now on the Channels page forces an immediate read.
When something is wrong
"That link did not return a calendar feed." The link is not a calendar export. Go back to the calendar sync screen and copy the .ics link.
Campsites.co.uk shows you full when you are not. Almost always the multi-unit problem above: a booking on one unit of a multi-unit pitch type marks the whole date busy.
Blocked dates with no booking to open. That is a Campsites.co.uk stay: dates held here, guest on Campsites.co.uk.
Sync history with exact failure reasons is on the Channels page, and the note on double bookings applies to Campsites.co.uk like every iCal channel.
Further reading
Guides from the blog that go deeper on this topic.
Still stuck?
If this page didn't answer your question, it's our page that needs fixing. Tell us.
Get in touch