Where Athel lands in HubSpot

Athel is the system of capture; HubSpot stays the system of record. That division only works if what your reps capture lands somewhere your reporting can actually use — so the one architectural decision in the integration is where your Events live in HubSpot.

Athel supports two destinations: HubSpot Marketing Campaigns or a custom object. This is the thesis behind the choice. (For the setup steps themselves, see the connect play.)

The datum that has to fit

Everything Athel captures rolls up to one shape: this person, at this Event, was this kind of conversation — a decision maker who asked for pricing, a warm intro to follow up in Q4, whatever your labels say. Plus the note, in the rep’s own words.

The key property is that qualification is per contact, per Event. The same person can be a tire-kicker at one show and a buyer at the next, and attribution you can defend depends on keeping those threads separate. Whatever structure holds your Events in HubSpot has to carry that granularity — which is what rules some structures in and others out.

What Athel writes, in either mode

Per imported Event, a static list named Athel: {Event name} — the roster on the HubSpot side. Then per contact, as your team captures and wraps up:

• The contact itself, created or matched by email — never duplicated
• Membership in the Event’s Athel: … list
• An association between the contact and the Event’s record, with association labels driven by the rep’s interaction labels
• Notes and voice-note summaries as timeline engagements on the contact
• Event feedback from the team, as a note on the Event’s record

The association labels are the load-bearing piece: they’re how “engaged decision maker at this show” becomes a one-filter query instead of a spreadsheet reconstruction.

Why we recommend a custom object

For teams that measure event ROI seriously, a dedicated custom object for events is the structurally strongest home, and it’s what we recommend:

• Arbitrary associations. Custom objects can associate with contacts and deals and companies. “Which open deals trace to this show” — the question leadership actually asks — becomes a native HubSpot report rather than an export exercise.
• Custom association labels. Per-contact-per-Event qualification lives on the association itself, so one person’s story at three different shows stays three distinct records.
• Full property control. Your event object carries whatever your ops team needs — budget, region, owner, tier — and Athel maps onto the properties you already have (name, start date, end date, type).

The trade-off is setup: you (or your ops team) define the object once and map its properties during connect. After that, day-to-day is identical to the HubSpot Campaigns mode — import the Event, and everything above flows.

When Marketing Campaigns is the right fit

If your marketing team already organizes event spend as HubSpot Marketing Campaigns and your reporting runs on their influence reports, use that mode. Athel Events map onto records your team already recognizes, with zero setup — and the association labels still carry qualification.

What you give up relative to a custom object is structural: HubSpot Campaigns don’t support deal or company associations the way custom objects do, so deal-level rollups per Event take more report-building. For plenty of teams — especially where a marketing ops function already lives and breathes influence reporting — that’s the right trade, and it’s a genuinely good default. You can also start here and move to a custom object later; the capture side doesn’t change.

Why not HubSpot’s Marketing Events object

The short, honest version: HubSpot’s native Marketing Events object records attendance — who registered, who showed up. Its participation records carry a state and timestamps, nothing else: no per-contact custom properties, no deal or company associations, no documented API surface for attaching notes. The one thing Athel exists to capture — per-contact, per-Event qualification with context — has nowhere to live there, so Athel doesn’t write to it.

If webinar tools like Zoom or Eventbrite already sync attendance into Marketing Events, keep them; that data coexists fine with Athel writing your field events into HubSpot Campaigns or a custom object. They’re different layers answering different questions.

Set it up

The connect play walks the OAuth connect, the property mapping, and a five-minute end-to-end verification. Then the reports play turns what synced into the three views your next budget conversation needs.