How wikiHow Found the Right Ad Monetization Partner in Aditude

For nearly two decades, wikiHow has thrived with a lean team and a deeply ingrained do-it-yourself culture. This scrappy approach served them well as they built and maintained their entire ad stack internally, managing their own Prebid integration, Google Ad Manager, AdSense, and direct SSP relationships.

But as the programmatic advertising landscape grew increasingly complex, it became clear that their ad stack could be further optimized with additional expertise. 

Attempts to find a partner with traditional ad ops companies revealed fundamental mismatches though:

• Pricing Models: Standard 20%+ revenue shares felt excessive relative to the incremental value actually being offered by these services. 
• Relationship Management: Most vendors also required taking over wikiHow's SSP relationships and absorbing wikiHow into their own GAM network, but wikiHow recognized the benefits of maintaining these direct relationships.
• Rigidity:  Most other services had predefined rigid frameworks that couldn’t accommodate wikiHow’s specific needs.
• Support: Other companies typically rely on non-technical account managers as a single point-of-contact, creating an intermediary that caused communication bottlenecks that weren't conducive to wikiHow’s fast-paced workflow. 

wikiHow realized it could benefit from an ad partner if they were the right fit: one that could match their technical sophistication, work at their pace, and provide genuine value without requiring ownership of their relationships or charging high fees.

wikiHow's leadership took a characteristically thorough approach to optimizing their ad stack.  Over the course of a year, wikiHow talked to trusted peers and partners to narrow the field to the best possible matches.

Three key differentiators drove the decision to partner with Aditude:

• Cost Structure That Made Sense: Aditude’s transparent, impression-based pricing aligned with wikiHow’s internal costs of managing their ad stack. Unlike traditional rev shares, it felt proportionate and reasonable.
• A True SaaS Partnership: wikiHow retained its SSP seats, maintained transparency, and remained in control of its monetization strategy. Aditude acted as an extension of the team, not a replacement.
• Collaborative, Fast-Paced Support: Aditude matched wikiHow’s preferred working style—quick Slack responses, direct access to engineers, and zero “we’re not set up for that” attitudes. 

wikiHow approached the transition with characteristic caution, starting with tests before committing to a full rollout. What they discovered was an implementation process that felt more like collaboration than vendor onboarding.

• Speed Without Sacrifice – Rather than weeks of complex integration work, Aditude provided placements for wikiHow's existing ad unit structure within days. The team simply explained their naming conventions, page layouts, and requirements, and Aditude delivered a working solution that matched their specifications exactly.
• Custom Solutions, Not Rigid Templates – Aditude embraced wikiHow’s custom needs and requests:
• CMP Integration: Other providers wanted to change wikiHow's CMP to their own preferred partners (often with added costs); Aditude simply worked with wikiHow’s existing, preferred partner.
• Outstream Video Player: Deploying new ad formats like outstream video went from multiple weeks of internal development today with Aditude's support.
• Prebid server Demand Setup: When wikiHow was looking to supplement their existing Prebid client demand, Aditude helped quickly implement Prebid server demand in just days without requiring wikiHow to set up and maintain its own infrastructure to support Prebid server-side demand.

Today, wikiHow's ad operations look fundamentally different—not in complexity, but in efficiency and capability.

Operational Improvements:

• Fill Rates: Immediate and sustained improvements in fill rates provided both performance gains and revenue optimization.
• Setup Acceleration: New ad unit creation and SSP onboarding, previously multi-week processes, now happen in days or hours.
• Data-Driven Insights: Rather than conducting lengthy investigations into performance fluctuations, wikiHow can now get immediate expert analysis from Aditude's team, complete with specific diagnoses and recommendations.

Strategic Capabilities:

• Informed Decision-Making: wikiHow now has a trusted advisor for evaluating new SSPs, cookie-less identity solutions, and industry trends, eliminating guesswork and reducing risk.
• Custom Problem-Solving: Complex challenges become collaborative projects with Aditude developing novel solutions based on wikiHow’s needs.

Resource Liberation:

• Executive Focus: wikiHow can spend more time concentrating on strategic responsibilities rather than daily ad ops troubleshooting.
• Engineering Efficiency: Development resources previously tied up in ad tech maintenance are now available for core product innovation.
• Responsive Support: Same-day answers to technical questions eliminate the bottlenecks.

After over a decade of operating and managing their own stack, wikiHow was looking for a partner that could optimize things further. But they were skeptical they’d be able to find the right fit — they needed someone who worked with the same flexibility, pace, and creative spirit that they did. 

Aditude proved to be that partner, providing a unique SaaS model that honored wikiHow’s need for control and transparency. This collaborative relationship has enabled wikiHow to unlock new levels of efficiency and innovation, proving that the right partnership can amplify a company's strengths without compromising its values.