Postback URL Builder
Keeps macro names consistent across partners.
Open tool >Postback troubleshooting
Postback Macro Not Replaced
Callbacks arrive but still contain literal {clickid} or {payout} strings because the template never swapped values.
Introduction
Macro Not Replaced corrupts reporting quietly. Partners receive literal placeholders, so conversions cannot be matched to traffic.
Why the problem happens
Macros substitute only when the platform recognizes the token. Naming or encoding mistakes keep them literal.
Common causes
- Tracker expects {subid} but the template uses {clickid}.
- Spreadsheet tools double-encode braces into %7B and %7D.
- Partners strip parameters they do not recognize.
Step-by-step troubleshooting
-
Document macro expectations
List tracker macros and partner-required parameters. Highlight naming differences.
-
Inspect the live template
Check for encoding, casing, or typo issues inside the callback URL.
-
Replay with Postback Tester
Fire the template and confirm which placeholders stayed literal.
-
Update and retest
Rename macros or adjust encoding until the payload carries real values.
Tools that help solve the problem
Postback Tester
Shows exactly which macros substituted correctly.
Open tool >Redirect Checker
Confirms the original click had identifiers ready for substitution.
Open tool >Conclusion
Maintain a macro glossary, require template reviews, and watch for literal braces in payloads.