Migrate a Conversion

Overview

Xandr refers to their Conversions as Conversion Pixels and Universal Pixels. This page uses IQM's terminology.

The API Comparison table highlights the main actions and API methods for managing Conversions. Select an endpoint from IQM or Xandr to review that platform's relevant API documentation. By comparing APIs, you can migrate your workflow from Xandr to IQM.

API Comparison

Base URLs

  IQM: https://app.iqm.com
  
  Xandr: https://api.appnexus.com

Action	IQM Endpoint	Xandr Endpoint	Notes
Get Conversion Details	GET/api/v3/conversion/{conversionId}	GET/pixel GET/universal-pixel/pixel	IQM endpoint returns typeId parameter specifying whether the Conversion is a Pixel (1) or Postback (2). Xandr endpoints use id query to return Conversion details.
Get List of Conversions	GET/api/v3/conversion/list	GET/pixel GET/universal-pixel/pixel
Create a Pixel Conversion	POST/api/v3/conversion/pixel/add	POST/pixel	Xandr endpoint requires advertiser_id or advertiser_code to create a Pixel Conversion.
Create a Postback Conversion	POST/api/v3/conversion/postback/add	POST/universal-pixel/pixel
Update a Conversion	PATCH/api/v3/conversion/pixel/update PATCH/api/v3/conversion/postback/update	PUT/pixel PUT/universal-pixel/pixel/{PIXEL_ID}
Assign Conversion to a Campaign	PATCH/api/v3/conversion/assign-to/campaign	POST/line-item PUT/line-item	IQM endpoint supports assigning multiple Conversions to multiple Campaigns, or removing from multiple Campaigns. Xandr assigns Pixel Conversions when a Line Item is created or updated with the pixels object.

More Conversions Resources

IQM:

• Conversions API
• Choose your Conversion

Xandr:

• Conversion Pixel Service
• Universal Pixel Service