Questions:
There are some possibilities on how to send the events to be consumed in mParticle. Below you can find the suggestions. Final implementation decision should be reviewed with Data RBI stakeholders.
Technical Refinement
Description
1-) When the agreement update modal is showed up during transition pages:
logRBIEvent({
name: CustomEventNames.MODAL_SHOWN,
type: EventTypes.Modal,
attributes: {title: "Terms updated"},
})
no attributes being passed… only registering the event…
Create new custom event MODAL_SHOWN in
workspaces/frontend/src/state/mParticle/constants.ts
Pass attribute title “Terms updated”
Take a look how attributes should be passed
workspaces/frontend/src/state/mParticle/mparticle-adapter.ts
2-) When user clicks on the Continue button (Accepted the updated agreement)
2.a -) Using existing CLICK_EVENT : 
logRBIEvent({
name: CustomEventNames.CLICK_EVENT,
type: EventTypes.Navigation,
attributes: {
component: ClickEventComponentNames.BUTTON,
text: 'Accepted updated agreement',
},
});
OR
2.b -) New event without attributes Accepted updated agreement:
logRBIEvent({
name: 'Accepted updated agreement',
type: EventTypes.Other,
attributes: {
<>
},
});
OR
2.c -)new event with customized attributes AGREEMENTS_UPDATE_DECISION:
{
const data = {
updatedAgreements?[]: string,
action : 'accepted'
};
logRBIEvent(CustomEventNames.AGREEMENTS_UPDATE_DECISION, EventTypes.Other, data);
}
3-) When user clicks on the disagree and logout button
3.a -)Using existing CLICK_EVENT :
mParticle.logRBIEvent({
name: CustomEventNames.CLICK_EVENT,
type: EventTypes.Navigation,
attributes: {
component: ClickEventComponentNames.BUTTON,
text: 'Disagree and Logout',
},
});
OR
3.b -)New event without attributes Disagree:
logRBIEvent({
name: 'Disagree',
type: EventTypes.Other,
attributes: {
<>
},
});
OR
3.c -)new event with customized attributes AGREEMENTS_UPDATE_DECISION :
{
const data = {
updatedAgreements?[]: string,
action : 'disagree'
};
logRBIEvent(CustomEventNames.AGREEMENTS_UPDATE_DECISION, EventTypes.Other, data);
}
0 Comments