Skip to main content
All CollectionsSales TrackingJavascript Tracking
Test & Troubleshoot Javascript Tracking
Test & Troubleshoot Javascript Tracking

A Step-by-Step Guide to Testing Your Javascript Postback Implementation

Heather Clark avatar
Written by Heather Clark
Updated this week

Follow these steps to complete a test purchase and verify that your Javascript Postback tracking is set up correctly to record clicks and conversions.

Placing a Test Order

Step 1: Copy your Offer ID

Go to Reporting > Sales Tracking, then select an offer. Click the information icon ("i") next to the offer name, then click “Instructions”.
​

Locate the postback URL in the highlighted box. Copy the number that appears immediately after offer_id=.
​


For example, in the URL below, the offer ID is 12345.
​https://get.aspr.app/aff_lsr?offer_id=12345&amount=AMOUNT

Step 2: Create a test link

To create a test link, take the Offer ID you copied in Step 1 and paste it into the URL below, replacing OFFER_ID with your Offer ID.
​

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

Step 3: Click on the test link and make a test purchase

Click on the test link you created in Step 2. Add an item to your cart and complete the purchase as a regular customer would.

Important: Avoid using a 100% discount code so we can confirm the recorded amount reflects the actual sale amount. You may apply a partial discount if needed and can cancel the order immediately after placing it.

Step 4: Confirm your test purchase was tracked

After placing the test order, reach out to Aspire’s Support Team at [email protected], or contact your CSM or Implementation Manager. Please provide the following details:

  • Offer ID

  • Order subtotal amount

  • Order number

Note: This test purchase will not appear as a conversion in your Sales Tracking dashboard. Our team will verify if the conversion was recorded on our end and notify you of the results.

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

Frequently Asked Questions

Why is the recorded sale amount different from the order subtotal?

  • Ensure the correct amount is passed in the postback URL.

  • If the order was placed using a non-USD currency, make sure the amount is properly converted to USD before being sent in the postback URL. See this article on Aspire's recommendations for managing currency conversions.

I placed a test order, but it’s not appearing in the Sales Tracking dashboard. Why?

  • Test purchases made using a test link will not show up in the dashboard and will only be tracked in Aspire’s backend. Contact Aspire Support at [email protected] to confirm if the conversion was recorded.

  • If you made a test purchase using a unique link generated within an offer, there may be a delay before the conversion appears in your reporting. Wait one hour and check again.

I placed two test orders, but the second one wasn’t recorded as a conversion. Why?

When testing an offer that uses Javascript Postback or Server Postback with Transaction ID as the conversion tracking method, the transaction id is generated based on:

  • Date

  • Offer ID

  • IP Address (unique to your computer)

  • User-Agent (browser used to place the order)

If you click an affiliate link multiple times without changing any of the above factors, the same transaction ID will be generated. Since conversions with duplicate transaction IDs are rejected by default, your second test order won’t be recorded.

To test again, try one of the following:

  • Use a different browser

  • Connect to a VPN to change your IP address

  • Wait until the next day before retesting

Troubleshooting Tips

1. Check your Offer setup.

Ensure the Offer URL contains transaction_id={transaction_id} and the conversion tracking method is set to "Javascript Postback".

2. Inspect Network Calls and Look for Console Errors.

Open your browser's Developer Tools while placing a test order to inspect the Network tab and check for any console errors

Step-by-Step Instructions
​

To verify that the postback request is being sent, use your browser’s developer tools to check if the postback URL is triggered when a test order is placed.

The steps below use Chrome's DevTools. If you're using a different browser, the process may vary slightly.
​

Step 1: Open Developer Tools before clicking the test link

  1. Open a new browser window or tab

  2. Right-click anywhere on the page and select Inspect to open the Developer Tools.

  3. Navigate to the Network tab

  4. Clear existing network logs by clicking the 🚫 icon

