Truace
Subscribe
50/100

Moderate evidence

ProblemPublished recordLifestyleProblem Space

Full story
More
Export record JSONEmailLinkedInX

Greedy and biased algorithms in AI recommendation systems: effects on emotional arousal and impulsive buying

Truvace record
TRV-2026-2549raw data (JSON)
Version
v1Published
First published
Evidence type
Survey
Sources
1 sourcePeer-reviewed
sha256
560a712dd286…check it

Purpose This study aims to examine the influence of greedy and biased recommendation algorithms on consumers’ emotional arousal, impulsive buying behavior and post-purchase dissonance in artificial intelligence (AI)-driven short video platforms, such as TikTok, Instagram Reels and YouTube Shorts. It further investigates the moderating roles of promotion-proneness and inferences of manipulative intent. Design/methodology/approach A quantitative survey was conducted with 766 Vietnamese consumers who had recently m…

The problem

A survey of 766 Vietnamese consumers found that greedy and biased recommendation algorithms on short-video platforms heightened emotional arousal, which led to impulsive buying and then to post-purchase dissonance.

What this doesn’t fix

The study relies on cross-sectional, self-reported data from Vietnamese consumers, which may limit causal interpretation and generalizability to other cultural and market contexts.

Sources

1 on file
  1. Journal of Systems and Information Technologydoi:10.1108/jsit-08-2025-0375
    Peer-reviewed2026-09-23

Cite this record

v1

Truvace Impact Record TRV-2026-2549, v1: “Greedy and biased algorithms in AI recommendation systems: effects on emotional arousal and impulsive buying.” Truvace, 2026-11-12. /record/TRV-2026-2549 (accessed on the day you copy it). sha256 560a712dd286b1a2…

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

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