# Events & data model

This page documents what The Wallet Crew synchronizes into Klaviyo.

Two categories exist.

* **Events (metrics)** used for triggers and reporting.
* **Profile properties** used for segmentation and personalization.

<details>

<summary><strong>Real-world examples</strong></summary>

* A flow triggers when a pass is installed.
* A campaign targets profiles with no active installation.
* A template link uses `neostore.authenticationToken` to open a wallet page.

</details>

### Events sent from The Wallet Crew to Klaviyo

The current connector sends at least:

* a registration event when a customer registers through The Wallet Crew
* install and uninstall events when a pass is installed or removed

Install/uninstall events can also be backfilled for existing customers with existing installed passes.

{% hint style="info" %}
Metric names and payload fields are visible in Klaviyo once the first events are ingested.

For validation, open one event in Klaviyo and inspect its properties.
{% endhint %}

### Profile properties managed by The Wallet Crew

#### `neostore.authenticationToken`

This property is synced to new and existing profiles.

It enables authenticated links in Klaviyo templates.

#### Wallet installation status

The user guide relies on wallet status properties similar to:

* `neostore.wallet.loyaltyCard.Apple`
* `neostore.wallet.loyaltyCard.Google`

Typical values include `Installed`.

{% hint style="info" %}
Property naming can differ across pass types and tenant configuration.

For validation, inspect one synced profile in Klaviyo and copy the exact property path.
{% endhint %}

### Debugging data

Debugging usually starts with one question: “is this an ingestion issue or a mapping issue?”.

* If events are missing, validate The Wallet Crew flow includes the `klaviyo` step.
* If profile properties are missing, validate the Klaviyo sync flow webhook is enabled and back-populated.
* If a template cannot personalize, validate `neostore.authenticationToken` exists on the profile.

### FAQ

<details>

<summary><strong>Can install events fire multiple times?</strong></summary>

Yes. A pass can be installed multiple times (multiple devices or re-install).

Metrics and segmentation should be designed with this in mind.

</details>