Delivery Logs

One place to see every conversion message that moved between AffClix and your partners: the postbacks advertisers send you, the postbacks you send to affiliates, and the conversions you push to ad platforms like Google and Meta.

What Delivery Logs Are

When a conversion "goes missing", the cause is almost always one hop in the chain: the advertiser never told you, you never told the affiliate, or the ad platform refused the upload. Delivery Logs show each of those hops as it actually happened, with the exact URL and the answer that came back.

Open it from Reports → Delivery Logs. You land on the first tab your role is allowed to see, and a tab strip at the top lets you switch between the others.

Every tab opens on today

If the table looks empty, widen the date range first. Searching by Click ID is an exact match, so paste the full ID.

The Three Tabs

TabDirectionWhat it shows
Advertiser PostbacksAdvertiser → AffClixEvery conversion call an advertiser made to your postback URL, and what AffClix decided: accepted, click not found, IP not whitelisted, duplicate event blocked and so on.
Affiliate PostbacksAffClix → AffiliateEvery postback AffClix fired to an affiliate's server, the final URL with macros filled in, and the HTTP response their server returned.
CAPI DeliveryAffClix → Ad platformEvery server-side conversion upload to Google Ads, Meta, TikTok and other Conversions API destinations, with the platform's reply.

The first two tabs have their own detailed guides: Advertiser Postbacks and Affiliate Postbacks.

Don't see a tab?

Team members only see the tabs their role allows. The Advertiser and Affiliate Postbacks tabs each need their own report permission, which an account owner can grant under Settings → Team Members.

CAPI Delivery

This tab lists each attempt to send a conversion to an ad platform through a Conversions API destination. One row is one attempt, so a conversion that was retried appears more than once.

ColumnMeaning
TimeWhen the upload was attempted.
PlatformWhere the conversion was sent, for example Google Ads or Meta.
Integration IDThe Conversions API destination that sent it.
Conversion ID / EventThe AffClix conversion and the event name it was sent as.
StatusDelivered or Failed.
HTTP / ErrorThe platform's response code and, on failure, its error message.
AttemptsHow many times this conversion has been tried.

Filter by a single Conversion ID to see every attempt for that conversion. The date range is ignored when you do this, so older retries still show up.

Only approved conversions are sent

Pending, rejected or cut-back conversions are never uploaded to an ad platform. If a conversion is missing from this tab, check its status in the Conversions report first.

Which Tab Do I Need?

The questionLook here
"The advertiser says they sent a conversion, but I don't see it."Advertiser Postbacks. Search by Click ID and read the status remark.
"My affiliate says they never received a conversion."Affiliate Postbacks. Check the response code their server returned.
"Google Ads or Meta isn't showing our conversions."CAPI Delivery. Look for Failed rows and read the error.
"The conversion is in AffClix but the payout looks wrong."None of these. Use the Conversions report.

Good to Know

A delivered postback can still be refused. On the Affiliate Postbacks tab, a 4xx response means their server received the call and rejected it. That needs fixing on their side, not yours.
Test traffic lives elsewhere. Postbacks fired by the Postback Tester are recorded in Test Logs, not here.
Use it at launch. After a new advertiser or affiliate goes live, check this report once you expect the first conversions. It is the fastest way to confirm the integration really works.
Rate this article
★★★★★
Thanks for rating!

Was this article helpful?