How to integrate Unify with Demandbase
To use Demandbase with Unify, enable Unify Intent and install the account-specific website client. Demandbase is part of the provider mix used for visitor identification. The documented route runs through Unify Intent and does not require a separate Demandbase API-key setup.[1]
- Connection
- Via Unify Intent
- Intent & identification
- Tool
- Demandbase
- Unify Intent
- Data flow
- Website activity → Unify Intent
- Account-specific configuration
At a glance
- Enable Unify Intent in settings
- Install the website client once
- Treat Demandbase as part of the documented provider mix
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
The practical starting point is a website-intent process: collect activity, inspect the available identification, and decide what deserves follow-up. Treat the provider mix as supporting infrastructure. The workflow itself needs a clear owner and an account-review rule before any activity becomes a reason to contact someone.
A good fit when
Teams planning a website-intent process through Unify Intent and wanting to understand where Demandbase fits.
Reconsider the plan when
If the requirement is a standalone Demandbase API-key connection or provider-specific routing, the cited Unify documentation does not establish that setup.
Design the handoff
Use this framework to agree on the input, the next action, and who owns the result.
Suggested workflow design, based on the documented capabilities below.
| Stage | Decision to make |
|---|---|
| Collection | Choose the website pages and account-specific client installation to validate. |
| Context | Inspect available identification without assuming every visit can be resolved. |
| Decision | Define which observed activity deserves human review before follow-up. |
| Ownership | Decide who reviews the account and how existing customer relationships change the action. |
Explore the scenarios
Choose the situation that fits your team and work through the proposed plan.
Open a scenario to explore its plan. Checklists track your selections in this page only.
Start collecting website intent
The website has no Unify Intent collection yet and the team wants to inspect visits.
This route starts in Unify Intent. The source does not call for a separate Demandbase API-key setup.
- Enable Unify Intent
- Install the account-specific website client once
- Inspect collection and the identification available in Unify
Check an existing installation
Unify Intent is enabled, but the team is unsure whether the website is sending useful activity.
Audit collection before changing provider assumptions. Demandbase is one part of the documented provider mix.
- Confirm which pages contain the client
- Check whether the client can load and send requests
- Inspect the account activity without assuming every visit can be identified
Illustrative workflow, not a preconfigured automation. Complete these checks in your own account.
Define success before launch
Inspect the data and the intended outcome separately. Connection status is only the first check.
Expected, not tested
Collected website visits can be processed for identification using Demandbase and the other providers available through Unify Intent.
Validate the website client and the resulting Unify activity. The source does not establish a provider-by-provider identification result for each visit.
Documentation-based reference. This workflow has not been tested end to end. Use a record or event you control before enabling live activity.
Questions answered
Common decisions when connecting Unify and Demandbase.
How does Unify integrate with Demandbase?
Unify Intent uses Demandbase and other data sources to identify website visitors. Enable Unify Intent and install the website client to collect the visits that can be identified.[1]
Do I enter a Demandbase API key in Unify?
The documented Demandbase setup uses Unify Intent activation. It does not instruct you to enter a separate Demandbase API key.[1]
Is installing the website tag enough?
The guide calls for both enabling Unify Intent and setting up the client on the website. Check both parts when validating the connection.[1]
Does Unify use only Demandbase for identification?
No. The documentation describes Demandbase together with other data sources. It does not describe a Demandbase-only identification mode.[1]
Does this setup guarantee identification of every visit?
No identification-coverage guarantee is stated in the guide. Assess the activity available in your account after confirming that collection works.[1]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- The documentation does not specify a standalone Demandbase account connection
- No identification-rate or timing guarantee is provided
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + Demandbase workflow.
Demandbase + other providers
| Decision | What to know |
|---|---|
| Activation | Enable Unify Intent[1] |
| Provider model | Demandbase is used together with other data sources[1] |
| Website requirement | The Unify Intent client must collect visits[1] |
| Separate Demandbase key | Not part of the setup described in this article[1] |
This page documents activation through Unify Intent. The source does not describe a separate Demandbase credential flow or a custom request body to configure.
Technical setup reference
References and requirements for the Demandbase connection.
Connection requirements and setup checklist
Before connecting
- Access to Unify Intent settings
- Permission to install the Unify Intent client on the website
Troubleshooting
Start with the stage where the expected data or action stops appearing.
Unify Intent is enabled but no visits appear
Check that the website client is installed on the pages being visited and is able to load and send requests.[2]
You are looking for a Demandbase API-key field
Follow the documented Unify Intent activation path. The cited Demandbase guide does not specify a separate API-key connection.[1]
Sources & review
Official documentation reviewed on September 15, 2026.
Technical claims link to primary documentation from Unify and the destination tool. Scenarios, field choices, and recovery plans are editorial implementation examples. Documentation review is separate from execution testing.
Documentation reviewed; end-to-end execution not tested. No named technical reviewer has signed off on these articles yet.
Content updated: . Report a correction to Unify with the tool name, source URL, and behavior you observed.
Keep exploring
