HubSpot Integration: Supporting Records & What Is Not Mapped

Last updated: April 23, 2026

This article covers how supporting concepts (campaigns and funds) surface in HubSpot, and provides a clear list of what the integration does not sync. Use it to set expectations and answer the question that comes up often: "why isn't X showing up in HubSpot?"

Campaigns

HubSpot does not have a native "campaign" object that maps cleanly to a WeGive campaign. Rather than force a fit, the integration denormalizes campaign attribution onto every donation and recurring deal using two custom deal properties. You can slice donation data by campaign directly on deal reports without needing a separate HubSpot campaign record.

Campaign attribution properties carried on each deal:

WeGive Data	HubSpot Property	Lives On
`campaign_id`	`wegive_campaign_id`	Deal
Campaign name	`wegive_campaign_name`	Deal

The campaign record itself is not synced to HubSpot. There is no separate HubSpot object to open or edit.

What this means in practice

You can filter and report on donation deals by wegive_campaign_name in HubSpot.
You cannot manage the campaign (edit its name, goal, media, preset amounts) from HubSpot. Campaign configuration lives only in WeGive.
If the campaign is renamed in WeGive, the new name will flow to future deals. Historical deals keep the snapshot of the campaign name at the time of the gift unless the record is re-synced.

Funds

Like campaigns, funds are denormalized onto the deal rather than synced as separate HubSpot records. The primary fund on a donation is surfaced through two custom deal properties.

Fund attribution properties carried on each deal:

WeGive Data	HubSpot Property	Lives On
`fund_id`	`wegive_fund_id`	Deal
Fund name	`wegive_fund_name`	Deal

Multi-fund splits: If a donor splits a gift across multiple funds in WeGive, HubSpot will only see the primary fund on the deal. The split detail stays in WeGive and is visible in WeGive reporting.

What this means in practice

You can filter and report on donation deals by wegive_fund_name in HubSpot.
You cannot manage the fund itself from HubSpot. Fund configuration lives only in WeGive.
For accurate fund revenue totals, WeGive's fund reporting remains the source of truth (especially when splits are common).

What Is Not Mapped

The HubSpot integration intentionally does not sync the following WeGive concepts. Some have no equivalent in HubSpot, and others are excluded to keep the sync predictable.

No HubSpot Equivalent

These WeGive concepts have no standard object in HubSpot, so they cannot sync without a custom HubSpot object.

WeGive objects with no HubSpot equivalent:

WeGive Object	Why It Does Not Sync
Soft Credits	No HubSpot object to represent secondary credit on a gift.
Pledges	No HubSpot object. Would require a custom object.
Fund Allocations (splits)	HubSpot deals are single-amount. Multi-fund splits cannot be modeled.
Fundraisers (P2P pages)	HubSpot has no peer-to-peer fundraising concept.
Events	Event management is outside HubSpot's core CRM.
Event Registrations	Tied to Events above.
Communication Lists	WeGive list membership does not map to HubSpot lists.
Communication Preferences	Subscription and channel preferences are not synced.
Payouts	Operational settlement data not useful in HubSpot CRM.

Explicitly Excluded

These features exist in both systems but are left out of sync by default.

WeGive features intentionally excluded from sync:

WeGive Feature	Status	Notes
Custom Questions	Not mapped	Form field responses from checkouts stay in WeGive.
Custom Fields on supporter or transaction	Not mapped by default	Custom mapping can be configured on request.
Tags	Not mapped	Use `wegive_donor_status` or custom properties for segmentation.
Notes	Not mapped	Supporter notes stay in WeGive.
Refunds (as separate records)	Not mapped	The original deal moves to Failed.
Transaction fee breakdown	Limited	Net amount and fee total only, not the per component breakdown.
Tribute (memorial/honor) information	Not mapped	Stays in WeGive.

Partial or Limited

These sync, but with limits worth calling out.

Concepts that sync with limitations:

Concept	Limitation
Fund attribution on deals	Only the primary fund syncs per transaction. Splits stay in WeGive.
Campaign attribution on deals	Name and ID sync. Goals, media, preset amounts, and form configuration do not.
HubSpot to WeGive recurring creation	The pull direction only links existing scheduled donations. It never creates new ones.
Deleting a record	Deletion sync is HubSpot to WeGive only, and must be turned on in settings.

Sync Direction Summary

Use this table as a one page reference when a customer asks what goes which way.

Complete push and pull direction reference:

Object	Push (WeGive to HubSpot)	Pull (HubSpot to WeGive)
Supporter (individual)	Yes	Yes
Household	Yes	Yes
Company supporter	Yes	Yes
Transaction	Yes	Link only (updates existing, never creates)
Scheduled donation	Yes	Link only (never creates in WeGive)
Campaign (as deal property)	Yes (on related deals)	No separate record to pull
Fund (as deal property)	Yes (on related deals)	No separate record to pull
Household membership	Yes (via Household association label)	Not modeled on pull
Deletion	No	Yes (if Deletion Sync is enabled)
Soft credit	No	No
Pledge	No	No
Fundraiser / P2P	No	No
Event / Registration	No	No
Custom question	No	No
Custom field	No (unless custom mapping is configured)	No
Tag	No	No
Note	No	No
Refund (as record)	No	No

If You Need Something That Is Not Mapped

A few paths to consider when a customer needs data that is out of scope:

Use a custom property: If the data lives on a supporter or transaction, a custom WeGive field can often be mapped to a new HubSpot custom property. Contact WeGive Support to set this up.
Use a WeGive export: For one time analysis, WeGive exports (CSV) can be dropped into HubSpot through the HubSpot import tool.
Use Zapier or an iPaaS: For edge cases like pledges or tribute information, a Zapier flow or iPaaS connector can bridge the gap without customizing the core integration.

Common Questions

Can I build a HubSpot dashboard of revenue by campaign?
Yes. Report on deals grouped by wegive_campaign_name. Because this property lives on every donation and recurring deal, you can slice total, new, and recurring revenue by campaign without a separate campaign object.

Can I build a HubSpot dashboard of revenue by fund?
Yes, with one caveat: only the primary fund is on the deal. Gifts split across multiple funds will show the primary only. For accurate fund totals when splits are common, use WeGive reporting.

Why doesn't a campaign I created in HubSpot show up in WeGive?
Campaigns are not a shared object. The fields on the deal (wegive_campaign_id, wegive_campaign_name) are populated from WeGive. Creating a campaign in HubSpot, even a native HubSpot marketing campaign, will not create anything in WeGive.

What about deletions?
HubSpot deletions can soft-delete the matching record in WeGive if Deletion Sync is enabled. WeGive deletions do not propagate to HubSpot. See Article 1 for the setting, and Article 6 (coming soon) for the full behavior.

Next Steps

This completes the setup and data mapping series.

Overview & Setup
Contacts & Companies
Donations
Recurring Donations
Supporting Records & What Is Not Mapped (this article)

Sync Behavior & Monitoring and FAQ & Known Limitations will be drafted next after live setup testing.