Troubleshooting Integrations
Fix missing conversions, click_id errors, and data validation issues across native and custom AnyTrack integrations.
Before you troubleshootMake sure the Tracking Tag is installed on every page where you send traffic. If you use a free plan, confirm you have not exceeded your monthly session limit.
Conversion Sources
If conversions are missing, triggering errors, or returning unexpected data, start by checking the Event Log in your AnyTrack dashboard. The Event Log shows the raw conversion payload, any errors, and the processing status for each event.
Identify whether the issue affects a native integration (preconfigured in the Integration Catalog) or a custom integration you set up manually. The root causes differ between the two.
Native Integrations
Native integrations are platforms preconfigured in the AnyTrack Integration Catalog. They use standardized Postback URLs and predefined conversion mapping, so data should flow without manual configuration.
The most common native integration error is a missing or unknown click_id. This means AutoTag did not append the AnyTrack click_id to the offer link. Check that your affiliate links use standard a elements and are not hidden behind JavaScript redirects. If AutoTag cannot detect the link, add the --CLICK-ID-- token manually to the URL.
Conversion Data Shows No Error but Is Not Validated
If a conversion appears in the Event Log without an error but is not validated:
- Verify the Postback URL in your affiliate network matches the one AnyTrack provides. Update it if they differ.
- Copy the Event Reference from the Event Log and contact support with the reference ID.

The Integration Event Logs where you can get the payload reference
No Conversions Arriving
If no conversions appear in the Event Log at all:
- Confirm the AnyTrack Postback URL or webhook is set and active in your platform integration settings.
- Check that your affiliate network has not paused or reset the postback configuration.
Custom Integrations
Custom integrations use the Custom Integration builder and require manual setup with standard tracking parameters. Because the configuration is manual, errors usually come from incorrect parameter mapping or missing tokens.
Common custom integration errors include missing click_id, wrong conversion attributes, or incorrect Postback URL tokens. Verify that you pass the correct AutoTag subid parameter in the offer link, and that each token in your Postback URL (e.g., {amount}, {transaction_id}) matches the exact field name your platform replaces at conversion time. See Event Attributes for the full list of supported parameters.
Integration Troubleshooting FAQ
FAQ was last reviewed on 2026-03-18
click_id to the offer link. Check that your links use standard a elements and are not behind JavaScript redirects. For custom integrations, verify the subid parameter is mapped correctly. If AutoTag cannot detect the link, add the --CLICK-ID-- token manually.click_id and cannot be attributed. This is normal for recently connected integrations. New conversions from tracked traffic will process correctly.Updated 6 days ago
