Operational Workflow
How VelisAds takes a domain from signup to safe ad delivery.
The workflow is structured around verification, policy readiness, delivery controls, creative review, live reporting, and settlement-safe payments so teams do not depend on manual memory or undocumented steps.
Step 1 to 3: onboarding and verification
- Create an account and register a real public website domain.
- Add a sitemap so the system can inspect policy coverage and structural quality.
- Verify domain ownership through supported methods before ad serving can begin.
- Install the publisher script and keep the code live on the approved website.
Step 4 to 6: delivery controls and launch
- Configure ad delivery controls such as placement, quantity, platform, and refresh rules.
- Create campaigns with budget, bidding model, category targeting, and creative details.
- Pass policy review and final verification before campaigns become eligible for live delivery.
- Use reports and diagnostics to optimize performance after launch.
Why the workflow is built this way
- Ownership verification reduces fake-domain abuse and prevents silent traffic leakage.
- Policy page discovery helps preserve ad-quality and compliance standards before monetization starts.
- Ledger-backed payments make add-funds, refunds, withdrawals, and provider mismatches auditable.
- Archive retention keeps website and ad-rule history available until settlement windows complete.
Search and launch readiness checklist
- Use HTTPS domains with crawlable policy pages and stable page load performance.
- Keep title tags, descriptions, and public content pages aligned with real product capabilities.
- Ensure campaign landing pages and creative assets are public, fast, and policy compliant.
- Monitor reports, reconcile pending payments, and settle completed campaigns on time.
Common questions
- Most teams can complete setup in one working session if their site and policy pages are ready.
- Campaigns do not stay live forever; end-dated campaigns can be settled automatically.
- Unpaid add-funds requests do not remain pending forever; they expire after the configured window.
- Payout methods need complete beneficiary details before automated withdrawals can run safely.
Next actions