Truace
Subscribe
70/100

Moderate evidence

GainPublished recordLifestyleGood Space

Full story
More
Export record JSONEmailLinkedInX

Transparency Disclosure Mechanisms for AI ‐Generated Advertising on Online Platforms: An Empirical Study of User Trust and Engagement

Truvace record
TRV-2026-2608raw data (JSON)
Version
v1Published
First published
Evidence type
Randomized controlled trial
Sources
1 sourcePeer-reviewed
sha256
7e3d5d5f5e8d…check it

ABSTRACT AI‐powered ads are revolutionizing digital marketing by generating content, tailoring targeting, and leveraging data analytics for more effective promotions on platforms like social media, search engines, and other digital channels. However, transparency, authenticity, and consumer trust issues have grown considerably. Many times, when consumers do not know that ad creation is supported by artificial intelligence technologies, they react negatively to the advertisements. This study explores consumer res…

The gain

In an online experiment with 300 digitally active consumers, adding a transparency label to an AI-generated ad increased trust in the ad and its credibility.

What this doesn’t fix

The finding rests on a scenario-based vignette in an online survey of 300 consumers, not on real ad campaigns or observed purchases.

Sources

1 on file
  1. Internet Technology Lettersdoi:10.1002/itl2.70354
    Peer-reviewed2026-07-01

Cite this record

v1

Truvace Impact Record TRV-2026-2608, v1: “Transparency Disclosure Mechanisms for AI ‐Generated Advertising on Online Platforms: An Empirical Study of User Trust and Engagement.” Truvace, 2026-11-12. /record/TRV-2026-2608 (accessed on the day you copy it). sha256 7e3d5d5f5e8d1857…

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

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