Case study at a glance
About this case study: this is an Infinite360 Tech Academy project case study delivered on a simulation environment with synthetic data. It shows the scope, architecture and approach our consultants and learners practise. It is not a client engagement and implies no affiliation with, or endorsement by, any company or brand.
| Industry | Retail |
|---|---|
| Platforms | AEP, Web SDK, Mobile SDK, Real-Time CDP |
| Type | Academy project case study (simulated environment, synthetic data) |
| Roles practised | Web SDK engineer, identity architect, QA specialist |
| Environment | aepsimualtor.infiante360techacademy.com |
The business challenge
A retailer has a website on Web SDK, a mobile app on Mobile SDK, CRM batch files and a streaming point-of-sale feed. A shopper browses anonymously, views products, adds items to the cart, logs in and later buys in store — yet the profile still looks anonymous. The team needs a repeatable way to find the break.
Target architecture
Implementation approach
- Check Web SDK — identityMap after login
- Edge debugger — ECID, email, CRM ID
- Identity graph — links present?
- Dataset — profile-enabled?
- Merge policy — correct precedence
- Root cause & fix — retest
Use cases implemented
- Anonymous-to-known stitching on login
- Cart-abandonment audience across web and app
- Store purchase linked to the online profile
- Suppression of recent purchasers from cart journeys
- Identity graph health monitoring
- Troubleshooting runbook for unstitched profiles
Validation and governance checks
- Authenticated identity sent in identityMap on login with the correct authenticated state
- Same namespace and hashing used for email in every source
- All datasets that should build the profile are profile-enabled
- Merge policy precedence reviewed so the newest trusted data wins
- Graph checked for over-merging from shared devices
What Infinite360 brings
Architecture first
A documented target architecture, identity strategy and data model before a single journey is built.
Reusable accelerators
Schema patterns, naming conventions, backlog templates, QA checklists and runbooks reused across projects.
Validation discipline
Every stage is validated - payloads, identity graphs, profile fragments, audience counts and journey test runs.
Governance built in
Consent, data usage labels and least-privilege access are designed in, not bolted on at go-live.
Knowledge transfer
Walkthrough recordings, documentation and pairing so your team can run and extend the solution.
Day-one-ready people
Consultants and contract engineers who have practised the same pattern end to end before joining your team.
From case study to contract delivery
The roles that practise this case study — Web SDK engineer, identity architect, QA specialist — are the same profiles we place through contract hiring and staff augmentation. Because they have already built this pattern end to end, onboarding focuses on your systems and standards rather than on learning the platform.
Frequently asked questions
Why does a profile stay anonymous after login?
The most common root cause is that no authenticated identity is sent after login, so ECID is never linked to the email or CRM ID.
What tools help debug identity?
The Adobe Experience Platform Debugger, the identity graph viewer and the profile viewer, plus Query Service checks on the datasets.
Last updated: