How to Set Up Postback URLs in Impact.com

Impact.com calls their postback feature an Action Tracker URL. Here's how to wire one up so your Meta CAPI or Google Ads attribution stays accurate.

1. Find the Action Tracker settings

1. Log into Impact as the partner (publisher).
2. Open Settings → Action Tracker URLs.
3. Click Create New Tracker and pick the action you want to receive (usually Sale).

2. Build the URL

Use the Impact macros for the data you need:

https://yourdomain.com/p?click_id={SubId1}&payout={Payout}&order_id={OID}&currency={Currency}&status={ActionStatus}

Useful macros:

• {SubId1} — the click ID you injected on landing (e.g. fbclid).
• {Payout} — your commission.
• {OID} — Impact's unique action/order ID. Use this as your idempotency key.
• {ActionStatus} — PENDING, APPROVED, REVERSED. Filter to APPROVED-only if you want clean signal.

3. Pass the click ID through SubId1

On your landing page, capture fbclid/gclid from the URL and forward it to your Impact link as subId1:

https://goto.merchant.com/abcd?subId1=ENCODED_FBCLID

Always URL-encode the value. Impact does not encode SubIDs for you.

4. Test the postback

From the Action Tracker page, click Send Test. Watch your endpoint logs — you should see a request with the test macros populated.

5. Verify in production

Run a real test purchase. The postback should arrive within minutes of the action being recorded. Check three things:

• The SubId1 matches the original click ID you set.
• The payout and currency look right.
• Your downstream platform (Meta CAPI / Google Ads) shows the event.

Gotchas specific to Impact

• Action Trackers fire on status changes. If you only forward APPROVED, you'll wait days. Forward PENDING for fast feedback, dedupe by OID.
• SubId1 is limited to 256 characters. Don't pack JSON in there.
• Test postbacks come from Impact's IP range — whitelist if you firewall.