Troubleshooting and support#

Start with the failing step in your Visualizer SDK integration: loading the SDK, matching a product or importing data. Keep the request context available without sharing credentials.

The storefront button does not appear#

1. Check the Network panel for https://sdk.ideal.house/sdk.js and inspect any load failure.
2. Confirm there is one loader with the correct Shop ID and Publishable Key.
3. Open Dashboard → Settings. Confirm Allowed Origins (CORS) includes the exact storefront origin you are testing, click Save after any changes, and reload the storefront. Also check the target's exact data-product-code. See origin configuration.
4. Verify the product is ready and the selected variant has a mapping.
5. For authored buttons, check that your styles allow the validated active state to become visible.

Do not force an unvalidated button visible to bypass eligibility. Follow the platform guide and mapping guide.

The wrong product opens#

Inspect the target after changing the variant, opening a quick view or navigating without a reload. Clear stale SDK attributes according to dynamic pages and confirm your platform callback actually runs.

An import was accepted but products are missing#

A 202 Accepted response starts asynchronous work. Read job status, inspect item failures and use errors and retries. The status endpoint returns the current or most recent shop job; it is not a history lookup by arbitrary job ID.

What to send to support#

Use the support channel supplied during onboarding or the contact option in your account. Include the affected storefront URL, Shop ID where relevant, product code or import job ID, approximate time, browser, expected result and sanitized error response. Remove Client Secret, API keys, tokens and private customer images before sharing logs or screenshots.