Can ClickMagick send a Postback to another service?
You bet! In ClickMagick, we call these “Custom Postbacks” and you can set one up for any Tracking link or Campaigns project so that when an Action, Engagement, or Sale is generated the Custom Postback request will be sent and your service will be notified.
To set up a Custom Postback just follow these steps:
Get your Postback URL from the service you want ClickMagick to send the Postback to.
If you use any of these tokens in the Custom Postback URL they will be replaced with actual values when the Custom Postback request is sent. For example, [amount] would be replaced with the actual amount for a Tracking Link sale, and [cmc_amt] would be replaced with the amount of a Campaigns sale.
Can you show me an example?
With Tracking Links, as a general rule you’ll need to use the [s1] and [amount] tokens in your Custom Postbacks.
The [s1] token represents the Click ID or Transaction ID that was originally sent to ClickMagick by the original service (typically a traffic source), and in the case of a sale, the [amount] token represents the amount of the sale that was made. So with a Custom Postback for Tracking Link Sales you would normally use both of these tokens.
For example, your Postback URL for MGID would look like this, with “golf82573” being changed for different offers:
Note: ClickMagick can both send and receive postback requests. The “Custom Postbacks” talked about in this article are postbacks sent from ClickMagick to other services, whereas the Postback URL List and Postback Log tools are used to manage postbacks that are sent to ClickMagick from other services. To learn more about the differences between these two types of Postback, read this article: