Hey @kelliechenson!
They did update the native Marketing Events object to show up as a primary data source in the custom report builder recently. Which is a good step in the right direction to solve for this. BUT they don’t properly expose the registrant data as a separate object selectable in the data sources, which makes what you are looking to do in seeing total registrations over time much more difficult since you are just playing with whats available on the event records properties.
Full disclosure we built an app called event•hapily that solves for this, il just get that out of the way so this does not seem like a veiled sales pitch lol. I will show you how we solve for that and maybe you can steal a page from our playbook/app logic. The trick is having a sepaprate object that represents the individual instance of the registration. That record would hold information about who the registrant is, what event it is for, WHEN the registration took place, and what the final status of that registration ended up being (attended, did not attend, cancelled, etc..).
The whole reason having it as its own object (associated to the event) is that it makes it much easier to do cross object reporting in the custom report builder and chop the data up in ways that you need to to get the desired results.
With event•hapily we have our own direct zoom integration that works w/ meetings + webinars. When one of those is created it automatically generates an event record (we use a custom object instead of the marketing events one) and when people register for the event on our landing page they auto register into zoom, and vice versa (if you like zoom registration pages). But it creates a unique registration record that is assocaited to our event object. Thus splitting the concept of the representation of the event itself, and the individual registration. That registration has it’s own create date, since it’s its own individual record. So total registration trends over time can be easily reported on and broken down by event and any time frame you want. Here is a ROUGH example below.
In the above example I am showing count of registrants created over time based on the CREATE DATE of the individual registrant record, and then I am doing a BREAKDOWN by the associated event’s NAME. But you can also create single object reports that live on event records themselves and show registration trends over time for a specific event. Example below is one of these reports sitting on an individual event record in a middle panel card.
Our app makes this super easy out of the box to do this kind of stuff. BUT if you don’t wanna get an app to solve it and want to build it on your own, the key is having an individually separate REGISTRANT record that represents “that time, that person, registered for that event”. Having a instance of that “thing” and associating it to the record of the event, is the key to breaking that data down the right way in the custom report builder.
It looks like HubSpot kind of exposes the back end record of a registration in the report builder calls “marketing event participation” but its pretty limited in the data is exposes and does not have individual properties for “create date” which is crucial for counting how many registrations in a given timeframe. It has an “occured at” field but i think thats going to change each time a status gets updated which can really weird out reporting if you are trying to just get registrations created over time. But it’s worth looking into these 2 types of data points that HubSpot gives out of the box in the custom report builder.
As an experiment, i’d try using the custom report builder, and create a report with “Event particpations” as the PRIMARY data source, and throw in marketing events as the SECONDARY in case you want to breakdown by the event they are assocaited to. Do “COUNT OF marketing event participations” as the Y axis and put the “occured at” date on the X access and see if it gets you closer to “number of registraitons over time”. I THINK that could get you there. I put an example of this below.
Try this configuration in the report builder!
Hope that helps a little bit! If it dosent let us know!