Auctionly

A complete campaign manager

Advertisers, publishers and campaigns, on your own server.

Auctionly is a complete campaign manager: the bidder, publisher portal and billing for buying and selling push, pop, domain redirect and deeplink traffic. Buy from ad exchanges over OpenRTB 2.5 with a bid out in under 100 ms, or from publishers you onboard yourself, who send visitors through a tracked link with their own sub ID and click ID. Every click, conversion and dollar stays on a server you control.

View docs

You deploy it. You own the database. Nothing phones home.

publisher linkno ad tag, no ad server
GET /r/z-4f2a91c07b
  ?adv=5&floor=0.005&sig=hmac
  &sub=push_us_1&clickid=a81f2c…&keyword=intel_i5
  &product_url=https%3A%2F%2Fbrand.com%2Fp%2F1
redirect302 · served from Redis
Location: https://network.example/go
  ?url=…brand.com%2Fp%2F1&cid=35f1668d…&camp=1

click booked · advertiser debited · publisher credited, once
no campaign takes it → the link's fallback URL
conversion postbackfrom the advertiser's network
GET /conversion?click_id=35f1668d…
  &event=purchase&value=25&tx=order-1
{ "status": "recorded" }

matched to the click → counted → publisher postback
LanguagePHP 8.3
ProtocolOpenRTB 2.5
RuntimeDocker-native
DataPostgreSQL, Redis, Elasticsearch
PaymentsStripe and bank transfer
Static analysisPHPStan level 8
How it works

From funded wallet to billed visit.

Advertisers, and two ways to bring supply: exchanges over OpenRTB, or publishers you onboard directly. One event stream either way. Each step writes to rtb:events, so billing and reporting read the same facts the bidder produced.

  1. STEP 1

    Advertisers fund and launch

    Sign up, add funds by card or bank transfer, create a campaign in one of four formats: push, pop, domain redirect or deeplink. It reaches the bidder about three seconds after you save it.

  2. STEP 2

    Supply arrives from exchanges or publishers

    An exchange registers once and posts OpenRTB 2.5 to its own /bid/{exchange} endpoint. A publisher verifies a site and makes a link in the Link generator, with its own sub ID, click ID and keyword.

  3. STEP 3

    A campaign is picked, billing happens once

    Exchange traffic runs an auction inside the exchange's tmax. Publisher traffic goes to matching campaigns in turn at their fixed prices. The aggregator debits the wallet and credits the publisher one time per visit.

Life of one exchange bidEvery hop is HMAC-signed
  1. Bid/bid/{exchange}Auction runs against in-memory campaigns.
  2. Win/winExchange reports the clearing price. Wallet is debited, once.
  3. Pixel/pixelThe push is shown and the view is confirmed.
  4. Click/clickRedirect to the advertiser's page, click recorded.
  5. Conversion/conversionPostback matched to the click inside its window.
Billing event. A win delivered twice is charged once. rtb:events Aggregator writes stats and spend. Indexer writes each event to Elasticsearch.
Life of one publisher visitNo auction, no ad tag
  1. Link/r/{zone}The publisher's link, with its sub ID, click ID and keyword, is opened.
  2. ChecklimitsA real browser, within the visitor, address and zone limits. Bots are not sold.
  3. PickrotationMatching campaigns take turns, each at its own fixed price.
  4. CountvisitThe visit is the view and the click. Advertiser debited, publisher credited, once.
  5. Land302Redirect to the advertiser, or its network, with a click id. The sub ID and click ID stay on the click.
Pop, domain redirect and deeplink traffic counts the view and the click in one visit. /r/{zone} The same event stream feeds billing, publisher earnings and reports.
Life of one conversionReported by the advertiser's side
  1. Click idcidThe platform hands its click id to the advertiser's network in the destination URL.
  2. Salebrand siteThe visitor buys. The brand confirms the sale to its network or tracker.
  3. Postback/conversionThe network calls the platform with the click id it kept, the event, the value and a transaction id.
  4. CreditconversionMatched to the click inside its window and counted. A campaign can hold it for approval.
  5. Publisher{clickid}The publisher's own click id goes back to its tracker in a postback.
