Configure a HubSpot campaign decision log with exact object fields, associations, permissions, workflow gates, failure tests and a worked record.
Short answer: answer: On HubSpot Enterprise, create a Campaign Decision custom object, associate each record with the relevant campaign and commercial records, and require a rationale, owner, evidence link and review date before status can become Approved. On lower tiers, use a dedicated standard-object pipeline only after checking that its semantics and reporting remain clear. A note on a campaign is not a decision log because it cannot reliably drive permissions, review or analysis.
Teams often record the launch choice in meeting notes and later ask HubSpot to explain performance. The CRM can show activity, contacts and revenue, but it cannot recover the assumption, rejected option or decision rule that was never structured.
The opposite mistake is turning every discussion into a record. Log consequential choices—audience, offer, claim, budget, channel, stop rule or measurement method—not commentary that adds no future decision value.
The CRM Decision Object Model
The CRM Decision Object Model treats a decision as a first-class record joined to the entities it governs. CDM’s position is that a campaign record without its rationale and review rule is operationally incomplete, even if attribution fields are immaculate.
1. Choose the object honestly
HubSpot’s public documentation says custom objects are available on Enterprise subscriptions across named hubs and Smart CRM, with limits varying by subscription. An account needs the relevant access to create them, and an object’s internal name cannot be changed after creation. Confirm entitlements before designing around a custom object.
If available, create Campaign Decision with a unique primary display property such as Decision ID. Associate it to contacts, companies, deals and tickets where relevant. Confirm whether your portal exposes a direct association to the campaign tool; HubSpot’s marketing campaign asset association is not the same as a universal CRM-object association. Where a direct campaign association is unavailable, store a validated Campaign ID/URL and relate the decision to the underlying commercial records.
Lower-tier fallback: use a separate ticket pipeline named Marketing Decisions, not notes scattered across deals. Document the compromise because ticket semantics, automation and reporting may confuse service operations.
2. Use a field schema that captures judgment
| Field | Type | Required rule |
|---|---|---|
| Decision ID | Unique text | Immutable human-readable key |
| Decision statement | Single-line text | One choice, written as an action |
| Decision class | Dropdown | Audience, offer, claim, budget, channel, measurement, stop |
| Campaign ID/URL | Text or association | Controlling campaign reference |
| Options considered | Multi-line text | At least two, including “do nothing” where valid |
| Evidence links | Multi-line URL/text | Source records, not pasted conclusions |
| Rationale | Multi-line text | Why this option wins now |
| Assumption | Multi-line text | Most uncertain premise |
| Success threshold | Number/text | Metric, value, window and population |
| Stop condition | Text | Observable halt or escalation rule |
| Owner / approver | Owner fields | Separate for high-consequence decisions |
| Status | Pipeline stage/dropdown | Draft, Review, Approved, Superseded, Closed |
| Decided / review dates | Date | Approval and reconsideration clocks |
| Supersedes | Same-object association | Link the replacement record |
Do not overwrite a rationale after learning the outcome. Create a follow-up result field or a new superseding decision. Otherwise hindsight rewrites the evidence.
3. Build the setup sequence
First, inventory five recent campaign choices and confirm the fields can represent them. Second, ask a super admin to create the object, labels and primary display property. Third, configure associations and a pipeline. Fourth, set the manual record-create form so essential properties appear.
HubSpot documents that requiring properties or associations during manual record creation generally needs Starter, Professional or Enterprise, while custom-object creation configuration is Enterprise. Required UI fields do not govern imports, integrations or every workflow-created record, so add a completeness check.
Fifth, build views for Awaiting decision, Review overdue and Superseded but still referenced. Sixth, build reports that join decision class and chosen option to outcome records without claiming causation. Finally, test with non-admin roles before release.
4. Put approval before automation
Automation may assign the reviewer, stamp dates, create follow-up tasks and notify owners. It should not decide whether a claim, spend or audience is appropriate. A human approves by setting Decision outcome and recording the rationale; the workflow then changes status and creates the operational task.
Use workflow permissions deliberately. HubSpot distinguishes viewing, editing and enrolling workflows, and manual enrolment also depends on object access. A workflow must be turned on, and repeated use needs appropriate re-enrolment settings. Asset-level limited access can further restrict a user even when their broad permission looks adequate.
Permissions map:
- Super admin/object admin: schema and association definitions.
- Decision owner: create and edit Draft records.
- Approver: edit decision/status fields and record rationale.
- Campaign operators: view Approved; update execution references, not the decision.
- Analyst/finance: read decision and outcome fields; certify revenue definitions separately.
5. Test the failure paths
Use a sandbox or disposable records. Create one complete decision through the UI, one through import with missing rationale, one through an integration with an invalid Campaign ID and one assigned to a user without object access. Test re-enrolment after Review date changes.
The design passes only if incomplete records enter an exception view, unauthorized users cannot approve, a superseded decision remains findable, and reports do not silently treat missing associations as zero performance. Capture screenshots of object definition, fields, association card, permissions, workflow history, failed test record and final view. Do not claim the screen matches documentation until tested in your portal.
Worked record: an illustrative creator campaign choice
This is a fictional configuration example, not a HubSpot test result.
- Decision ID: DEC-2026-041
- Statement: Allocate the pilot to three specialist creators instead of one celebrity placement.
- Class: Channel/partner mix
- Options: one celebrity; three specialists; defer pilot
- Rationale: specialists reach three distinct use cases and allow comparison within the same budget
- Assumption: creator audiences have low overlap
- Success threshold: 120 qualified demo starts within 30 days at or below £70 each
- Stop condition: pause new spend if verified cost exceeds £105 after 60 qualified starts
- Campaign reference: CMP-779 / portal campaign URL
- Associations: six contacts, three companies, resulting deals
- Owner / approver: partnerships lead / marketing director
- Status / review: Approved / 30 days after launch
The eventual result belongs in Outcome fields linked to DEC-2026-041. It does not replace the pre-launch rationale.
How to verify the blueprint
This design was checked against current public HubSpot documentation on 26 September 2026; CDM did not enter a customer portal. In a test portal, record subscription, object limits, tester role and UI labels. Run the four failure cases, export workflow history and reconcile a sample decision from campaign to deal. Recheck after subscription or permission changes.
Related guides
Frequently asked questions
Do I need HubSpot Enterprise for this decision log?
You need Enterprise to implement the clean custom-object version described here. HubSpot documents custom objects as an Enterprise capability, with object and record limits varying by subscription. A smaller portal can use a dedicated ticket or deal pipeline, but it must avoid mixing decisions with service tickets or revenue stages.
The fallback is acceptable for a pilot; once reporting, permissions or associations become confusing, move to a purpose-built object or an external decision register linked by stable IDs. Price the migration effort before the pilot becomes permanent infrastructure.
Why not store the rationale in a campaign note?
A note is readable context, not a governed object. It lacks consistent required fields, lifecycle stages, review dates and dependable joins to analysis. Notes also invite multiple, conflicting versions of “the decision.” Keep discussion links as evidence, but capture the final choice and rationale in structured properties.
The exception is a genuinely trivial, reversible choice with no measurement or compliance consequence; do not burden the CRM with low-value records merely to maximize documentation. Define that materiality boundary in the team’s operating guide.
Can a HubSpot workflow approve decisions automatically?
It can technically change properties, but it should not make the substantive judgment. Use automation to validate completeness, route the record and implement a human decision already expressed in an approval field. This preserves accountable authorship and makes exceptions visible.
A narrow exception exists for deterministic policy, such as auto-closing an expired Draft after 90 days; the rule is administrative, not an evaluation of marketing merit. Always test workflow permissions, re-enrolment and integration-created records separately. Log automated transitions so investigators can distinguish system and human actions.
How should decisions connect to revenue?
Associate the decision with the deals and companies it actually governs, preserve the campaign reference, and define the outcome window before launch. Report decision-to-outcome relationships as evidence for learning, not automatic causal attribution. Revenue may be influenced by sales action, product availability and other campaigns.
The caveat is that a clean controlled experiment can support stronger inference; record its assignment rule and analysis plan in the decision so the CRM result is interpreted under the right method. Reconcile the selected revenue definition with finance before publication.
Who should be allowed to edit an approved record?
Limit approved-decision edits to the owner and designated approver, while giving operators read access and separate execution fields. If the decision changes materially, create a superseding record rather than rewriting the original rationale. HubSpot permissions operate at several levels and limited asset access can override broader rights, so test using representative accounts.
Administrators will retain elevated capabilities; for high-stakes retention, export or mirror signed decisions to a controlled archive with an agreed retention policy. Review privileged access whenever roles or teams change.
What should a failure test prove before launch?
It should prove that incomplete, unauthorized, unassociated and superseded records fail visibly. Create records through every path the production system will use—manual UI, import, integration and workflow—and confirm each lands in the correct view. Test a departed owner and an overdue review too. Passing a happy-path screenshot is insufficient.
The caveat is that sandbox behavior may differ from production entitlements or connected apps, so repeat a small, reversible production smoke test before relying on the log. Save expected and actual results with the tester’s identity.
Next decision: Build a modern content supply chain without creating commodity content
Related reading: Design the contemporary marketing operating system · Connect creator campaigns to CRM and retention · Build a creator dashboard executives will trust
Sources and research notes
- HubSpot, Create custom objects.
- HubSpot, Set up fields shown when manually creating records.
- HubSpot, User permissions guide and Manage user permissions.
- HubSpot, Manually enroll objects in workflows.
Research checked 26 September 2026. Public documentation was verified, but no CDM access to a customer HubSpot portal or test records was available; plan limits and interface behavior require portal-level confirmation. The worked record and screenshot list are illustrative, and revenue relationships should not be presented as causal proof without an appropriate design.
This article is editorial guidance. Apply the principles in proportion to your market, evidence, and responsibilities.
