XML and JSON can carry equivalent business information, but their schemas, parsing behavior and partner conventions differ. The platform should isolate those differences from downstream commercial logic.
XML feeds
XML remains common in search and affiliate advertising because it supports established schemas and broad partner compatibility. It can also introduce inconsistent nesting and field conventions.
- Established partner contracts
- Explicit document structure
- Schema variation
JSON feeds
JSON is compact and natural for API-oriented services, but a JSON response is not automatically standardized. Field names and commercial semantics still require a contract.
Normalization as the boundary
Nexus positions normalization and mapping before campaign or demand routing, allowing the downstream decision layer to work with an understandable contract.
This guide describes Nexus product architecture and general AdTech operating concepts. Exact enforcement and integration behavior depends on the enabled revenue engine and agreed deployment configuration.