aceModerate evidence
Published recordBusinessThe Trace
More
Overcoming the Uncanny Valley Effect in AI-Generated Emotional Ads: Matching AI to Ad Themes
- Truvace record
- TRV-2026-2672raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Controlled or validated comparison
- Sources
- 1 sourcePeer-reviewed
- sha256
- 5f0d075d5835…check it
Whereas perceived eeriness in an artificial intelligence (AI)-generated emotional video ad can negatively influence consumer attitudes, thematic alignment between the ad content and the use of AI can help mitigate these negative reactions. Across two experiments, we proposed and tested the AI fit attribution model in the context of AI-generated emotional advertising. Study 1 demonstrated that disclosing AI use increases perceived eeriness, which reduces emotional intensity and weakens viewers’ attitudes toward t…
60Gain side
How the two sides scoreClose call
57Problem side
The gain
In a second experiment, viewers who saw AI use match an emotional ad's theme were more likely to attribute the eeriness to creative intent rather than cost-cutting, which reduced its negative effect on attitudes.
The problem
In the first of two experiments on AI-generated emotional video ads, disclosing AI use raised perceived eeriness, which lowered the ads' emotional intensity and weakened viewers' attitudes toward them.
A fixed formula sets both scores from the evidence and its sources. Reader votes don’t move them.
What the scores mean
G is the gain side, out of 100. It goes up when the gain is specific, when it measurably helped people and when the sources behind it are strong.
P is the problem side, out of 100. It goes up when the problem is specific, when it measurably hurt people and when the sources behind it are strong.
Sources
1 on file- Journal of Interactive Advertisingdoi:10.1080/15252019.2026.2701061
Cite this record
v1Truvace Impact Record TRV-2026-2672, v1: “Overcoming the Uncanny Valley Effect in AI-Generated Emotional Ads: Matching AI to Ad Themes.” Truvace, 2026-11-12. /record/TRV-2026-2672 (accessed on the day you copy it). sha256 5f0d075d5835e4ec…
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-2672 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.