Platform-Neutral Diagnostic Tool

Postback Troubleshooting Guide

Identify exactly why conversion postbacks are missing, delayed, or showing discrepancies between your MMP (AppsFlyer, Adjust, Singular) and bidding engine.

Step 1: Select Your Current Symptom

Detailed Root Cause Analysis

Zero Conversions Arriving (0 Events Logged)

Your campaign is serving impressions and clicks, but the DSP dashboard logs 0 installs or conversion events.

11. Macro Expansion Failure (click_id)

The tracking URL rendered on the creative did not replace {click_id} or {event_id} with a real unique hash, resulting in literal '{click_id}' being passed to the MMP.

Recommended Resolution:Check your DSP creative tag setup. Ensure the macro matches the DSP's exact token syntax (e.g., {click_id} vs %CLICK_ID% vs ##CLICK_ID##).

22. Server-to-Server SSL Certificate or Redirect Blocking

The DSP postback endpoint URL is HTTP instead of HTTPS, or returns a 301/302 redirect. Many MMPs (AppsFlyer, Adjust) drop postbacks if endpoints trigger redirects or have expired SSL certificates.

Recommended Resolution:Test your raw postback URL via curl or Postman. Ensure it returns an immediate HTTP 200 OK without intermediate redirects.

33. MMP Partner Integration Toggle

In the MMP dashboard (e.g., AppsFlyer Configuration > Integrated Partners), 'Send all in-app events' or the primary postback toggle was left unchecked or restricted to 'Only attributed to this partner'.

Recommended Resolution:Log into your MMP, open the Visprisca or DSP partner configuration, and verify that postbacks are active for both install and target in-app events.

Step 2: Postback URL Syntax Inspector

Paste your raw postback or click tracking template to check for common syntax errors, missing macros, or insecure protocols.