| If the Personalization API response contains a reference to a product that doesn't exist in the dashboard, Appcharge silently filters out that offer. The player sees an empty or partial store. |
What happens
Appcharge validates each offer in the Personalization API response against the products configured in your Publisher Dashboard. If an offer references a product that does not exist — for example, a product SKU that has been deleted or renamed — the system generates a Personalization API invalid offer error and removes that offer from what the player sees.
How to identify the cause
- Check whether the player was able to see offers at a later time (transient vs. persistent issue)
- Ask your backend team to verify the Personalization API response for the affected player — look for any productsSequence entries referencing product IDs or SKUs
- Cross-check each product SKU in the Personalization API response against the products configured in your Publisher Dashboard
Common causes
- A product was deleted from the dashboard but the Personalization API endpoint still returns it in offer definitions
- A product was renamed in the dashboard but the old SKU is still referenced in the Personalization API payload
- A new offer was created and added to Personalization API before the corresponding product was created in the dashboard
How to fix
Recreate the missing product in the Publisher Dashboard (matching the exact SKU referenced in your Personalization API payload), or update your Personalization API endpoint to remove references to the non-existent product.