> For the complete documentation index, see [llms.txt](https://headless.intelligems.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://headless.intelligems.io/latest-1.2.19/usage/update-prices-on-page.md).

# Update Prices on Page

## The `<IgPrice/>` Component

The [`<IgPrice/>`](/latest-1.2.19/reference/components/price-components.md#less-than-igprice-greater-than) component is recommended as it automatically applies assigned test prices and uses Integration Mode styling.

## The `useIgPrices()` Hook

The [`useIgPrices()`](/latest-1.2.19/reference/hooks/price-hooks.md#useigprices) hook may be used to pull updated prices based on the user's test group and then render the result however your storefront needs.

## Internationalization

1. Set a default `activeCurrencyCode` prop for the provider. `USD` will be used by default if not set.
2. If necessary, update `activeCurrencyCode` through context:

```typescript
const { dispatchData } = useContext(IntelligemsContext);

dispatchData({
  type: "SET_ACTIVE_CURRENCY_CODE",
  payload: "EUR",
});
```

3. Experiment currency is set through the Intelligems app. Prices for experiments with a currency that does not match `activeCurrencyCode` will return the original price.


---

# 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://headless.intelligems.io/latest-1.2.19/usage/update-prices-on-page.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.