Migrate a conversion

Migrate a conversion from Beeswax to IQM by comparing each platform's API methods for creating and managing conversions.

Beeswax refers to their conversions as Conversion Tags and Event Tags. This page uses IQM's terminology.

The API comparison table highlights the shared actions and API methods between IQM and Beeswax 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 Beeswax to IQM.

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

API comparison

Base URLs

  IQM: https://api.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/v2/conversion-tags/{id}	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/v2/conversion-tags
Create a Pixel conversion	POST/api/v3/conversion/pixel/add	POST/rest/v2/conversion-tags
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/v2/conversion-tags/{id}
Assign conversion to a campaign	PATCH/api/v3/conversion/assign-to/campaign	POST/rest/v2/conversion-tag-assignments	IQM endpoint supports assigning multiple conversions to multiple campaigns, or removing from multiple campaigns.

More conversions resources

IQM:

• Conversions API guidelines
• Create a conversion tutorial
• Conversions and tracking Help Center article

Beeswax:

• Conversion Events