The platform learns about a sale only when the advertiser's side calls it. /conversion?click_id=… A pixel and an API call work too, for advertisers without a network.
Ad formats

Four formats, one campaign form.

Pick a format and the form asks for exactly what that format needs. The web form and the REST API share one rule set, so neither can save a campaign the other would refuse. The platform sells traffic: there are no banners, video or ad sizes to manage.

PushpushNotification title, body, icon and a destination URL. Sent to exchanges as an OpenRTB native ad.
PoppopA destination URL. No creative to host.
Domain redirectdomainA destination URL for redirect traffic, such as parked and type-in domains sent straight to the offer.
DeeplinkdeeplinkA network or tracker deeplink with {product_url} where the product page goes. The visit brings the page.

Through exchanges all four run. Publishers you onboard directly sell pop, domain redirect and deeplink through a tracked link. Push stays on OpenRTB.

OpenRTB objects cannot tell these formats apart, so an exchange either sends imp.ext.adformat on each impression or is registered with the one traffic type it sells.

Deeplinks, the way networks do them

  • No product page in the campaign. The advertiser keeps a place for it with {product_url}, as the value of one parameter.
  • The visit brings the page. The platform fills it in, URL-encoded, and redirects to the network or tracker, which forwards the visitor.
  • Only the brand's own site. A product page on another website is not sold, so a publisher cannot send traffic anywhere else through a deeplink.
  • Checked when saved. A destination where the tag would replace part of the address is refused, and the form links to a guide with the parameter of each network.
destination URL of a deeplink campaignexample
# the network's deeplink, parameter replaced
https://network.example/deeplink
  ?offer=12
  &url={product_url}
  &cid={click_id}&camp={campaign_id}

visit brings https://brand.com/p/1
→ …?offer=12&url=https%3A%2F%2Fbrand.com%2Fp%2F1
Billing

Card or bank transfer. Credited when the money is real.

Advertisers fund a prepaid wallet. Spend is debited as visits, clicks and conversions are booked, at the campaign's price, and a campaign pauses when its funds run out. You choose which funding methods to switch on.

Card via Stripe

stripe checkout
  1. Advertiser pays on Stripe's hosted checkout.
  2. Stripe confirms with a signed webhook.
  3. Wallet is credited. Never because a browser said so.
  • A worker asks Stripe about anything still pending every minute, in case a webhook was lost.
  • A refund in Stripe debits the wallet.
  • No Stripe SDK. The app calls Stripe's HTTP API directly, so there is less code to audit.

Bank transfer

admin approved
  1. Advertiser requests a top-up and sees your bank details.
  2. You check your account and enter the amount received and the bank reference.
  3. Wallet is credited once you approve.
  • Requests nobody approves expire on their own.
  • Leave your bank details empty and the option disappears. Run card-only or transfer-only.
  • Implausible amounts are refused, and every confirmation or rejection lands in the audit log.
Minimum top-up
$10
Maximum top-up
$10,000
First top-up cap
$500
Billing and tax details
advertisers and publishers

Limits are defaults you can change in the environment file. The first-top-up cap applies until an advertiser's first payment has settled, which limits the damage from a stolen card. The wallet balance shows in the top bar, with a warning when it will not cover the recent daily spend. Every credited top-up has a printable receipt with your company details.

Architecture

Built for scale, not demos.

The path that answers an exchange is kept small and separate from everything that can be slow.

Hot path · answers the exchange

exchangepublisher linkbidderredis

The bidder reads campaigns from memory and Redis, for exchange bids and publisher visits alike. It never opens a database connection, so a slow Postgres cannot slow a bid.

Cold path · money, reports, admin

campaign-managerpostgresaggregatorindexermonitorelasticsearchreportingoptimizer

Campaigns, wallets and users live in PostgreSQL. Events flow through a Redis stream to the aggregator and the indexer, at their own pace.

