B2B INTELLIGENCE PLATFORM · DATA SCHEMA

A defined record for every buyer relationship.

InMarketIQ connects company profiles, resolved people, professional roles, research events, customer outcomes, buying-group relationships, and activation instructions. The public schema shows how those record types connect without presenting them as physical database tables.

Connected record modelREPRESENTATIVE
CompanyBusiness identity and classification
PersonPersistent individual identity
Professional rolePerson-to-company relationship
Research eventPerson-level buyer activity
Customer outcomeRevenue result and CRM context
Buying groupPeople and buying relationships
Activation instructionPriority, reason, and destination
Connectedrecord types and relationships
Persistentperson and company keys
Field-leveldefinitions and lineage
Usableprofiles for activation
CONNECTED RECORD TYPES

A logical model for how InMarketIQ uses the information.

These are public-facing record groups, not a claim about the number or names of physical database tables. They explain how company, person, research, customer, buying-group, and activation information remains connected across the platform.

01

Company

Business identity, domains, website-derived classification, firmographics, locations, and connected relationships.

02

Person

Persistent individual identity, names, professional profile, location, history, and contact points.

03

Professional Role

The relationship between a person and company, including original title, normalized role, department, seniority, and dates.

04

Research Event

The resolved person, research subject, event timing, professional relationship, and connected market context.

05

Customer Outcome

Account, contact, opportunity, stage, outcome, value, reason, and customer-quality evidence supplied by the business.

06

Buying Group

The people connected to a potential purchase and the role each may play in the buying process.

07

Activation Instruction

The priority, supporting reason, selected people, action, destination, and suppression state used by the workflow.

REPRESENTATIVE FIELD MODEL

Readable to executives. Specific enough for technical evaluation.

Public field
Definition
Class
Record type
Persistent Person ID
Stable identifier connecting records belonging to one individual
Identity
Person
Persistent Company ID
Stable identifier connecting company records, domains, people, and events
Identity
Company
Normalized Professional Role
Standardized title, department, and seniority while preserving the original title
Normalized
Role
Business Classification
Website-derived commercial category based on products, services, business model, customers served, and market
Derived
Company
Research Subject
Keyword, topic, or category connected to a person-level research event
Observed
Research
Customer Outcome
Won, lost, stalled, disqualified, or customer-quality result connected to the account and people
Customer
Outcome
Buyer Role
The person’s potential relationship to the buying process
Derived
Buying group
Priority Reason
Explanation supporting the buyer’s priority and activation destination
Output
Activation
Field names shown here are normalized public labels. Implementation-level names, physical tables, and supplier conventions are not published.
RECORD RELATIONSHIPS

Persistent identifiers preserve context across the system.

Person identifierConnects identity, contact points, roles, and research
Company identifierConnects domains, firmographics, people, CRM, and outcomes
Relationship layerPerson ↔ Role ↔ Company ↔ Evidence
Customer outcomeConnects account and opportunity results
Activation recordConnects priority, reason, destination, and status
DATA CLASSIFICATION

The schema distinguishes fact, transformation, and output.

Observed

Values and events received or observed directly, including names, titles, domains, timestamps, and research subjects.

Normalized

Standardized values used consistently across records, including companies, titles, departments, and domains.

Derived

Attributes produced through classification and connected context, including business categories and buying roles.

Output

Instructions created for execution, including priority, reason, destination, routing, and suppression status.

SEE THE SYSTEM APPLIED

Review the schema behind your buyer market.

See how your company, person, research, and CRM records would connect inside the InMarketIQ operating model.

Book a working session