> 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/product-viewed.md).

# Product Viewed

### Description <a href="#id-02ef3240-4408-41f3-bec9-eede48353245" id="id-02ef3240-4408-41f3-bec9-eede48353245"></a>

This client-side event fires on the storefront product pages (PDPs).

### Instrumentation <a href="#f566db7b-d919-4e8a-b782-f224176402d1" id="f566db7b-d919-4e8a-b782-f224176402d1"></a>

This event is implemented with our javascript analytics library. The tracking code is managed in the storefront theme.

💡

Note: We do not fire a Page event on product pages, as this would cause duplicate event data that makes journey analytics more difficult in tools like MixPanel or Amplitude. Some CDPs do recommend that both a page event and a Product Viewed event fire on product pages. That can be accomplished, if a merchant requests it.

**Event Properties**

| Property    | Type   | Description                               |
| ----------- | ------ | ----------------------------------------- |
| product\_id | String | Database id of the product being viewed   |
| sku         | String | Sku of the product being viewed           |
| category    | String | Product category being viewed             |
| name        | String | Name of the product being viewed          |
| brand       | String | Brand associated with the product         |
| variant     | String | Variant of the product (e.g. Black)       |
| price       | Number | Price ($) of the product being viewed     |
| currency    | String | Currency of the transaction               |
| value       | Number | Total value of the product after quantity |
| url         | String | URL of the product page                   |
| image\_url  | String | Image url of the product                  |

### Example: <a href="#df4dd446-be63-48d9-808b-dbc474171e7e" id="df4dd446-be63-48d9-808b-dbc474171e7e"></a>

```javascript
analytics.track('Product Viewed', {
  product_id: '507f1f77bcf86cd799439022',
  sku: 'G-35',
  category: 'Games',
  name: 'Monopoly: 3rd Edition',
  brand: 'Hasbro',
  variant: '200 pieces',
  price: 15.99,
  quantity: 1,
  currency: 'usd',
  position: 3,
  value: 15.99,
  url: 'https://www.example.com/product/path',
  image_url: 'https://www.example.com/product/path.jpg'
});
```


---

# 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/product-viewed.md?ask=<question>&goal=<user_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.