> 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/identify.md).
# Identify
### Description
This client-side event fires whenever a customer is identified on the Shopify storefront. This primarily happens at checkout, or when a use logs in, creates an account on the Shopify store, or self-identifies with an event like the newsletter sign-up.
### Instrumentation
This event is implemented with our javascript analytics library. The tracking code is managed in the storefront theme.
The tracking code is managed in two places:
* An Identify event fires during checkout, leveraging attribution code managed in storefront checkout settings.
* The Identify events that fire when a customer logs in or creates an account are managed in attribution code that’s included in the storefront theme.
**Event Properties**
| Property | Type | Description |
| ------------------ | --------------- | -------------------------------------------- |
| email | String | The customer’s email address |
| name | String | The customer’s name |
| address | Array\ | The customer’s address |
| address.street | String | The customer’s street |
| address.city | String | The customer’s city |
| address.state | String | The customer’s state |
| address.postalCode | String | The customer’s postal code |
| address.country | String | The customer’s country |
| allOrderIds | String | Comma-separated list of customer’s order IDs |
### Example:
```javascript
analytics.identify({
userId: 'peter@example.com',
traits {
addresses {
address: {
firstName: 'Peter',
lastName: 'Parker',
street: '7th St',
city: 'Queens',
state: 'NY',
postalCode: '12345',
country: 'USA'
},
}
createdAt: new Date('2021-01-1T18:11:37.000Z'),
email: 'peter@example.com',
externalCustomerId: '48908733345342',
firstName: 'Peter',
lastName: 'Parker',
phone: '+15555555555',
}
});
```
---
# 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/identify.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.