Skip to main content
Submit a request

Getting Started — Freestar Integration Guide (Expanded)

Updated

1. Overview

This guide walks you through integrating Freestar’s monetization stack, which leverages both Prebid.js and Google Publisher Tag (GPT.js) within Google Ad Manager (GAM). You'll receive fully configured tags and placements optimized for your site’s layout and revenue yield.  

 

2. Pre-Integration Cleanup

Before installing Freestar tags, you’ll want to remove any duplicative or conflicting GAM ad tags or Prebid wrappers that may already be on the page. In certain cases, such as controlled testing scenarios, your Freestar team may provide alternate guidance.

Important: You will continue to use and control your own Google Ad Manager (GAM) account — nothing needs to be removed.  This only applies to conflicting 3rd party GAM references.

  • Your GAM remains fully intact and under your control.
  • Freestar simply provides new tags that wrap around GPT and Prebid logic.
  • We’ll map our placements in the Freestar Admin Dashboard (FAD), Freestar’s internal configuration tool, directly to your existing GAM ad units—preserving your setup, naming conventions, and direct-sold campaigns.
     

This ensures there’s no loss of control — just a cleaner, conflict-free integration environment.

 

3. Ad Tag & Wrapper Deliver

You'll receive Freestar’s ad bundle, which includes:

  • A universal GPT.js file—either Freestar or the publisher can host it; it works the same way across implementations.
  • The header bidding wrapper—this wraps around the GPT call and invokes Prebid.js, all initialized via Pubfig.min.js included in your <head> tag.
    • More information on Head Code Installation can be found here
  • This approach allows Freestar to load auction code while preserving your page performance.

 

4. Tag Installation & Ad Unit Naming

  • Replace your existing ad tags with the Freestar-provided wrapper code in both the <head> and appropriate <body> sections.
  • Freestar's code supports maintaining your current ad unit naming conventions, minimizing disruptions to your direct-sold campaigns and creative setups.
    • More information on Tag Installation can be found here.

 

5. Freestar Placements & GAM Ad Unit Mapping

The connection to your GAM account happens via Freestar’s FAD platform:

  • Each “placement” created in FAD includes an ad unit path that embeds your GAM ID and ad unit code.
  • Freestar maps these placements to your existing GAM configuration without needing manual overrides

 

6. Line Item Generator in Publisher GAM

To complete the integration, Freestar uses a Line Item Generator that automates the creation of GAM line items required for header bidding. This process ensures that key values passed from Freestar’s wrapper properly match against GAM’s orders and line items.

How It Works

  • The generator is typically run once per GAM account.
  • It builds a compact structure in your GAM (about 6 orders with 250 line items each) instead of the larger, demand-partner-split setup in Freestar’s GAM.
  • Key values determine which order is selected when an impression is eligible; GAM then decides which specific line item serves.
  • Line items usually target Run of Network (RON), so the default assumption is that Freestar code should run site-wide across your inventory.

Why It Matters: Ensures traffic allocation is correct before launch and keeps FAD placements in sync with GAM, supporting direct-sold campaigns and future optimization.

 

7. Handling Multi-Domain and Flexible Slots

  • Freestar’s wrapper supports both GPT.js and Prebid.js, plus flexible mapping through FAD, enabling highly scalable setups.
  • Whether you're managing ~80 domains (Lee) or ~1,000 (Blox), Freestar’s channel variable and placement flexibility allow you to support domain-specific slot names and structures at scale.
    • More information on Channel Variable can be found here.
       

8. TAM & AdX Integration Strategy

  • TAM (Amazon Transparent Ad Marketplace): Your Amazon ID will be integrated into the Flex dashboard. Freestar will coordinate with Amazon to ensure a smooth transition under the Freestar ecosystem.
  • AdX: If Freestar is operating within your GAM, AdX remains in place as-is—this aligns with standard GAM compatibility practices.

 

9. Post-Installation Ads.txt, Testing & Launch

  • Freestar requires updates to your ads.txt file to initiate demand partner approvals. At minimum, please add the provided static ads.txt lines to production as soon as possible; some networks will not approve your site until these are live. The full ads.txt file must be placed on production at least one week prior to launch.  The full ads.txt file can be found here.
  • If you prefer to make only one update during onboarding, we recommend implementing Freestar’s dynamic ads.txt file. This approach eliminates manual updates while preserving your current ads.txt entries. You can view dynamic ads.txt implementation instructions here.
  • Once ads.txt is verified, begin testing in a dev or low-traffic environment and schedule QA with your Freestar Point of Contact.
  • Verify that the wrapper is running correctly, Prebid auctions fire, bids are passed to GAM, and ad unit mapping aligns with expectations.
  • Ensure that any direct-sold campaigns and placements continue to function as before, thanks to naming and structure consistency.

 

10. Onward: Optimization & Reporting

Once live, use the Freestar dashboard to:

  • Monitor yield, auction performance, and reporting.
  • Iterate on demand partners, price floors, and timeouts via your Flex dashboard—leveraging AI/ML tools for real-time optimization.
  • Run A/B tests, adjust identity frameworks, and optimize further over time

 

Integration Resource Bundle

To support your onboarding, we’ve pulled together a set of resources that complement this guide. These links provide tactical instructions, troubleshooting steps, and deeper dives into optimization strategies once you’re live.

 

Technical Setup & Verification

  • Testing Your Integration
    Step-by-step instructions for validating tag implementation, confirming Prebid/GPT calls, and QA’ing your integration before launch.
  • Lazy Loading & Viewability Setup
    Best practices for reducing CLS, maintaining site performance, and optimizing ad viewability.

 

Tagging & Implementation

  • Standard Web Tags — Downloading tag files, head/body installation, re-using tags, event-based tagging, channel variables, disabling products, key-value targeting, and sticky ads. Includes SPA pageview tracking, CLS prevention, and GTM (BETA) options.
  • React Tags — Installation steps, tag anatomy, available props, API methods, and configuration options for React-based sites.
  • AMP Tags — Setup for Accelerated Mobile Pages, including installation, RTC, video support, and fully managed AMP flows.

 

Reporting & Optimization

 

Compliance & Advanced Configurations

Related articles