Cart Migration Documentation

Migrating is a simple process when conducted through LitExtension migration solution. Before beginning to migrate from your store to another eCommerce platform, you must complete the preparation tasks bellow

Data you can send to Customer.io

Our system is designed to receive information about your customers and the activity they perform in your system. This lets us send highly targeted messages based on that activity. A deliberate approach to mapping your product’s user and behavioral data to Customer.io is critical for your success.

You may want to send us:

What to send Description When
Profile Attributes Properties stored per Person in your account. Send when you store data that is unique to an individual so you can use it for messaging or segmenting.
Events Actions performed by the People in your account. Send when you want to trigger an Event-triggered Campaign or when you want to log an activity for the purpose of segmenting users by what they’ve done (or haven’t done) in your system.
Page Views Special events that describe web pages visited by your People. Send when you want to segment People based on pages they have (or haven’t) visited on your website.
Devices The physical objects used by People in your account to interact with your system. Only required when you send mobile push notifications through Customer.io.
Triggers Data sent to trigger specific API Triggered Broadcasts. Only required when using API Triggered Broadcasts to send messages through Customer.io.
 

Practical Examples

Profile Attributes:

Here are some examples of what you can do once you have data in your Peoples’ profile Attributes:

  • Segmentation – If you store a Person’s subscription plan as an Attribute (e.g., free/basic/premium), you can create Segments to match specific subscriber types. With Segments like that you can ensure certain messages only get sent to People who have subscribed to a particular plan. (E.g., subscription_plan: premium)
  • Messaging – If you store a Person’s birthday as an Attribute, you can send them a message every year on their birthday. You can create Campaigns that trigger based on any date stored as an Attribute.
  • Customization – If you store Attributes like first_name, you can personalize messages by displaying the Person’s name in the subject or body using Liquid.
  • Accommodation – If you store a Person’s preferred contact method as “SMS”, you can use that attribute to ensure you send them SMS messages instead of email messages.

Events:

Here are some examples of what you can do once you start sending Events to Customer.io:

  • Timely Messaging – If you send an event that describes a purchase that a Person just made in your system, you can send them a receipt with an upsell offer right away while you are still on their mind.
  • Segmentation – If you send an event every time someone achieves a goal in your app, you can create a Segment that matches People who have done that event six times in the last month. With a Segment like that you can send a targeted message to your most engaged users.
  • Intervention – If you send an event every time someone submits a support request, you can send a Slack message to your team for someone to investigate when the same Person has submitted more than three requests in a week.

Page Views:

Here are some examples of what you can do once you start sending Page Views to Customer.io:

  • Monitor – You can create a Segment to match People who keep viewing your best selling products but haven’t made a purchase yet. Then you can optionally message them about an upcoming promotion for the item they’ve been looking at.
  • Classify – Have topical articles? You can create a Segment to match People who viewed an article about “Game of Thrones.” Then you can use that Segment to trigger a Campaign that will update their profile to reflect that interest.

Devices:

Here are some examples of what you can do once you start sending Devices to Customer.io:

  • Alert – Send People urgent push notifications based on their current location.
  • Inform – Let People know about major app updates nudge them to install the new version or check out a new feature.
  • Remind – Send People reminders to complete key actions in your app.

Triggers:

Here are some examples of what you can do once you set up API Triggered Broadcasts and start sending trigger data to Customer.io:

  • Topical Updates – Send an announcement to People about subjects they care about. Imagine two announcements using the same message templates: “Game of Thrones reboot already underway.” and “Stranger Things actors on strike over script mishap.”
  • Location-based Alerts – Notify People when an incident occurs in a location they care about. Imagine one configuration that can send both: “Mapletown’s Fall Festival dates updated to October 29-30.” and “Power out in much of Manhattan.”

Data you can send to Customer.io

Our system is designed to receive information about your customers and the activity they perform in your system. This lets us send highly targeted messages based on that activity. A deliberate approach to mapping your product’s user and behavioral data to Customer.io is critical for your success.

You may want to send us:

What to send Description When
Profile Attributes Properties stored per Person in your account. Send when you store data that is unique to an individual so you can use it for messaging or segmenting.
Events Actions performed by the People in your account. Send when you want to trigger an Event-triggered Campaign or when you want to log an activity for the purpose of segmenting users by what they’ve done (or haven’t done) in your system.
Page Views Special events that describe web pages visited by your People. Send when you want to segment People based on pages they have (or haven’t) visited on your website.
Devices The physical objects used by People in your account to interact with your system. Only required when you send mobile push notifications through Customer.io.
Triggers Data sent to trigger specific API Triggered Broadcasts. Only required when using API Triggered Broadcasts to send messages through Customer.io.
 

Practical Examples

Profile Attributes:

Here are some examples of what you can do once you have data in your Peoples’ profile Attributes:

  • Segmentation – If you store a Person’s subscription plan as an Attribute (e.g., free/basic/premium), you can create Segments to match specific subscriber types. With Segments like that you can ensure certain messages only get sent to People who have subscribed to a particular plan. (E.g., subscription_plan: premium)
  • Messaging – If you store a Person’s birthday as an Attribute, you can send them a message every year on their birthday. You can create Campaigns that trigger based on any date stored as an Attribute.
  • Customization – If you store Attributes like first_name, you can personalize messages by displaying the Person’s name in the subject or body using Liquid.
  • Accommodation – If you store a Person’s preferred contact method as “SMS”, you can use that attribute to ensure you send them SMS messages instead of email messages.

Events:

Here are some examples of what you can do once you start sending Events to Customer.io:

  • Timely Messaging – If you send an event that describes a purchase that a Person just made in your system, you can send them a receipt with an upsell offer right away while you are still on their mind.
  • Segmentation – If you send an event every time someone achieves a goal in your app, you can create a Segment that matches People who have done that event six times in the last month. With a Segment like that you can send a targeted message to your most engaged users.
  • Intervention – If you send an event every time someone submits a support request, you can send a Slack message to your team for someone to investigate when the same Person has submitted more than three requests in a week.

Page Views:

Here are some examples of what you can do once you start sending Page Views to Customer.io:

  • Monitor – You can create a Segment to match People who keep viewing your best selling products but haven’t made a purchase yet. Then you can optionally message them about an upcoming promotion for the item they’ve been looking at.
  • Classify – Have topical articles? You can create a Segment to match People who viewed an article about “Game of Thrones.” Then you can use that Segment to trigger a Campaign that will update their profile to reflect that interest.

Devices:

Here are some examples of what you can do once you start sending Devices to Customer.io:

  • Alert – Send People urgent push notifications based on their current location.
  • Inform – Let People know about major app updates nudge them to install the new version or check out a new feature.
  • Remind – Send People reminders to complete key actions in your app.

Triggers:

Here are some examples of what you can do once you set up API Triggered Broadcasts and start sending trigger data to Customer.io:

  • Topical Updates – Send an announcement to People about subjects they care about. Imagine two announcements using the same message templates: “Game of Thrones reboot already underway.” and “Stranger Things actors on strike over script mishap.”
  • Location-based Alerts – Notify People when an incident occurs in a location they care about. Imagine one configuration that can send both: “Mapletown’s Fall Festival dates updated to October 29-30.” and “Power out in much of Manhattan.”

Copyright © 2011 - 2020 LitExtension.com. All Rights Reserved.