The event context includes details about the current page, such as its URL, path, hash, title, referer information (host and query), and browsing history length. It also includes the IP address of the user.
When working with Tracardi, you have the option to configure whether or not to include page data in the context of each event. This configuration is done at the tracker level and can be customized according to your requirements. By adjusting the tracker context configuration, you can easily control whether or not page data is sent along with each event, providing you with flexibility and control over the data captured and processed.
Customizing Event Context
In the example above, a custom context object with a "tag" key and value "search" is added to the event options. This allows you to include additional information that is relevant to your specific use case.
Beacon events in Tracardi are events that are sent even if the customer leaves the page. These events allow you to track user interactions that may occur after a user has navigated away from a page, providing valuable insights into user behavior.
To configure a beacon event in Tracardi, you can add the asBeacon: true option to the track configuration. This indicates that the event should be sent as a beacon event.
Example of Beacon Event
Here is an example of how to configure a beacon event in Tracardi:
In the above example, the asBeacon option is set to true, indicating that the "page-view" event should be sent as a beacon event, even if the customer leaves the page.
Beacon events can be useful in scenarios where you want to track user interactions that may occur outside of the webpage, such as form submissions, button clicks, or other events that may happen after the user has navigated away from the page