An editorial, news, entertainment or vertical publisher is near or above one million monthly pageviews and has clear ad-ops ownership.
1. Platform role and category
Freestar sits across publisher ad technology, demand and ad operations, offering fully managed header bidding, Flex technology, identity, ad-block recovery and multiple ad formats.
The official site covers web, app, AMP and email, so it is more than a single web-ad plugin.
The site’s news banner states that Freestar has been acquired by Stagwell; buyers should consider ownership, data governance and service continuity.
2. Business model and commercial terms
The official FAQ says publishers typically need at least 1,000,000 monthly pageviews while still considering different sizes and categories. This is a typical threshold, not a universal absolute.
Onboarding from kick-off to launch usually takes about 3–6 weeks, including demand approvals, ad operations and QA. Lightweight code or SDK deployment is only one part.
No uniform revenue share is published. Verify managed/Flex fees, minimum volume, demand seats, data access, SLA, ad quality and termination.
3. Where value comes from
- Enterprise managed service: one team handles demand, floors, quality, technology, payments and account support.
- Flex control: sophisticated ad-ops teams can manage bidders, floors, timeouts, identity and A/B tests themselves.
- Multi-environment reach: web, app, AMP and email create a broader revenue portfolio.
- Rich formats: Video Adhesion, instream, outstream, interstitial and native can lift yield but require strict UX governance.
4. Who fits, and who should wait
- An editorial, news, entertainment or vertical publisher is near or above one million monthly pageviews and has clear ad-ops ownership.
- The business needs a unified approach across web, app, AMP or email.
- The team either needs full managed service or has sophisticated ad ops and wants Flex control.
- Traffic is far below the typical threshold but the publisher expects the same level of dedicated service.
- The team expects same-day automatic launch and cannot support a 3–6 week demand and QA process.
- The publisher cannot govern interstitials, sticky units, video and other high-impact placements.
- Brand safety, privacy, data and ad-quality responsibilities cannot be defined.
5. A controlled integration path
- Choose managed, Flex or an environment-specific pilot. Web, app and AMP should not share one undifferentiated KPI set.
- Request the demand list, floor logic, ad-quality rules, identity approach and blockable categories.
- Record LCP, CLS, INP, viewability, ad density and completion before and after the test.
- Break down RPM, fill, session revenue and reconciliation differences by device, country and content type.
- Define SLA, data ownership, intra-Stagwell data use, exit migration and ad-code control in the contract.
6. AdSense, SSP and publisher optimisation are different roles
| Role | Category | What it primarily sells |
|---|---|---|
| Freestar | Publisher operating system & header bidding | Managed or Flex across web, app, AMP and email |
| Mediavine | Publisher network & managed monetisation | Curated publisher network and premium demand |
| Raptive | Creator network & managed ads | Creator growth, demand and specialist services |
| PubMatic | Sell-side platform | Inventory monetisation, transactions and demand |
A publisher can use multiple layers together. The decision is not which logo replaces another, but who controls demand, inventory, testing, data, compliance and operations.
7. Typical customer scenarios
Put the platform back into a real publisher or advertiser workflow. The same feature set can be valuable for one team and premature for another.
The business needs a unified approach across web, app, AMP or email.
The team either needs full managed service or has sophisticated ad ops and wants Flex control.

Pause signals
- Traffic is far below the typical threshold but the publisher expects the same level of dedicated service.
- The team expects same-day automatic launch and cannot support a 3–6 week demand and QA process.
- The publisher cannot govern interstitials, sticky units, video and other high-impact placements.
- Brand safety, privacy, data and ad-quality responsibilities cannot be defined.
8. How to judge whether the value is real
Do not reduce the decision to one headline metric. Value must be visible in revenue quality, operating hours, risk control and the ability to explain results to management.
| Value source | What to verify | Evidence |
|---|---|---|
| Enterprise managed service: one team handles demand, floors, quality, technology, payments and account support. | Validate with live data, not a feature list. | Dashboard, contract, test page or implementation record. |
| Flex control: sophisticated ad-ops teams can manage bidders, floors, timeouts, identity and A/B tests themselves. | Validate with live data, not a feature list. | Dashboard, contract, test page or implementation record. |
| Multi-environment reach: web, app, AMP and email create a broader revenue portfolio. | Validate with live data, not a feature list. | Dashboard, contract, test page or implementation record. |
| Rich formats: Video Adhesion, instream, outstream, interstitial and native can lift yield but require strict UX governance. | Validate with live data, not a feature list. | Dashboard, contract, test page or implementation record. |

