Integration Event Log

The Integration Event Log displays conversion data received from your integration sources. Use it to troubleshoot integrations and verify the exact parameters your conversion source sends.

Locate the Integration Event Log

1. Open the AnyTrack Dashboard and go to Integrations
2. Click the integration you want to troubleshoot
3. Open the Events Log tab
4. Click an event to inspect it
5. The Payload appears on the right panel

Understanding the Payload

The payload is the raw data that AnyTrack received from your integration, typically in JSON format. It shows all parameters and their corresponding values.

Event Status Messages

Each event in the log has a status that tells you whether the conversion was recorded, skipped, or failed.

OK (Green)

The conversion was successfully recorded. Attributes listed with the event:

• Conversion Name — For example, Purchase
• Conversion Value — The monetary value
• Click Id — Click to view the conversion timeline

Discarded (Gray)

A discarded event means AnyTrack received the data but intentionally skipped it. This is normal behavior, not an error. Common reasons an event is discarded:

• Wrong conversion status — The conversion source sent a status that does not qualify as a trackable conversion. For example, a pending or rejected sale from an affiliate network. AnyTrack only tracks confirmed or approved conversions.
• Filtered event type — The event type is not mapped in your Conversion Mapping settings. If you only mapped Purchase and Lead, other event types sent by the source are discarded.
• Test or sandbox data — Some integrations send test conversions during setup. AnyTrack discards these when they lack valid tracking parameters.

Deduplicated (Gray)

A deduplicated event means AnyTrack already processed this exact conversion and skipped the duplicate. AnyTrack uses the transactionId (and other event attributes) to identify duplicates. This prevents the same conversion from being counted and sent to ad platforms more than once.

Common scenarios where deduplication occurs:

• An affiliate network fires the same postback URL twice for a single sale
• A webhook retries after a timeout, sending the same conversion again
• Multiple integrations report the same transaction (for example, both a Shopify webhook and a direct API call)

Learn more about how this works in the Deduplication article.

📘

Note

OK, Discarded, and Deduplicated statuses all indicate the integration works as expected. No action needed.

Tracking Errors

Errors prevent conversion tracking. Each error message points to a specific issue you can diagnose and fix.

Can't Find refId

Example message: Error: Can't find refId: [email protected]

The refId (reference ID) is an identifier AnyTrack uses to match a server-side conversion back to a web session. AnyTrack automatically collects Event Attributes from your website, such as email addresses captured through form submissions. When a conversion arrives from a server-side source, AnyTrack attempts to match it using these collected attributes.

AnyTrack prefers the AnyTrack click_id for matching, but when the click ID is not available, it falls back to other identifiers like email, phone number, or external IDs. This error appears when the refId value in the conversion payload does not match any previously collected attribute in AnyTrack.

Common causes:

• The email or identifier in the conversion was never captured on the website (the visitor did not fill out a form, or the Tracking Tag was not installed on the page where the form exists)
• The visitor used a different email at checkout than the one captured on the landing page
• The attribution window expired before the conversion occurred

No Click ID Value Passed

Example message: Error: No click id value passed to the "cid" parameter

This error means the conversion source sent a postback or webhook, but the parameter that should carry the AnyTrack click ID was empty. The parameter name varies by integration. For example, it might be cid, sub5, sub_id, aff_sub, or whatever subid parameter your specific affiliate network or conversion source uses.

Common causes:

• The AnyTrack click ID was not appended to the affiliate link or form. Check that AutoTag is active, or that you manually added the --CLICK-ID-- token to your links.
• The conversion source does not store or return the subid value. Verify that the network or platform supports passing back the click ID parameter in its postback or webhook.
• The wrong parameter name is configured in the postback URL. Double-check that the parameter name in the postback matches the one the network actually populates.

Unknown Click ID

Example message: Error: Unknown click_id

AnyTrack received a click ID value, but no matching click exists in the system. This typically happens when the attribution window has expired, or the click ID was generated by a different AnyTrack property.

Can't Find Event

This error means AnyTrack received a conversion reference (such as a transaction ID or event identifier), but no corresponding event exists in the system. This can happen when the initial event was not tracked (for example, the Tracking Tag was missing on the page), or when the conversion source references a transaction that AnyTrack never recorded.

Unauthorized Asset

This error means the incoming event references a property that is not associated with your AnyTrack account. Check that the integration is connected to the correct property. If you manage multiple properties, verify the postback URL or webhook points to the right one.

No IP Match

AnyTrack attempted IP-based attribution but found no matching session. This is a fallback method used when no click ID or reference ID is available. IP matching has lower accuracy and may not find a match if the visitor's IP changed between the click and the conversion.

📘

Note

Each integration has specific requirements. Follow the in-app integration instructions for setup and troubleshooting.

Related Articles

• Troubleshooting Integrations
• Event Attributes
• Deduplication