6Sense Enrichment Use Case

  • Published on Aug 24, 2026
  • 2 minute(s) read
Prev Next

RevSure can ingest 6sense-enriched fields when you license the appropriate 6sense packages. Equally, if you already enrich the same attributes from another provider, we can use that source instead to avoid redundant cost.

Use Case

IP Address → Account (Company Identification)

  • Use case: Enrich anonymous traffic by resolving IP to company and firmographics

  • 6sense access required: Platform or Sales Intelligence package (per 6sense offering)

  • Input we expect: IP Address captured via first‑party pixel or event stream

  • What we ingest: Company identification + firmographic attributes provided by 6sense

  • When to skip: If you already resolve IPs through another vendor with equivalent coverage

Account Scoring & Firmographics

  • Use case: Receive 6sense account scoring and firmographics for prioritization

  • 6sense access required: Platform subscription with the Advanced package

  • Input we expect: Account or email‑based identifiers (depending on the endpoint you use)

  • What we ingest: Account score(s), buying stage, segment labels, and firmographic fields

  • When to skip: If a separate system already generates the scores you standardize on

Lead / Person Enrichment

  • Use case: Append person-level attributes for leads/contacts

  • 6sense access required: Add‑on to any Platform or Sales Intelligence package

  • Input we expect: Email as the primary key

  • What we ingest: People enrichment results (title, seniority, company linkage, etc.)

  • When to skip: If existing enrichment (e.g., another vendor) already covers your needs

Mapping & Connections

Inputs we send to 6sense (by use case)

  • Company Identification (IP → Company): ip_address

  • Lead/Account Scoring & Firmographics: email (for person endpoints) or account domain for account endpoints

  • People Enrichment: email

A separate connection is created for each enrichment use case to keep scopes clear and troubleshooting simple.

Outputs we expect back (examples)

  • Company Identification: company_name, domain, firmographics (industry, employee_band, revenue_band), confidence

  • Account Scoring: account_score, buying_stage, segment, last_scored_at

  • People Enrichment: title, seniority, department, phone flags, location

We will confirm exact fields during onboarding and map them to RevSure’s objects (Account, Person/Lead/Contact, Engagement), preserving your system of record IDs.

End‑to‑End Data Flow

  • Export reports from 6sense UI (campaigns/engagements/segments)

  • Upload CSVs via the RevSure connector (drag‑and‑drop or S3 handoff)

  • Validate & map: RevSure runs header and type checks; we finalize field mapping

  • Load to RevSure’s normalized schema

  • Augment with optional 6sense enrichment feeds (if licensed)

  • Activate: Data available for ABM dashboards, attribution, and targeting workflows

Setup Checklist

  1. Confirm 6sense package(s) and intended enrichment scope

  2. Provide read access to the 6sense UI for export

  3. Align on report views and export cadence (daily/weekly)

  4. Finalize CSV templates and naming conventions

  5. Configure RevSure CSV connector and destination workspace

  6. Create enrichment connections (per use case) and set keys (IP or email)

  7. Field mapping walkthrough; QA on a sample file

  8. Go‑live; establish monitoring & error notifications

Maintenance & Monitoring

  • Cadence: Maintain the agreed export schedule; missed runs produce stale trends

  • Observability: You can review in the Data Hub sources

Security & Privacy

  • Data is stored and processed within RevSure’s standard security controls

  • PII handling follows least‑privilege and data‑minimization practices

FAQs

Is there an added cost to connect 6sense?
No. RevSure does not charge extra for integrations—now or in the future.

Can we automate the exports?
Currently, it is a manual export done on a weekly cadence.

What if we already enrich with another vendor?
That’s fine. We will pull enrichment from CRM (SFDC) to avoid duplicate spend.

Do we need separate connections for each enrichment type?
Yes. Separate connections keep scopes clear and make troubleshooting and auditing easier.

Reference (6sense API documentation)

For customers who do have enrichment API access, here are the public docs your technical team may reference:

Note: The APIs above are for enrichment. Campaign/engagement report exports are still performed via the 6sense UI at this time.