Overview

Workflow Goals

Video Walkthroughs

OMS (Boostr) → Frequency → Ad Server (Megaphone)

Creating a production request

Step-By-Step Process

Step 1. Setup Boostr IO, Push to Ad Server, & Push to Frequency

1. Create Deal Boostr

1.1 Deal is created with required data

• Navigate to Deals → Create New Deal

• Name: Frequency Test - [Date]

• Currency: USD

• Advertiser: Test 1 Advertiser

• Agency: [TBD]

• Start/End dates: Next month 1-31

• Source: Direct sold

1.2 Products are added with budget detail

• Click "Add" under Products

• Select: Digital Audio Streaming PG (Sports)

• Set Option 1 (duration): 0:30

• Budget: leave empty

• Click "Create"

1.3 Deal set to Closed Won

• Change status: 10% - Prospect → 100% - Closed Booked

2. Create Media Plan Boostr

2.1 Media Plan is created

• From deal page → Click "Add" to create media plan

• Name: Make it unique

• Rate Card: Select your rate card

• Budget goal: Leave blank

2.2 Media Plan Lines are created with relevant details

• Select product: Podcast Network (Full Network) Aud Megaphone (hard cost = $0.0)

• Quantity: 0 or 1

• Quantity type: Impressions

• Podcast Ad Type: Host Read or Producer Read (required for automation)

• Has Copy: Y

• Approval Required: Y (if brand approval needed)

• Ad Units Targeting:
• Open Ad Units modal → Go to Included
• Remove 2 default values
• Add at least 1 Megaphone show

2.3 Media Plan approved and set to Active and Primary

• Set Media Plan: Draft → Approved

• Navigate back to deal page

• Toggle media plan as Primary

3. Create Insertion Order (IO) Boostr

3.1 IO module activated

• Navigate to IO Details

• Set IO status: Draft → Active

3.2 Traffic request initiated in line items

• Navigate to Line Items tab

• Select line item (checkbox)

• Click "Create Traffic Order"

💡 Double-check that Podcast Ad Type is set (host read or producer read) if you want to auto-create a production request.

3.3 Traffic to ad server initiated

• Navigate to Trafficking tab

• Click "Ad Server Push"

• Verify in columns:
• Ad Server Push Status should say “Success”
• Last push timestamp
• Timing: Typically takes a few seconds

4. Push Data to Ad Server Boostr

4.1 Campaign auto-created in Megaphone

• Happens automatically in Megaphone after you click “Ad Server Push” in Boostr

4.2 Order(s) auto-created in Megaphone

• Flight created with targeting from Boostr

• All order details configured (impressions, placement, targeting, position, priority, etc)

4.3 Ad server ID sent to Boostr

• Happens automatically after Frequency processes

• ID flows back from Megaphone → Frequency → Boostr

Step 2. Produce Your Creative

5. Frequency Automations Frequency

5.1 Campaign auto-created in Frequency

• Boostr pushes data to Frequency API

• Campaign auto-created from Boostr deal data

• External ID: Boostr Traffic ID

• Timing: Instant, event-driven

5.2 Flight(s) auto-created in Frequency

• Flight auto-created from Boostr line item

• Duration, start date, end date, placement, ad read type, copy available, and approval required all flow

• Timing: Instant, event-driven

5.3 Targeting data syncs with campaign, flight, and production requests

• What this step does: Frequency automatically maps Boostr targeting to Megaphone shows and episodes, updating campaign, flight, and production request targeting within Frequency. Targeting syncs run automatically in the background to ensure data accuracy.

• Timing: Cron job updates hourly, 20 minutes after the hour

6. Production Request Frequency

6.1 Production Request created

• Auto-created if Podcast Ad Type set in Boostr

• PR format: {FlightName} - {AdType} - {Duration} - {DueDate}

• Status: Draft

6.2 User attaches script to PR

• Manual step

• Upload script document to PR

6.3 PR sent to Producer

• Workflow routing to production team

6.4 Producer attaches creative to PR

• Upload audio file

• Add metadata (title, duration)

6.5 Producer sends PR to Ad Ops

• Workflow continues to Ad Ops for approval

6.6 Ad Ops approves and closes out PR

• Final approval

• PR status: Complete

• Asset ready for ad unit assignment

7. Creative Manager (Optional) Frequency

7.1 Upload assets as required

7.2 Set resources on creative

• Add pixels (eg Podscribe, Claritas, DCM), banners, and scripts

7.3 Set data signals on creative

• Add dynamic targeting parameters like location, device type, weather, and more (30+ signals available)

7.4 Publish creatives

Step 3. Push Creative to Ad Server

8. Creative pushed to ad server flight Frequency

• Navigate to Frequency / Campaigns / Flight / Ad Unit

• Click Add File

• Add from Asset Library (recommended) or upload from Computer

• Click the overflow menu (···), then click “Set Live”

• Select “Publish Immediately” or Schedule (only available if scheduling a second version of the ad)

• 🎉 Success! Your ad creative is pushed to Megaphone for immediate delivery or scheduled delivery (depending on your setup)

9. Verify Order Details in Ad Server Megaphone

• Log into Megaphone

• Find campaign

• Verify campaign order exist

• Confirm campaign details are accurate (targeting, placement, position, priority, etc)

FAQs

What data is required to trigger automations?

• IO Status: Active

• Create Traffic Order

• Click Ad Server Push in Trafficking tab

• Campaign Name

• Campaign Start Date

• Campaign End Date

• Advertiser

• Deal Status: Closed Booked

• Line Item Name

• Start Date

• End Date

• Duration (seconds)

• Ad Placement (Pre-roll, Mid-roll, Post-roll)

• Target shows/episodes

• Ad Read Type: Host-read or Producer-read

• Production Request auto-created

• Format: {FlightName} - {AdType} - {Duration} - {DueDate}

• Due Date: 2 business days before flight start

• Status: Draft

What parameters can be pushed from Boostr to my Megaphone order?

• Impressions

• Devices Targeting (eg mobile)

• Geo Targeting (eg country)

• Key Value Targeting (e.g. advertiser categories)

• Placement (pre/mid/post)

• Position

• Priority

• Ad Duration (15, 30, 60, 90, etc)

Understanding platform-specific terminology