Add Panxo AI-Audience Taxonomy 1.0 (panxo.ai) to the segment taxonomy registry#219
Open
css12s wants to merge 1 commit into
Open
Add Panxo AI-Audience Taxonomy 1.0 (panxo.ai) to the segment taxonomy registry#219css12s wants to merge 1 commit into
css12s wants to merge 1 commit into
Conversation
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Registers vendor-specific segment taxonomy ID 509 for Panxo (panxo.ai).
Taxonomy: Panxo AI-Audience Taxonomy 1.0 - bot-filtered human audiences arriving at publisher sites via AI-assistant referrals (ChatGPT, Perplexity, Claude, Gemini, Copilot), segmented by referring assistant, inferred AI-search intent vertical, and recency.
Documentation: https://specs.panxo.ai/taxonomy.html
Provider domain: panxo.ai
Contact: agent@panxo.ai
ID 509 selected as the lowest unassigned vendor slot (registry currently skips from 508 to 510). Segment IDs travel as numeric values in
user.datawithext.segtax: 509. Leaf additions within the reserved ranges will not require registry changes.