Migrate a Conversion

Overview

The API Comparison table highlights the shared actions and API methods between IQM and The Trade Desk for creating and managing Conversions. Select an endpoint to review each platform's relevant API documentation. By comparing APIs, you can migrate your workflow from The Trade Desk to IQM.

For a comprehensive overview of IQM's Conversion services, see the Conversions API.

API Comparison

Base URLs

  IQM: https://app.iqm.com
  
  TTD: https://api.thetradedesk.com

Action	IQM Endpoint	The Trade Desk Endpoint	Notes
Get Conversion Details	GET/api/v3/conversion/{conversionId}	GET/v3/trackingtag/{trackingTagId} GET/v3/tracking/universalpixel/{universalPixelId}	IQM endpoint returns typeId parameter specifying whether the Conversion is a Pixel (1) or Postback (2). The Trade Desk endpoint returns TrackingTagCategory specifying whether Conversion is a StaticTag or a UniversalPixelTag.
Get List of Conversions	GET/api/v3/conversion/list	POST/v3/trackingtag/query/advertiser
Create a Pixel Conversion	POST/api/v3/conversion/pixel/add	POST/v3/trackingtag
Create a Postback Conversion	POST/api/v3/conversion/postback/add	POST/v3/tracking/universalpixel
Update a Conversion	PATCH/api/v3/conversion/pixel/update PATCH/api/v3/conversion/postback/update	PUT/v3/trackingtag PUT/v3/tracking/universalpixel
Assign Conversion to a Campaign	PATCH/api/v3/conversion/assign-to/campaign	POST/v3/campaign PUT/v3/campaign	IQM endpoint supports assigning multiple Conversions to multiple Campaigns, or removing from multiple Campaigns. The Trade Desk assigns tracking tags in the create and update Campaign endpoints with the CampaignConversionReportingColumns object.

More Conversions Resources

IQM:

• Conversions API
• Choose your Conversion

TTD:

• Tracking Tags