For publishers

You can link readers to AirnodeHub or to the listing your article discusses. Add campaign parameters to identify which publication and public content sent a browser visit to the Hub:

Parameter	What to use
utm_source	Your publication's stable lowercase slug
utm_medium	referral
utm_campaign	airnodehub
utm_content	An optional public article ID or content label

Start with this publisher link:

https://airnodehub.api3.org/?utm_source=publication_name&utm_medium=referral&utm_campaign=airnodehub

Replace publication_name with your publication's stable lowercase slug, such as my-publication, and use the same slug on every Hub link from that publication.

To link to a specific listing, keep the campaign values and use the listing's path. You can add utm_content to distinguish a public article. For example, a link to the CoinGecko listing:

https://airnodehub.api3.org/explore/coingecko?utm_source=publication_name&utm_medium=referral&utm_campaign=airnodehub&utm_content=coingecko-guide

Keep labels public and short: the Hub's browser analytics retains at most 100 characters per value. Do not include reader identities, email or wallet addresses, prompts, or conversation IDs.

Use these parameters on browser links to the catalogue or a listing, not on MCP connection URLs or API operation requests. Leave existing campaign parameters and signed or authenticated URLs unchanged, and keep canonical URLs untagged.

When browser analytics is enabled, these labels can help us attribute a visit; collection still depends on the visitor's browser and analytics availability. A tagged visit or resource click does not prove that an agent connected, an API call succeeded, or a payment settled. Direct MCP and API usage is measured separately from these browser visits.