Official product, documentation and case evidence
These screenshots come from official product, documentation, eligibility or case-study pages captured on 18 Nov 2026. They are included as visual evidence for the platform’s current public proposition, not as a guarantee of commercial terms.
9. Pre-integration evidence checklist
A platform introduction is not an integration recommendation. The following items should have an owner, a current artefact and a decision date.
- Choose managed, Flex or an environment-specific pilot. Web, app and AMP should not share one undifferentiated KPI set.
- Request the demand list, floor logic, ad-quality rules, identity approach and blockable categories.
- Record LCP, CLS, INP, viewability, ad density and completion before and after the test.
- Break down RPM, fill, session revenue and reconciliation differences by device, country and content type.
- Define SLA, data ownership, intra-Stagwell data use, exit migration and ad-code control in the contract.

10. Five-minute fit scorecard
Use this as a decision aid, not a platform rating. Start from zero, add two points for each matching fit condition and deduct two for each pause signal.
| Score | Condition |
|---|---|
| ('+2', 'Already true') | An editorial, news, entertainment or vertical publisher is near or above one million monthly pageviews and has clear ad-ops ownership. |
| ('+2', 'Already true') | The business needs a unified approach across web, app, AMP or email. |
| ('+2', 'Already true') | The team either needs full managed service or has sophisticated ad ops and wants Flex control. |
| ('-2', 'Deduct if true') | Traffic is far below the typical threshold but the publisher expects the same level of dedicated service. |
| ('-2', 'Deduct if true') | The team expects same-day automatic launch and cannot support a 3–6 week demand and QA process. |
| ('-2', 'Deduct if true') | The publisher cannot govern interstitials, sticky units, video and other high-impact placements. |
11. Four-stage validation plan
The goal is not to finish integration quickly. The goal is to produce evidence that can survive a commercial, technical and management review.
| Stage | Action |
|---|---|
| Week 1 | Choose managed, Flex or an environment-specific pilot. Web, app and AMP should not share one undifferentiated KPI set. |
| Week 2 | Request the demand list, floor logic, ad-quality rules, identity approach and blockable categories. |
| Weeks 3-4 | Record LCP, CLS, INP, viewability, ad density and completion before and after the test. |
| Post-test | Break down RPM, fill, session revenue and reconciliation differences by device, country and content type. |
12. Common failure modes
These are the situations that most often turn a platform introduction into wasted time or a migration problem.
Traffic is far below the typical threshold but the publisher expects the same level of dedicated service.
The team expects same-day automatic launch and cannot support a 3–6 week demand and QA process.
The publisher cannot govern interstitials, sticky units, video and other high-impact placements.
13. Continue reading: adjacent platform roles
Compare adjacent roles instead of treating every platform as a substitute. The strongest stack usually combines complementary layers.
14. Frequently asked questions
What traffic level does Freestar typically require?
The official FAQ cites a typical minimum of 1,000,000 monthly pageviews while saying different publisher sizes and categories are considered. Eligibility still requires confirmation.
What is the main difference between managed service and Flex?
Managed service delegates most ad operations to Freestar. Flex gives a sophisticated publisher team control over bidders, floors, timeouts and A/B testing.
Why does onboarding take 3–6 weeks?
Demand approvals, code or SDK work, ad operations, QA and testing all require time; it is not just copying a tag.
Are more high-impact ads always better?
No. Interstitials, sticky units and video can raise revenue but also affect speed, reading and SEO. Density, frequency and stop rules are essential.




