Default Data Collected By Web SDK
The following events and attributes are captured and updated automatically by the Dengage web SDK as part of the Session Start and Session End data points, or by the Dengage backend. You don’t need to record them separately as Custom events or Custom attributes.
Device Id for each device and browser
Session-Id of user
Visit counts
Web push permission status
Web push token if permission is accepted
Token connect date
Browser name
Device Model
Device OS version
App Type
Token Type
Device name
Device Type
Device Brand
Last activity date
Token Permission
Tracking Permission
Related Articles
How can I implement web SDK?
Execute the following steps to implement web SDK: Create a web application on Admin Panel. Then, the system will provide a JavaScript code and service worker file. Add the JavaScript code to your website's source code (You must put it into <head> ...
Event Data Integration
There are two options to send Event Data to D·engage: 1. Send event data via D·engage SDK First, you need to create a website application to use the dEngage Web SDK. Go to D·engage Event SDK page for detailed instructions to 'create an ...
D.engage Web SDK Setup
Requirements D.engage Application Definition Access to your website files D.engage Web SDK provides an interface that handles web push notifications. Optionally, It also provides event tracking functionality for your website. 1. Create D.engage ...
How can I import my previously collected web push tokens?
Import your previous web push tokens using file import. OR By creating an automation job But, you will not be able to use them to send push notification because for the service worker file to be updated the person should do these steps Remove all ...
Web Push SDK Implementation
With D·engage's Web Push SDK you can collect session and event data from your website. You can also use the Web SDK to engage with your users by sending web push notifications. Please check the following page to implement D·engage's Mobile Push SDK: ...