Direct answers, first sentence rules.
Every answer starts with the answer. Numbers appear only where they are real policy; everything else stays qualitative until it can be stated exactly.
Direct answers · numbers only when real
Onboarding
A standard mobile integration with the SDK runs in days once the account exists. CTV integrations through SSAI take longer and depend on the platform mix; the CTV team gives a timeline per channel during onboarding.
A published store presence for each app, a developer domain carrying app-ads.txt, and your inventory profile: platforms, geos and monthly impressions.
No. The SDK ships with mediation configured for your placements, and the migration guide covers teams coming from other mediation stacks.
Access is provisioned during onboarding. If credentials are missing or lost after your account is live, the support channel from onboarding reissues them.
Yes. Direct lines enter the same auction on price with competitive separation honored, and programmatic fills what direct does not. Every decision is logged, so your sales team sees exactly what its deals delivered.
No. There is no exclusivity requirement and no lock on running other networks: non-bidding sources participate through the managed waterfall inside the same decision.
Yes, for publishers with their own ad stack: impression injection over S2S with the same auction policy and the same reporting. The SDK remains the path that carries OMID measurement and client-side events.
Floors are imported per placement at migration, then managed like any other auction input. The switch itself runs as a parallel cohort test, not a blind cutover.
Payments
Net 30 for web inventory and Net 60 for in-app and CTV inventory. These are policy, not estimates.
Payment methods, minimum thresholds and currencies are configured in the account agreement, because they differ by region and entity. Your account manager confirms the exact schedule in writing before launch.
The forms depend on the paying and receiving entities and jurisdictions. Onboarding includes the exact list for your arrangement before the first payment cycle.
Always. The metrics in reporting are the metrics on the invoice, under the same published definitions.
Through your account manager with the period and placement concerned. Disputes are evaluated against the logged auction decisions, within the window stated in the account agreement.
Yes. Every guide and the glossary are public and free, with no account required.
Technical
iOS and Android for mobile, with TV platform support for CTV led by Google TV and Android TV. Minimum OS versions per platform are published in the SDK reference and confirmed during integration.
Wrapper availability, including Unity, Flutter and React Native, is tracked in the SDK reference. The native SDKs are the primary path, and wrappers expose the same API surface.
TCF v2.2 and GPP strings pass through the SDK to the auction, COPPA flags restrict child-directed apps, and US state privacy signals are respected per impression.
Yes. Test placements return marked creative, and debug logging exposes the auction lifecycle on device. Release builds strip the debug output.
Demand
Over OpenRTB 2.6 through a provisioned seat: sandbox first, then test traffic at agreed QPS, then production. The full specification is on the DSP partners page.
Open auction, private marketplace with deal IDs and floors, programmatic guaranteed with automated pacing, and direct deals trafficked into the same auction.
Seats are scoped with filters: geography, platform, format, content category and deal membership. Scope changes apply at the seat without re-integration.
The app object with declared bundle ID and store URL checked against the listing, the content object on CTV with pod position, impression types per format, and the supply chain object on every request.
Yes: read the schain node on any request, cross-check the seller registry behind the account IDs, and read the app-ads.txt declaration for any app you bid on. Our own seller declarations are provided during integration.
Win and loss reasons per auction, spend by deal and impression type, and settlement reporting that reconciles to the console, including rejection reasons from creative review.
Sandbox access is provisioned on request; most seats parse, test and go live inside one sprint, with ramp scheduled rather than flipped.
Compliance
Yes for publishers: a maintained file at your developer domain is part of the requirements, because we enforce authorized selling on both sides of the auction.
Child-directed apps are flagged in the SDK, and the flag restricts data processing and demand eligibility for those impressions.
IAB TCF v2.2 for GDPR regions and the IAB GPP signal format for US state privacy preferences, both passed through the SDK and enforced in the auction.
OpenRTB 2.6, app-ads.txt enforcement, a maintained seller registry, the supply chain object, OMID measurement where formats support it, VAST and VMAP for video delivery, TCF v2.2 and GPP for consent signals.
Through the published enforcement ladder: warning with a fix path, remediation pause, suspension, termination for fraud and misrepresentation. Appeals are reviewed by someone who did not issue the action.
Through the contact form or the ad policy page, with the creative, the app or channel it served on, and the time it appeared. Violating creatives are pulled while the report is assessed.
Everything else, asked and answered.
The contact form routes to the desk that owns the answer, and replies land within one business day.
Onboarding · payments · technical · demand · compliance