# [Install page: credentials and snippets](https://rebilder.com/help/console/console-install-page)

> Where your store ID and API key prefix live, and what each install section is for.

## Your store credentials

The card at the top of Console → Install shows the two identifiers an install needs:

- Store ID: the value your developer sets as `storeId` in the gateway configuration. It identifies your store on every recorded event.
- Active API key: shown as `sha256:` plus the first 8 characters of the key’s fingerprint, with an “active” badge. This is NOT the key itself: only the hash of your key is stored, and the raw key was shown once at creation. If it reads “none”, no key is active yet; generate one in Settings.

## The install sections

- Next.js: the 2-line integration. Install the package, wire the gateway to your product/policy data, and drop the proxy in front of your routes.
- Shopify app proxy: the Shopify Partners settings plus the handler snippet. Requests are HMAC-signed and never served unverified.
- Events sink (POST /v1/events): how the gateway reports visits to Rebilder, authenticated with your API key (Bearer). Your store ID is always resolved from the key, so a key can never write another store’s events.

With multiple stores, the switcher at the top selects which store’s credentials fill the snippets. A “Rotate it in Settings” link sits under the key display.