aceModerate evidence
Published recordLifestyleGood Space
More
Promoting responsible tourism using generative AI nudges
- Truvace record
- TRV-2026-2640raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 6233829c9ef3…check it
Purpose With rapid modernization and globalization, responsible tourism practices at cultural heritage sites are in decline, as many visitors disengage from activities like volunteering, donating or mindful visits. This shift presents a significant challenge for governments, organizations and societies working to promote meaningful interactions with cultural heritage. Encouraging responsible tourism – where visitors respect local cultures while minimizing negative impacts – is crucial. generative artificial inte…
The gain
In a mixed-methods study with 300 experiment participants, researchers found AI-generated nudge images raised tourists' emotional response (β = 0.108) and engagement with cultural heritage (β = 0.224), and engagement strongly predicted responsible behaviour intentions (β = 0.792).
What this doesn’t fix
The study used a small sample from Indian and UK contexts and measured short-term behavioural intentions in a controlled experimental setting, so lasting behaviour change was not assessed.
Sources
1 on file- European Business Reviewdoi:10.1108/ebr-11-2025-0402
Cite this record
v1Truvace Impact Record TRV-2026-2640, v1: “Promoting responsible tourism using generative AI nudges.” Truvace, 2026-11-12. /record/TRV-2026-2640 (accessed on the day you copy it). sha256 6233829c9ef3e744…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2640 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.