Your stack

How iCustomer Platform connects to the rest of your stack: connector categories, the connect flow, sync settings, and the recommended setup order.

iConnect is the integrations layer, and the only part of the platform that touches your systems. It works in both directions:

• Activation out: decisions land in your channels and your CRM.

• Governed connection in: your data is read where it lives, never copied to run the platform.

On Enterprise the connection is in place, in your cloud or warehouse, and nothing leaves except governed, approved activations. On SMB it connects to our managed cloud. Every connector is managed in one place: Settings → Integrations.

Connector categories

Category	Direction	Examples
CRM	Bidirectional	Salesforce, HubSpot (CRM sync)
Data warehouse	Inbound + write-back	Snowflake, BigQuery, Databricks, Redshift
Ad platforms	Outbound	LinkedIn, Meta, Google, Reddit
Email and outbound	Outbound	Instantly, Smartlead, Klaviyo
Events	Inbound	Pixel, product events
Enrichment and intent	Inbound	OneSource
Notifications	Outbound	Slack, email

Per-platform overviews live on our site: Connections. Warehouse connections (Snowflake, BigQuery, Databricks, Redshift) are set up with our team.

Enrichment is different from the rest of the table. It is 50+ data vendors behind one connection, one contract, and one credit meter, ours. Their data is resolved to OneSource IDs before it reaches your audiences, and it is never written raw into your CRM or media accounts.

Connecting a tool

1

Add

Go to Settings → Integrations, choose the platform, and select Connect.

2

Authenticate

Most connectors use OAuth: sign in to the platform and authorize access. API-key connectors ask for the key instead.

3

Configure

Set the sync direction, frequency (real-time, hourly, or daily), and field mappings. Filters limit what syncs.

4

Activate

The platform verifies authentication and permissions when you save. Once the check passes, toggle the connector active.

A connector shows one of four states: Connected (active and syncing), Paused (configured, not syncing), Error (usually credentials), or Not configured. Removing a connector stops its syncs but does not delete data that already synced.

When a connection misbehaves

Symptom	Likely cause	Fix
Invalid credentials	Expired OAuth or wrong key	Re-authenticate
Insufficient permissions	Missing scopes	Check the platform's permissions
Rate limited	Too many requests	Reduce sync frequency
Low match rate	Thin email or phone coverage	Improve identifier coverage
Audience not updating	Sync paused or failed	Check sync status in Data health

What you get back

A connected tool returns three things:

• a status you can trust (active, pending, expired, revoked, or error), surfaced here and raised in Pulse on failure,

• its data flowing into identity resolution, sharpening scores and unlocking the KPIs and plays that need it,

• and a destination the loop can act into, within your guardrails.

If a connection is quiet or a sync looks stale, ask iHarness why. That is always the shortest path to the answer.

Outside the app

Connectors can be managed outside the app via API and MCP as well.