Storefront Integrations and Tracking
Official guide · English · Version 9c253d0cf11816df
Open Storefront > Integrations to configure analytics, advertising pixels, site verification, chat tools and messaging buttons on the generated storefront.
Before you start
Have access to the corresponding provider property and the correct public installation identifier. A measurement ID is not an API secret. Review consent requirements and avoid duplicate trackers if a tag manager already installs the same tool. Private preview and a published custom domain can behave differently.
Configure an integration
- Find the relevant category and integration card.
- Enable the integration and enter the requested ID, not an entire script unless the field specifically asks for code.
- Complete required fields; optional labels are not interchangeable with IDs.
- Save the integrations form.
- Reload the form to confirm persistence, then verify a page on the intended domain using the provider's own test/debug view.
Fields by category
| Category | Typical requested values |
|---|---|
| Analytics & Tracking | GA measurement ID or Yandex counter ID |
| Tag Management | Google Tag Manager container ID |
| Advertising Pixels | Pixel/tag/partner ID; Google Ads also has conversion ID and optional label |
| Heatmaps & Session Recording | Clarity project ID or Hotjar site ID |
| Live Chat | Crisp website ID, Tawk property/widget IDs or Chatwoot public key |
| Search Engine Verification | Provider verification code for Google, Bing, Yandex or Pinterest |
| Messaging Buttons | WhatsApp phone/default message or Telegram username |
| AI Chat Widget | The storefront's own supported chat-widget setting |
The cards provide provider-specific setup hints. Use an identifier from the property for this website, not one copied from an unrelated account. A messaging button merely opens a conversation; it is not the same as connecting that messaging channel to DirectSale's AI.
Privacy and custom HTML
Review the privacy/consent controls shown on the page before enabling advertising pixels or session recording. Only add custom HTML you understand and are authorized to use. Sanitization or platform restrictions may remove unsupported markup. Do not add passwords, private API keys or customer information to site-wide code.
Search Console is a separate connection
A verification tag proves site control to the search provider. To retrieve query/performance data in DirectSale, also use Storefront > Search Console and connect the appropriate property. See Search Console.
Verification and troubleshooting
No data: confirm the integration is saved/enabled, ID belongs to the right property, and your browser's consent/ad-blocking state. Duplicate events: check whether the same tool is installed both directly and through a tag manager. A saved integration does not publish a private storefront or guarantee indexing. For private preview restrictions, see Domain and Publication.