Understanding Brij Events Sent to Klaviyo

Brij integrates with Klaviyo to provide event tracking and user properties, enabling businesses to personalize and optimize their marketing strategies. Below is an overview of the events Brij sends to Klaviyo and the associated user properties.

Klaviyo Events - Registration

Each time a customer advances through a step in the registration process, a corresponding event is sent to Klaviyo. These registration steps are outlined below

Registration Process Flow:

1. Registration Initiation
2. Subscribed to Email Marketing (if consent is collected during registration)
3. Registration Submission
4. Registration Approval OR Registration Denial

1. Registration Initiation:

• Description: This is the first step in the registration process where a customer begins the process of registering their product by entering their email address.
• Trigger: Customer starts the registration process by submitting their email
• System State: Initiated
• Properties Sent to Klaviyo:
  • Profile Properties
    • Email Address
  • Event Properties
    • Experience Name (experience_name):
    • Experience URL (experience_url)
    • Brij ID (brij_id)
    • Product Number (product_number)

2. Subscribed to Email Marketing

• Description: This is the step, where the user is added to the automated email marketing list.
• Trigger: Occurs immediately after the user subscribes.
• System State: Subscribed

Properties Sent to Klaviyo:

• Event Properties
  • Method (method)
  • Method Detail (method_detail)
  • Custom Method Detail (custom_method_detail)
  • Double Opt-In (double_optin)

💡 Note: This event will only take place if single opt-in is enabled in your Klaviyo API key configuration used for Brij. For more information, please check this link.

3. Registration Submission:

• Description: This is the second step in the registration process where a customer submits the necessary details to complete their registration, which may also include providing purchase information.
• Trigger: This depends on how the brand admin has set up the registration model.
  • If purchase details are not required: registration is submitted when the user enters their email and clicks 'Sign up with Email.'
  • If purchase details are required: registration is submitted when the user clicks 'Submit' after providing all mandatory information.
• System State: Submission
• Properties Sent to Klaviyo:
  • Profile Properties
    • First Name
    • Last Name
    • Phone Number
  • Event Properties
    • Experience Name (experience_name):
    • Experience URL (experience_url)
    • Brij ID (brij_id)
    • Product Number (product_number)
    • Place of Purchase (place_of_purchase)*
    • Purchase Quantity (purchase_quantity)
    • Purchase Date (purchase_date)
    • Receipt/Document Upload*

4. Registration Approval OR Registration Denial:

• Description: This is the step in the registration process, where customer registration is either approved or denied. There are three variations:
• Auto Approval: Registration is automatically approved as soon as the user registers.
• Manual Approval: Registrations are reviewed and approved by brand admins.
• Manual Denial: Registrations are reviewed and denied by brand admins.
• Trigger: The approval process is triggered based on the registration settings configured by the brand admin.
• System State: Approved/Denied

• Properties Sent to Klaviyo:

  • Event Properties
    • Experience Name (experience_name):
    • Experience URL (experience_url)
    • Brij ID (brij_id)
    • Product Number (product_number)
    • Approval Type (approval_type)
    • Place of Purchase (place_of_purchase)
    • Purchase Quantity (purchase_quantity)
    • Purchase Date (purchase_date)
    • Receipt/Document Upload*

  In case of Denial

  • Experience Name (experience_name):
  • Experience URL (experience_url)
  • Brij ID (brij_id)
  • Product Number (product_number)
  • Place of Purchase (place_of_purchase)
  • Purchase Quantity (purchase_quantity)
  • Purchase Date (purchase_date)
  • Receipt/Document Upload*

5. Brij Registration Profile Update

• Description: This is the step in the registration process where a customer updates their profile information.
• Trigger: Registration is completed and customer updates their profile details.
• System State: Profile Updated
• Properties Sent to Klaviyo:
  • Event Properties
    • Experience Name (experience_name):

💡 NOTE:

• Event properties will only appear if this field is added in the registration module.
• Profile properties will only appear if this field is added in the registration module OR if this profile property has been previously collected for this customer

</aside>