Redis only on the bid path

Campaigns are held in memory. The bidder has no database driver in its request loop.

Exactly-once billing

A visit delivered twice is charged once. The aggregator books each batch and its stream position in one transaction, so a crash or a redelivery cannot bill twice. Only one aggregator may run, and a lock enforces it.

Bad events cannot stall billing

An event that keeps failing is set aside after three tries in a quarantine list, so the rest of the stream keeps flowing and you are alerted.

Redis can be rebuilt

The campaign snapshot and today's spend counters are rebuilt from PostgreSQL. Only events not yet read by the aggregator live in Redis alone, and the monitor watches how old they are.

Under 100 ms target

A per-request deadline is derived from the exchange's tmax. make latency measures it with wrk on your hardware.

Fuzz-tested input

Seeded random malformed bid requests must never crash the parser or the auction. make fuzz

Chaos-tested outages

Redis, Postgres, Elasticsearch, mail and a killed worker are injected on purpose. make chaos

Fails in the exchange's favour

If Redis is down, win notices answer 503 so the exchange retries instead of losing the sale.

Images stay off the app server

Push icons and images are served from a media domain by Caddy straight from disk, with immutable caching. Point a CDN at it when traffic grows.

Publishers do not slow the bidder

Zones live in their own Redis hash, are fetched on demand and cached for seconds. A new zone never makes every bidder reload the campaigns.

Money is bounded per zone

Daily ceilings per address and per zone cap what any one zone can cost advertisers, whatever a script does. DIRECT_VISITS_PER_ZONE_PER_DAY

Every click is kept for two jobs

Counts and spend go to PostgreSQL for billing. The raw click goes to Elasticsearch for search and reports, kept 90 days by default.

Inside the box

Everything a campaign manager needs, in one repository.

Every service, one shared kernel, one Docker Compose file. Read it, change it, ship it.

campaign-manager

Web app and REST API

One campaign form with four ad-format cards, budgets, bid hierarchy, delivery limits, creatives, targeting and conversion setup. The API enforces the same rules.

reporting

Reports on every dimension

Totals, time series and breakdowns by campaign, day, hour, exchange, bid level, creative, country, OS, device, site, publisher, ad format, zone and sub ID. CSV export and event-log search.

optimizer

Bids that follow results

Give a campaign a CPA or CTR goal and a bid multiplier moves toward what converts, without anyone touching the bid.

links

Link generator and Test link

A publisher makes a link for an advertiser and a site, with a sub ID, click ID, keyword, bid floor and fallback URL. Test link shows where a visit would be sent and counts nothing.

sub ids

Sub IDs, click IDs, keywords

Everything a publisher puts on a link is stored with the click. Reports by sub ID and by sub ID per site, a click-level report, and allow and block lists by sub ID per advertiser.

placements

Whitelist, blacklist, bid per zone

Block or allow sources and placements, share large lists between campaigns, and set a bid for one zone straight from the report.

tracking

Destination tags and postbacks

Insert tags like {click_id}, {zone}, {country} and {product_url} into destination URLs. A postback builder writes the conversion URL for the advertiser's network or tracker.

deeplinks

A guide inside the form

The deeplink form links to a guide with the landing-page parameter of each affiliate network, and refuses a destination where the product tag would break the address.

limits

Budgets, pacing, caps

Daily and lifetime budgets, pacing, frequency caps, schedules, impression and click limits. A campaign that hits one pauses and records why.

metrics

Operable from day one

The bidder serves /health, a /ready that checks Redis and the loaded campaigns, and Prometheus /metrics: requests by exchange and outcome, rejections by reason, lost events, a latency histogram.

mail

Queued email with retries

Sign-up, password reset and payment email goes through a queue with retries after 1, 2, 4 and 8 minutes. Bodies are erased once sent.

demo

Realistic data in one command

make seed creates an admin, advertisers, campaigns, publishers with links and 30 days of traffic. make fresh gives an empty install with three logins and one test campaign, for local testing.

