Skip to content
Moviie

Troubleshooting

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.

Updated on October 23, 20264 min read

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

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

If no postback appears

  1. Confirm that the integration is active.
  2. Compare the URL in your checkout with the one displayed by Moviie.
  3. Check that the platform is configured to send approved-purchase events.
  4. Use the checkout's test, not only Moviie's Test action.
  5. 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.

In the earlier mapping format, 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.

Delivery content may be retained for up to 180 days. Retention does not make every delivery eligible for replay. For earlier integrations, contact support@moviie.ai to assess eligible history after correcting the mapping.

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.

Diagnose a universal integration

Receiving a request, interpreting its fields and attributing a sale are separate outcomes. An acknowledgment with receiptId confirms delivery, not a sale in the funnel. Check integration health. A preview that matches a key does not prove a real sale either.

  • Interpretation failure: review required fields, paths, amount units, currency and event translation. Load another sample if it expired.
  • Test processed: the notification was handled as a test without creating revenue. Real sales must arrive without the test marker.
  • Duplicate or older update: resending does not create another sale or replace newer data.
  • Conflicting data: check order identity, currency, key, source time and reversal totals. Do not change the order identifier to bypass duplicate protection.
  • Waiting for the original purchase: send the corresponding purchase. The reversal is reconsidered automatically while its content remains retained.

Publishing a correction does not silently reinterpret earlier deliveries. For an eligible failed delivery, open its preview in integration health, inspect the result and explicitly confirm replay. Replay can record a real sale. Test, already normalized, truncated, expired or purged deliveries are ineligible. Retention of up to 180 days is a limit, not a guarantee that any event can be replayed.

For a revision conflict, reload the configuration before trying again. Give support the receipt identifier, time and status. Do not send personal payload data, keys or notification URLs.

Keep learning

Keep going

Guides that help with the next step.

HUMAN SUPPORT

Still need help?

Tell us what is happening. Our team will help you find the next step.