In order to collect website events and use that data to create behavioral segments in dEngage you have to determine the type of events and data that needs to collected. Once you have determined that, you will need to create a “Big Data” table in dEngage. Collected events will be stored in this table. Multiple tables can be defined depending on your specific need.
Any type of event can be collected. The content and the structure of the events are completely flexible and can be changed according to unique business requirements. You will just need to define a table for events.
Once defined, all you have to do is to send the event data to these tables. dEngage SDK has only two functions for sending events: sendDeviceEvent. Most of the time you will just need the sendDeviceEvent function. For ecommerce accounts there is predefined event tables. And you can feed these tables by usern ecommerce event functions.
If the user loggs in or you have user information, this means you have contact_key for that user. You can set contact_key in order to match user with the browser. There are two functions for getting and setting contact_key.
If user logged in set user id. This is important for identifying your users. You can put this function call in every page. It will not send unnecessary events.
If you need to get current user information from SDK use this function.
There are standart ecommerce events in dEngage SDK.
For there event there is related tables in your account.
Page view events will be sent to page_view_events table. If you add new columns to this table. You can send these in the event data.
These events will be stored in shopping_cart_events and shopping_cart_events_detail. There are 4 shopping cart event functions. addToCart, removeFromCart, viewCart, beginCheckout Every shopping cart event function needs all items in cart as an array. You must send last version of the shopping cart.
For example: If there is one item in cart and item id is 5. And after that, an add to cart action is happened with the item id 10. You have to send 10 as product_id in event parameters and you must send current version of cart items. Meaning [5, 10]
Orders events will be sent to order_events and order_events_detail tables.
Search events will be stored in search_events table.
These events will be stored in wishlist_events and wishlist_events_detail. There are 2 wishlist event functions. addToWishlist, removeFromWishlist. In every event call, you can send all items in wishlist. It makes it easy to track current items in wishlist.
You can use sendDeviceEvent function for sending events for the browser. Events are sent to a big data table defined in your dEngage account. That table must have relation to the master_device table. If you set contact_key for that browser. Collected events will be associated for that user.
dengage(‘sendDeviceEvent’, tableName, dataObject [, callback]);