review

Approve before it bids

An advertiser's campaign waits in review until you approve it or send it back with a note. Trusted advertisers can skip it.

receipts

Receipts, Terms, Privacy

Every credited top-up has a printable receipt with your company details. Sign-up records which version of the Terms was accepted.

publishers

Portal for sites, links and payouts

Publishers sign up, add a site, make links and read their reports. Earnings, payout progress and billing details are in their own area, and an X-API-KEY API does the same by script.

verification

Ownership proven before traffic

A meta tag, a file or a DNS record proves a site is the publisher's. You approve it, and only then can it make links.

conversions

Hold, approve, reverse

A campaign can hold conversions for the advertiser's approval. Approved ones can later be reversed, and the wallet and the publisher's earnings are corrected with explicit adjustment rows.

monitor

Alerts before customers notice

A monitor checks event backlog, aggregator lag, lost events, errors and backups. A System page shows ok, warn or critical, and a webhook tells you when it changes.

ledger

Books that reconcile

Money is booked in whole micro-dollars by one aggregator. make reconcile-ledger proves every wallet equals its ledger, and make restore-drill restores a backup into a scratch database to prove it works.

media

Push images and a CDN-ready domain

Upload push icons and images in the form or with POST /api/v1/media. Serve them from their own domain, cached for a year, with a CDN in front when you need one.

environments

Local and production, one switch

APP_ENV=local lifts the click limits and accepts localhost as a site, to test with many clicks. Production keeps the limits and never accepts it, and the go-live check fails otherwise.

For advertisers

Self-serve buying, with the controls media buyers ask for.

Supply
Buy from exchanges, from your own publishers, or both, per campaign. Publisher-only campaigns pay a fixed price per visit, click or conversion.
Wallet
Fund by card (credited only after Stripe confirms) or by bank transfer approved by an admin.
Targeting
Geo (country to ZIP), device, OS, carrier, domain, app, zone, sub ID, category, keyword, audience.
Conversions
Postback builder, a window per campaign, and conversions that keep the click's format, zone and country. Hold them for your approval, and reverse one later if it turns out to be fake.
Attribution
Six attribution models.
Limits
Daily and lifetime budgets, pacing, frequency caps, schedules.
REST API
Token-based, using the same validation as the web form.

Bid hierarchy · most specific wins

  1. Zone z-100
  2. Site, app or publisher news.example
  3. Category IAB12
  4. Exchange xyz-ssp
  5. Campaign default bid

Pay more on the zone that converts, and the default everywhere else. Ties are split at random.

Quality control

Every campaign is reviewed before it bids.

Advertisers cannot put a campaign live by themselves. You decide what runs on your network, and the advertiser always hears the outcome.

  1. SUBMITTED

    Save and submit

    The advertiser presses submit. The campaign is In review and does not bid.

  2. YOU ARE TOLD

    Email and a queue

    Administrators get an email and see it on the dashboard, in the In review tab and as a count in the navigation.

  3. DECIDED

    Approve or send back

    Approve and it bids within seconds. Or send it back to draft with a note, which the advertiser is emailed.

  4. AFTERWARDS

    Stays approved

    Pausing and resuming needs no new review. Changing a creative or its landing URL sends it back.

  • Trusted advertisers skip the queue once you have seen their work.
  • The API follows the same rule. A token that asks for active gets 202 and pending_review.
  • One switch. REQUIRE_CAMPAIGN_REVIEW=false turns it off for everyone.
  • Every decision is in the audit log, with who made it and the note.

Why it matters. Exchanges and publishers hold you responsible for what you send. A review step is the cheapest protection against a misleading offer costing you a supply partner.

For developers

Everything in the web app is in the API too.

