How to integrate Unify with 6sense
To integrate Unify with an existing 6sense subscription, enter the account API key in Unify’s 6sense settings and confirm server-to-server Reveal API access. Validate website collection before evaluating identification. Unify Intent provides another documented path using 6sense and other providers.[1]
- Connection
- API key
- Intent & identification
- Tool
- 6sense
- Unify
- Data flow
- Website activity → Unify with 6sense
- Account-specific configuration
At a glance
- Connect the API key for your existing 6sense subscription
- Confirm server-to-server reveal access
- Check the website tag separately from the provider connection
When this workflow makes sense
Start with the decision your team needs to make, then choose the connection that supports it.
Identifying a company and deciding to contact it are separate steps. Start by understanding what activity reaches Unify and what account context is available. The team can then define a relevant review rule, including how to handle visits that cannot be identified. An existing 6sense subscription is one documented path; Unify Intent is another.
A good fit when
Teams evaluating how an existing 6sense account or Unify Intent should support website-based prospecting.
Reconsider the plan when
If the goal assumes that every visitor will be identified, revise the expectation. The cited setup documentation does not establish a coverage guarantee.
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 | Confirm that the intended website activity reaches Unify before evaluating identification. |
| Account context | Inspect the company context that is actually available for a visit. |
| Qualification | Agree which observed activity warrants review and how existing customer context changes the next step. |
| Review | Evaluate the resulting accounts before enabling a follow-up rule. |
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.
Use an existing 6sense subscription
Your team already has 6sense and wants to use that account in Unify’s website identification.
Validate API entitlement and website collection independently. A saved key is only one part of the setup.
- Confirm server-to-server company reveal access with the provider
- Connect the account key in Unify
- Check website collection and then inspect identification
Evaluate the Unify Intent route
The immediate need is website identification, rather than using a particular provider subscription.
The documentation offers Unify Intent as another path using 6sense and other providers. Decide which setup your team actually needs.
- Review the Unify Intent option alongside the existing-subscription path
- Choose one collection setup for the website
- Validate the available activity before building a follow-up rule
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
Unify can use the connected 6sense account when identifying collected website visits.
Check collection and provider access as two separate stages. A saved API key does not show that the website tag is collecting visits or that a given visitor can be identified.
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 6sense.
Do I need a 6sense subscription to use this connection?
Yes, the API-key connection uses an existing 6sense subscription. Unify Intent is a separate documented path that uses 6sense and other providers for visitor identification.[1]
Where do I enter the 6sense API key?
In Unify, open Settings → Integrations → 6sense and enter the API key for your existing subscription.[1]
Why does my 6sense key save but no visitors appear?
The documentation identifies disabled server-to-server API access as one possible cause. Check that the website tag is installed, then ask 6sense support or your CSM to verify company reveal API access.[1]
Is 6sense connected through a Unify Play webhook?
No. The documented connection is configured with an API key in integration settings and uses website-tag collection. A Play webhook is a different outbound automation path.[1]
Can I use Unify Intent instead of connecting my own 6sense account?
Unify documents Unify Intent as an out-of-the-box visitor-identification option powered by 6sense and other providers. The separate API-key path is for an existing 6sense subscription.[1]
Limits & decisions
Check these boundaries before designing a live workflow around the connection.
- The guide does not specify identification coverage or a delivery-time guarantee
- API access may need to be enabled by 6sense
What the connection supports
Understand the connection, the data involved, and the behavior that matters for a Unify + 6sense workflow.
6sense + website tag
| Decision | What to know |
|---|---|
| Connection credential | 6sense API key[1] |
| API access | Server-to-server company reveal access must be enabled[1] |
| Collection requirement | Unify website tag[2] |
| Alternative path | Unify Intent uses 6sense and other providers without connecting your own subscription[1] |
The documented setup uses the provider key and website collection. It does not require a custom Play webhook or a user-authored JSON handoff.
Technical setup reference
References and requirements for the 6sense connection.
Connection requirements and setup checklist
Before connecting
- An existing 6sense subscription and an API key enabled for the required server-to-server access
- Access to Settings → Integrations → 6sense in Unify
- The Unify website tag installed on your site
Check API access
Confirm that your 6sense token can access its company reveal API in server-to-server mode. Some subscriptions do not have that access enabled by default.[1]
Connect the account
Open Settings → Integrations → 6sense and enter the API key for your existing subscription.[1]
Install or check the website tag
Copy the tag from Unify settings and install it once on the website. Avoid adding a second instance if it is already present.[2]
Troubleshooting
Start with the stage where the expected data or action stops appearing.
No visitors are identified after connection
Check the tag installation, then ask your 6sense CSM or support team whether the API token is enabled for server-to-server company reveal access.[1][2]
The site blocks the tag
If a Content Security Policy is present, review the script-src and connect-src requirements in the Unify website-tag guide.[2]
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