Step 2: Verify Request URL

  1. Copy and paste the Aspire test link into your browser's address bar and press Enter

  2. In the Network tab, locate the request with a name that begins with transaction_id or affiliate_id

  3. Click on the request, then navigate to the Headers tab

  4. Under Request URL, confirm that the transaction id or affiliate id is correctly populated after transaction_id= or affiliate_id=
    ​
    ​Note: The parameter names may vary based on your implementation. If the expected values are missing, consult your engineering team to verify the correct query parameters.
    ​

Step 3: Confirm the transaction ID is being stored

  1. Navigate to the Application tab within the Developer Tools

  2. Under Storage on the left-hand side, click Session Storage, then select your website URL

  3. In the filter bar, enter tdl_default to locate the relevant key

  4. Confirm that the value for this key begins with 102

  5. Next, under Storage, click Cookies, then select your website URL

  6. Use the filter bar to search for tdl_default in the cookies list

  7. Verify that the value of the tdl_default cookie matches the transaction ID found in Session Storage.

Step 4: Complete a test purchase

  1. Place a test order on your website, keeping the Developer Tools open throughout the process.
    ​
    ​Note: If you're not tracking purchases, complete whichever action you want to track as a conversion (e.g., filling out a lead gen form or making a reservation).

Step 5: Review the Network Call

  1. After the order is placed, go to the Network tab in your browser’s developer tools

  2. Use the filter bar and enter aff_lsr to search for the relevant request

  3. Click on the request name that begins with aff_lsr

  4. Click on Headers and look under the General section:

    1. Request Method should be GET

    2. Status Code should be 200 OK, which means the postback was received successfully

    3. If you see a 400 or 500 error, this may indicate a formatting issue or a server error
      ​

Step 6: Review the Payload

  1. Click on the Payload tab to inspect the values passed in the request URL

  2. Under Query String Parameters, you should see these parameters:

    • transaction_id or affiliate_id

    • amount (sale amount)

    • adv_unique1 (containing the order ID)
      ​

Step 7: Check for Console Errors

If the postback request did not fire successfully, check for console errors by following these steps:

  1. On the thank-you page, navigate to the Console tab within the Developer Tools

  2. Look for any JavaScript errors related to the tdl.convert call. These may indicate issues preventing the tracking code from firing correctly.​

3. Check for Multiple TUNE Scripts on Your Website

If your test conversion is not being recorded and you work with multiple TUNE networks, this requires a slightly different implementation.

How to Check For Multiple TUNE Scripts

  1. Open Developer Tools

    • Right-click on your website and select Inspect, or press F12 / Cmd + Option + I on Mac.

  2. Search for TUNE Scripts

    • Navigate to the Elements tab.

    • Press Ctrl + F (Windows) or Cmd + F (Mac) to open the search bar.

    • Enter "tune.js" and look for multiple script tags referencing TUNE.

  3. Check the Sources Tab

    • Click on the Sources tab.

    • Expand the list of scripts loaded on your website and look for any URLs related to js.go2sdk.com or other TUNE networks.

  4. Review the Network Requests

    • Navigate to the Network tab and filter for "tdl" or "tune" to see if multiple tracking scripts are loading simultaneously.

  5. Resolve Conflicts

    • If multiple TUNE scripts are present, ensure they are properly configured to support multiple networks by following the steps in the section below titled "How to Adjust Your Setup".

How to Adjust Your Setup

The 'init' call for the TUNE Javascript should reflect all of the partners you are working with. This is how the initialization call should be structured in these cases:

tdl.init({
 '[Network ID For Network A]': '[Tracking Domain for Network A]',
 '[Network ID For Network B]': '[Tracking Domain for Network B]',
 ...
})

Example:

tdl.init({
  'aspireiq': 'https://aspireiq.go2cloud.org',
  'othernet2': 'https://othernet2.go2cloud.org'
})

Aspire's Network ID is "aspireiq" and our tracking domain is https://aspireiq.go2cloud.org.

You must also ensure that you include Aspire’s Network ID in your Offer URLs. The Network ID should be included at the end of the Offer URL as follows:

...&network_id=aspireiq

Example:

https://brand.com?transaction_id={transaction_id}&network_id=aspireiq

Did this answer your question?