Guide to Migrate From Klaviyo Basic to Advanced Integration
Plans: Enterprise Standard, Enterprise Advanced, API users Platforms: All platforms
Enhance your Klaviyo integration experience by transitioning from Basic to Advanced. This migration will empower you with a broader array of flow triggers and an extensive set of supported text variables. Let’s discuss the attributes of Basic and Advanced integrations, from integration methods to flow metrics and text variables.
In this tutorial, we’ll discuss:
Difference between Klaviyo Basic and Klaviyo Advanced
Parity info for Metrics
Parity info for Events property
Steps to migrate from Klaviyo Basic to Klaviyo Advanced
Have a look at the flow metrics for Basic and Advanced Klaviyo integration.
Compared to the Basic Klaviyo integration, the advanced integration supports more flow triggers and text variables. So, we recommend you migrate your basic notifications to the advanced integration for an enhanced and feature-rich experience.
Trigger Frequency: Notifications are typically triggered once for most metrics. Exceptions include certain metrics where notifications are sent multiple times at a frequency of 24 hours. For detailed information, refer here.
Skip Historical Events: AfterShip refrains from sending historical events to Klaviyo, defined as events occurring 36-72 hours prior, to ensure shoppers do not receive outdated messages. For more details, see here.
Follow the steps below to seamlessly migrate from Klaviyo Basic to Klaviyo Advanced.
Follow the provided steps here to set up an advanced Klaviyo integration. No adjustments are needed in your existing flow setup at this stage.
Save your email template as a reusable one for your advanced flow.
Navigate to your enabled flow
Enter the drag-and-drop editor
Click Manage template and choose Save as template.
Utilize the new metrics available in the advanced Klaviyo integration. Check the available metrics here.
After creating the flow metrics, follow the provided steps to create an advanced Klaviyo flow SMS message.
Once the flow metric is in place, start creating email content and use the saved template to save time.
Add an Email Action to your Klaviyo Flow
Click Edit and select Drag and drop template
choose the template saved in Step 2
Complete your email content set up
Be mindful of text variable differences between Basic and Advanced Klaviyo integrations. Refer to the provided table for the differences.
Check the complete list of text variables in the advanced Klaviyo integration here.
After completing your setup on the flow triggers and content, make sure you preview the email content with test order information. Once verified, disable the Basic Flows and immediately turn on the Advanced Flows. If necessary, you can remove the webhook URLs for the Basic Flow. However, we recommend keeping it until you are confident in the smooth operation of your Advanced Flow.
If you have any queries, feel free to connect with our support team for quick assistance.
Overview
Enhance your Klaviyo integration experience by transitioning from Basic to Advanced. This migration will empower you with a broader array of flow triggers and an extensive set of supported text variables. Let’s discuss the attributes of Basic and Advanced integrations, from integration methods to flow metrics and text variables.
What you’ll learn
In this tutorial, we’ll discuss:
Difference between Klaviyo Basic and Klaviyo Advanced
Parity info for Metrics
Parity info for Events property
Steps to migrate from Klaviyo Basic to Klaviyo Advanced
Difference between Klaviyo Basic and Klaviyo Advanced
Have a look at the flow metrics for Basic and Advanced Klaviyo integration.
Compared to the Basic Klaviyo integration, the advanced integration supports more flow triggers and text variables. So, we recommend you migrate your basic notifications to the advanced integration for an enhanced and feature-rich experience.
| Object | Basic | Advanced |
|---|---|---|
| Integration Method | Tracking updates feed from AfterShip webhook | Direct Klaviyo Account Connection |
| Flow Metrics | 6 | 16 |
| Text Variables | 20 | 57 |
| Items Table Block | 0 | 5 |
| Plan | All Plans | Enterprise Only |
Parity info for Metrics
| Basic integration metrics | In parity with the advanced integration metrics |
|---|---|
| Delivery Exception | AfterShip: Delivery exceptions - Exception |
| Failed Delivery Attempt | AfterShip: Delivery exceptions - Failed attempt |
| In Transit | AfterShip: Delivery updates - In transit |
| Out for Delivery | AfterShip: Delivery updates - Out for delivery |
| Received Delivery | AfterShip: Delivery updates - Delivered |
| Shipped Package | AfterShip: Delivery updates - Info received |
Parity info for Events property
| Basic integration events property | In parity with the advanced integration events property |
|---|---|
| CourierName | CourierName |
| CurrentStatus | ShipmentCurrentStatus |
| ShipmentPackageCount | ShipmentPackageCount |
| ShipmentType | CourierServiceType |
| TrackingPostalCode | DestinationPostalCode |
| TrackingShipDate | ShipDate |
| CheckpointTime | LatestUpdateTime |
| City | DestinationCity |
| Countrylso3 | DestinationCountrylso3 |
| CountryName | DestinationCountryName |
| CourierPhone | CourierContact |
| CourierWebURL | CourierWebURL |
| CurrentSubStatus | ShipmentCurrentSubStatus |
| DeliveryTime | TransitTime |
| DestinationCountry | DestinationCountrylso3 |
| ExpectedDelivery | CourierEstimatedDeliveryDate |
| Message | LatestCourierMessage |
| Order ID | OrderID |
| OriginCountry | OriginCountrylso3 |
| ShipmentWeight | ShipmentWeight |
| ShipmentWeightUnit | ShipmentWeightUnit |
| SignedBy | SignedBy |
| State | DestinationState |
| Title | ShipmentTitle |
| Tracking Number | TrackingNumber |
| Zip | DestinationPostalCode |
Trigger Frequency and Skip Historical Events
| Feature | Basic | Advanced |
|---|---|---|
| Trigger frequency | No | Yes |
| Skip historical events | No | Yes |
Trigger Frequency: Notifications are typically triggered once for most metrics. Exceptions include certain metrics where notifications are sent multiple times at a frequency of 24 hours. For detailed information, refer here.
Skip Historical Events: AfterShip refrains from sending historical events to Klaviyo, defined as events occurring 36-72 hours prior, to ensure shoppers do not receive outdated messages. For more details, see here.
Steps to migrate from Klaviyo Basic to Klaviyo Advanced
Follow the steps below to seamlessly migrate from Klaviyo Basic to Klaviyo Advanced.
Step 1. Create an Advanced Klaviyo integration
Follow the provided steps here to set up an advanced Klaviyo integration. No adjustments are needed in your existing flow setup at this stage.
Step 2. Save email template (For Email users)
Save your email template as a reusable one for your advanced flow.
Navigate to your enabled flow
Enter the drag-and-drop editor
Click Manage template and choose Save as template.
Step 3. Create flow metrics with Advanced integration
Utilize the new metrics available in the advanced Klaviyo integration. Check the available metrics here.
Step 4. Create flow SMS message (For SMS users)
After creating the flow metrics, follow the provided steps to create an advanced Klaviyo flow SMS message.
Step 5. Create flow email content (For Email users)
Once the flow metric is in place, start creating email content and use the saved template to save time.
Add an Email Action to your Klaviyo Flow
Click Edit and select Drag and drop template
choose the template saved in Step 2
Complete your email content set up
Step 6. Change the text variables
Be mindful of text variable differences between Basic and Advanced Klaviyo integrations. Refer to the provided table for the differences.
| Basic | Advanced |
|---|---|
| CourierName | CourierName |
| CurrentStatus | ShipmentCurrentStatus |
| ShipmentPackageCount | ShipmentPackageCount |
| ShipmentType | CourierServiceType |
| TrackingPostalCode | DestinationPostalCode |
| TrackingShipDate | ShipDate |
| CheckpointTime | LatestUpdateTime |
| City | DestinationCity |
| Countrylso3 | DestinationCountrylso3 |
| CountryName | DestinationCountryName |
| CourierPhone | CourierContact |
| CourierWebURL | CourierWebURL |
| CurrentSubStatus | ShipmentCurrentSubStatus |
| DeliveryTime | TransitTime |
| DestinationCountry | DestinationCountrylso3 |
| ExpectedDelivery | CourierEstimatedDeliveryDate |
| Message | LatestCourierMessage |
| Order ID | OrderID |
| OriginCountry | OriginCountrylso3 |
| ShipmentWeight | ShipmentWeight |
| ShipmentWeightUnit | ShipmentWeightUnit |
| SignedBy | SignedBy |
| State | DestinationState |
| Title | ShipmentTitle |
| Tracking Number | TrackingNumber |
| Zip | DestinationPostalCode |
Check the complete list of text variables in the advanced Klaviyo integration here.
Step 7. Migrate
After completing your setup on the flow triggers and content, make sure you preview the email content with test order information. Once verified, disable the Basic Flows and immediately turn on the Advanced Flows. If necessary, you can remove the webhook URLs for the Basic Flow. However, we recommend keeping it until you are confident in the smooth operation of your Advanced Flow.
If you have any queries, feel free to connect with our support team for quick assistance.
Updated on: 17/07/2024
Thank you!