Klaviyo Fields

Audience Profile Data

QPilot syncs the following values to Klaviyo customer profiles. Learn more about each field here.

• Customer Email
• Customer Created Date (UTC)
• First Scheduled Order Created (UTC)
• Total Scheduled Orders Active
• Total Scheduled Orders Active Value
• Total scheduled Orders Paused
• Total Scheduled Orders Paused Value
• Total Scheduled Orders Failed
• Total Scheduled Orders Failed Value
• Total Scheduled Orders Deleted
• Total Scheduled Orders Deleted Value
• Total Scheduled Orders Lifetime Value
• Average Processing Cycle Value
• Last Successful Processing Cycle Date (UTC)
• Last Failed Processing Cycle Date (UTC)
• Last Paused Scheduled Order Date (UTC)
• Total Successful Processing Cycles

Event Metrics

QPilot sends the following metrics to Klaviyo that can be used to trigger flows Learn more about each event here.

• Scheduled Order Created
• Scheduled Order Paused
• Scheduled Order Locked
• Upcoming Scheduled Order

Coming Soon:

• Scheduled Order Deleted
• Scheduled Order Succesfully Processed
• Upcoming Scheduled Order Validation Errors
  • "Empty Scheduled Order" Error Emails
  • "No Items To Ship" Error Emails
  • "No Payment Method" Error Emails
• Scheduled Order Error Notifications
  • "Payment Authentication Required" Error Emails
  • "Empty Scheduled Order" Error Emails
  • "No Items To Ship" Error Emails
  • "Payment Method Null" Error Emails
  • "Payment Failed" Error Emails

👍

Dynamic Fields

QPilot uses the same (Liquid) templating language as Klaviyo. This means that the same dynamic fields that are able to be used in QPilot's Email Templates can also be used in Klaviyo.

To use a QPilot dynamic field in a Klaviyo Template, simply prepend the name of the dynamic field with "event.".

Subscription Data

QPilot sends the following subscription data to Klaviyo that can be used to customize flows. Learn more about each value here.

• Id
  • Scheduled Order Id
• CustomerId
• LastOccurrenceUtc
• NextOccurrenceUtc
• Scheduled Order Status
  • Can be one of the following: Active, Failed, Paused, Deleted, Locked, Processing, or Queued.
• CreatedUtc
• UpdatedUtc
• FrequencyType
• Frequency
• FrequencyDisplayName
• Cycles
• ShippingTotal
• TaxTotal
• Total
• ShippingFirstName
• ShippingLastName
• ShippingStreet1
• ShippingStreet2
• ShippingCity
• ShippingState
• ShippingPostcode
• ShippingCountry
• Subtotal
• CurrencyIso
• Name
• EstimatedDeliveryDate
• ShippingRateName
• LifetimeValue
• OriginalExternalId
• Note
• ScheduledOrderFailureReason
  • A string describing why a Scheduled Order failed on its last processing cycle (will be null if the last processing cycle was successful/the Scheduled Order has never been processed before)
• PhoneNumber
• Company
• LastProcessingCycleId
• ProcessingErrorCode
  • The processing error code that caused the Scheduled Order to fail on it’s last processing cycle if any (may be null if it’s never processed or processed successfully last)
• PreProcessingValidationResultCode
  • Why the Scheduled Order is failing pre-processing validation checks.
• Metadata
  • Sends metadata as a JSON object.
• NextOccurrenceOffset
• Origin
  • The source of creation. Can be admin, customer, or customer API (subscriber portal).
• SiteShippingAddressId
• PreferredShippingRateOption
• ScheduledOrderFailureSlug
  • The error reason and code if the Scheduled Order’s last processing cycle failed
• UtcOffset
• LastChangeToDeleted
• ScheduledOrderItems
  • List of Scheduled Order Item Ids attached to the Scheduled Order
• CouponsHistory
  • List of coupon JSON objects that have ever been applied to the Scheduled Order
    It can’t be used effectively in an email
• Coupons
  • List of coupon JSON objects that are currently applied to the Scheduled Order
• Coupon Code
  • List of coupon codes that are applied to the Scheduled Order
• DaystoNextOccurrence
  • Calculation of days until the next occurrence date
• ShippingRateCalculationErrors
  • If a shipping rate can’t be found/applied, this describes the error

📘

Protip:

Audience profile data can also be used in flows using segments, lists, or filters.