> For the complete documentation index, see [llms.txt](https://learn.fueled.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.fueled.io/integrations/destinations/segment.com/segment-event-specifications/checkout-started.md).
# Checkout Started
### Description
This client-side event fires when a customer starts the checkout process (ie, when they land on the /checkout page — not when they click the “checkout” link on the cart page).
### Instrumentation
This event is implemented with our javascript analytics library. The tracking code is managed in the storefront theme.
💡
Note: Standard Shopify stores do not allow us to inject javascript on the checkout page. However, for Shopify stores built on Shopify Plus, we have access to the checkout page’s theme and can quickly implement this event there. Otherwise, we have to implement this event whenever someone clicks “Check out” on Shopify’s cart page.
**Event Properties**
| Property | Type | Description |
| ---------------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| checkout\_id | String | Checkout ID |
| affiliation | String | Store or affiliation from which this transaction occurred (e.g. Google Store) |
| value | Number | Revenue ($) with discounts and coupons added in. For better flexibility and total control over tracking, we let you decide how to calculate how coupons and discounts are applied |
| revenue | Number | Revenue ($) associated with the transaction (excluding shipping and tax) |
| currency | String | [Currency code](https://support.google.com/analytics/answer/6205902#supported-currencies) associated with the transaction |
| products | Array | Products in the order |
| products.$.product\_id | String | Database id of the product being viewed |
| products.$.sku | String | Sku of the product being viewed |
| products.$.name | String | Name of the product being viewed |
| products.$.brand | String | Brand associated with the product |
| products.$.variant | String | Variant of the product (e.g. Black) |
| products.$.price | Number | Price ($) of the product being viewed |
| products.$.quantity | Number | Quantity of a product |
| products.$.coupon | String | Coupon code associated with a product (e.g MAY\_DEALS\_3) |
| products.$.position | Number | Position in the product list (ex. 3) |
| products.$.url | String | URL of the product page |
| products.$.image\_url | String | Image url of the product |
### Example:
```javascript
analytics.track('Checkout Started', {
order_id: '20614a8e9bff000150000000',
affiliation: 'Google Store',
value: 30,
revenue: 25.00,
shipping: 3,
tax: 2,
discount: 2.5
currency: 'USD',
products: [
{
product_id: '503f1f77bcf86cd799439022',
sku: '42740-32',
name: 'Monopoly: 3rd Edition',
price: 19,
quantity: 1,
url: 'https://www.example.com/product/path',
image_url: 'https://www.example.com/product/path.jpg'
},
{
product_id: '505bd76783ebk509cf183783',
sku: '46443-35',
name: 'Uno Card Game',
price: 3,
quantity: 2
}
]
});
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://learn.fueled.io/integrations/destinations/segment.com/segment-event-specifications/checkout-started.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.