Commerce integrations

Connect commerce providers to Hoko link attribution through the shared engine.

What this guide covers

Commerce adapters connect a provider product or order to Hoko attribution. The adapter validates provider signatures and tenant ownership, then calls the shared commerce engine. It never writes directly to Hoko analytics tables.

Supported planning families are Shopify, Salla, Zid, WooCommerce, BigCommerce, Adobe Commerce, and Stripe. A catalog entry or local adapter does not mean a provider account, app listing, or hosted connection is available.

Required inputs

  • provider store or account identifier;
  • provider OAuth or API credential stored in the provider connection;
  • product, checkout, order, payment, and refund identifiers as applicable;
  • webhook signing secret and delivery identifier for event adapters;
  • Hoko workspace and scoped API access for customer-owned recipes.

Safe implementation path

  1. Choose the provider-specific contract and confirm its account requirements. 2. Install the provider adapter in a disposable account and disposable Hoko database. 3. Create one product link with an external identity. 4. Rehearse one paid event, one duplicate, one refund, and one rejected tenant. 5. Record provider receipts before enabling hosted or public distribution.

See the provider package READMEs in integrations/, the Apps catalog, and the automation guide.