Define what traffic this vendor campaign is authorized to send. Saved here now — automatic enforcement during PING/POST is a later phase.

One per line. A bare domain (example.com) matches any page on that site; a full URL matches only that exact page. "www.example.com" and "example.com" are treated as different domains.

Inbound requirements this vendor campaign's traffic must meet — separate from Buyer Campaign lead filters.

Control when this vendor campaign is eligible to receive PING traffic, and how many sold leads it can accept per period. Leave a cap blank for Unlimited.

Counts sold leads only — not raw PING attempts. Leave blank for Unlimited.

A cap of exactly 0 blocks all traffic for that period. Leave blank for Unlimited.

Determines the maximum amount GoatPing may offer this vendor for a lead once a buyer bid is in hand. Floor Price and Ceiling Price (set on the Basics tab) still apply on top of whatever this tab calculates.

GoatPing calculates this vendor's offer automatically from the available buyer revenue, while protecting the required minimum margin below.

GoatPing already enforces a Buyer Campaign minimum margin (and any buyer vendor-rule override). Setting this adds one more requirement for this Vendor Campaign specifically — the strictest (highest) of all applicable margin requirements is always the one enforced.

Floor Price is the lowest vendor payout GoatPing will accept for this campaign — if margin/pricing can't reach it, the opportunity is skipped.
Ceiling Price is the highest vendor payout GoatPing will ever pay — a higher calculated payout is simply capped to it.
Both are set on the Basics tab.

When enabled, GoatPing rejects a lead before buyer routing if any selected field matches a qualifying lead previously received by this Vendor Campaign within the dedupe window. A match on any one of the fields checked below is enough to block it — it doesn't need to match on all of them. This only compares leads within this same vendor campaign; it never compares against other vendor campaigns.

A duplicate lead is rejected before any buyer is contacted — no buyer ever sees it, and it is never billed or recorded as sold. The rejection reply confirms which field matched (for example, phone), but never repeats back the phone number, email address, or Lead ID itself.

When enabled, GoatPing checks required lead fields and basic contact-data formatting before the lead is routed to any buyer. Leads that fail validation are rejected immediately and are not sent to buyers.

A lead that fails validation is rejected before any buyer is contacted — no buyer ever sees it, and it is never billed or recorded as sold. The rejection reply confirms which field failed, but never repeats back the value that was submitted.

Verify lead-consent and provenance data with supported third-party providers before routing the lead to a buyer.

Traffic Rules can require that a provider value is present. Verification goes further by checking that value with the configured provider before buyer routing.

Provider connection: Mock / Development

A lead that fails verification is rejected before any buyer is contacted — no buyer ever sees it, and it is never billed or recorded as sold. The rejection reply confirms which provider failed, but never repeats back the certificate URL or LeadID value that was submitted.

Choose how GoatPing routes this campaign's PINGs across its eligible Buyer Campaigns once every other check (status, geography, schedule, caps, lead filters, vendor rules, pricing and margin) has already passed. This choice never changes what makes a Buyer Campaign eligible — only which of the eligible ones GoatPing contacts, in what order, and how a winner is chosen among them.

Exactly one eligible Buyer Campaign is contacted per PING: GoatPing picks the highest-priority tier that has an eligible campaign, then deterministically splits traffic within that tier by each campaign's Distribution Weight (set per Buyer Campaign under Routing). This is the original GoatPing behavior and is the default for every campaign that has not chosen a different strategy.

GoatPing tries eligible Buyer Campaigns one at a time, in order (highest priority tier first, then each campaign's Waterfall Order, set per Buyer Campaign under Routing), and stops at the first one that returns a qualifying bid. If a buyer no-bids, errors, or its bid does not clear GoatPing's margin/pricing rules, GoatPing automatically tries the next eligible campaign instead of giving up.

GoatPing contacts every eligible Buyer Campaign for this PING, waits for each to respond, and compares only the bids that qualify (clear the buyer's minimum bid and GoatPing's own margin/pricing rules). The campaign that produces the best qualifying result for GoatPing wins and is the only one that receives the Vendor POST; every other buyer's bid is recorded in the trace but never contacted again for this lead. Priority tier and Distribution Weight are not used by Auction — every eligible campaign gets a chance to compete.