What a campaign is

Explains: D-B2-20, D-CPC-26, D-DIST-10, specs/003-campaign-segment#req-001, specs/013-campaign-preview-at-scale#req-002, specs/013-campaign-preview-at-scale#req-003, specs/014-publisher-feed#req-002, specs/014-publisher-feed#req-005

A campaign decides which of a customer's jobs go to which publishers, and what each publisher is paid per click. It has three parts: a segment that picks jobs from the customer's feeds, the publishers it may go to, and its bidding, which sets the publisher's price (How a campaign prices a click). A campaign may also carry a budget (Budgets).

The segment picks the jobs

Under Job segment, "Match jobs where" lists conditions on a job's fields: City, State, Country, Category, Company, Title, Location, Feed ID, Feed name and Description. Each condition is one of is, is not, contains, does not contain, is any of or is none of, and ignores upper and lower case (specs/003 REQ-001). Conditions combine as all of (AND) or any of (OR), and groups can nest: at most three levels deep and ten conditions in all (D-B2-20).

A field the job does not have counts as empty, so is not and does not contain match it. A feed with no name is matched by "Feed #" and its number (specs/013 REQ-002).

The preview shows what matches

While you build the segment, the form shows how many of the customer's jobs match and up to ten of their titles (specs/003 REQ-001). It waits until you stop typing and the condition is complete, and keeps the last count on screen meanwhile (specs/013 REQ-003). The Jobs column on the campaign list shows the same count.

A job the import marked invalid is never matched, in any campaign, whatever its bidding (D-DIST-10, D-CPC-26). Why a job is invalid explains each reason.

Which publishers receive it

Once the campaign is saved, its screen's Publishers list is where you tick who may receive its jobs. A publisher can receive them only while the campaign is active and ticked for that publisher; pausing or archiving the campaign takes its jobs out at the next build of each publisher's feed and leaves the ticks as they were (specs/014 REQ-002).

A job two campaigns match

When two active campaigns both match a job and both go to the same publisher, that publisher gets the job once, under the campaign that pays it more; on a tie, the campaign already sending it keeps it (specs/014 REQ-005). Raising the other campaign's bid above it moves the job to that campaign at the next build.