68/100

Moderate evidence

ProblemPublished recordLifestyleProblem Space

Artificial intelligence in digital tourism: evidence from an experimental study of consumer decision-making

Truvace record
TRV-2026-2662raw data (JSON)
Version
v1Published
First published
Evidence type
Controlled or validated comparison
Sources
1 sourcePeer-reviewed
sha256
284a6db372c3…check it

Introduction This study examines how different digital environments influence user experience and consumer behavior when selecting accommodation in tourism, comparing Booking, ChatGPT, and general internet search. Methods A controlled experiment was conducted with 165 participants from Croatia, Serbia, and Bosnia and Herzegovina. User experience was assessed through pragmatic and hedonic dimensions, while decision-making outcomes included booking likelihood and perceived simplicity. Results Significant differenc…

The problem

In a controlled experiment with 165 people choosing a hotel in Graz, Booking.com users rated their experience and booking likelihood significantly higher than web-search users, while ChatGPT users did not differ significantly from either group and did not surpass Booking.

What this doesn’t fix

ChatGPT was compared with Booking.com without live availability, verified reservations or booking functions, and the sample was mostly young adults, so the comparison is not between equivalent services and may not generalise.

Sources

1 on file
  1. Frontiers in Sustainable Tourismdoi:10.3389/frsut.2026.1924194
    Peer-reviewed2026-08-26

Cite this record

v1

Truvace Impact Record TRV-2026-2662, v1: “Artificial intelligence in digital tourism: evidence from an experimental study of consumer decision-making.” Truvace, 2026-11-12. /record/TRV-2026-2662 (accessed on the day you copy it). sha256 284a6db372c3eac8…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1284a6db372c3…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2662 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.