Administration
Manage ad providers, placements, and operator accounts.
Session unavailable
Your session may have expired. Sign in again to continue. No account data is shown until the server confirms your access.
Go to sign inProviders
Provider and format choices come from the server capability registry. Routing preferences are separate for Iran, non-Iran, and unknown locations.
Each rule needs at least one enabled, configured provider before saving. Providers are attempted in order, with failover staying within the same cohort and experience. Unconfigured cohorts return no ad.
Placements
Placement IDs remain stable iframe paths. Each placement has one experience and provider-specific units that must match the server capability registry.
User management
New accounts receive the operator role and must set up TOTP and change their initial password.
Iframe setup
Manage approved host-page origins in the Applications section. Only enabled application origins can frame embed and reward pages.
Application registration controls browser framing. It does not authenticate direct HTTP requests or server-to-server clients.
The URL keeps the stable placement path and includes the required experience_type parameter. Host applications must be in the approved origin list.Format samples
Previews are static and do not load live provider scripts.
Consumer applications
Register the web applications that host Akads iframes. Each origin must be an exact HTTPS origin, such as https://shop.example, with no path. HTTP is accepted only for localhost development.
Enabling an application allows its listed origins to frame Akads embed and reward pages. This is browser framing policy, not API authentication.