Klaviyo Tracking
When using the Track API, make sure to include at least $email or $phone_number within the custom_properties object to identify the user.
If an event needs to be unique and not have duplicate events show up in the user's activity, include an $event_id within the properties object.
User Auth​
| Trigger | Event Name | Page | Timing | Layer | $event_id (unique) |
|---|---|---|---|---|---|
| User starts | [Auth] User Registered | - | - | Backend | - |
| User sent PIN | [Auth] PIN Sent | - | - | Backend | - |
| Verify PIN | [Auth] PIN Verified | - | - | Backend | - |
| User completed | [Auth] Completed Registration | - | - | Backend | - |
Health & Care​
| Trigger | Event Name | Page | Timing | Layer | $event_id (unique) |
|---|---|---|---|---|---|
| User starts intro | [H&C] Intro Started | H&C Intro | On page load | Frontend | hcIntroStarted |
| User shown data input | [H&C] Shown Data Input | H&C Key Details | On page load | Frontend | hcShownDataInput |
| User proceeds past data input | [H&C] Proceeded Past Data Input | H&C Key Details | On submit | Backend | hcPassedDataInput |
| User starts main flow | [H&C] Main Flow Started | H&C Climate | On page load | Frontend | hcMainFlowStarted |
| H&C Stepper {pageName} Completion | [H&C] {pageName} Step Completed | H&C Stepper Pages | On submit | Backend | hc{pageName}Completed |
| User is shown H&C Summary | [H&C] Summary Shown | H&C Summary/Overview | On page load | Frontend | hcSummaryShown |
| User shares with family | [H&C] Plan Shared | Share H&C Page | On submit | Backend | - |
Final Wishes​
| Trigger | Event Name | Page | Timing | Layer | $event_id (unique) |
|---|---|---|---|---|---|
| User starts intro | [FW] Intro Started | FW Intro | On page load | Frontend | fwIntroStarted |
| User shown data input | [FW] Shown Data Input | FW Key Details | On page load | Frontend | fwShownDataInput |
| User proceeds past data input | [FW] Proceeded Past Data Input | FW Key Details | On submit | Backend | fwPassedDataInput |
| User starts main flow | [FW] Main Flow Started | FW Experience | On page load | Frontend | fwMainFlowStarted |
| FW Stepper {pageName} Completed | [FW] {pageName} Step Completed | Each FW Step | On submit | Backend | fw{pageName}Completed |
| User is shown FW summary | [FW] Shown Summary | Plan Overview | On page load if completedPlanning(?) | Frontend | fwShownSummary |
| User shares with family | [FW] Plan Shared | Share FW Page | On submit | Backend | - |
SLI​
| Trigger | Event Name | Page | Timing | Layer | $event_id (unique) |
|---|---|---|---|---|---|
| User is shown SLI Advertorial | [SLI] Shown Advertorial | SLI Intro | On page load | Frontend | sliShownAdvertorial |
| User starts SLI process | [SLI] Start Process | SLI Intro | When Let's Get Started button is clicked | Frontend | - |
| User is shown gender/bday page | [SLI] Shown Gender/Bday Page | SLI Details | On page load | Frontend | sliShownGenderBday |
| User proceeds past gender/bday page | [SLI] Completed Gender/Bday Page | SLI Details | On submit | Backend | sliCompletedGenderBday |
| SLI Stepper {pageName} Completion | [SLI] {pageName} Completed | SLI Slider Steps | On submit | Backend | - |
| User is shown proposal | [SLI] Shown Proposal | SLI Proposal Page | On page load | Frontend | sliShownProposal |
| User is shown application | [SLI] Shown Application | SLI Application Page | On page load | Frontend | sliShownApplication |
| User submits application | [SLI] Submitted Application | SLI Application Page | On submit | Backend | - |
Examples​
{
"token": "PUBLIC_KEY",
"event": "[SLI] Submitted Application",
"customer_properties": {
// make sure to include at least $email or $phone_number to be able to identify the user
"$email": user.email,
"$phone_number": user.phone
},
"properties": {
// including an $event_id (optional) makes the event unique and will prevent duplicates in Klaviyo
"$event_id": "uniqueName",
"something_about_the_event": "nice"
}
}