Post Contents
To import 6sense target account lists into Integrate, connect 6sense in Integrate with your API key, select published 6sense segments, choose how they should appear as reusable lists, set a sync cadence, and apply those synced lists to campaigns or sources. According to Integrate’s help article, that is the supported path, not a manual CSV routine.
Key Takeaways
- Use the native 6sense connector in Integrate.
- Sync published 6sense segments into reusable domain, name, or target lists.
- Apply those lists to campaigns or sources, especially when you need target-account validation during lead intake.
- Treat this as an operational workflow, not a one-time import task.
What does the 6sense connector do?
According to the Integrate 6sense connector help article, the connector syncs published 6sense segments into reusable lists inside Integrate. The 6sense integration page describes the same workflow as a way to validate inbound leads against target-account lists during ingestion.
In practice, the division of labor is clean: let 6sense define the accounts, then let Integrate keep those segments usable inside the systems where lead governance actually happens.
What do you need before setup?
You need a live 6sense account, a valid 6sense API key, access to Integrate’s connector library, and at least one published segment in 6sense. Unpublished segments do not appear through the connector, so it helps to confirm segment status before you start.
How do you connect 6sense in Integrate?
Start in Integrate, open Integrations, then Connector Library, and add the 6sense connection with your API key. If the connector is not visible in your account, the help article says to contact Integrate support or your representative.
Once the connection is saved, you can choose the 6sense segments you want to sync and decide whether they should appear as domain, name, or target lists inside Integrate.
How do you sync published segments?
Only published 6sense segments are available through the API. According to Integrate’s help article, you can run a manual sync or set an automatic schedule after the connector is configured.
Choose the cadence your campaign actually needs, and confirm the available sync options directly in the connector settings in Integrate rather than relying on older documentation.
How do you use synced 6sense lists in campaigns?
After sync, the list can be assigned inside Integrate to a campaign or source. The public help article explicitly points to content syndication campaigns, and the 6sense integration page frames the same workflow as validating inbound leads against the synced 6sense list during intake.
A simple way to think about the split is this:
| System | Job |
|---|---|
| 6sense | Build and publish the target segment |
| Integrate | Sync the segment into reusable lists and govern inbound lead acceptance against it |
What should you check if something is not working?
The segment does not appear
Make sure the segment is published in 6sense. Unpublished or newly created segments may not be ready for sync yet.
The connector is missing
If the 6sense connector is not visible in your Integrate account, Integrate’s help documentation says to contact support or your account representative.
You are unsure how often to sync
Use the live connector settings as the source of truth. Example cadences vary across older documentation, so the product itself is the safest reference point.
To see how target-account governance fits into your wider lead management workflow, reach out for a demo.
Frequently Asked Questions
Can I import a 6sense segment with a CSV instead?
You could build a manual workaround, but the supported path in Integrate is the 6sense connector. That is the workflow documented in Integrate’s help article.
Can I use more than one 6sense segment?
Yes. Integrate’s help documentation describes selecting the segments you want and syncing them into reusable lists inside Integrate.
What is the real value of this connector?
It keeps target-account definitions closer to the campaigns and lead-governance flows that depend on them, so teams spend less time rebuilding lists by hand.
About The Author
