Shopify server event tracking

overview when installed on your shopify store, chord sends tracking events from two sources your storefront , using either the chord shopify web pixel or @chordcommerce/analytics (see docid 7ggdgpvq4j3qwbprhy1fr ) chord's server events service , which sends tracking events from a shopify webhook source in your chord workspace in response to webhook triggers from shopify when chord provisions your workspace, it includes a shopify webhook source this source listens for webhook events from shopify and transforms them into chord events requirements locate the webhook source in your chord workspace, named "shopify webhooks " chord typically creates this source as part of your workspace provisioning you will need the settings page of this source during the "create an admin api key" step the webhook url of this source during the "create webhook subscriptions" step if you cannot find the source or are unsure which one it is, contact mailto\ help\@chord co step 1 create an admin api key chord's webhook source requires an admin api key with the read orders scope to retrieve order details from shopify we recommend creating a dedicated custom app in your shopify account for chord, which makes it easy to manage access create the api key in shopify in your shopify admin, go to settings > apps and sales channels > develop apps > create an app name the app (e g , "chord webhooks") click configure admin api scopes select read orders only and click save on the overview tab, click install app copy the admin api access token add the token to your chord workspace in your chord workspace, navigate to your shopify webhook source open settings > connection enter the admin api access token in the access token field click save changes step 2 create webhook subscriptions in your chord workspace, navigate to your shopify webhook source find the webhook url under the configure your webhook heading copy this url in your shopify admin, go to settings > notifications > webhooks (or use the shopify admin api to create subscriptions programmatically — you can use the same admin api access token you created in step 1) create a webhook subscription for each of the supported topics listed below each subscription should use the same webhook url you copied from your chord workspace supported webhook topics true 244,244 left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type left 1 1 unhandled content type verifying the installation shopify's built in webhook testing does not send payloads that match real webhook payloads to verify that server events are flowing correctly complete a test transaction in your shopify store in your chord workspace, navigate to the shopify webhook source and open the debugger tab confirm that the expected events (checkout created, order completed, etc ) appear subscription events if your store sells subscriptions, chord can also track subscription lifecycle events (creation, cancellation, payment failures, etc ) due to shopify platform restrictions, subscription events require a different setup using shopify flow see docid 3irbd314fqajoowdjv6ax for details associating server events with storefront sessions to link server events with front end storefront events from the same customer session, the storefront must save certain browser identifiers as attributes on the cart or order these identifiers are then retrieved by the webhook source and included in chord events for details, see