NEWVectors or files. Pick a path.Start →
    analytics

    Cloudflare Workers Connector

    Edge-deployed content intelligence for advertising and analytics

    A shared content intelligence layer deployed at Cloudflare's edge that provides cached content profiles for advertising, analytics, and personalization systems. Implements a 'one analysis → many consumers' model where content understanding happens once at the edge, then distributes to multiple downstream systems.

    cloudflare
    edge computing
    workers
    content intelligence
    GAM
    analytics

    Use Cases

    1

    Google Ad Manager targeting key injection

    2

    Prebid Server ortb2 configuration

    3

    GA4/GTM custom dimensions and metrics

    4

    Server-side cache pre-warming on publish

    Features

    Edge-first processing at Cloudflare infrastructure
    Cloudflare KV caching for instant profile retrieval
    Multi-format output (GAM, OpenRTB, Analytics, JSON)
    IAB Content Taxonomy 1.0 category codes (IAB1 to IAB26)
    Real-time brand safety and sentiment scoring
    Privacy-focused with no cookies or PII

    Get Started

    Integrations

    Cloudflare Workers
    Cloudflare KV
    Google Ad Manager
    Prebid Server
    GA4
    GTM

    Details

    LicenseApache 2.0
    Categoryanalytics

    Resources

    Documentation

    Learn how to use this connector

    Quick Info

    LicenseApache 2.0
    Categoryanalytics

    Frequently Asked Questions

    What is the Cloudflare Workers Connector?

    The Cloudflare Workers Connector is an edge-deployed content intelligence layer that analyzes content once and distributes cached profiles to multiple downstream systems. It runs on Cloudflare's global edge network, providing low-latency content analysis for advertising, analytics, and personalization use cases.

    How does the caching strategy work?

    Content profiles are stored in Cloudflare KV after initial analysis. Subsequent requests retrieve the cached profile instantly from the edge location nearest to the user. Cache TTL is configurable (default 3600 seconds), and you can invalidate profiles when content is updated.

    What output formats are supported?

    The connector supports multiple output formats: GAM format for Google Ad Manager targeting keys, OpenRTB/Prebid format for header bidding integration, Analytics format for GA4/GTM/BigQuery, and raw JSON for custom integrations.

    How do I integrate with Google Ad Manager?

    Fetch the profile from the /v1/profile/gam endpoint before loading ads, then apply the returned targeting keys using googletag.pubads().setTargeting(). The profile includes IAB categories, brand safety scores, and sentiment data formatted as GAM key-value pairs.

    Does this replace my ad tech stack?

    No, the worker is designed to complement your existing stack, not replace it. It does not make bid decisions, store user identifiers, or execute client-side JavaScript. It provides content intelligence that your ad servers, analytics platforms, and ML services can consume.

    Related connectors

    n8n Workflow ConnectorMultimodal AI processing for workflow automationPrebid.js RTD AdapterPrivacy-first contextual targeting for header biddingIAB Content Taxonomy MapperMigrate content taxonomy from IAB 2.x to Content Taxonomy 3.1LangChain IntegrationGive your AI agents eyes, ears, and memory

    Ready to integrate?

    Get started with Cloudflare Workers Connector in minutes. Check out the documentation or explore the source code on GitHub.