SMARTe supports configuration-driven enrichment to accommodate different client data models and enrichment requirements. Custom enrichment allows enrichment behavior to be tailored using predefined configurations rather than bespoke integrations.

Custom enrichment uses the same enrichment engine, endpoints, and governance model as standard APIs.

Custom Input Configuration

Custom input configuration defines which identifiers are accepted for enrichment. It can be configured to provide:

Email only
LinkedIn URL only
A specific combination of identifiers
Custom or proprietary identifier fields

This ensures enrichment requests align with available data and validation rules.

Custom Output Configuration

Custom output configuration defines which fields are returned in the enrichment response. Configured outputs allow clients to:

Receive only required data
Reduce response payload size
Comply with internal data usage policies

Output configuration is applied consistently across all enrichment requests.

Output Field Mapping

Enriched fields can be mapped to:

Client-specific field names
Internal schemas
CRM or downstream system conventions

This allows enriched data to be consumed directly without additional transformation logic.

Configuration Management

All custom input, output, and mapping configurations are stored in a centralized configuration repository.

Configurations are applied automatically at request time
Configurations are consistent across environments
Reach out at support@smarte.pro to modify configurations

End users can consume enrichment using existing configurations but cannot change them directly.

📘
When to Use Custom Enrichment

Standard input identifiers do not match your data model

You require strict control over returned fields

You need schema-aligned outputs for downstream systems

You want to onboard or update enrichment behavior without code changes