Verify and Troubleshoot
Prove the install on the storefront, run the integration check, and work through the five things that usually go wrong
Copy this guide and your current settings as a prompt for your AI agent.
Preview agent promptSee the guide, code and settings included when you copy.
On this page
01Three quick checks
- The app Overview shows Live on storefront.
- Connection health reads Configured / Active / Installed / Installed across all four integrations.
- Typing
Coframein the storefront’s browser console returns an object withstatus.initialized: true.
02Verify on the storefront
Open the storefront, launch the browser developer console, and type
Coframe:
> Coframe
{ status: { initialized: true }, projectId: '…', sessionId: '…', userToken: '…', … }The object exists with status.initialized: true, alongside the store’s
projectId, a sessionId and a userToken. That is the SDK being served and
running for a real visitor.
03The integration check
The app’s integration check looks for events from the storefront in the last five minutes. It reads No events detected in exactly two situations: the Coframe app is not installed on that store, or nobody has visited the storefront since the scripts went live. With the app installed, one storefront visit sends events and the check verifies. The video walks the flow end to end on Coframe’s test store.
04If a check does not pass
Most failed installs come down to one of these. Work through them in order.
| What you see | What to check |
|---|---|
| Coframe scripts read Not installed | The theme editor tab was not saved after Install Coframe Scripts; the embed is inactive until then. Save, then click Recheck. The status is verified from the public script URL, so it only turns green once the storefront serves the script |
| The connect step rejects the credentials | The project ID is 24 or 32 hexadecimal characters with no dashes, and the key begins with cfpv1_. Paste both exactly as provided, with no surrounding spaces |
Coframe is undefined in the console |
Confirm the Overview reads Live on storefront, then hard-refresh. If it stays undefined, note which page was tested |
| Events appear twice | The manual script tag or the manual custom pixel is still in place somewhere, on the live theme or on a theme planned for publishing. See Migrating from the manual install |
| The storefront stays blank for a moment on load | That is anti-flicker holding the page. Lower the duration on the Configuration tab or switch it off. ?cf_disable=true on a URL loads the page with Coframe and the protection off |
For a purchase that does not show up as a conversion, see Tracking and consent.
# Verify and Troubleshoot
Prove the install on the storefront, run the integration check, and work through the five things that usually go wrong
[Video: Video: the storefront console check, and what to do when a check does not pass (63s, narrated)](assets/videos/shopify-app-verify.mp4)
Watch: 63s — the storefront console check, and what to do when a check does not pass
## Three quick checks
- The app Overview shows Live on storefront.
- Connection health reads Configured / Active / Installed / Installed
across all four integrations.
- Typing `Coframe` in the storefront’s browser console returns an object
with `status.initialized: true`.
## Verify on the storefront
Open the storefront, launch the browser developer console, and type
`Coframe`:
JS
```
> Coframe
{ status: { initialized: true }, projectId: '…', sessionId: '…', userToken: '…', … }
```
The object exists with `status.initialized: true`, alongside the store’s
`projectId`, a `sessionId` and a `userToken`. That is the SDK being served and
running for a real visitor.
## The integration check
[Video: Video: why the check reads 'No events detected' until the app is installed and the storefront visited, then the full verification on a test store (90s, narrated)](assets/videos/shopify-app-integration-check.mp4)
Watch: 90s — why the check reads 'No events detected' until the app is installed and the storefront visited, then the full verification on a test store
The app’s integration check looks for events from the storefront in the
last five minutes. It reads No events detected in exactly two
situations: the Coframe app is not installed on that store, or nobody has
visited the storefront since the scripts went live. With the app installed,
one storefront visit sends events and the check verifies. The video walks the
flow end to end on Coframe’s test store.
## If a check does not pass
Most failed installs come down to one of these. Work through them in order.
What you see |
What to check |
Coframe scripts read Not installed |
The theme editor tab was not saved after Install Coframe Scripts; the embed is inactive until then. Save, then click Recheck. The status is verified from the public script URL, so it only turns green once the storefront serves the script |
The connect step rejects the credentials |
The project ID is 24 or 32 hexadecimal characters with no dashes, and the key begins with `cfpv1_`. Paste both exactly as provided, with no surrounding spaces |
`Coframe` is undefined in the console |
Confirm the Overview reads Live on storefront, then hard-refresh. If it stays undefined, note which page was tested |
Events appear twice |
The manual script tag or the manual custom pixel is still in place somewhere, on the live theme or on a theme planned for publishing. See [Migrating from the manual install](../docs/setup.html#migrating-from-the-manual-install) |
The storefront stays blank for a moment on load |
That is anti-flicker holding the page. Lower the duration on the Configuration tab or switch it off. `?cf_disable=true` on a URL loads the page with Coframe and the protection off |
For a purchase that does not show up as a conversion, see
[Tracking and consent](../docs/tracking-and-consent.html).BACK TOShopify App