Skip to content

Commerce attribution

  • Shopify customer events describe the storefront journey.
  • Aabhas widget events describe VTO interaction and results.
  • Shopify Admin orders and verified commerce facts describe purchases, payment state, refunds, cancellations, fulfillment, and RTO.

checkout_completed is useful session evidence but is not the sole canonical purchase source.

After successful VTO, Aabhas issues an opaque attribution marker scoped to the shop, product, and variant. The Liquid extension or Hydrogen integration attaches it to the cart line. If it is present on the authoritative purchased line, Aabhas can report exact attributed units and product revenue.

With-VTO and without-VTO session cohorts compare journeys even when exact line attribution is unavailable. Their denominator is a qualifying session cohort, not raw event count.

External checkout works without a custom connector when it preserves Shopify line properties and writes lifecycle state back to Shopify. If it removes relevant evidence, affected metrics become unavailable. Aabhas does not require or expect merchants to share payment-provider secrets merely for browser event collection.

Provider-specific mappings can be added when a real, documented capability gap exists. Event names are normalized into canonical meanings rather than assuming the same custom event means the same thing for every provider.