Key Takeaways

• ads.txt and sellers.json both change over time, often without notification. SSPs update sellers.json during platform migrations, data cleanups, and rebrands. Publishers edit ads.txt when adding or removing partners.
• Unmonitored changes cause silent revenue loss. A sellers.json change that removes your entry costs you CPMs from the moment it happens until someone notices.
• Change monitoring has two sides: your ads.txt and your SSPs' sellers.json. Both need tracking because either side can introduce verification failures.
• Version control is the simplest form of ads.txt change tracking. Git, file diffing, or even manual snapshots provide a change history you can reference.
• Automated monitoring tools detect SSP-side changes you can't control. This is where the highest-value monitoring happens because SSP changes affect your revenue without any action on your part.

---

How to Monitor ads.txt Changes Over Time

When you first set up ads.txt, you verify everything works. A month later, your SSP migrates to a new platform and changes your seller_id format.

Two months later, someone on your team removes an entry during routine maintenance. Three months later, an SSP marks your account as confidential during a data cleanup.

Each change introduces a potential verification failure. Without monitoring, these failures accumulate silently.

What Changes to Monitor

Your ads.txt Changes

Changes you or your team make to your own ads.txt file:

• New entries added (hopefully matching new SSP partnerships)
• Entries removed (hopefully matching ended partnerships)
• Account ID updates (SSP migrations, restructuring)
• Formatting changes (accidental or intentional)
• File accessibility changes (server configuration, CDN updates)

SSP sellers.json Changes

Changes SSPs make to their sellers.json files that affect your entries:

• Your entry removed (data cleanup, account migration)
• Your entry modified (domain change, type reclassification, name update)
• Your entry marked confidential (default change, policy update)
• SSP's entire sellers.json file going offline or changing URL
• New entries added (when you onboard with a new SSP)

Infrastructure Changes

Changes to the systems that serve or access these files:

• CDN configuration changes affecting ads.txt accessibility
• DNS changes affecting domain resolution
• SSL certificate changes affecting HTTPS access
• Server-side redirects being added or modified

Monitoring Methods

Method 1: Version Control (ads.txt)

The simplest approach for tracking your own changes. Put ads.txt in a git repository.

Setup:

1. Add ads.txt to your site's git repository
2. Commit every change with a meaningful message
3. Use git diff to review changes before deploying
4. Use git log to see the full history of changes

Benefits: Full history of every change, who made it, and when. Easy to revert if a change causes issues.

Limitations: Only tracks your side. Doesn't detect SSP-side sellers.json changes.

Method 2: Periodic Snapshots

Take regular snapshots of both your ads.txt and relevant sellers.json files.

Setup:

1. Weekly: Download and save your ads.txt file
2. Weekly: Download sellers.json from your top SSPs
3. Compare each snapshot against the previous one
4. Flag any differences for investigation

Benefits: Tracks both sides. Doesn't require special tools.

Limitations: Manual, time-consuming, and only catches changes at the snapshot frequency. A change that happens and reverts between snapshots is missed.

Method 3: Automated Change Detection

Use tools that continuously monitor ads.txt and sellers.json files and alert you when changes occur.

BeamFlow provides automated monitoring that:

• Tracks your ads.txt for changes
• Monitors sellers.json entries across all your SSPs
• Alerts you when verification status changes
• Provides before/after comparisons when issues appear

Benefits: Continuous monitoring. Catches changes as they happen. Alerts you automatically.

Limitations: Requires a monitoring service.

What to Do When Changes Are Detected

Your ads.txt Changed

Expected change (you made it): Verify the change deployed correctly. Check that new entries cross-verify against sellers.json. Confirm no formatting issues were introduced.

Unexpected change: Someone or something modified your file without your knowledge. Investigate:

• Did a CMS or deployment pipeline overwrite the file?
• Did another team member make an undocumented edit?
• Did a security incident modify the file?

SSP sellers.json Changed

Your entry was removed: Contact the SSP immediately. Ask why the entry was removed and when it will be restored. Every day without the entry costs you verified demand through that SSP.

Your entry was modified: Check what changed. If the domain, type, or name changed to incorrect values, contact the SSP with the correct information. If the change is accurate (you changed your business name, for example), update your records.

Your entry was marked confidential: Contact the SSP and request non-confidential status. There's rarely a legitimate reason for a publisher to be confidential.

SSP sellers.json went offline: Check if the URL changed or if there's a temporary outage. If the file is consistently unavailable, all publishers on that SSP lose identity verification.

Setting Up Alerts

Effective monitoring requires alerts that reach the right person at the right time.

What to Alert On

Critical alerts (immediate attention):

• Your ads.txt file becomes inaccessible (404, 500, etc.)
• A sellers.json entry for a high-revenue SSP disappears
• Multiple sellers.json entries fail simultaneously (SSP-wide change)

Warning alerts (review within 24 hours):

• A sellers.json entry field changes (domain, type, name)
• A sellers.json entry becomes confidential
• Your ads.txt file content changes unexpectedly

Informational alerts (review weekly):

• New sellers.json entries verified for recently added SSPs
• Minor changes in sellers.json data that don't affect verification status

Where to Send Alerts

Send alerts to whoever manages your programmatic monetization:

• Email for non-urgent warnings
• Slack or SMS for critical issues
• Dashboard or report for informational tracking

Building a Change Log

Maintain a log of notable changes for reference:

| Date | Source | Change | Impact | Action Taken |

|------|--------|--------|--------|-------------|

| 2025-01-15 | Our ads.txt | Added SSP-X entry | New partnership live | Verified sellers.json match |

| 2025-02-01 | SSP-A sellers.json | Domain changed | Mismatch detected | Contacted SSP, fixed 02/03 |

| 2025-02-10 | SSP-B sellers.json | Entry removed | Verification failed | Contacted SSP, restored 02/12 |

A change log helps you:

• Track patterns (does a specific SSP frequently cause issues?)
• Reference past resolutions when similar issues recur
• Demonstrate due diligence in supply chain management
• Estimate the revenue impact of change-related outages

Frequently Asked Questions

How often do sellers.json files change?

It varies by SSP. Large SSPs may update daily or weekly as they onboard new sellers and process changes. Smaller SSPs may update monthly or less frequently. Major changes (platform migrations, rebrands) can cause large-scale sellers.json updates affecting many publishers at once.

Can I prevent SSP-side changes from affecting me?

You can't prevent changes to sellers.json (SSPs control their own files). What you can do is detect changes quickly and respond before the revenue impact compounds. Automated monitoring reduces the gap between when a change happens and when you know about it.

What if my ads.txt keeps getting overwritten by my CMS?

Some CMS platforms regenerate or overwrite certain files during deployments. If this is happening, configure your CMS to preserve ads.txt or manage it outside the CMS deployment pipeline. Store ads.txt as a static file that isn't affected by CMS updates.