Truace
Subscribe
68/100

Moderate evidence

GainPublished recordLifestyleGood Space

Full story
More
Export record JSONEmailLinkedInX

The Confidence Boost: How Generative Artificial Intelligence Nudges Consumer Decisions Through Preference Matching

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

ABSTRACT As generative artificial intelligence (GenAI) continues to transform e‐commerce, platforms increasingly deploy AI shopping assistants to enhance user experiences. However, the impact of AI‐generated information on consumer psychology remains underexplored. This study proposes and tests a decision‐structure nudge—preference‐matching presentation—in AI‐mediated shopping contexts. Across four experiments, we demonstrate that this nudge significantly boosts consumers' decision confidence, with this effect m…

The gain

In four experiments on AI-mediated shopping, presenting product information matched to a shopper's stated preferences significantly raised consumers' decision confidence, because the information became easier to evaluate.

What this doesn’t fix

The confidence boost weakened as consumers' product knowledge increased, so the nudge helps knowledgeable shoppers less.

Sources

1 on file
  1. Journal of Consumer Behaviourdoi:10.1002/cb.70172
    Peer-reviewed2026-05-17

Cite this record

v1

Truvace Impact Record TRV-2026-2695, v1: “The Confidence Boost: How Generative Artificial Intelligence Nudges Consumer Decisions Through Preference Matching.” Truvace, 2026-11-12. /record/TRV-2026-2695 (accessed on the day you copy it). sha256 19494b4a631683d8…

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. Publishedv119494b4a6316…

    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-2695 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.