Ten endpoints under /api/v1, JSON in and out, one personal token per script. An advertiser's token only ever sees that advertiser's campaigns, and the same validation applies as in the form. Publishers have their own API: an X-API-KEY header, a rate limit, and endpoints for links, reports, sites, placements, sub ID lists and postbacks.

  • GET /api/v1/me

    Who the token belongs to.

  • GET /api/v1/advertisers

    The accounts you can see, with wallet balance.

  • GET /api/v1/campaigns

    List with filters, paging and sorting.

  • POST /api/v1/campaigns

    Create. The body is the campaign form.

  • GET · PUT · DELETE /api/v1/campaigns/{id}

    Read, change or delete one campaign.

  • POST /api/v1/campaigns/{id}/status

    Activate, pause, draft or archive. Activating can answer 202 while it waits for review.

  • POST /api/v1/media

    Upload a push icon or image and get its address.

  • GET /api/v1/reports/campaigns

    Spend, clicks and conversions per campaign.

upload, create, go liveexample
$ curl -X POST $BASE/api/v1/media \
    -H "Authorization: Bearer $TOKEN" \
    -F image=@push-icon.png
{ "data": {
    "url": "https://media.example.com/media/ab/3f…c1.png",
    "width": 192, "height": 192 } }

$ curl -X POST $BASE/api/v1/campaigns/123/status \
    -H "Authorization: Bearer $TOKEN" \
    -d '{"status":"active"}'
HTTP 202
{ "data": { "id": 123, "status": "pending_review" } }
For exchanges

Connect an SSP in minutes.

An administrator registers the exchange with its token, seat, network margin and traffic type. The exchange gets one endpoint.

  • A dedicated endpoint at /bid/{exchange}, token-checked, pausable.
  • OpenRTB 2.5 request, impression, device, geo, deal and native objects.
  • Deal support as a targeting dimension on each campaign.
  • Traffic-type classification for pop, push and redirect supply that OpenRTB cannot describe.
  • Win-price macro and signed win, pixel and click URLs per exchange.
  • Plain no-bids. A 204 with the reason in a header, so partners can debug.
try it locally
$ curl -X POST localhost:9501/bid/demo \
    -H 'Content-Type: application/json' \
    -d @services/bidder/fixtures/sample-bid-request.json

$ make win
# bid, win notice (sent twice), pixel, click
# wallet debited once
For publishers

Give site owners a link, not an ad tag.

Most publishers cannot speak OpenRTB. They sign up, add a website, prove it is theirs and make a link in the Link generator. There is no ad to render and no auction: matching campaigns take turns at fixed prices, and the publisher is paid on terms you set.

  1. SIGN UP

    Submit a site

    A publisher creates an account and adds the website it sends traffic from. The site waits for review.

  2. VERIFIED

    Prove it is theirs

    A meta tag, a file at the root, or a DNS TXT record. Any one is enough, and the check refuses private addresses.

  3. APPROVED

    You review the site

    Approve or reject with a reason, and the publisher is emailed. Suspend a site and its links stop at once.

  4. LIVE

    Make a link

    Only an approved site can make links. Pick an advertiser and a site, add a sub ID, click ID, keyword, bid floor or fallback URL if wanted, and copy the link.

  • One link per source. The advertiser, bid floor and fallback are signed by the platform. The publisher adds its own sub ID, click ID and keyword as query parameters, and every click is stored with them.
  • Fixed prices, no auction. Campaigns that match the visitor rotate. Advertisers pay per visit, per click or per conversion.
  • Test link. A dry run that shows where a visitor would be sent and counts nothing.
  • Reports by source. By day, advertiser, sub ID, sub ID per site and site, a click-level report with every click ID, and conversions. Allow or block sub IDs per advertiser.
  • Postbacks to its own tracker. A conversion goes back with the publisher's click ID, sub ID and payout.
  • Pay on your terms. A share of the advertiser's spend, or a fixed amount per visit, click or conversion, per publisher or per zone. Earnings are held for a few days, then paid out on request with progress from requested to paid.
  • An API of its own. An X-API-KEY header and a rate limit, for links, reports, sites, placements and postbacks.
