Map what you have
Review one client’s available loyalty, POS and email exports. Check the identifiers, coverage and gaps before promising a result.
THE 3-DAY ASSESSMENT
One client.
Three days. A clear direction.
Bring a client name, the systems they use, and the retention question you want to answer. We agree on scope, access and timing before the clock starts.
No price on this page, no automatic booking, and no promised lift. Client work starts from the exports they already have — not an installed POS feed, and not a platform replacement.
A CTA click opens the LucidDataMind contact form. It is not a confirmed booking.
WHAT TO BRINGExports, not a live feed
Files you already have.
The merchant or agency holds the files. There is no public upload on this site.
- REQUIRED
- A purchases / POS CSV and a written column map
- USUALLY USEFUL
- Email events; loyalty members if a program already exists
- OUT OF SCOPE
- Live POS APIs, fuzzy match, merchant self-serve
WHAT THE THREE DAYS COVER
Map the files.
Find a next move.
The three-day window starts once scope and data access are agreed — typically when mapped files are in hand, not when the inquiry arrives.
Find the retention opportunity
Assess what the data can tell us about visit cadence, repeat purchases and customers who may be drifting.
Leave with a practical next step
Get a readout of what is usable, what is missing, and the scope for a first audience or customer-intelligence build.
FILES NEEDED
A POS export is required.
The rest raises coverage.
Headers are mapped in writing. Similar-looking column names are rejected. Excel workbooks and a public upload portal are out of scope.
Purchases / POS CSV
One row per sale. Mapped fields: amount (≥ 0), occurred-at, and at least one of loyalty ID, email, or phone. Optional location and a ticket id if they have one — that id is the purchase idempotency key.
A column-map.json and a written scope.json sit next to the file so we are not guessing headers.
Email, and loyalty if they have one
An email / engagement export raises coverage. It does not drive lapse math. If they already run a loyalty program, a members file is required (loyalty ID and email). Starting from zero: omit that file.
Never required for this assessment: live Toast, Shopify or Klaviyo adapters.
EXACT-MATCH ONLY
Known identifiers.
Clear coverage.
Loyalty ID, email, phone
Match on those three identifiers using agreed exact-match rules. Email is lowercased. Phone is digits. Loyalty IDs are trimmed. No fuzzy identity matching.
Unmatched stays unmatched
Rows with missing keys and clusters we cannot join are first-class output. We do not silently invent people so a match rate looks better.
Less identity in the analysis
Identity is stripped at ingest by default. Analysis runs on hashed keys and aggregates. When a deliverable needs an addressable audience, identity is rejoined only at that last step.
WHAT YOU LEAVE WITH
A readout.
A first motion. Not a blast calendar.
The assessment pack is a coverage and quality memo, a ranked win-back list with evidence, and one recommended offer type — not finished copy. If phones exist, an audience file can hand off into the Twilio account the agency or founder already runs.
Your agency owns the creative, the client relationship and the decision to send. LucidLoyalty is not a campaign studio and not a LucidLoyalty-branded SMS product. Available data determines what we can build. There is no outcome guarantee on this page.
SEE THE SHAPE OF THE WORK
A fictional sandbox, not a live tenant.
The sandbox uses sample members and transactions so you can open Intelligence, inspect a member, and try a purchase or redemption in the browser. It is not a client program and it is not wired to a production ledger.
Picture one of your clients, then bring that client and the question you want answered.
START HERE
- Open Intelligence
See who needs attention and why.
- Look at Members
Connect the recommendation to customer history.
- Request the assessment
Same LucidDataMind form as the rest of this site.
AFTER YOU SUBMIT
The form is the start of a conversation.
Inquiries go to the existing LucidDataMind contact form. There is no chat widget and no second form on lucidloyalty.com.
- You review the prefilled note and send the inquiry yourself. A click is not a booking.
- We agree scope in writing — client, identifiers, history window, and who holds the files.
- Mapped files land and the three-day clock starts.
- You leave with the readout and a decision about whether a first audience is worth building.
Book a 3-day data assessment
Prefer email? dmt@luciddatamind.com is the backup.
The three-day window starts once scope and data access are agreed.