Page view events are recorded in the page_view_events table. If you add new columns to this table, you can include them when sending event data.
// page_type can have these values // home / category / product / cart / checkout / promotion / pricing / login / logout / other
// Home page view dengage("pageView", { page_type: "home" // ... extra columns in page_view_events table, can be added here });
// category page view dengage("pageView", { page_type: "category", category_path: "Electronics > Laptop"//category path here // ... extra columns in page_view_events table, can be added here });
// product page view dengage("pageView", { page_type: "product", product_id: '123'//product id here category_path: "Electronics > Laptop", //category path here price: 100.50, //price discounted_price: 80.50, //if there is no discount, give the same price stock_count: 1, //If stock count is not available you can give 1 or 0 as stock availability info, or you can omit // ... extra columns in page_view_events table, can be added here });
// promotion page view dengage("pageView", { page_type: "promotion", promotion_id: '123'//promotion id here // you can add product_id and category_path too // ... extra columns in page_view_events table, can be added here });
// for cart, checkout, pricing, login, logout pages dengage("pageView", { page_type: "cart", // cart / checkout / pricing / login / logout // ... extra columns in page_view_events table, can be added here });
// for the others dengage("pageView", { page_type: "other" // ... extra columns in page_view_events table, can be added here });
If your D·engage account is an eCommerce account, you should use standard eCommerce events in the SDK. If you need some custom events or your account is not a standart ecommerce account, you should use custom event functions. Events for Ecommerce ...
Event Collection In Web SDK In order to collect website events and use that data to create behavioural segments in D·engage you have to determine the type of events and data that needs to collect. Web SDK provides some functions to collect page view ...
Event Collection for Custom Events You can send custom events using the sendDeviceEvent function. Events are stored in a Big Data table in your D·engage account, which must be linked to the master_device table. If you provide a contact_key for the ...
dengage_flutter Installation a) Edit your project's pubspec.yaml file to include the dengage_flutter SDK: Shell dependencies: 1.1.1 b) Run flutter pub get to install the SDK. Platform Specific Extra Steps Following extra steps after the installation ...
SDK Setup Requirements Minimum iOS version supported 11.0 SDK Installation CocoaPods Integration Dengage is available through CocoaPods. To install it, simply add the following line to your Podfile: Ruby pod 'Dengage', '~> 5.89' Run pod install via ...