# Kibble installation contract: section 8 of 29 (guide version 3)

> This is **one section only**, not the whole contract. Complete document: https://www.usekibble.dev/AI/guide.md

## 8. Inputs you need from a person {#inputs}

1. The **public property key** (starts with `pk_`) and the **collector origin** (the Kibble API URL). Both are shown on the Setup page right after a property is created, and later on the property's Data tracking → Setup page (`/manage/data-tracking/setup`).
2. The **website hosts** of the property (the primary host and any other host the client controls) and every **external connection** (a booking engine or checkout run by a provider: provider, host, tenant, routes) registered under Manage → Settings (`/manage/property`). Each connection has its own recipe on Data tracking → Setup. Events from unregistered hosts, or from a connection outside its tenant and routes, are rejected.
3. The site's **consent mechanism**: a custom banner, a consent management platform, or Google Consent Mode.
4. The **platform**: Next.js, WordPress, a tag manager, a booking engine, Shopify or BigCommerce.

### Integration status

| Integration | Status |
| --- | --- |
| Plain HTML, Next.js App Router, booking-engine dataLayer hooks | **direct integration** |
| First-party gateway (reference implementation, run by the hotel demo) | **direct integration** |
| Google Tag Manager (template and Custom HTML tag) | **importable template** |
| WordPress plugin (Contact Form 7 events fixture-tested) | **importable template** |
| Shopify custom pixel (self-contained, checkout and order status pages) | **fixture-tested adapter** |
| rezStream booking-engine tag (recipe, never run on a live booking) | **importable template** |
| BigCommerce Script Manager (BODL) | **fixture-tested adapter** |

The fourth label, "live-verified installation", belongs to a specific site after its checklist ([Verify the installation](https://www.usekibble.dev/AI#verify)) was completed. None is claimed here.

END OF SECTION inputs