dozenfold Docs Custom storefront integrations
Run a custom commerce frontend or buying flow? Contact us to work through the integration with your developer. This is a guided engagement, not a universal copy-and-paste installation.
Bring your setup
- Your storefront URL, frontend stack and deployment process.
- Where the cart, checkout and purchase confirmation run.
- Your consent platform and the permissions required for collection.
- Approximate session volume and the buying journey you want to investigate.
- The developer or agency responsible for implementation.
Agree the evidence and rollout
We scope browser errors, requests, performance and shopper actions around your frontend. Commerce events and purchase context need an agreed mapping; a browser script alone does not make checkout or revenue evidence available.
The integration plan covers collection permissions, session continuity, workspace access and source context. We agree what will be connected, how it will be verified and the commercial terms before rollout. Follow-up checks establish that the intended journey is being captured.
Give your team access
A custom storefront has its own workspace. The owner invites teammates as viewers from Team. New people get an email link to set their password. It works once and expires in 7 days. Only the owner can invite or remove people and create MCP keys.
Understand the documentation scope
Shopify theme embeds, the Shopify Pixel, Shopify analytics permission and in-app subscription approval are specific to the Shopify integration. They are not generic installation instructions for a custom storefront.
Feature guides describe the investigation workflow. The evidence available in a custom implementation depends on its agreed instrumentation; revenue estimates require suitable purchase and comparison data. We confirm that mapping with you instead of assuming every store exposes the same events.
Pricing and next step
Use the session pricing calculator as a starting point, then contact our team with your setup. All website plans lead to a conversation; an enquiry does not create a subscription.