Linking Cyberimpact as a source

Let AI connect your sources for you

Skip the manual setup — run this in your project and the wizard auto-detects your databases and APIs and connects them to PostHog.

Learn more
PostHog Wizard hedgehog

Contents

The Cyberimpact connector syncs your Cyberimpact email marketing data – members, groups, unsubscribes, bounces, mailings and their statistics, opens, clicks, and templates – into PostHog.

Adding a data source

  1. Go to the sources tab of the data pipeline section in PostHog.
  2. Click + New source and then click Link next to Cyberimpact.
  3. Next, you need an API token from Cyberimpact. An account administrator creates the token in Cyberimpact under Settings > API tokens. Copy the token value.
  4. Back in PostHog, paste the token in the API token field and click Next.
  5. Select the tables you want to sync, set the sync method and frequency, then click Import.

Once the syncs are complete, you can start using Cyberimpact data in PostHog.

Available tables

TableDescriptionSync method
membersSubscribed members (contacts) of the account, both in groups and in no groupIncremental
unsubscribed_membersMembers who unsubscribed from the account's mailingsFull refresh
bounced_membersMembers for whom the last mailing sent to them returned a hard bounceFull refresh
groupsGroups (mailing lists) of the accountFull refresh
group_membersMembers of each group, one row per group and memberFull refresh
custom_fieldsCustom member fields defined in the accountFull refresh
sent_mailingsSent mailings, without archived mailingsFull refresh
scheduled_mailingsMailings scheduled to be sentFull refresh
archived_mailingsArchived mailingsFull refresh
mailing_statsDetails and delivery, open and click statistics of each sent mailingFull refresh
mailing_opensRecipients who opened each sent mailing, one row per mailing and recipientFull refresh
mailing_clicksRecipients who clicked a link in each sent mailing, one row per mailing and recipientFull refresh
templatesEmail templates of the accountFull refresh

Incremental tables sync only new or updated records on each run. Full refresh tables reload all data on each sync.

Sync limitations

Unsubscribed and bounced member tables only filter on their event date (unsubscribe or bounce), but a profile edit can change the row afterward, so they must use full refresh. The child tables (group_members, mailing_stats, mailing_opens, mailing_clicks) make one request per parent record, so they also sync as full refresh.

Configuration

OptionTypeRequired
API tokenpasswordYes

Supported tables

TableDescriptionSync methodIncremental fieldPrimary key
members

Subscribed members (contacts) of the account, both in groups and in no group.

Incremental, Full refreshupdatedOn—
unsubscribed_members

Members who unsubscribed from the account's mailings.

Full refresh——
bounced_members

Members for whom the last mailing sent to them returned a hard bounce.

Full refresh——
groups

Groups (mailing lists) of the account.

Full refresh——
group_members

Members of each group, one row per group and member.

Full refresh——
custom_fields

Custom member fields defined in the account.

Full refresh——
sent_mailings

Sent mailings, without archived mailings.

Full refresh——
scheduled_mailings

Mailings scheduled to be sent.

Full refresh——
archived_mailings

Archived mailings.

Full refresh——
mailing_stats

Details and delivery, open and click statistics of each sent mailing.

Full refresh——
mailing_opens

Recipients who opened each sent mailing, one row per mailing and recipient.

Full refresh——
mailing_clicks

Recipients who clicked a link in each sent mailing, one row per mailing and recipient.

Full refresh——
templates

Email templates of the account.

Full refresh——

Still have questions?

Was this page useful?