NIXP Marketing
Performance dashboard
Connected
Loading website events, commerce records, and contacts.
01 / Overview
What is moving
Paid orders come from the commerce ledger. Audience figures will come from consented site events.
Sales / traffic
Daily trend
Each series uses its own scale.HighMid0
Signal
Attention points
Merchandise
Top products
| Product | Artist | Views | Added | Paid orders | Net sales |
|---|
02 / Audience
Who is visiting
Geography is approximate. No raw IP address or personal identity is stored in analytics events.
Geography
Visitor location
Device
Session mix
Acquisition
Where visits came from
| Source | Sessions | Product views | Paid orders | Conversion |
|---|
03 / Funnel
From visit to order
Each stage is counted independently and deduplicated by event ID.
Paid conversion0%
Checkout health
Order outcomes
0Paid
0Expired
0Cancelled
0Refunded
Revenue quality
Net sales basis
Net sales are based on provider-verified payments and exclude refunded merchandise. Shipping is kept separate from product revenue.
04 / Campaigns
What brings people in
Campaign attribution is read from referrer and UTM parameters, never guessed from customer identity.
| Source / campaign | Sessions | Product views | Add to cart | Paid orders | Sales |
|---|
Measurement rules
Reliable attribution
01
One event ID per action prevents refreshes from inflating counts.
02Admin and Finance traffic is excluded from audience metrics.
03Revenue is reconciled against paid orders, not browser events.
05 / Consent
Permission, clearly separated
Essential checkout functions are never blocked. Optional measurement starts only after consent.
Stored record
Consent audit trail
06 / Contacts
Customer audience
Contacts are created from orders or an explicit newsletter opt-in. Campaign eligibility always follows recorded consent.
| Customer | Source | Last order | Orders | Consent | Lifetime sales |
|---|
Customer data rules
Separate from behavioural analytics
01
Browser events use anonymous session identifiers, never raw email addresses.
02Contact data is access-controlled and never exposed on the public storefront.
03Withdrawing email consent immediately removes the contact from campaign audiences.
07 / Data
Marketing data pipeline
Read-only reporting sources support this dashboard. None can write stock, orders, reservations, or Finance.
marketing_events
Event stream
Consent-gated, append-only records for page views, product views, add-to-cart, and checkout starts.
- Rows in range
- 0
- Status
- Loading
daily metrics
Daily metrics
On-request rollups for visitors, sessions, funnel stages, paid orders, sales, and refunds.
- Latest date
- -
- Refresh
- On request
campaign attribution
Campaign sources
Referrer and UTM attribution records, normalized before reports calculate campaign performance.
- Tracked sources
- 0
- UTM fields
- 5
order_records
Customer contacts
Protected contact summaries derived from customer order records. Marketing consent remains separate.
- Known contacts
- 0
- Opted in
- 0
Event stream
Latest consented events
| Time | Event | Path | Source | Session |
|---|
Data health
Pipeline checks
Event deduplicationEvent ID enforced
Metrics freshnessSample: 4 min ago
Sales reconciliationAwaiting live connection
Consent enforcementRequired before ingest
Daily metrics
Recent rollups
| Date | Visitors | Product views | Add to cart | Paid orders | Net sales |
|---|