Postback troubleshooting

Postback Macro Not Replaced

Callbacks arrive but contain literal {clickid} or {payout} strings because the template never swapped values.

Introduction

Macro Not Replaced means templates still contain placeholder braces when the callback hits its destination.

The root cause typically lies in mismatched macro names, extra encoding, or platforms that stripped braces.

Why the problem happens

Macros are only substituted when the tracker recognizes the token. If naming conventions drift or placeholders get double-encoded, nothing swaps.

Partners and agencies often copy templates across offers without updating macros, so literal braces slip into production.

Common causes

Pinpoint who owns each macro: tracker, network, or advertiser. Compare documentation to your live template so you see the mismatch.

Step-by-step troubleshooting

Create a side-by-side comparison of the desired payload and the actual callback. Correcting macros is straightforward once you see the difference.

  1. Document macro expectations

    List tracker-supported macros and partner-required fields. Highlight mismatches.

  2. Inspect the live template

    Review the callback template for brace encoding, casing differences, or typos.

  3. Replay with Postback Tester

    Fire the template and confirm which macros still appear literally.

  4. Update and retest

    Rename macros, adjust encoding, and retest until the payload carries real values.

  5. Add linting

    Set up a sanity check that flags callbacks containing curly braces.

Tools that help solve the problem

Conclusion

Build a macro glossary for every partner and share it with agencies.

Monitor callbacks for literal braces and treat alerts as high priority.

Related issues

Tracking bugs rarely travel alone. Explore these related guides to build a full remediation plan.

Postback Not Working

Networks show zero conversions because callbacks never trigger or fail validation.

View guide >

Postback Not Received

Trackers show callbacks firing, yet partners insist nothing arrived because firewalls or filters intercepted them.

View guide >

Click ID Not Stored in CRM

Landing pages capture identifiers, but middleware or the CRM drops them before analysts ever see the data.

View guide >

Recommended tools

Use this diagnostic stack whenever you need to capture evidence or verify that a fix worked.

Redirect Checker

Check HTTP redirect chains and status codes.

Open tool >

Click ID Extractor

Extract click IDs and tracking parameters from URLs instantly.

Open tool >

UTM Builder

Create campaign tracking URLs with UTM parameters.

Open tool >

Postback Tester

Fire sample conversion callbacks and read the raw response before launch.

Open tool >

Pixel Scanner

Verify Meta, TikTok, and Google tags fire on any landing page instantly.

Open tool >

Knowledge base articles

Need deeper theory? These long-form KB articles expand on the concepts touched in the troubleshooting guide.

Postback macro explained

Understand how macros map tracker data into partner payloads and how to manage them as your funnel evolves.

Read article >

How to test a postback

Build a repeatable QA routine for postbacks before launching campaigns or onboarding new partners.

Read article >