Explore XML / JSON feed examples for pop, opted-in push, parked domains and search, with source mapping and reporting explained.
Explore traffic & setup examplesProvide source identifiers, traffic origin, geography and intended placements.
An XML or JSON feed exchanges advertising requests and responses in a structured format. A feed integration defines the data contract; it does not define the appearance of the ad.
XML and JSON describe exchanged data, not what an ad looks like. These examples follow a source through a compatible feed to a result or destination.
A publisher’s pop placement requests an eligible advertising destination through its feed connection. The returned data supplies the destination for the configured browser opening, while source identifiers connect the request with the publisher’s reporting.
The placement controls the opening; XML or JSON carries the response. Validate source eligibility, destination handling and browser behavior together.
A publisher with opted-in subscribers requests an eligible offer through the feed. Its notification workflow displays the permitted message; a subscriber’s click opens the associated destination while preserving the source attribution agreed for that connection.
The feed does not collect permission or deliver browser notifications by itself. Subscription, creative and delivery requirements belong to the push setup.
A visitor reaches a domain’s parking page. An approved integration requests feed results for that source; the page displays permitted sponsored links, and a link the visitor chooses leads to the returned advertiser destination.
Confirm the domain, traffic origin and permitted page presentation with the provider. A parked-domain visit is not automatically a payable event.
A visitor enters a genuine query in a publisher’s search experience. The integration sends the agreed query and source context to a compatible feed, then presents eligible sponsored results according to the provider’s display rules.
Keep queries, returned results and clicks distinct in reporting. The provider contract determines response fields, presentation and which activity can be monetized.
Illustrative source-to-feed arrangements. Each provider must accept the traffic source and intended use; a response is not a confirmed click or revenue.
Provide source identifiers, traffic origin, geography and intended placements.
Validate macros, response fields, destination handling and request limits.
Compare source activity and recorded clicks with the agreed commercial reports.
Separate requests, eligible responses and recorded clicks. Use persistent source identifiers to investigate discrepancies.
A returned result is not a click or guaranteed revenue. Direct-link routing belongs to this workflow; CPA offer terms are separate.
Source identifiers and SubIDs can be included in the agreed integration. Confirm the supported fields and reporting dimensions during setup.
Not necessarily. Each partner’s field names, macros and response structure need validation.
Tell us about your website, audience and current setup. We’ll map the next step together.