Events Tracked by the Web Pixel

the custom web pixel subscribes to shopify's customer events and delivers them to chord as tracking plan events this page lists what you get without writing any theme code these thirteen events are the complete set of standard customer events https //shopify dev/docs/api/web pixels api/standard events shopify exposes to web pixels — not a subset chord selected if an interaction you care about is not in this list, shopify does not publish an event for it, and it has to be instrumented in the theme see custom events on shopify https //shopify dev/docs/api/web pixels api/emitting data storefront events these fire on your theme's pages the pixel forwards them to @chordcommerce/analytics on the top window, which delivers them to chord and to any device mode destinations shopify event chord event notes page viewed page() call sends path, url, and title product viewed product viewed product detail pages collection viewed product list viewed includes the collection's product variants search submitted products searched sends the search query cart viewed cart viewed only on the /cart page — see mini cart drawers # product added to cart product added product removed from cart product removed checkout events these fire on shopify hosted checkout pages the pixel sends them directly to chord via cloud mode and forwards them by postmessage , so they are captured whether or not your storefront library is present on the page shopify event chord event notes checkout started checkout started includes line items, coupon, discount, tax, and shipping checkout contact info submitted checkout step completed (step 1) also sends an identify with the shopper's email and phone checkout address info submitted checkout step completed (step 2) checkout shipping info submitted checkout step completed (step 3) payment info submitted payment info entered (step 4) checkout completed order completed also sends an identify with the shopify customer id device mode destinations cannot run on shopify hosted pages, so checkout events reach those destinations through cloud mode only this is a shopify platform restriction, not a chord one customer identification the pixel sends an identify call in three situations on load , when shopify reports a logged in customer traits come from shopify's customer object email, first and last name, phone, and order count at checkout contact info submitted , with the email and phone entered in checkout no user id is set here — an email is not a stable identifier at checkout completed , with the shopify customer id as the user id shopify's event bus has no sign in event, so a shopper who logs in mid session is not identified until the next page load to identify them at the moment they sign in, add an identify() call to your storefront see identify users on sign in # what the pixel does not track three gaps come up on most themes sign in covered above — shopify publishes no login event instrument it in the storefront mini cart drawers shopify fires cart viewed only when a shopper navigates to /cart a theme that opens the cart in a slide out drawer never triggers it, so cart viewed will be missing call window\ chord trackcartviewed() when the drawer opens merchandising interactions no standard event covers clicks within a collection grid, quick add buttons, wishlist actions, or variant switching on a product page these are theme specific and must be tracked from theme code see custom events on shopify https //shopify dev/docs/api/web pixels api/emitting data related server event tracking docid\ q6xvtfkffipmhvvi2qcg0 — order and refund events delivered from shopify webhooks custom events on shopify https //shopify dev/docs/api/web pixels api/emitting data — adding events shopify does not publish sdk reference docid\ rr6ou mambvvhmdqlygh8 — the typed tracking methods available on window\ chord