Ad Network SSP/Publisher Onboarding Guide

1. Account Creation & Setup

1.1 Initial Contact

Start by contacting partners@digibid.com to request account creation for either:

SSP Account
Publisher Account

1.2 Account Assignment & pos_id Distribution

After account approval, the partner will assign the necessary credentials and pos_id (position IDs) for production use.

SSP Partner: For SSP partners, we will assign separate pos_ids for each ad format/placement type (banner, video, native, etc.). This allows granular tracking and optimization per inventory type.

Publisher Account: For publisher account, we suggest you register every ad placement for each pos_id, so that you can use our platform functions to optimize your placements.

1.3 Information Collection

We will require the following information from the partner:

Primary domain(s) or app package names
Ad format types and dimensions (300x250, 728x90, video, native, etc.)
Monthly traffic volume (uniques/impressions)
Geographic coverage (primary countries/regions)
Device mix (desktop, mobile, tablet, CTV)
Current tech stack (GAM, header bidding, custom, etc.)

Owners: Technical Onboarding, Account Management
Output: Account credentials + multiple pos_ids (one per format) + partner information document

2. Technical Foundation & Requirements

2.1 Pre-Integration Confirmation

Before proceeding to technical integration, confirm the following core requirements:

Requirement	Details
Integration Protocol	Confirm support for OpenRTB (oRTB) protocol
Billing Model	Confirm settlement is CPM-based
Creative Review	Clarify if creative pre-approval is required, including process and turnaround time
Latency Requirements	Define acceptable latency thresholds (e.g., bid timeout, request timeout)
Sample Request	Request a sample OpenRTB bid request for initial validation

2.2 Sample Bid Request Validation

Once the partner provides a sample bid request, we will:

Parse and validate the request structure
Confirm our system can generate a valid bid response
Validate response format and required fields
Document any integration issues or special requirements

Owners: Technical Onboarding, Engineering
Output: Technical requirements document + sample request validation report

3. Integration & Pre-Production Testing

3.1 Full Technical Integration

Proceed with complete OpenRTB integration validation:

Request parameters are correctly parsed
Bid response is properly formatted and returned
Creative rendering works as expected
Tracking pixels and monitoring are functional
Error handling and fallback logic are correct

3.2 Budget Confirmation with Commercial Team

Before launching traffic, coordinate with the commercial team to confirm:

Test budget allocation and daily spend limits
Settlement terms during test phase
Testing duration and expected volume
Approval to proceed with traffic

Important: Do NOT proceed to traffic until commercial confirms budget allocation. This ensures proper resource planning and billing alignment.

3.3 Traffic Ramp-Up

Once budget is confirmed, gradually increase traffic volume:

Start with low volume (5-10% of target)
Monitor system performance and stability
Gradually increase to full test volume (50-100%)
Validate data consistency at each stage

Owners: Technical Onboarding, Engineering, Commercial
Output: Integration report + commercial budget approval + ramp-up status

4. Testing & Data Reconciliation

4.1 Testing Period

Execute a 1-week testing period with the following targets:

Minimum 1,000 impressions
Minimum 100 clicks
Sufficient volume for statistically valid data comparison

4.2 Key Data Points to Track

Total impressions served
Total clicks/interactions
Bid rate (requests with valid bids)
Win rate (impressions where partner's bid won)
eCPM and total revenue
Response latency (p50, p95, p99)
Error rate and timeouts

4.3 Data Alignment & Reconciliation

After testing period ends, reconcile all metrics:

Compare impressions: our log vs. partner's log (target: ±5% variance)
Compare clicks: our tracking vs. partner's tracking (target: ±5% variance)
Validate revenue calculation and payout accuracy
Investigate and resolve any discrepancies
Confirm data consistency across all touchpoints

4.4 Launch Decision

Based on test results, determine readiness for production:

All tests passed: Proceed to full production launch
Minor issues resolved: Schedule extended test or launch with monitoring
Major issues: Return to integration phase for fixes

Owners: Analytics, Technical Onboarding, Product Management
Output: Test data reconciliation report + launch go/no-go decision

5. Production Launch

5.1 Staged Launch

Roll out production traffic in stages:

Phase 1: 10% of expected daily volume
Phase 2: 50% of expected daily volume
Phase 3: 100% of expected daily volume

Each phase should be monitored for 24-48 hours before proceeding to the next.

5.2 Production Monitoring

During first week of production, maintain active monitoring:

Real-time dashboards for key metrics
Daily standups with technical and commercial teams
Rapid incident response capability (P1: 1 hour)
Weekly performance reviews

5.3 Ongoing Optimization

Post-launch, focus on optimization:

Analyze eCPM trends and identify optimization opportunities
Test price floor adjustments
Monitor fill rate and timeout metrics
Regular business reviews (weekly first month, then monthly)

Owners: Operations, Account Management, Analytics
Timeline: Ongoing

6. Key Contacts & Escalation

Role	Responsibility	Availability
Account Manager	Primary point of contact, relationship, optimization	Business hours
support@digibid.com	Integration support, troubleshooting, architecture	24/5 (Mon-Fri)
Finance/Operations	Billing, payout, reconciliation	Business hours

7. Document Control

Version	Date	Author	Changes
1.0	2026-03-31	Ad Network Team	Initial version - SSP/Publisher onboarding flow

Last Updated: 2026-03-31 | Next Review: 2026-06-30