Question 1

What HeyReach data can Polytomic read?

Accepted Answer

Campaigns including their configuration, status, and progress stats, campaign leads with profile and lifecycle fields, lead lists and their members, conversations with correspondent and LinkedIn account details, and individual messages flattened out of each conversation. Two things are not separate objects: there is no standalone LinkedIn accounts table, since account information is embedded in conversations and campaign account IDs, and there is no separate stats object, since the available metrics come through as progress stats on campaigns.

Question 2

Can I push leads into HeyReach from my data warehouse?

Accepted Answer

Yes, and this is the reverse ETL pattern most teams want here. You can write into campaign leads with create or update, and into lead list members with create, update, or remove. Polytomic can also create a new empty lead list and then load it, so a segment defined in your data warehouse becomes a HeyReach list without a manual export. Leads are matched on exact LinkedIn profile URL, writes are batched a hundred leads at a time, and both campaign and list writes need a first and last name mapped alongside the profile URL.

Question 3

How do incremental reads work?

Accepted Answer

Only campaign leads and list leads read incrementally, and both filter on creation time rather than last modified time. That means new leads flow through efficiently, but a status change on a lead created weeks ago may not be captured by an incremental run. Campaigns, lists, conversations, and messages are full reads on every execution. If lead status transitions drive your reporting, schedule a periodic full resync alongside the incremental sync so late changes are reconciled.

Question 4

Can I remove leads from a list automatically?

Accepted Answer

From lead lists, yes. The list target supports a remove mode, so a model that identifies people who should no longer be contacted, existing customers, open opportunities, or anyone who has asked to be left alone, can pull them out of the list on a schedule. Campaign leads do not support removal, so suppression works at the list level. Company list writes are intentionally disabled in the connector, so this applies to lead lists rather than company lists.

Question 5

Why connect HeyReach to a data warehouse at all?

Accepted Answer

Because outbound performance is only meaningful next to what happened afterward. HeyReach knows who replied; your CRM knows which of those replies became pipeline and which closed. Neither answers the question alone. Running ETL from HeyReach into your data warehouse lets you attribute revenue back to sequences and messaging, and reverse ETL closes the loop by pushing better targeting back in, so lists are built from customers you actually want rather than from a static export someone made last quarter.

HeyReach

Perfect pairings

Read and write HeyReach

Conversations and messages

Build lists from your warehouse

Example workflows

What you can sync

From HeyReach

To HeyReach

How it works

How to set up

Frequently asked questions

Why teams choose Polytomic

No engineering required

Flexible data modeling

Handles scale automatically

Start syncing your data with HeyReach in minutes

More integrations beyond HeyReach