Troubleshooting

Most integration issues fall into one of three categories: attribution was never captured, attribution was lost before order submission, or the submitted order did not produce the outcome you expected in Affilibee. This page is intended to help you narrow the problem down quickly.

The fastest way to isolate an issue

When something is wrong, check the flow in order:

1. did the incoming affiliate link contain the expected slug
2. did your platform store that slug at visit time
3. did the created order still contain that slug
4. did your platform send the order to Affilibee successfully
5. did the order appear in Affilibee with the expected attribution and commission result

That sequence usually tells you whether the problem belongs to the affiliate link, your attribution handling, the order payload, or your Affilibee configuration.

The order was not attributed

If an order appears without the expected affiliate attribution, the first thing to check is whether the affiliate slug was still present on the order at the moment your platform submitted it. Affilibee can only use the attribution data your system sends.

If the slug was lost between arrival and checkout, inspect your cookie or attribution persistence logic first.

The wrong affiliate was credited

This usually points to attribution behavior on your side rather than the API request itself. Check whether your platform uses last-touch attribution, whether a later affiliate click replaced the earlier one, and whether the stored slug on the order matches the affiliate you expected.

If the stored slug already points to the wrong affiliate before submission, the issue is upstream from Affilibee.

The request was not accepted

If your platform attempted submission but Affilibee did not accept the request, inspect the response and the request payload first. Confirm that you are sending the correct authentication token, that the order data matches the API requirements, and that the submission is happening from the right point in your order lifecycle.

Use Authentication for the required token format and Create order as the source of truth for the endpoint contract.

The order appears, but the commission looks wrong

If the order is visible in Affilibee but the commission result is unexpected, review your merchant configuration before assuming the submission was wrong. Commission results depend on the active tier, default rate, and any matching product segments.

That usually makes this a configuration question, not an API question. Review Commissions and Core concepts.

The order exists in your platform, but not in Affilibee

If the order was created correctly in your system but never appears in Affilibee, verify that your submission trigger actually ran when the order entered the correct state. Many integration issues come from sending too early, not sending at all, or silently swallowing an error response.

This is where request logging on your side becomes especially valuable.

When to escalate with support

If you need help from support, include the order identifier from your own system, the affiliate slug you expected, the approximate submission time, and any relevant request or response logs. That usually makes the issue much faster to diagnose than a general description of the symptom.

Where to go next

If you need to validate the happy path again, return to Testing your integration. If you need to revisit the intended implementation flow, return to API integration.