what a publisher usesexample
<!-- a link from the Link generator -->
<a href="https://bid.example.com/r/z-9c13
  ?adv=5&floor=0.005&fb=…&sig=…
  &sub=push_us_1&clickid=a81f2c…
  &keyword=intel_i5">Open</a>

a new click id for every click, made by the publisher
site verified → link → click stored → earnings
portal

Sites, links, reports

A portal of their own: sites and their review status, the Link generator, reports by source and a dashboard of visits, clicks, conversions and earnings.

earnings

Exact, once

Earnings are credited together with the advertiser's charge, one time per visit, with the terms that applied kept on each row.

payouts

Requested to paid

A payout moves through requested, processing and paid, with a reference. The money leaves the balance when it is asked for, and comes back if it is rejected.

admin

A queue for you

Sites waiting for review, payouts to send, quality flags per zone, a click-level log with each publisher's own click ID, and a margin view of what advertisers paid against what publishers earned.

Traffic quality

When a publisher is paid for what it counts, every count is checked.

Exchanges are contracted companies. Publishers are anyone who signs up, so the platform assumes any number a publisher produces could be false and bounds what it can cost.

Verified sites only

A link works only while its site is approved. Suspending a site stops its zones at once.

Signed links

The advertiser, bid floor and fallback in a link carry an HMAC. A changed or forged link is refused.

Real visitors

Bots, crawlers and scripts are not sold. Country and device come from your edge network, not from the publisher.

Visit limits

A visitor is sold a few times a day through one zone, and addresses and zones have per-minute and per-day ceilings, whatever browser string is used.

Labels stay labels

Sub ID, click ID and keyword are the publisher's own names. They never decide who the publisher is, what it is paid or what a campaign sees.

OpenRTB off by default

A publisher's own bid requests prove nothing, so the endpoint is opt-in per zone for partners you trust.

Payout hold

Earnings are held for a few days so bad traffic can be taken back with an adjustment before the money leaves.

Quality flags

Zones with a very high click rate, no conversions, or a payout above what advertisers pay are flagged for you, with a review queue to dismiss or act on each one.

Honest limits. A redirect has no page to inspect, and a script can fake a referrer. The limits, the hold and the flags are what bound the cost, not a promise that no fake traffic exists.

Security

Money and tracking you can defend.

Two-factor, enforced

Admins must enable TOTP. Recovery codes and a 48-hour cancellable lost-phone flow.

Signed tracking URLs

Win, pixel and click URLs carry an HMAC, so they cannot be forged.

Audit log

Sign-ins, account changes and admin actions are recorded.

Stripe-confirmed only

Cards are credited after Stripe confirms. A worker reconciles lost webhooks.

Automated backups

make backup dumps the database and creatives, keeping as many as you set.

Confirmed sign-ups

Switch it on and a new account cannot sign in until it opens a one-time link. Only a button confirms, so mail scanners cannot use the link up.

Terms on record

Sign-up requires accepting the Terms and Privacy Policy, and stores which version and when.

Signed postbacks

An advertiser can require an HMAC on conversion postbacks. Without it, a click id alone is the credential, and a click can credit at most five conversions.

Privacy signals

The bidder reads TCF v2, GPP and US privacy strings and refuses to bid where consent was not given. It is on by default and set in the environment.

Tested restore

A backup you have never restored is a hope. make restore-drill restores the latest one into a scratch database and checks it.

Abuse limits

Failed sign-ins lock out for 15 minutes. Sign-up, password reset, confirmation email and uploads are rate-limited per address.

Deployment

Runs anywhere Docker does.

Every service is its own container. Start on a laptop, then move the same images to a server.

One-server quick start development

shell
$ cp .env.example .env
$ make install
$ make up
$ make migrate
$ make seed
→ campaign manager on :9502, bidder on :9501

Seeds an admin, advertisers, campaigns, publishers with links and 30 days of traffic. make traffic sends 300 requests through bid, win, pixel, click and conversion. For a local test with many clicks, set APP_ENV=local and run make fresh.

Production Caddy · HTTPS

