Signal
A wishlist from a guest session
Someone wishlists the Linen Overshirt without logging in. The signal carries a device and the email entered for a restock alert.
The engine Step 03 of the loop
Customer 360
Ayra Customer 360 is the single customer profile at the centre of the Shopify retention engine. It holds wallet balance, tier, lifetime value, lifecycle stage, intent score, subscription state, review history, open support issues and a full timeline, written by every Ayra module and by Shopify, and read by every decision the engine makes.
One profile per customer, written by every module and by Shopify.
Customer 360
Hira VIP · 9 orders · since 2024
- Wallet
- $42.50
- Tier
- Gold
- LTV
- $1,284
- Lifecycle
- Loyal
- Intent
- High
- Subscription
- Active
- Reviews
- 3 · 4.7★
- Support
- None open
- Tue 09:12 Restock alert sent +200 pts · WhatsApp
- Mon 18:40 Wishlisted Linen Overshirt Intent ↑
- Sep 28 Order #4791 delivered Review published
01 The merchant problem
Six apps, six partial customers.
The loyalty app knows the balance, the review app knows the rating, the subscription app knows the skip, and Shopify knows the orders. Nobody knows the customer.
-
Identity is split
A guest wishlist, an email subscriber and a logged-in buyer are three records until someone merges them, and usually nobody does.
-
Every app keeps its own facts
Lifetime value in one tool, tier in another, intent nowhere. The same customer is 'VIP' in one app and 'inactive' in the next.
-
Support is invisible to marketing
An open delivery complaint does not stop the review request, because the help desk is not on the customer record.
-
There is no timeline
When a customer asks why they got a message, nobody can show the sequence of events and decisions that led to it.
02 How Ayra solves it
What Customer 360 does
- 01Explore Signals
Identity resolution
Email, phone, customer ID and device resolve to one person. A guest wishlist merges into the account on login, so nothing is counted twice.
- 02Explore Loyalty
Every module writes to it
Loyalty writes balance and tier, Wishlist writes intent, Subscriptions writes state, Reviews writes ratings, and Shopify writes orders and deliveries.
- 03
A timeline with reasons
Every signal, opportunity, action, hold and skip is an entry with the rule behind it, in order.
- 04Explore Segments
Readable from Shopify
Profile fields are mirrored to customer metafields in the ayra namespace, so themes, Shopify Flow, Shopify Segments and other apps can read them.
- 05Explore Opportunities
Read by every decision
Eligibility, scoring and Journey Guard all read the same profile, so a decision never relies on stale data copied from another app.
03 Inside
What is on the profile
The fields every module and the engine read. Each is written by a named source and mirrored to a customer metafield.
| Field | Written by | Example |
|---|---|---|
| Wallet balance | Loyalty (Smart Wallet) | $42.50 credit · 1,100 points |
| Tier | Loyalty | Gold |
| Lifetime value | Shopify orders | $1,284 |
| Lifecycle stage | The engine | Loyal · lapsed · at risk |
| Intent score | Wishlist, Back in Stock (Intent Engine) | High |
| Subscription state | Subscriptions | Active · skipped ×2 · paused |
| Review history | Reviews | 3 reviews · 4.7★ average |
| Open support issues | Support signals | 0 open |
| Channel preference | Customer Account Hub | |
| Timeline | Every module | Restock alert sent · +200 pts · Tue 09:12 |
In the loop One profile: wallet balance, tier, LTV, lifecycle stage, intent score, subscription state, review history, open support issues, timeline. How it works
04 The workflow
Customer 360, one customer at a time.
Hira, VIP · 9 orders. Five stages, one decision, every reason recorded.
Hira
VIP · 9 orders
5 stages
Customer
Resolved to Hira
The email matches Hira's account. The guest wishlist merges into her profile: Gold tier, 9 orders, $1,284 lifetime value, intent now high.
Opportunity
A profile change opens an opportunity
When the item restocks the next day, VIP_RESTOCK opens with the profile fields as its evidence.
Action
Decided from one record
Eligibility reads tier and open tickets, scoring reads intent and lifetime value, Journey Guard reads the send history. All from the same profile.
Outcome
Timeline entries with reasons
The send, the points, the suppressed duplicate email and the order are entries on her timeline, each with the rule that produced it.
05 Use cases
Where it shows up.
Support 01
A customer emails about a late delivery.
Ayra decides
Marketing sees the open issue on the same profile and holds. When it is resolved, the timeline shows both the hold and the release.
Theme 02
You want to show a VIP badge on the account page.
Ayra decides
Read the tier from the customer metafield in your theme. No extra app block, no script.
Segments 03
You want a Shopify Segment of high-intent Gold customers.
Ayra decides
Tier and intent are synced as tags and metafields, so Shopify Segments and Shopify Flow can use them directly.
Fed by these modules
Loyalty
Writes wallet balance, tier and points expiry. Reads tier for perks and Reward Shield checks.
Wishlist
Writes saved items and the intent score. Reads channel preference for alerts.
Subscriptions
Writes subscription state and skips. Reads lifecycle stage for Save Engine.
Reviews
Writes ratings and review history. Reads open support issues before any request goes out.
For developers
Profile fields in the ayra namespace
Every profile field is mirrored to customer metafields under the ayra namespace, and profile changes are typed events on the webhooks API, so your theme, Shopify Flow and your own services read what the engine reads.
Solutions built on Customer 360
- See the workflow
Retention automation
One loop that decides per customer instead of a stack of triggers.
- See the workflow
Increase repeat purchases
Turn deliveries, wishlists and balances into second and tenth orders.
- See the workflow
Customer winback
Detect lapsed customers from their own rhythm and bring them back once.
06 FAQ
Customer 360 questions
Is Customer 360 a CDP?
It is the customer profile inside Ayra, built for decisions rather than for export. It is mirrored to Shopify metafields and exposed over the API, so it can feed other tools, but it is not a general data platform.
Where does the data live?
On the customer record in Ayra, mirrored to Shopify customer metafields in the ayra namespace. Nothing is injected into your theme.
Does it merge guest and account activity?
Yes. Email, phone, customer ID and device are resolved to one person, and guest activity merges on login.
Can I see why a field changed?
Yes. The timeline records the signal or action that changed it, with the module and the rule.
Can other apps read it?
Yes, through the ayra metafields, Shopify Flow triggers and the REST API.
07 The rest of the engine
The other two parts of the loop.
- EngineExplore Signals
Customer Signals
Every event from Shopify and every module, typed, on one profile.
- EngineExplore Opportunities
Opportunities
Every retention chance, typed and prioritised, with evidence and an expiry.
- Private betaExplore Loyalty
Loyalty & Rewards
Points, store credit and VIP tiers that know who the customer is.
Private beta
See your customers as one record each.
Private beta merchants get Customer 360 populated from their Shopify order history and from every module they turn on.