TRV-2026-1903Certified recordPeer-reviewed

PUBLIC PERCEPTION AND TRUST IN AI FOR FRAUD DETECTION AND INFLUENCER AUTHENTICITY IN INFLUENCER MARKETING

The rapid growth of influencer marketing has created diverse opportunities for the brands to interact with the consumers. At the same time, concerns regarding manipulated follower counts, artificial engagement and questionable influencer authenticity have become increasingly relevant. Artificial Intelligence (AI) is used as a technological mechanism for finding skeptical patterns and supporting fraud detection. However, the use and acceptance of these systems are largely influenced by consumers’ perceptions and…

Crime · The Trace — both readings · certified 2026-10-19 · v1 · article view · machine-readable

Current reading — gain

Surveyed consumers generally support AI-based verification and favour brands using AI tools to evaluate influencers, suggesting AI can help improve authenticity in influencer marketing.

Current reading — problem

Respondents raised concerns about transparency, privacy, false identification and possible bias in AI fraud detection, and complete trust in AI was limited.

What this doesn’t fix

The findings rest on a descriptive questionnaire of only 70 respondents, so they reflect perceptions rather than measured fraud-detection performance.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1903, v1: “PUBLIC PERCEPTION AND TRUST IN AI FOR FRAUD DETECTION AND INFLUENCER AUTHENTICITY IN INFLUENCER MARKETING.” Truvace, 2026-10-19. /record/TRV-2026-1903 (accessed at citation time). sha256 4e273a01d2e6856f…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv14e273a01d2e6…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1903 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.