docker-compose.prod.yml
internet → caddy :80 :443
          ├─ campaign-manager
          └─ bidder
private network only:
  postgres · redis · elasticsearch
  reporting · aggregator · indexer · monitor

Caddy is the only published service. It issues certificates, speaks HTTP/2 and limits request sizes. The written guide takes a fresh Linux server to HTTPS in about 45 minutes, plus DNS.

Go-live check before the first customer

./scripts/prod-check.shexample
  ok   DB_PASSWORD looks strong
  ok   administrators must use two-factor
  ok   Stripe is in LIVE mode
  FAIL LEGAL_REVIEWED is not true
  FAIL COMPANY_ADDRESS is empty

NOT READY: 2 blocking problem(s)

It refuses to pass while a secret is weak, debug is on, email goes nowhere, Stripe is in test mode, APP_ENV is not production or your company details are missing. The owner's guide walks from an empty server to your first advertiser.

Push images and a CDN optional

.env
MEDIA_DOMAIN=media.example.com
MEDIA_BASE_URL=https://media.example.com
# or the address of a CDN that pulls from it

uploads  →  ads.example.com   →  disk
viewers  →  media.example.com →  disk

Uploads always go to the app and are saved on your server. The media domain only reads and serves them, so push images never load from the web app.

Fully self-hosted. There is no Auctionly cloud. Campaigns, wallets, events and creatives stay on your infrastructure, and your data never leaves it.

Pricing

Buy the source. Run it as your own.

You receive the code and deploy it yourself. Choose how much help you want with it: none, ongoing support, or a white-label setup we plan with you.

Tier A

Source licence

$999 one-time

The code, sold once. No consultation and no support: you read it, you run it.

  • Full source for all services
  • One payment, no renewal
  • No consultation, no support
Tier B

Subscription

$1,499

Everything in Tier A, with a team behind it when something needs answering.

  • Everything in Tier A
  • Continuous updates
  • Support channel
Tier C

White-label

Your brand on the whole platform, with our support and consultation. The terms are agreed in a conversation, not listed.

  • Everything in Tier A and B
  • Support and consultation included
  • Price defined together

Prices are in US dollars.

Questions

Answers for people who have evaluated campaign managers and ad networks before.

Is Auctionly a hosted service?

No. Auctionly is self-hosted software. You deploy it with Docker on your own server, and your campaigns, wallets and events stay on your infrastructure.

Which OpenRTB version does it support?

OpenRTB 2.5. Each exchange gets its own /bid/{exchange} endpoint and receives a bid, win notices and tracked clicks.

How fast does the bidder respond?

The target is under 100 ms, typically a few milliseconds. The bidder never touches the database on the bid path, and it applies a deadline derived from the exchange's tmax.

Which ad formats can advertisers run?

Four: push, pop, domain redirect and deeplink. Through exchanges all four run. Publishers you onboard directly sell pop, domain redirect and deeplink through a tracked link, and push stays on OpenRTB. There are no banners, video or native ads in a page: the platform sells traffic.

Can publishers send traffic without an ad server?

Yes. A publisher signs up, adds a website, verifies it and makes a link in the Link generator. It adds its own sub ID, click ID and keyword to the link, and every click is kept with them. There is no ad tag, no OpenRTB and no auction on that path: matching campaigns take turns at their own fixed prices.

What does a publisher put on a link?

The Link generator makes the link for an advertiser and a site. The advertiser, bid floor and fallback URL are signed by the platform. The publisher adds a sub ID (its own name for the source), a click ID (its own unique id for the click) and a keyword, as query parameters. They are stored with the click, shown in the publisher's reports, and the click ID goes back to the publisher's tracker in the conversion postback. A Test link shows where a visit would be sent and counts nothing.

How does a deeplink campaign work?

The advertiser takes the deeplink made by its affiliate network or tracker and replaces the network's landing-page parameter with {product_url}, for example https://network.example/deeplink?url={product_url}&cid={click_id}. The product page comes with each visit. The platform puts it into the tag, URL-encoded, and redirects to the network, which forwards the visitor. Only product pages on the brand's website are sold, so a publisher cannot send traffic anywhere else, and a visit without a product page is not sold.

