This repository was archived by the owner on Mar 15, 2026. It is now read-only.
Evolve from Audience to Signals Activation Protocol#2
Merged
Conversation
This commit aligns the implementation with the specification changes in adcontextprotocol/adcp#6, expanding the protocol from audience-specific to supporting multiple signal types. Key changes: - Renamed from "Audience Agent" to "Signals Agent" throughout - Updated all API methods (get_audiences → get_signals, etc.) - Added support for multiple signal types: - Audience signals (demographic/behavioral) - Contextual signals (content classification) - Geographical signals (location-based) - Temporal signals (time-based) - Environmental signals (weather/events) - Bidding signals (custom bidding data) - Updated database schema and added example data for new signal types - Enhanced AI prompts to understand and rank different signal types - Updated all documentation to reflect broader scope The implementation now supports activation of any type of data signal that can be activated on advertising platforms, not just audiences. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This PR aligns our implementation with the specification changes in adcontextprotocol/adcp#6, evolving from an audience-specific protocol to a comprehensive signals activation framework.
Key Changes
🔄 Terminology Updates
get_audiences→get_signalsactivate_audience→activate_signalcheck_audience_status→check_signal_statusaudience_agent.dbtosignals_agent.db🎯 Expanded Signal Types
Added support for multiple signal types as defined in the spec:
💾 Database Updates
🤖 AI Integration
📚 Documentation
Testing
Alignment with Spec
This implementation fully aligns with the broader scope defined in the specification PR, supporting activation of any type of data signal that can be activated on advertising platforms.
🤖 Generated with Claude Code