Buyer Groups

Why Groups Exist

A buyer group is a container that applies shared configuration
to multiple buyers at once. Groups are used when a set of
buyers share a routing priority, caps, business hours, or
conversion rules, and the operator wants to configure those
rules in one place.

Group Tier and Weight Override the Buyer's Own

When a buyer belongs to a group, the group's tier and weight
override the buyer's tier and weight during routing. This is a
deliberate inheritance model: configuring priority at the
group level is more maintainable than configuring it per
buyer. If you want a buyer within a group to deviate in
priority, you must remove it from the group or put it in a
different group.

Tier, Weight, and Routing

The offer's router walks buyers in order of tier (ascending),
then weight (descending) within a tier. A lower tier number
means higher priority. Weight is used to distribute load among
buyers of the same tier: a buyer with weight 3 gets roughly
three calls for every one call a weight-1 buyer gets in the
same tier.

Route-By-Type and Negative Tier

An offer can be configured to route by revenue or EPC
(earnings per call). When this is set, the router computes a
synthetic tier value for each buyer based on that buyer's
historical revenue or EPC and uses the synthetic value instead
of the configured tier. The synthetic value is negated (so
higher revenue becomes a lower tier number, which sorts
earlier), which is why you will see negative tier values in the
runtime debug logs for revenue- or EPC-routed offers. This is
expected and not a bug.