Skip to content
Browse documentation

Inbound postback log (Received)

See every conversion request your workspace received, with its result code, parameters and the conversion it created.

Last updated 4 min read

On this page

The inbound log records conversion requests — /pb, /postback, /conversion, /px (and /px.gif, /px.js deliveries) and the landing-page SDK's /lp calls — together with what happened to each one, including requests that never became a conversion (unknown click, malformed amount, wrong offer). Use it first when an advertiser says "we sent it".

Open the log#

  • Network: Reporting → Postback log → Received tab (/app/reports/postbacks?tab=received). Needs the postbacks.read permission.
  • Advertiser portal: Postback log (/advertiser/postbacks) shows the requests attributed to that advertiser.

Pick the date range at the top. Entries appear within a few seconds and are kept for 90 days.

Columns#

ColumnContent
ReceivedTime of the request (your time zone).
ResultThe result code (below); hover it for the status reason or error message.
RequestMethod, path and kind (s2s, pixel, js or lp).
ParametersThe query string and form fields, sorted by name. token and any name containing secret or password are shown as REDACTED; email is shown as sha256: plus the first 16 hex characters of its hash. Up to 4 KiB.
ConversionThe conversion ID (links to the conversion), or —.
IPThe sender's IP address.
Tokenworkspace, advertiser or — (pixels).
HTTPThe HTTP status TrackCrown answered.
msProcessing time in milliseconds.

The KPI strip shows Received, Accepted (stored approved/pending, updated or forwarded), Duplicates & rejected and Errors (with the number of token problems: invalid, missing, or an inactive advertiser's).

Result codes#

Filter with Result in the toolbar, or search parameters, IP address or conversion ID.

CodeLabelMeaning
approvedApprovedNew conversion stored approved.
pendingPendingNew conversion stored pending (default status, hold, throttle or rule).
rejectedRejectedStored rejected with a reason (outside_window, too_fast, cap_exceeded, ip_not_allowed, fraud:…, rule:…, postback…).
duplicateDuplicateStored as a duplicate of an existing conversion.
updatedUpdated (reversal)An existing conversion was changed by this request.
forwardedForwarded (migration)An unknown click ID was forwarded to the advertiser's migration postback URL.
testTesttest=1 dry run; nothing stored.
invalid_tokenInvalid tokenWrong token, or a token not valid for the offer.
token_requiredToken missingNo token on an S2S request.
advertiser_inactiveAdvertiser inactiveThe advertiser token of a Paused or Inactive advertiser (HTTP 401); nothing stored.
unknown_clickUnknown clickNo click with this click ID / gclid / gbraid / wbraid / msclkid in the workspace.
unknown_conversionUnknown conversionconversion_id not found.
unknown_offerUnknown offerOffer missing, unknown or not matching the click.
coupon_errorCoupon problemUnknown, inactive or wrong-offer coupon.
ip_not_allowed(shown as code)conversion_id update or migration forward from an IP outside the allowlist.
malformedMalformedHTTP 400/413: bad amount, status, currency, click ID format, unknown event, body.
method_not_allowed(shown as code)Not GET/POST.
unavailableUnavailable (503)A dependency was briefly down; the sender should retry.
errorOther errorAnything else (for example offer does not accept pixel conversions).
param, gclid, gbraid, wbraid, organic, direct(shown as code)Landing-page SDK (/lp) calls: how the click ID was found or created (The /lp endpoint).

Which workspace a request is filed under#

Each entry is filed under the workspace, advertiser and offer the engine identified while processing it. A request that fails before that point — a missing or invalid token, a malformed parameter, a pixel or /lp call without a known click — is filed by what it names, in this order:

  1. the owner of its token (also a token that was since regenerated, or the token of a paused advertiser);
  2. its offer_id / offer;
  3. its click_id / transaction_id / tid (looked up in recent clicks, then in the click store);
  4. the tracking domain it was sent to, when that domain belongs to one workspace.

So token problems, malformed requests and failed pixels or SDK calls appear in your Received tab — and, when they carry the advertiser's token or offer, in the advertiser portal. The Token missing and Invalid token filters list them.

A request that names none of these (no token or an unknown one, no known offer or click, sent to a shared tracking domain) belongs to no workspace. Platform administrators see those under Admin → Unattributed postbacks (/admin/postbacks, same columns and filters, 90 days). If a sender's requests are missing from your Received tab, check the HTTP response it received (for pixels the X-ArcTrack-Conversion header) and verify the token under Settings → Postback tokens.

Typical investigations#

"We sent 100 sales, you show 95."

  1. Received tab, date range of the sales, filter Result = Duplicate, Rejected, Unknown click.
  2. Duplicates: the advertiser retried or reused an order ID (Duplicates).
  3. Rejected: read the reason (codes).
  4. Unknown click: the click ID was altered, truncated, from another tracker, or older than click retention.
  5. If some requests are missing entirely, see Which workspace a request is filed under.

"A conversion changed status by itself." Open Reports → Conversions → row menu → Change history, or search the Received tab for its conversion ID to find the reversal request.

Outbound deliveries#

Postbacks you send to partners are on the Delivery log tab — see Postback delivery, testing and retries.

Something unclear or missing in this article?Tell us