Solutions/Website Visit → Ad
PIPELINEWebsite Visit Ad
Audience activationWeb → Paid media

Turn anonymous web traffic into addressable, verified audiences synced to your paid media.

Turn anonymous web traffic into addressable, verified audiences synced to your paid media — higher match rates, less wasted spend.

Schedule a callView usage rates
Overview

How it works

Website Visit → Ad turns anonymous traffic on your site into addressable paid-media audiences in real time. It runs as two infrastructure products in sequence: User from Page recognizes the visitor and resolves their User Agent Instance ID (UAIID) to a hashed identity, then User to Ad matches the identity to your ad platform's audience.

Each product runs its own resolution and draws on the data it needs, so a resolved visitor produces several metered events. You're billed only on OK results — Ingesting, Graphing, and Decisioning are included, and you pay on egress, per event, for what activates.

Pipeline

Signals in. Ad audience out.

Anonymous visitor
IaaSUser from Page
↳ UAIID to Hash Email
IaaSUser to Ad
↳ Hash Email to Email
Ad audience
Usage & rates

What you activate, and what each event costs.

You activate Products — the IaaS lines below. The DaaS lookups each Product triggers are included with it; they're listed here so the full cost is visible.

ProductIDProductTypeUsageIDUsageOK status
8010 User from Page IaaS 921 Action Page Visit Success
DaaS 602 ↳ UAIID to Hash Email Match
8112 User to Ad IaaS 1121 Use Case Ad Success
DaaS 579 ↳ Hash Email to Email Match

Activatable units

You switch on Products — the IaaS lines. The DaaS lookups they trigger come bundled; there's nothing separate to activate.

Shown for transparency

DaaS rates appear so the full cost is visible. On direct API access, where Products aren't bundled, the same rates apply à la carte.

OK results only

A call bills only on an OK outcome — Success for a Product event, Match when a lookup returns data. No Match and Exception aren't charged. How pricing works →

Ready to put this pipeline to work?

We'll map it to your stack and the usage you'd expect.

Talk through your use case