[MoM] Integration Discussion with Data, User, and Engineering Team - 5 April

Date
05 Apr 2017
Attendees

Goals

Marketing Tech to share the project background & objective and integration items
Discuss about MoEngage integration from Data and Engineering perspective

Minutes
1. Dellyna highlight main objectives to onboard vendor such as:

Improve audience builder with real time events, segmentation, and personalization
Improve content builder and automate campaign flow
Improve user experience through several features such as Rich Push Notif, best time sending optimization, cross device and cross channel campaign delivery.

2. BK highlight that during integration we might need to review from various team such as:

Infosec
site infra
all engineering product
engineering @backend-arch-board

3. BK and Mas Ainun highlight that the most feasible way to integrate the data is using Kafka. This is to avoid any development or change in current traveloka system architecture and also there's concern in terms of engineering resource allocation.
4. Segmentation, Campaign Journey, Content Builder, and Audience Builder can be executed in moEngage system while for the job sending can leverage current message tools (so MoEngage will talk to our message tools API)
5. From point no 3 & 4, SDK might not required from engineering perspective. But this statement will be recheck during tomorrow discussion with MoEngage.
Action Items
1. Gather some more details information from MoEngage during the discussion on 6th April, such as:

Data SLA - what happen to our API if their system down
How to export the data outside MoEngage
How to handle the traffic

2. After discuss with MoEngage, all team will sit together to discuss the integration plan to move forward

Reference:
Confluence Page