Issue 1 — “A customer is missing”
Likely Cause
The customer was merged into another persona.
Fix
Use the merge search operator:
merge:[email or phone]
Examples:
merge:6035551212 merge:[email protected]
If the customer appears, they were merged.
Issue 2 — “The wrong email or phone is attached to a persona”
Likely Causes
Duplicate signups
Shared contact info
Staff entering temporary/placeholder data
Stale POS or Ecom PII syncing in
Fix
Update the correct PII in General > Traits, then wait for the overnight sync to complete.
Issue 3 — “Transactions are showing under multiple personas”
Causes
Partial PII captured at checkout
POS created duplicate customer profiles
Recent purchase hasn’t merged yet (24-hour processing delay)
Fix
Determine the correct phone/email
Update PII on the correct persona
Wait for the merge to process overnight
For POS systems: customer may need a new transaction before updated PII syncs.
Issue 4 — “A purchase was made within 24 hours and the merges look wrong”
Reason
AIQ merges overnight. Recent data may not be processed yet.
Fix
Wait 24 hours for merging/unmerging to complete.
Issue 5 — “Staff added placeholder data and now merges are incorrect”
Cause
Fake phone numbers/emails (e.g., 1234567890, [email protected]) were used and accidentally merged with real customers.
Fix
Correct the PII in Traits
Reach out to Support if the data must be removed entirely
Retrain staff to avoid placeholder entries
Best Practices to Prevent Merge Issues
Always collect accurate phone + email
Never enter fake PII for checkouts
Strengthen staff training for POS behavior
Only use Name + DOB merging if your use case requires it
When to Escalate to Support
You need PII removed from a merged record
A customer cannot be located via merge searches
A merge created impossible point totals
You can’t determine the correct “master profile”
Support can safely adjust PII or undo merges that cannot be corrected through the UI.