https://github.com/sarkartanmay393/identity-reconciliation

This project aims to address the challenge of linking different orders made with different contact details to the same customer.
https://github.com/sarkartanmay393/identity-reconciliation

Last synced: 19 days ago
JSON representation

This project aims to address the challenge of linking different orders made with different contact details to the same customer.

• Host: GitHub
• URL: https://github.com/sarkartanmay393/identity-reconciliation
• Owner: sarkartanmay393
• Created: 2024-05-29T10:57:39.000Z (8 months ago)
• Default Branch: main
• Last Pushed: 2024-06-05T13:48:17.000Z (8 months ago)
• Last Synced: 2025-01-01T04:47:44.438Z (22 days ago)
• Language: TypeScript
• Homepage:
• Size: 29.3 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
## Bitespeed Assignment: Identity Reconciliation

### Introduction

FluxKart.com, committed to offering personalized customer experiences, has integrated Bitespeed into their platform. Bitespeed needs to identify and track customer identities across multiple purchases made with varying contact information. This project aims to address the challenge of linking different orders made with different contact details to the same customer.

### Demo: [Watch the video](https://vimeo.com/953969226?share=copy)

### Requirements

Design a web service with an endpoint `/identify` to receive HTTP POST requests with a JSON body:

```json

{

  "email": string,

  "phoneNumber": string

}

```

The service should return an HTTP 200 response with a JSON payload containing consolidated contact information:

```json

{

  "contact": {

    "primaryContactId": number,

    "emails": string[], // First element is the email of the primary contact

    "phoneNumbers": string[], // First element is the phone number of the primary contact

    "secondaryContactIds": number[] // Array of all secondary contact IDs

  }

}

```

#### Instructions

1. Ensure orders always have either an email or phone number in the checkout event.

2. Link contact rows if they have either email or phone as common.

3. Create a new primary contact if no existing contacts match the incoming request.

4. Create secondary contacts if the request has either email or phone common to an existing contact but contains new information.

### Stack

- **Database:** PostgreSQL

- **Backend:** Node.js, Express, TypeScript, Sequelize

### Hosting and Endpoint

- **Hosted Endpoint:** 

- **Identify Route:** 

### Contact Information

For any queries or issues, please contact me at .

---