Event Integration

This page answers common questions about sending events to Dengage Big Data tables and how to structure those tables.

Can I send events without the SDK?

Yes. You have several options for sending your events to the big data tables. You can integrate the SDK and event JS directly into your source code, or include them with Google Tag Manager (GTM). You can also use the SendEvent API method, which requires API integration.

📘
Note
If you want to proceed with the Event API method, you can get the "Key" from the SDK and send it. Or, if you generate the "Key" yourself, you can send it directly.

Should I store events in one table or several?

The choice between a single table or multiple tables should align with your overall data strategy and the needs of your customers who will be using these tables for event definitions and segment creation. Here are some considerations to help you decide:

Split high volume event data into separate tables to improve query performance and data management.
Use separate tables when different event types have significantly different attributes or fields. This helps maintain data integrity.
Use separate tables when you often need to retrieve data across multiple events or need complex joins between event data.
Consider scalability. Separate tables make it easier to scale horizontally by adding servers or resources for increased data volume.
Use separate tables to ensure that changes or issues with one type of event data do not impact others. This can be crucial for data quality and reliability.
Use separate tables for easier maintenance, such as backups, indexing, and optimising for specific types of queries.
Keep a single table when your event data shares a similar structure and you want to keep the data model simple.

Where will my events be written in the database?

Dengage records events in the "Big Data" tables. For standard e-commerce activities, the events are written to the following tables:

Event type	Table
Page view	page_view_events
Add to cart, remove from cart, view cart, begin checkout	shopping_cart_events
Search	search_events
Add to wishlist	wishlist_events

For non-e-commerce applications, you can create a custom events table with custom event fields as per your requirements.

You must create the tables used for event storage as Big Data tables.

How can we collect different website events into a single account?

To collect various website events into a single account in Dengage, follow these steps:

Determine the types of events and data you want to collect, such as page views or ecommerce events.
Use the Dengage Web SDK to collect standard events like page views and ecommerce events.
For custom events, create a "Big Data" table in the Dengage admin panel. This table will store collected events, and you can define multiple tables based on specific needs.
Define the structure and content of the events in the custom table according to your business requirements. This offers flexibility in capturing any type of event.
Identify logged in users with the Web SDK. If you have a user ID for logged in users, use the following code snippet anywhere on your page:

dengage('setContactKey', 'user_unique_contact_key');

You can then use the collected events to create behavioural segments.