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. |
Here are some examples of what you can do once you have data in your Peoples’ profile Attributes:
subscription_plan
: premium)first_name
, you can personalize messages by displaying the Person’s name in the subject or body using Liquid.Here are some examples of what you can do once you start sending Events to Customer.io:
Here are some examples of what you can do once you start sending Page Views to Customer.io:
Here are some examples of what you can do once you start sending Devices to Customer.io:
Here are some examples of what you can do once you set up API Triggered Broadcasts and start sending trigger data 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. |
Here are some examples of what you can do once you have data in your Peoples’ profile Attributes:
subscription_plan
: premium)first_name
, you can personalize messages by displaying the Person’s name in the subject or body using Liquid.Here are some examples of what you can do once you start sending Events to Customer.io:
Here are some examples of what you can do once you start sending Page Views to Customer.io:
Here are some examples of what you can do once you start sending Devices to Customer.io:
Here are some examples of what you can do once you set up API Triggered Broadcasts and start sending trigger data to Customer.io:
Data In or Out – Points to Conside
メールアドレスを入力すると、利用規約とプライバシーポリシーに同意したことになります。
住所: 埼玉県ふじみ野市鶴ケ岡2丁目21−15
TEL: 090-6051-6686