Podscribe Automated Campaign Google Sheet Sync
Overview
Podscribe’s Automated Google Sheet (G‑Sheet) Campaign Sync allows you to bulk‑create and maintain hundreds of campaigns directly from a Google Sheet. Instead of manually building campaigns one by one in the Podscribe dashboard, you can sync a structured spreadsheet and let Podscribe automatically create, update, and organize campaigns for you based on your provided campaign data.
This feature is designed for teams managing high campaign volume, working with multiple publishers, or looking to automate campaign and pixel setup at scale.
What the G‑Sheet Sync Does
When enabled, Podscribe will:
- Read campaign rows from a connected Google Sheet
- Automatically create new campaigns in the dashboard
- Update existing campaigns when the sheet changes
- Preserve a single source of truth for campaign setup
This makes it possible to manage hundreds of campaigns from one spreadsheet with consistent formatting and fewer manual errors.
When to Use G‑Sheet Sync
G‑Sheet sync is ideal if you:
- Receive campaign details via spreadsheets or planning docs
- Work with many publishers or networks
- Frequently update expected dates, impressions, or placements
- Want to reduce manual campaign and pixel creation
Implementation
- Copy the Podscribe Campaign Import Template
- If you are interested in setting up radio campaigns, please use the Podscribe Campaign Import Template for Radio
- Populate required campaign fields
- If you are setting up radio campaigns, see required fields for radio
- Grant edit access of the Google Sheet to adops@podscribe.com
- Podscribe will confirm when the sheet is synced
- Maintain campaigns by editing the sheet going forward
Campaign Import Template Structure
Each row in the sheet represents one campaign line item. Below is a breakdown of the supported fields and how Podscribe uses them.
Required Fields
These fields are required for a campaign to sync successfully:
- Expected Date (or Week Start Date)
The campaign start date or the start of the delivery week.
- Advertiser
Brand or advertiser name associated with the campaign.
- Podcast / Channel / Campaign Name
The show, channel, or campaign identifier. This is used to name and organize campaigns in Podscribe.
- Publisher
The publisher or network running the placement (e.g., Acast, Audioboom, Kast Media).
Commonly Used Fields
These fields enhance reporting, pacing, and attribution but are not required:
- Expected End Date (defaults to 7 days from start date if not set)
Used for multi‑week or longer campaign flights.
- Geo (if not Global or US)
Geographic targeting if delivery is outside the US.
- Spot Rate
Cost of the placement (CPM or flat rate depending on setup).
- Expected Impressions
Planned or contracted impressions for the campaign.
- Expected Unit
Placement type (Pre, Mid, Post, or combinations).
- Expected Length
Creative length (e.g., :30, :60).
- Category
Baked‑In or DAI.
- Media Type
Podcast, YouTube, Simulcast, Streaming Audio, Display, Video
- Promo / URL
Vanity URL or promo code used in the read.
- Expected Offer
Promotional offer mentioned in the ad read.
- Talking Points File Link
Link to creative or talking points documentation.
Required Fields (Radio)
These fields are required for a campaign to sync successfully:
- Advertiser
Brand or advertiser name associated with the campaign.
- Station (or National Radio Show title)
The station call sign (e.g. ABCD-FM) or national radio show title (The Free Beer & Hot Wings Morning Show)
- Start Date
The start date of the radio campaign
- End Date The end date of the radio campaign
Commonly Used Fields (Radio)
These fields enhance reporting but are not required:
- Daypart
Days of the week and time ranges you expect the ads to air
- Publisher
The publisher of the radio station or show
- Expected Length
Expected length of the ad
- Expected Spots
Expected number of ads within campaign date range
- Promo
Campaign promo codes expected to be read in the ad
- Market
The target market (e.g. Seattle, WA)
Sync Behavior & Rules
Campaign Creation
- New rows create new campaigns
- Campaigns are matched based on internal identifiers once created
- The Google Sheet is the system of record.
Campaign Updates
- Editing a synced row will update the corresponding campaign
- Manual dashboard edits may be overwritten on the next sync
- Removing a row from the Google Sheet will archive the campaign or flight in the dashboard
Best Practices
- Use one row per placement or flight
- Avoid manually editing campaigns in the dashboard after syncing
- Validate Spot Rate and Expected Impressions before syncing
- Keep naming conventions consistent
Need Help?
Reach out to adops@podscribe.com for guidance.
Powered by