How is a conversion reported?

When a visitor buys, the advertiser's affiliate network or tracker, or its own site, calls the platform's /conversion postback with the click ID the platform gave it, for example /conversion?click_id=35f1…&event=purchase&value=25&tx=order-1. The conversion is matched to the click inside its window and counted for the campaign and the publisher. It can be held for approval or reversed later, and the publisher's own click ID goes back to its tracker.

How do you verify that a publisher owns a site?

The publisher proves it with a meta tag on the home page, a file at the root of the site, or a DNS TXT record. An administrator then approves the site, and only an approved site can make links. Suspending or rejecting a site stops its zones at once.

How are publishers paid?

On terms you set per publisher or per zone: a share of what the advertiser spent, or a fixed amount per visit, click or conversion. Earnings are credited once, held for a few days, and paid out on request, with progress from requested to processing to paid.

How do you stop fake traffic from publishers?

Bots are not sold. A visitor can be sold only a few times a day through one zone, and addresses and zones have per-minute and per-day ceilings that bound what any zone can cost. The advertiser, bid floor and fallback in a link are signed, OpenRTB is off by default for publisher zones, and earnings are held so bad traffic can be taken back. Zones with odd click rates are flagged for review.

How do advertisers pay?

They fund a prepaid wallet by card through Stripe or by bank transfer. Card payments are credited only after Stripe confirms them. Bank transfers are credited when an administrator approves the request.

Can a click be billed twice?

No. A visit, click or conversion that is delivered twice is charged once. Events are keyed by their stream id, so a redelivered event overwrites itself instead of billing again.

Can I hold conversions until I have checked them?

Yes. Switch it on per campaign and new conversions wait as pending until the advertiser approves or rejects them. An approved conversion can be reversed later, which corrects the wallet and the publisher's earnings with adjustment rows instead of rewriting history.

How is the conversion postback trusted?

By default the signed click id is the credential. An advertiser can turn on a secret and sign each postback with HMAC-SHA256, and an unsigned or wrongly signed one is refused. A single click can credit at most five conversions either way.

How do I know something is broken?

A monitor checks the event backlog, aggregator lag, lost events, errors and backups. The System page shows each as ok, warn or critical, and a webhook can notify you of a change. The bidder also has a /ready endpoint for load balancers.

Does it respect user consent signals?

The bidder parses TCF v2, GPP and US privacy strings. By default it does not bid on a request that says consent was not given for the purposes you list. You can switch it off or change the purposes in the environment, and you stay responsible for your own legal review.

What happens if Elasticsearch goes down?

Reporting falls back to PostgreSQL rollups. The dimensions that only the event log knows are then reported as unavailable, and bidding is not affected because the bidder only uses Redis.

Are campaigns reviewed before they go live?

Yes, by default. An advertiser's campaign waits in review until an administrator approves it or sends it back with a note, and the advertiser is emailed either way. Administrators can mark an advertiser as trusted to skip the review, or switch the review off.

Can advertisers and publishers use an API?

Yes. The advertiser REST API has ten endpoints for campaigns, status changes, image upload and reports, with personal tokens and the same validation as the web form. Publishers have their own API, authenticated with an X-API-KEY header and rate limited, for links, reports, sites, placements, sub ID lists and postbacks. A token only sees its own owner's data.

Do push notification images need a CDN?

Not at first. By default the web app serves uploaded icons and images. When traffic grows, serve them from a separate media domain, cached for a year, and put a CDN in front of it. Uploads always go to the app; the media domain only serves files.

Own your traffic stack.

Run the demo on your machine, then put it on your own server.

make stan · make fuzz · make chaos
$ make stan    # PHPStan level 8, every service
$ make fuzz    # malformed bid requests
$ make chaos   # kill redis, postgres, elastic

We reply by email.