Short and powerful: confection.submitEvent("eventName", JSON.stringify({%Your Object/Array Here%}));

Confection custom event values support any JSON-encoded string. Use this feature to create your own event-based custom objects and arrays. Organize data so it's convenient for you and customized for target endpoints.

About Confection Events

Confection automatically tracks the following kinds of events:

• form fields (which we treat as PII)
• page load speed
• pageviews and associated session intel (eg., acquisition data)

With a few lines of code, customers can also track eCommerce purchase events and send them directly to GA and Matomo. See this documentation for more information.

As we outline in our dashboard documentation, Confection also supports generic custom events. To submit a custom Confection event, use this syntax:

Add that above your site’s </head> tag and below your Confection header code. For example, if you wanted to submit a custom event named click with a value of 1, you’d add this to your site:

<script>
confection.submitEvent("click", 1);
</script>

Example 2: Closed Form (Endpoint Specific)

Let's imagine you want to structure event data so it meets the schema requirements of a particular platform. Our CAPI and Google Ads API are examples of this in action. One other follows.

We know HubSpot's core analytics script is is frequently blocked. The script name varies by account number, but ours is https://js.hs-analytics.net/analytics/1692897900000/7349006.js. When this script fails to fire, HubSpot users experience severe consequences:

• HubSpot can't collect and record user interactions, such as pageviews, clicks, form submissions, and other engagement events. This will lead to incomplete or inaccurate data in analytics reports.
• The failure to track user interactions and incomplete analytics data will make it difficult to analyze user behavior, identify trends, and make informed decisions.
• Conversion events such as sign-ups, downloads, or purchases won't be captured. As a result, a HubSpot user won't have an accurate portrait of their website's ability to convert visitors.
• HubSpot users will miss insights into user behavior, preferences, and engagement patterns, which could hinder their ability to optimize website content and UX.
• If a HubSpot user is tracking data to personalize content for visitors, the lack of data could lead to subpar personalization experiences.
• If a HubSpot user is running marketing campaigns and relying on accurate tracking data to measure their performance, the failure of tracking could hinder that user's ability to assess campaign effectiveness.
• Any reports generated using incomplete or inaccurate data would be unreliable and might not reflect the true state of a website's performance.
• If a HubSpot user is collecting user data and tracking interactions, this script's failure could potentially lead to privacy concerns or compliance issues. HubSpot's banner.js (eg., https://js.hs-banner.com/v2/7349006/banner.js) also routinely fails to fire, which increases and compounds this particular risk.

You can use a Confection custom event to ensure this data fires properly, and you can use a custom JSON object to easily prepare the payload for ingestion into the HubSpot API. As a simple example, let's assume we want to write pageview events and associated campaign data to HubSpot contact records. You could just add code like this below your Confection footer JS and above your site's closing </body> tag:

This will use HubSpot first-party cookie data to identify the relevant user and pass the pageview and campaign details to your Confection account as a custom event structured as follows:

Note, this matches the data schema HubSpot API expects.

Today is your data independence day.
Take control of your pageviews, acquisition intel, and other "atomic-level" digital marketing data. Get +52-125% better analytics data, +20-30% more effective paid ads, and +88% larger audiences.