Every tourism RFP we read asks the same question in different words: can you show that the website sent people to our partners? That is a measurement problem before it is a design problem, which is why the reporting on this page is not an afterthought to the build.
What you get on every site
These are not add-ons and not a tier. Every Queantic site is hosted, updated, backed by monitoring and measured, whoever it belongs to.
Included
- A WordPress site your staff can edit. Events, offers, itineraries and seasonal pages are posts and pages your team changes without a ticket.
- Hosting, SSL, updates and monitoring. Run by us on U.S. infrastructure, checked every five minutes, with the history public on our status page.
- Analytics with no cookie banner. No cookies, no stored identifiers and no profile of a visitor — so nothing to consent to and nothing to disclose.
- Real traffic separated from automated. Peak-season numbers you can put in an annual report without a caveat about bots.
- Unlimited traffic. A festival weekend is not a hosting bill.
What we build for you
Quoted as named line items on the pricing sheet, so your board sees what each one costs rather than a single number with a story attached. Nothing here is a switch we flip — it is work, and it is priced as work.
Built to order
- Events calendar with partner submissions. Partners submit their own events through a form; your staff approve, edit or decline before anything appears. This is being built now — ask us where it is before you write it into a scope.
- Filterable listings with a map. Dining, shopping, lodging and attractions, filtered by category, area, price and season, each listing with its own page and pin.
- Referral-click tracking to partners. Every outbound link to a partner is counted, so "the website sent 1,240 people to lodging partners last quarter" is a number and not a claim. Built on the redirect tracker the product already uses for campaign links.
- Visitor guide requests and downloads. A request form for the printed guide and a counted download for the PDF, reported separately — they are different intentions and a board reads them differently.
- Newsletter sign-up. Wired to the mailing platform you already use, with sign-ups counted by the page they came from.
What your board sees each month
One report, in plain language, built from the same analytics the site collects as it runs. No tag manager, no sampling, and no second tool to licence.
| On the report | What it answers |
|---|---|
| Sessions, real and automated, separately | How much of the season’s traffic was a person |
| Referral clicks out to partners | Whether the site is doing the job your partners fund it for |
| Guide requests and guide downloads | Planned trips against idle browsing |
| Newsletter sign-ups by source page | Which content earns a returning visitor |
| Events and listings page detail | Which events pull, and which listings never get opened |
| Ranked recommendations | The three changes most likely to move the numbers above |
The report is one of the things we are still building to a shape a board can accept without a covering note. Ask for the current version when you ask for the quote, and judge it rather than this paragraph.
Residents and visitors are not profiled
Queantic's analytics set no cookies, store nothing in the browser, and build no cross-site identifier — so a Queantic site needs no consent banner for them, and there is no visitor profile for anyone to request, sell or leak. Traffic is separated into real and automated before it reaches a number you report. The architecture is described on how the analytics work.
Accessibility
We build to WCAG 2.1 Level AA and test every release against it: automated scans plus manual keyboard and screen-reader passes. We have not been independently audited yet, so we claim no conformance level and publish no Accessibility Conformance Report — both are in progress and neither is something to take our word for. What we do today, how we test it, and how to report a problem are on our accessibility page.
Hosting, uptime and the paperwork
Run for you
- U.S. hosting, SSL issued and renewed automatically
- WordPress, plugin and security updates are ours
- Monitored every five minutes, with a public 90-day history per component on our status page
- Unlimited traffic — a busy season is never a bill
For procurement
- Itemised one-time build and annual hosting and support
- You own the site, the content and the data; full export on request
- A written handover plan, so leaving is a procedure and not a negotiation
- The vendor packet is on our procurement page
Questions tourism boards ask
Can partners submit their own events, with our staff approving them?
That workflow is being built. It is not live today. We will tell you where it stands on the call rather than have you discover it after an award.
Can you report referral clicks to partner businesses?
Yes. Outbound clicks are counted through a redirect the product already uses for campaign links, so partner referrals become a figure per partner and per period.
Can we compare this month to the same month last year?
Not in the dashboard yet — that comparison is part of the board report we are building. The underlying data is kept indefinitely, so nothing is lost in the meantime and the first comparison can look back as far as the site has existed.
The rest — domains, editors, outages, cookie banners, pricing — are answered on the public-sector overview.
Two ways to start
Tell us what you need and we will send an itemised quote. If you already have an RFP or an ITB out, send it and we will answer it in the format you asked for — including three written quotes if that is what your policy requires.