Open-web pool
Require country, device, format, source identity and a clear trigger. Assess accidental visits and short sessions for attention-heavy units.
Use separate cells when mobile and desktop supply behave differently.
Qualify Adnium competitors against one approved inventory environment at a time. The shortlist records user context, access requirements, token depth and paid-subscription evidence.
Begin with the user environment the campaign needs: ordinary mobile or desktop supply, authenticated member-area exposure, video, popunder, direct-link flow or dating-origin clicks. A company belongs on the shortlist only for the context it can document. Broad network size and a familiar brand name do not satisfy that requirement.
Write the campaign's permitted vertical, countries, devices, destination behavior, creative restrictions and validated paid-subscription outcome before researching providers. This prevents a platform with impressive but unusable inventory from receiving a high score.
Treat advertiser buying, publisher monetization, mediation and managed service as separate roles. A product on the wrong side of the transaction may be adjacent to Adnium without being a competitor for the selected advertiser job.
| Qualification gate | Evidence required | Disposition |
|---|---|---|
| Inventory context | First-party format and user-environment description | Advance only the relevant route |
| Vertical and policy | Current rules for offer and destination | Reject unresolved prohibited use |
| Source observability | Placement or zone field plus exclusion control | Lower confidence if aggregate only |
| Business trace | Click-to-paid-subscription join | Do not rank on platform action alone |
Create one pool for open-web display or popunder inventory, one for authenticated or member-area placements, one for video, and one for deliberate direct-link or dating interactions. Add another pool only when its user trigger and creative constraints are genuinely different.
Score within a pool before comparing across pools. A member-area specialist can be the strongest option for a narrow audience while being irrelevant to broad mobile acquisition. Cross-pool ranking without a declared campaign job rewards reach rather than suitability.
Document context evidence with a screenshot, official description or live account observation. If a seller cannot identify the environment behind a placement, label it unknown and keep it outside the finalist test until the ambiguity is resolved.
Require country, device, format, source identity and a clear trigger. Assess accidental visits and short sessions for attention-heavy units.
Use separate cells when mobile and desktop supply behave differently.
Identify authentication state, community purpose, placement role and allowed message. Do not infer purchasing intent from membership alone.
Confirm that the offer and destination are appropriate for the environment.
Describe the interface action that initiates the visit and whether the destination continues the same user task.
Exclude unlabeled redirects that cannot preserve origin evidence.
Give product facts, authenticated controls and matched campaign observations separate columns. Official documentation can establish that a format or token exists. A live account can establish that the reviewed buyer can access it. Only joined campaign data can establish how it performed for the declared offer.
Use hard gates for inventory context, policy, destination behavior and essential tracking. Apply weighted scoring only after those gates pass. Suggested weighted dimensions include source exclusion, cost visibility, creative control, frequency, payment route, support response and completeness of the paid-subscription join.
Mark not verified when research or access is incomplete. Reserve not available for a conclusion supported by current first-party or authenticated evidence. This distinction prevents a poorly documented platform from being rejected as incapable and prevents an unsupported feature claim from entering the score.
| Evidence class | Supports | Does not support alone |
|---|---|---|
| Official product page | Documented format or workflow | Access for this account |
| Authenticated control | Observed capability and current condition | Universal availability |
| Matched source test | Result for one inventory cell | Network-wide quality ranking |
| Independent commentary | Research lead or risk question | Commercial or technical fact |
Select the smallest set of finalists that passes the same context and policy gates. Freeze the offer, landing page, country, device, subscription price, validation rule and review delay. Adapt creative only as the format requires, and record why the adaptation preserves the same promise.
Capture source or zone distribution daily. If a platform changes the inventory basket while the test runs, split the interval. Compare qualified sessions, paid subscriptions, reversals, complaints and operator workload alongside media cost.
Use a predefined evidence floor and loss limit. A candidate with too little eligible volume remains inconclusive; it does not automatically lose. A candidate that violates policy, obscures source origin or cannot maintain the conversion join fails regardless of early conversion rate.
Store the exact product URL, account role, format evidence, review date and exclusion reason for every candidate. An exclusion caused by unavailable account access has a different reopening trigger from an exclusion caused by an incompatible user context.
Update the affected row when a platform adds a format, changes policy, exposes new tokens or alters commercial access. Do not republish the same ranking with a new date while the underlying evidence remains unchanged.
Retain the earlier shortlist and test exports. Historical context shows why a candidate moved, prevents repeated discovery work and makes it possible to distinguish a product change from a different campaign requirement.
Measure the time required to qualify placements, review creative, maintain exclusions, investigate source shifts, reconcile conversion identifiers and resolve payment or policy questions. Two platforms with similar media cost can have different total acquisition cost when one requires substantially more manual control.
Record which tasks can be performed through stable exports or rules and which depend on support or manual interface checks. A feature that exists but cannot be audited at the required cadence may not satisfy the operating requirement.
Convert recurring work into a comparable period cost without inventing precision. Use staff time ranges, escalation counts and unresolved-case age. Keep these operational figures beside paid-subscription results, not inside the media CPM.
| Operating task | Evidence | Comparison effect |
|---|---|---|
| Source review | Zones inspected and exclusions applied | Quality-control workload |
| Compliance | Approvals, rejections and response time | Launch and interruption risk |
| Data repair | Unmatched events and reconciliation time | Confidence and staffing cost |
| Finance | Payment and balance exceptions | Capital administration |
Recalculate the finalist order under at least three declared weight sets: strict source observability, lowest capital exposure and strongest specialist-context fit. Keep the hard gates fixed. A candidate that wins only because one subjective weight is unusually high should be presented as conditional rather than best overall.
Run a missing-data sensitivity check. Replace every not-verified score first with the lowest defensible value and then with the highest defensible value. If the winner changes, the next action is evidence collection, not budget allocation.
Model operational capacity explicitly. A small team may rationally choose a platform with clearer source controls over a marginally cheaper candidate requiring constant manual review. A specialist team may accept that workload for access to an inventory environment unavailable elsewhere.
Document the final job assignment for every selected provider. One may own member-area acquisition, another open-web discovery and another a controlled retargeting stage. The portfolio is valid only when audience overlap, conversion credit and exclusion responsibilities are named.
Before signing the shortlist, ask each evidence owner to confirm that cited product access and commercial terms still apply to the intended account. Record unanswered questions as launch prerequisites. The ranking should never convert an unverified capability into a promised feature merely because the candidate scores well elsewhere.
Schedule a post-test review that compares the predicted operating burden with actual source investigations, compliance work and reconciliation time. This closes the loop between selection criteria and daily use.
Archive candidate responses and the account route used to obtain them so future reviewers can verify whether a later product change is real.
A provider serving the same advertiser job in the required inventory environment with acceptable policy, source evidence and downstream measurement.
No. Open-web, member-area, video and deliberate-click contexts should be qualified in separate pools.
No. The relevant supply must be accessible, policy-compatible, observable and testable for the chosen campaign.
Use not verified until current first-party or authenticated evidence establishes availability or absence.
Apply role, inventory context, vertical policy, destination behavior, essential tracking and payment-access gates before weighted scoring.
Keep offer, market, device, landing experience, subscription definition, validation delay and attribution rule stable.
Not always. Adapt to the format while preserving the same truthful promise, and document the change.
Join placement or zone delivery to qualified sessions, paid subscriptions, reversals and complaints after the stated maturity window.
Yes, if each has a distinct portfolio job and audience overlap or duplicate attribution is controlled.
A changed format, policy, token set, account route or campaign requirement triggers a targeted evidence update.
The Adnium shortlist uses help-center evidence captured on to classify candidates by inventory environment before platform name. Zone context, popunder permission, available tracking tokens and vertical rules are hard qualification fields.
Do not merge member-area, dating-click and open-web options into one score. A candidate advances only for the context it can document and the offer can legitimately use.
FroggyAds product statements are based on FroggyAds documentation and live platform controls, not on the external sources listed above.
Continue with a separate FroggyAds guide for this decision stage.
Continue with a separate FroggyAds guide for this decision stage.
Continue with a separate FroggyAds guide for this decision stage.
Continue with a separate FroggyAds guide for this decision stage.