VelisAds Network

Ad Delivery Policy

Effective date: February 24, 2026 | Version: 2026.02-global

This policy defines placement quality, inventory standards, and traffic integrity rules for web and app ad delivery.

Placement and Format Rules

  1. Ad placement metadata must accurately reflect real on-page position and context.
  2. Scroll feed placements must use approved vertical sizes and clear user-visible boundaries.
  3. Image and image+link creatives are supported; deceptive overlays and hidden placements are prohibited.
  4. Refresh settings must follow quality thresholds and must not create forced impression inflation.

Traffic Quality and Enforcement

  1. Invalid traffic, bot amplification, and click manipulation are strictly prohibited.
  2. Rate-limit and geo/device controls must be respected by integration implementations.
  3. Suspicious inventory can be throttled, paused, or removed from serving.
  4. Repeated policy violations can lead to campaign rejection or account enforcement.

Operational Expectations

  1. Publishers must keep install snippets and verification state aligned with active domains.
  2. Campaign settings should match approved categories, schedules, and policy declarations.
  3. Delivery anomalies should be triaged through Workflow Center and Error Center first.

Operational Interpretation and Regional Mapping

These requirements should be interpreted as global baseline controls for a live ad operations platform. Teams must map each requirement to local legal obligations, contractual duties, and traffic-source constraints before enabling production delivery at scale.

When regional regulations impose stricter standards, the stricter standard applies. Where legal ambiguity exists, operations should default to least-risk handling and documented escalation to legal or compliance owners.

Policy-to-Workflow Mapping

  • Map each policy control to one concrete workflow checkpoint.
  • Define accountable owner, review cadence, and evidence source.
  • Link policy failures to clear remediation and rollback actions.
  • Track policy exceptions with expiry and approval metadata.

Evidence and Audit Quality

  • Keep verifiable logs for approvals, enforcement, and account state changes.
  • Maintain immutable records for policy acceptance and version changes.
  • Preserve incident evidence with timestamp accuracy and actor context.
  • Support regulator and partner audits with structured evidence retrieval.

Release and Change Governance

  • Run policy impact review before major workflow or billing changes.
  • Gate high-risk releases behind compliance and security readiness checks.
  • Document rollback criteria for policy or abuse regressions.
  • Communicate material policy updates with effective-date clarity.

Extended Compliance Checklist

  1. Confirm access controls for admin, publisher, advertiser, and support roles.
  2. Verify domain ownership, sitemap coverage, and install-code integrity before launch.
  3. Validate ad creatives, landing behavior, and category eligibility rules.
  4. Ensure budget, spend, and settlement paths align with billing model selection.
  5. Run fraud and abuse controls for both ad-serving and click attribution pathways.
  6. Confirm user data handling for consent, retention, and rights-response timelines.
  7. Check payout safeguards, webhook integrity, and transaction audit visibility.
  8. Review security events, incident triage flow, and postmortem documentation quality.
  9. Ensure policy pages remain reachable, indexable, and version-consistent in sitemap.
  10. Require periodic policy refresh training for operational and support teams.

Policy FAQ for Operations Teams

How often should this policy be reviewed?

Review before each major release and at recurring governance intervals, especially when billing logic, targeting controls, or verification workflows change.

What happens if live behavior conflicts with policy text?

Live enforcement should default to safer behavior immediately, then trigger incident review and documented correction to either implementation or policy wording.

How should teams handle partner-specific requirements?

Apply partner requirements as stricter overlays where needed, while preserving baseline platform controls and maintaining auditable policy-to-process mapping.