Table of Contents

XML integration

Servers

Our servers are located in Ashburn, Virginia, USA.

To see the average latency please ping 35.186.184.138. Pinging rtb.ato.mx will always have a lower latency as this is a Google Loadbalancer in front of our servers.

SSP

Our XML endpoint looks like:

http://rtb.ato.mx/bid?s=<ssp id here>&ua=<full user agent string>&user_ip=<ip>&url=<url which the ad will be on including http:// part>&subid=<site name>&query=<keywords separated by | or space>

An example would be:

http://rtb.ato.mx/bid?s=0&ua=Mozilla%2F5.0+(Windows+NT+6.1)+AppleWebKit%2F537.36+(KHTML%2C+like+Gecko)+Chrome%2F41.0.2228.0+Safari%2F537.36&user_ip=11.22.33.44&url=http%3A%2F%2Fwww.example.com%2F&pub=Test+Pub&subid=Test+Site&query=test|query

The &pub= and &subid= can be used to group you traffic into publishers and sites respectively. &pub= and &subid= are optional but highly recommended.

The &query= parameter is optional and can be used for keyword targeting.

Our response will look like:

HTTP/1.1 200 OK
Connection: keep-alive
Content-Type: text/xml

<result><link bid="0.0001" url="http://example.com?foo=bar&something=something"/></result>

Reporting

Billing

SSPs are only billed for unsold traffic. Meaning all requests that Atomx didn't receive any win notification for. A count of these requests can be found in the Sell Side Reporting under the SSP Metrics. The CPM fee Atomx bills for these unsold requests can be found on your network overview page as the SSP Fee.

DSP

Macros

The endpoint URL you provide us can have the following macros:

Macro Description
[ua] This will be replaced by the User-Agent.
[url] This will be replace by the full URL the pop is on.
[ip] This will be replace by the IP of the visitor.
[domain] This will be replace by the domain name the pop is on.
[placement_id] This will be replaced by the Atomx placement ID.
[site_id] This will be replace by the Atomx site ID.
[publisher_id] This will be replace by the Atomx Publisher ID.
[keywords_pipe] This will be replaced by a | separated list of keywords if available.
[language] This will be replaced by the users ISO 639-1 browser language code. For example US.

For example:

http://rtb.example.com/bid?user_ip=[ip]&url=[url]&pub=[publisher_id]&subid=[site_id]&query=[keywords_pipe]&ua=[ua]

Will be requested as:

http://rtb.example.com/bid?user_ip=11.22.33.44&url=http%3A%2F%2Fwww.example.com%2F&pub=123123&subid=456456&query=test|query&ua=Mozilla%2F5.0+(Windows+NT+6.1)+AppleWebKit%2F537.36+(KHTML%2C+like+Gecko)+Chrome%2F41.0.2228.0+Safari%2F537.36

Response formats

For your response we support and auto-detect the following response formats:

<result>
<link bid="0.0001" url="http://example.com" site="something" title="hi there" />
</result>

Or:

<result>
<listing bid="0.0001" url="http://example.com" site="something" title="hi there" />
</result>

Or:

<result>
<listing>
<bid>0.0001</bid>
<url>http://example.com</bid>
<site>something</site>
<title>hi there</title>
</listing>
</result>

Or:

<result>
<link>
<bid>0.0001</bid>
<url>http://example.com</bid>
<site>something</site>
<title>hi there</title>
</link>
</result>

site and title are always optional but recommended so we can distinguish and categorize your creatives.

Reporting

Billing

DSPs are only billed for unsold traffic. Meaning all requests that the DSP didn't win. A count of these requests can be found in the DSP Reporting. The CPM fee Atomx bills for these unsold requests can be found on your network overview page as the DSP Fee.