Tracking Events

Must Read

We recommend that you get yourself acquainted with the concept of Event Structure before proceeding. Doing so will help you understand the workings of this section, better.

Antsomi offers two distinct methods to facilitate event tracking within your application. The first method, trackScreen(), should be triggered whenever your user interacts with any screen within your application. The second method, track(), serves as a comprehensive solution for tracking various events, encompassing both System Events and Custom Events, providing you with a unified approach to monitor user interactions and behaviors effectively.

Tracking Event Screen View

Screen View events can be effortlessly tracked using the AntsomiSDK's trackScreen() method in your ReactNative application. This method allows you to monitor user interactions with various screens and gather valuable insights.

TypeScript

import AntsomiRnSDK from '@antsomicorp/antsomirnsdk';

AntsomiRnSDK.trackScreen('ProductDetail');

Tracking Other Events

Other events can be effortlessly tracked using the AntsomiSDK's track() method within your React Native application. This method allows you to monitor user interactions and events beyond screen views, providing you with comprehensive insights into user behavior. Additionally, you have the flexibility to include associated data as Event Attributes with each event, enriching your Antsomi dashboard with valuable contextual information.

For example, the Add to Cart event can be tracked by below

TypeScript

import AntsomiRnSDK from '@antsomicorp/antsomirnsdk';

const { userData }  = useSelector((state) => state.auth);
const { items: cartItems, subtotal, itemCount }  = useSelector((state) => state.cart);

// Build event data
const items: Record<string, any>[] = [];
cartItems.forEach((element) => {
  const value: Record<string, any> = element;
  
  items.add({
    type: "product",
    id: value.sku,
    name: value.name,
    sku: value.sku,
    price: +value?.salePrice,
    original_price: +value?.price,
    quantity: +value?.quantity
  });
});

const event: CDPEvent = {
  en: "add_to_cart_product" // Event internal code,
  items: items, // Multiple Items
  customerProps: {
    customer_id: MD5Hash().generateMd5(userData.email),
    name: userData.name
  },
  eventProps: { // Event Attribtues
    event_source: "add_to_cart",
    cart_subtotal: subtotal,
    cart_item_count: itemCount
  }
};

await AntsomiRnSDK.track(event);

Notice about the setter objectProps and eventProps

• The attribute objectProps accepts an object as its parameter, where the key represents the internal code of the CDP Business Object, and the value is another map. This inner map contains key-value pairs, with the key being the internal code of the object attribute and the value representing the attribute value.

• You can include multiple objects in the setter as needed, but it's important to note that only the object registered in the CDP365 event settings can have its value updated through the event. Any other objects will be excluded from our backend processing.

• The attribute customerProps setter functions uniquely; when invoked, it automatically attaches customer data to the event data. This attachment persists until you call the resetCustomer() method.

• Similarly, the attribute eventProps setter operates comparably. However, it accepts a parameter in the form of a map, where the key corresponds to the Event Attribute's internal code, and the value denotes the attribute value. As with the attribute objectProps, you can include multiple attributes as needed. Keep in mind that only the attributes registered in the system can be received in CDP.

For a sample event tracking template, you can refer to one of the links below:

• E-Commerce Events