Segmenting your audience allows you to send contextual notifications to your subscribers based on their activity and interests thus making them relate to your campaigns more and more.

Predefined Properties

The moment you go live with iZooto you start gathering subscribers. Along with capturing subscribers our system also captures a few additional properties that give us some basic intel about our subscribers. Here are the properties that system captures by-default:


The device they have subscribed from: Desktop, Mobile, Tablet

The location of the device they have subscribed from. However, if a subscriber changes cities, the location doesn’t get updated automatically.
Subscription Date
The day when the subscription occurred.
In order to make a notification more personalised, predefined properties play a vital role but for better retargeting we need Behavioural Properties so that you understand a user’s activity on the website. Behavioural Properties help you understand the various stages of a user’s journey on your website and create targeted and personalised notifications for better results. Two types of Behavioural Properties can be captured on iZooto - Events & Event Properties and User Properties.

User-Events & Event Properties

User-events let you capture specific user actions on your website. For instance, events like Page Visits, Items Added to Cart and Successful Transactions can be captured for an e-commerce website. You can pass User-Events with or without Event-Properties.
iZooto system supports 5 data types for Event Properties - String, Numeric, Date, Boolean, Float.
1. String Data type:
<script> window._izq.push(["event","added_to_cart",{ "product_title":"Earphones" /*Name of the product*/ }]);</script>
Operations in Create Audience:
  • Is any of
  • Is none of
2. Numeric Data type:
<script> window._izq.push(["event","added_to_cart",{ "product_price":25000 /*Price of the product*/ }]);</script>
<script> window._izq.push(["event","added_to_cart",{ "cash_on_delivery":"true" }]); </script>
Operations in Create Audience:
  • Equals
  • Not equals
3. Date Data Type:
<script>window._izq.push(["event","added_to_cart",{ "delivery_date":"2018-04-19 00:00:00" }]);</script>
Operations in Create Audience:
Absolute Filter
  • Before
  • After
  • On
  • Relative Filter
  • In past ‘x’ days
  • Was exactly ‘x’ days ago
  • Today
4. Float Data Type:
<script> window._izq.push(["event","added_to_cart",{ "product_price":191.50 }]); </script>
Operations in Create Audience:
  • Greater than
  • Less than
  • Equals
  • Not equals

Tracking User Activities and Properties

Capturing User Activities
User actions, for instance - page visits, button clicks, form submissions, etc. can be captured in the form of events using custom JavaScript codes. Additionally, properties related to that event can be passed too for better identification. For instance, on an e-commerce website the clicks on the add to cart button can be captured as an event while the product name, category, ID, price, size and quantity can be captured as event properties.
<script> window._izq.push(["event","added_to_cart",{ "product_title":"Earphone", "product_brand":"Sony", "product_price":25000 }]); </script>

Sample Code for Tracking Views on Collection/Category Pages

<script> window._izq.push(["event”,”collection_viewed",{ “collection_id":12345, /*optional*/
"collection_handle”:”first page”,
/*optional parameter*/ "collection_link":"", /*required*/
}]); </script>

Sample Code for Tracking Views on Product Pages

<script> window._izq.push(["event","product_viewed",{ "product_id":12345, /*optional*/
"product_title":"Emoji half sleeve teeshirt",
/*optional*/ "product_price":499.00, /*required*/
}]); </script>

Sample Code for Tracking Clicks on the Add to Cart Button

<script> window._izq.push(["event","added_to_cart",{ "product_title":"Emoji half sleeve teeshirt", /*required*/
}]); </script>

Sample Code for Tracking Successful Purchases

<script> window._izq.push(["event","order_placed",{ "cart_token":"1abc23", /*optional*/
"cart_value":2000, /*required*/
}]); </script>

Capturing User Properties

User properties allow us to capture a subscriber's interests and demographics thus helping us in profiling. Attributes like age group, gender, brand affinity, etc. can be passed as user properties with the help of simple JavaScript codes.
<script> window._izq.push(["userProfile",{"add":{"Gender":"Female"}}]); </script>
Once you are done with the required implementation for tracking user activities and properties, you can verify the implementation using Google Tag Manager or using the browser console.

Verification (Using GTM)

  • Open your website linked with GTM in Preview mode.
  • Imitate the user activity you want to verify.
  • If the implementation is done correctly, you will be able to see the events fired in the GTM preview panel.
Follow this link to know in detail.


  • The maximum number of events supported are 8.
  • ​Max length supported for event name ​are 32 characters. Incase, it exceeds the excess would get trimmed.​
  • Max length allowed for events key/values are 32/64​ character​s. Incase, it exceeds the excess would get trimmed.
  • If key/value exceeds 32/64 characters​,​ it will be trim as per limit and send. (Currently this condition ignore the key/value pair).
  • Maximum ​number of ​values possible in a multi-value array is 64 (Each value ​can ​have characters​ limit of 64 max)​​
  • The maximum number of properties supported per event are 16.
  • The maximum number of customer-defined User-Properties are 64.
  • Values for String type User-Properties support a maximum of 64 characters.
  • Data types supported are String, Numeric, Date, Boolean.
  • There are no language restriction.
  • The data type for existing User-Property will be modified as per the last entry. For instance, if you define a User-Property as 'Numeric', and pass 'String' value to it, the data type will be changed to 'String', and operation filters in Audience Builder will be changed accordingly. You won't be able to see older data sent with the previous data type in 'Audience Builder' anymore.
  • Below mentioned are system properties reserved for internal use only. Please refrain from using these properties while defining user-properties at your end:

Did this help answer your question?


Thanks for the feedback! 🙏🏽

Help by drift