# noisy-kiwi Data Schema

Source: Loomi MCP discovery on 2026-05-31.

## Customer Properties

Available customer properties:

| Property | Type | Source | Used |
| --- | --- | --- | --- |
| `city` | string | data | yes |
| `country` | string | data | yes |
| `email` | string | data | yes |
| `external_score` | string | data | yes |
| `first_name` | string | data | yes |
| `gender` | string | data | yes |
| `language` | string | data | yes |
| `last_name` | string | data | yes |
| `phone` | string | data | yes |
| `is_internal_traffic` | string | data | yes |

## Key Events

### `purchase`

Order-level purchase event.

Properties:

- `currency`
- `payment_method`
- `product_ids`
- `product_list`
- `purchase_id`
- `purchase_source_type`
- `purchase_status`
- `total_price`

Use for revenue, order completion, purchase conversion, first purchase, repeat purchase, and post-purchase entry logic. Confirm `purchase_status` filtering and returns treatment before publishing financial metrics.

### `purchase_item`

Item-level purchase event.

Properties:

- `brand`
- `category_level_1`
- `category_level_2`
- `category_level_3`
- `is_new`
- `price`
- `product_id`
- `purchase_id`
- `purchase_source_type`
- `purchase_status`
- `quantity`
- `size`
- `title`

Use for product, category, basket, cross-sell, and item-level reporting.

### `cart_update`

Cart change event.

Properties:

- `action`
- `brand`
- `product_id`
- `product_ids`
- `product_list`
- `size`
- `title`
- `total_price`
- `total_quantity`

Use for cart abandonment, cart value, product intent, and pre-checkout recovery.

### `checkout`

Checkout event.

Properties:

- `product_ids`
- `product_list`
- `total_price`

Use for checkout abandonment and high-intent conversion recovery.

### `view_item`

Product detail view event.

Properties:

- `brand`
- `category_level_1`
- `category_level_2`
- `category_level_3`
- `price`
- `product_id`
- `stock_level`
- `title`
- `browser`
- `categories`
- `color`
- `device`
- `location`
- `os`
- `style`

Use for browse abandonment, category/product affinity, recommendation fallbacks, and merchandising analysis.

### `view_category`

Category browsing event.

Properties:

- `category_level_1`
- `category_level_2`
- `category_level_3`
- `category_name`
- `browser`
- `category_id`
- `device`
- `location`
- `os`
- `title`

Use for category affinity, browse behavior, and top-of-funnel merchandising analysis.

### `page_visit`

Page-level visit event.

Properties:

- `browser`
- `device`
- `os`
- `referrer`
- `url`
- `location`
- `path`

Use for web behavior, landing page, URL/path targeting, and traffic source context.

### `campaign`

Campaign interaction/event tracking.

Properties:

- `action_name`
- `action_type`
- `browser`
- `campaign_id`
- `campaign_name`
- `platform`
- `sent_timestamp`
- `status`
- `url`

Use for campaign engagement, attribution, and suppression logic.

### `banner`

On-site banner or web layer interaction.

Properties:

- `action`
- `banner_name`
- `type`
- `variant_name`

Use for web layer measurement and on-site interaction analysis.

### `consent`

Consent event.

Properties:

- `action`
- `category`
- `source`
- `valid_until`
- `identification_type`
- `identification`
- `imported_timestamp`

Use for consent-state auditing and channel eligibility checks. Confirm exact consent rules before activation.

## Other Available Events

- `installation`
- `session_start`
- `first_session`
- `session_end`
- `store_visit`
- `loyalty_update`
- `return`
- `experiment`
- `paper_catalogue`
- `support_ticket`
- `registration`
- `merge`
- `survey`
- `inbound_call`
- `outbound_call`
- `retargeting`
- `user_active`
- `menu`

## Mapping Status

Bloomreach standard mapping is currently empty:

- Standard ecommerce events are not mapped.
- Standard customer attributes are not mapped.
- Catalogs are not mapped.
- Consent categories are not mapped.

Agents should use raw event and customer property names unless mapping is configured later.