How AdServeKit Works

AdServeKit is a direct digital advertising and analytics platform designed for direct partnerships between website owners (Publishers) and brands or marketers (Advertisers).

Unlike traditional ad networks that insert opaque middle layers, arbitrary algorithms, and heavy revenue cuts, AdServeKit connects buyers and sellers directly. Publishers maintain full control over which ads run on their properties, and advertisers know exactly which websites and ad slots their ads appear on.

Every AdServeKit account operates within a Workspace. A single workspace can act as a publisher, an advertiser, or both — for example, monetizing your own websites while simultaneously running promotional campaigns across partner sites.

Digital advertising involves two primary roles. Understanding which role you are playing determines which tools and workflows you will use most often:

- The Publisher: You own or manage a digital property (such as a website, blog, or publication). Your goal is to monetize your audience by displaying advertisements in dedicated spaces on your pages, either for your own internal promotions (house ads) or for external sponsor deals.

- The Advertiser: You represent a brand, business, product, or agency. Your goal is to reach relevant audiences by designing ads and configuring campaigns that run across publisher websites.

In AdServeKit, publishers and advertisers collaborate directly: an advertiser sets up a campaign, a publisher designates an ad slot, and a secure relationship called a Campaign Connection links the two together.

Everything in AdServeKit revolves around five core objects. They work together in a logical chain, but each has a distinct purpose and they are not interchangeable:

1. Website (Publisher side): A publisher-owned website registered and verified in AdServeKit. It represents the property where advertising inventory will be created and ads may eventually appear. Answers: 'Which site owns this advertising space?'

2. Placement (Publisher side): A specific advertising location or slot on a publisher's website (for example, a header banner, a sidebar rectangle, an in-article slot, or a footer banner). A placement defines supported dimensions (such as 300x250 or 728x90), lazy-loading rules, and empty-slot behavior. Answers: 'Where can the ad appear?'

3. Creative (Advertiser side): The actual visual or interactive advertisement visitors see (for example, an image ad, a video ad, an animated graphic created in the Advanced Studio, or a custom HTML5 bundle). Answers: 'What does the visitor see?'

4. Campaign (Advertiser side): The advertiser's operational delivery configuration and rulebook. A campaign connects one or more published creatives with flight dates, timezone-aware schedules, device and country targeting, frequency capping per visitor, and delivery budgets. Answers: 'When, where, and under what rules should this creative run?'

5. Campaign Connection (The Bridge): The authorized relationship that allows an advertiser's campaign to deliver through a publisher's approved placement. It acts as the secure bridge between the advertiser and publisher, allowing ads to serve without sharing private accounts or workspace credentials. Answers: 'Which publisher inventory is this advertiser campaign allowed to use?'

Understanding how an ad moves from initial creation to a visitor's screen helps demystify the platform:

Publisher hierarchy: Website → Placement → Ad appears here.

Advertiser hierarchy: Creative → Campaign → Campaign Connection.

The connected delivery flow: Creative → Campaign → Campaign Connection → Publisher Placement → Website Visitor sees ad → Analytics → Billing.

Because each object is modular, changing one does not disrupt the others: an advertiser can edit an ad headline without recreating the campaign schedule, and a publisher can adjust page layout styling without modifying the advertiser's campaign.

The AdServeKit Marketplace is the discovery and commercial layer of the platform. It provides an open, searchable directory where publishers list verified advertising spaces and advertisers find relevant audiences.

How it works: Publisher lists inventory → Advertiser discovers publisher → They message to agree on terms → Campaign Connection is created → Campaign delivers.

Clear boundary: The Marketplace itself is not the ad slot (placement) and not the campaign. It is the commercial discovery and negotiation space where relationships begin.

AdServeKit includes an integrated invoicing and accounts-receivable ledger built specifically for digital advertising agreements.

The plain-English commercial flow: Advertiser and publisher agree on terms → Ads run on publisher placements → Delivery and impressions are measured → Invoice is issued → Payment status is tracked.

What AdServeKit does: Creates sequential, professional invoices, generates print-ready PDF and standard electronic UBL XML files, provides private online customer review links (/invoice/[token]), and tracks payment status (Draft, Issued, Paid, Void).

What AdServeKit does NOT do: AdServeKit is not a payment merchant or escrow service. Advertisers transfer funds directly to publishers via bank transfer, wire, or PayPal according to the instructions on the invoice. Once payment arrives, the publisher records it in their dashboard ledger to mark the invoice as Paid.

AdServeKit provides clear, real-time analytics for both publishers and advertisers. Here are the core concepts explained simply:

- Impressions: The total number of times an ad was requested, successfully delivered, and rendered on a visitor's screen.

- Viewability: The percentage of rendered ads that were actually seen by visitors. AdServeKit uses the industry-standard threshold: at least 50% of the ad area must remain visible on screen for at least 1 continuous second.

- Clicks: The number of times visitors clicked an ad to visit the destination landing page.

- CTR (Click-Through Rate): The percentage of impressions that resulted in a click (Clicks ÷ Impressions × 100%).

- Conversions: Meaningful business outcomes completed on the advertiser's website after clicking an ad (such as account sign-ups, newsletter subscriptions, or purchases).

- Spend: The advertiser's accumulated advertising cost based on the campaign's agreed billing rate (e.g., CPM rate or flat fee).

- Revenue: The publisher's earnings generated from running the campaign.

- Delivery Progress: Real-time progress tracking of flight dates, daily spend caps, and overall budget pacing.

Advanced measurement concepts (such as attribution query parameters, transaction deduplication, and SDK internals) are documented in dedicated reference guides.

To see how all these pieces fit together, consider this realistic example:

1. A hiking and outdoor review website (Summit Trails) registers their website in AdServeKit, verifies domain ownership, and creates a 300×250 placement named 'Gear Review Sidebar'.

2. An outdoor gear brand (Alpine Footwear) designs a 300×250 creative in the AdServeKit Studio featuring their new trail boot.

3. Alpine Footwear creates a campaign with flight dates for the spring season, sets a $500 budget cap at a $10 CPM rate, and attaches their published 300×250 creative.

4. Alpine Footwear discovers Summit Trails on the AdServeKit Marketplace. They agree via direct messages to run the campaign, and Alpine Footwear generates a Campaign Connection code.

5. Summit Trails accepts the connection code in their dashboard, assigning it to their 'Gear Review Sidebar' placement.

6. When a reader visits Summit Trails to read a trail guide, the publisher's page tag requests an ad. AdServeKit matches the active connection and serves the Alpine Footwear creative into the sidebar slot.

7. The visitor sees and clicks the ad. Both Summit Trails and Alpine Footwear immediately see the impression and click in their respective real-time analytics.

8. At the end of the month, Summit Trails generates an invoice in AdServeKit for the delivered impressions. Alpine Footwear pays Summit Trails directly via bank transfer, and Summit Trails marks the invoice as Paid.

Now that you understand the platform concepts and how the objects connect, choose the setup guide for your role:

- If you are a Publisher wanting to connect your website and show ads: Read the Connect a website guide.

- If you are an Advertiser wanting to build campaigns and buy inventory: Read the Create a campaign guide or the Buying on the Marketplace guide.