Migrate a Conversion

Overview

Beeswax refers to their Conversions as Conversion Tags and Event Tags. 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 Beeswax to review that platform's relevant API documentation. By comparing APIs, you can migrate your workflow from Beeswax to IQM.

API Comparison

Base URLs

  IQM: https://app.iqm.com
  
  Beeswax: https://{buzz_key}.api.beeswax.com

Action	IQM Endpoint	Beeswax Endpoint	Notes
Get Conversion Details	GET/api/v3/conversion/{conversionId}	GET/rest/event	IQM endpoint returns typeId parameter specifying whether the Conversion is a Pixel (1) or Postback (2). Beeswax endpoint returns event_type_id specifying Conversion type. Endpoint uses event_id query to specify event.
Get List of Conversions	GET/api/v3/conversion/list	GET/rest/event
Create a Pixel Conversion	POST/api/v3/conversion/pixel/add	POST/rest/event
Create a Postback Conversion	POST/api/v3/conversion/postback/add
Update a Conversion	PATCH/api/v3/conversion/pixel/update PATCH/api/v3/conversion/postback/update	PUT/rest/event
Assign Conversion to a Campaign	PATCH/api/v3/conversion/assign-to/campaign	POST/rest/event_assignment	IQM endpoint supports assigning multiple Conversions to multiple Campaigns, or removing from multiple Campaigns.

More Conversions Resources

IQM:

• Conversions API
• Choose your Conversion

Beeswax:

• Conversion Events

warning

The Conversion Events page for the Beeswax API corresponds to their legacy 0.5 versioning. Information may not accurately reflect the endpoints linked here for the 2.0 versioning.

See the Migrating from 0.5 to 2.0 REST API page for more information.