Raptive

Overview

Raptive (formerly AdThrive and CafeMedia) is a premium publisher ad management platform that handles the full programmatic advertising stack for content creators and media publishers. It appears on publisher websites as a header bidding wrapper and ad serving orchestration layer, coordinating bids from dozens of demand partners to maximize CPM revenue. Raptive manages the ad infrastructure for thousands of independent publishers across lifestyle, food, parenting, and similar verticals.

What This Script Does

Raptive loads a header bidding wrapper script — typically served from ads.raptive.com or a publisher-specific subdomain — that initializes before page content renders to run prebid auctions. The script contacts multiple demand-side platforms and ad exchanges simultaneously to collect bids, then passes the winning bid to the ad server (typically Google Ad Manager via GPT).

Cookies set include persistent audience segmentation cookies (180–365 day expiry), frequency capping cookies, and consent signal storage. Common cookie names follow patterns like raptive-*, cto_* (Criteo, a common demand partner), and standard IAB TCF consent strings stored in euconsent-v2. The script reads and writes to localStorage for identity resolution and bid caching.

Domains contacted extend well beyond Raptive's own infrastructure: header bidding calls go out to AppNexus (ib.adnxs.com), Index Exchange (casalemedia.com), Rubicon (rubiconproject.com), OpenX (openx.net), and others depending on the publisher's demand partner configuration. The script collects browser fingerprint signals, viewport dimensions, scroll depth, content category signals inferred from page metadata, and any available user identity signals (cookie-matched or email-hashed).

Raptive participates in the IAB TCF and passes consent signals downstream to demand partners. The platform also supports Google's Additional Consent specification for vendors not on the IAB GVL.

Consent & Compliance

Raptive's core function — behavioral ad targeting, audience profiling, and cross-site tracking for advertising — falls squarely under IAB TCF Purposes 1 (Store/access device information), 3 (Create a personalised ads profile), 4 (Select personalised ads), 7 (Measure ad performance), and 9 (Apply market research to generate audience insights).

Under GDPR and the ePrivacy Directive, all persistent tracking cookies and cross-site data collection require prior consent under Article 6(1)(a). Legitimate interest cannot be relied on for creating behavioral advertising profiles (IAB TCF Purpose 3 and 4 require consent). Under CCPA/CPRA, sharing audience data with ad demand partners constitutes a "sale" or "sharing" of personal information, requiring opt-out rights and clear disclosure in a privacy notice.

The EU-US Data Privacy Framework (DPF) is relevant for Raptive and its US-based demand partners processing EU visitor data. Publishers using Raptive must ensure their consent management platform integrates with Raptive's TCF-compliant consent signals.

The consent category is marketing.

Should You Block This Without Consent?

Yes. Raptive's header bidding infrastructure loads persistent tracking cookies, contacts dozens of third-party ad tech domains, and builds behavioral audience profiles before the user has any opportunity to consent. Loading it without prior consent violates ePrivacy Directive requirements and GDPR Article 5(1)(a) (lawfulness, fairness, transparency). Publishers must gate Raptive script initialization behind a valid TCF consent signal.