How to fix postback and attribution errors

Use integration health to find out why a delivery failed, was rejected, or could not be matched to a video session.

Open Sales, find the integration, and select Health. The page shows its latest delivery, attribution rate, rejected signatures, and failures that need review.

Understand each status

Status	What it means	What to do
Received	The delivery arrived and is waiting for processing.	Refresh the page after a few moments.
Processed	The event was validated and normalized.	If the sale is missing, check attribution, event type, and reporting period.
Unattributed	The event is valid but was not matched to a session.	Check the attribution parameter and the URL used for checkout.
Signature rejected	The received secret does not match the integration.	Copy the Hottok, Secret Key, or webhook secret again.
Unsupported event	The delivered status does not map to a known event.	Adjust checkout events or the event map.
Failed	The delivery content could not be processed.	Open the displayed error and review values, currency, and mapping.
Ignored	The delivery arrived while the integration was paused.	Reactivate it before sending another test or event.

If no postback appears

Confirm that the integration is active.
Compare the URL in your checkout with the one displayed by Moviie.
Check that the platform is configured to send approved-purchase events.
Use the checkout's test, not only Moviie's Test action.
Return to Health and select Refresh.

If you rotated the URL, replace it in the checkout. The previous address works for 48 hours and then stops receiving events.

If the signature was rejected

The secret saved in Moviie must match the one used by the platform to sign the delivery. Do not use your account password or an API key intended for another feature.

Create a new integration when you need to replace a secret that cannot be edited on the screen. Test its new URL before removing the previous integration.

If the sale is unattributed

A postback may be processed and still stay out of the funnel. This happens when:

the checkout did not return the attribution parameter;
the key arrived in a different field from the configured one;
the CTA URL already contained another value in the same parameter;
the purchase happened more than 30 days after the key was created;
the key belongs to another organization or does not match a valid session;
the session was identified as a bot or the event was marked as a test.

Open the integration card and check the parameter name. For custom integrations, also review the Moviie key field in Mapping.

If the event is unsupported

For Generic webhook, Zapier, Make, and n8n, open Mapping. Check the Event type/status path and the Event map.

Accepted targets are purchase_approved, payment_pending, purchase_refused, refund, chargeback, subscription_renewed, checkout_abandoned, test, and unsupported.

An unmapped status remains visible in health but does not enter the funnel or revenue.

Fix the integration before reading the funnel

Use Attribution found as a connection-quality signal. A low rate means that some events arrived without a link to the video. The sale-per-play rate is incomplete in this situation.

Postbacks remain available for replay for 180 days. After fixing a mapping, contact support@moviie.ai if you need eligible history to be reprocessed.

When requesting help, include the integration name, platform, approximate delivery time, and the status shown on the screen. Do not send personal buyer data or the signature secret.