Testing Server Postback

Guide to testing server postback implementation

Heather Clark avatar
Written by Heather Clark
Updated over a week ago

The steps below will guide you through the process of completing a test purchase to ensure that your postback is firing properly.

Directions

1. Copy your Offer ID.

Go to Reporting > Sales Tracking, then select your offer. Click “Instructions” to locate your offer ID.

Next, copy the ID after "offer_id" in your postback URL.

2. Create a test link.

To create a test link, copy your Offer ID from above and paste it into the URL below where it says "OFFER ID".

https://aspireiq.go2cloud.org/aff_c?offer_id=OFFER_ID&aff_id=1&source=testoffer&aff_sub=testoffer

3. Click on your test link and complete a purchase on your site.

Add an item to your cart and fill out your billing and shipping information, then complete the purchase. We recommend testing without using a discount code to ensure the order amount is being passed through properly.

4. Reach out to confirm that your purchase was captured and tracked.

Once you reach the order confirmation page, please reach out to our Support Team at help@aspireiq.com or email your CSM/Implementation Manager, and provide us with your Offer ID and the order amount.

Please note, this test conversion will not appear in your Sales Tracking dashboard. We will check if the conversion came through on our end, then let you know if it was successful or not.

Once confirmed, your sales offer is ready to track traffic and conversions driven by your creators! 🎉


Why might your test fail?

When testing Server Postback w/Transaction ID, the transaction id is generated based on:

  • IP Address - unique to your computer (can use VPN to change this)

  • Date

  • Offer ID

  • User-Agent - browser (can switch browsers to change this)

This means if you try and click on an affiliate link and none of the above has changed, you will get the same transaction id. If you have already had a conversion with that transaction id, you will not be able to test again as the conversion will be considered a duplicate due to the same transaction id. We recommend changing browsers, using a VPN to change your IP Address, or waiting until the next day before testing again.

Did this answer your question?