Engage

Last updated:

|Edit this page

Connect PostHog to Engage, a marketing automation platform, and sends data to Engage for use in segmentation, targeting and automation.

Specifically, it only exports your Custom and $identify events to Engage.

Extra event properties and metadata are also processed and sent to Engage.

posthog.identify(
'[user unique id]', // distinct_id, required
{ userProperty: 'value1' }, // $set, optional
{ anotherUserProperty: 'value2' } // $set_once, optional
);

The example above, using the PostHog browser JS SDK, appends extra properties to the identify event. These extra properties are also sent to Engage.

Requirements

This requires either PostHog Cloud with the data pipeline add-on, or a self-hosted PostHog instance running version 1.30.0 or later.

Not running 1.30.0? Find out how to update your self-hosted PostHog deployment!

You'll also need access to a Engage account, obviously.

Installation

To install this destination, you will need your Engage secret key and public key to send data to PostHog. These are available on the 'Settings' page of your Engage dashboard, under the 'Account' > 'API' Keys section.

Once you have made a note of your keys, log in to your PostHog instance and follow the steps below.

  1. In PostHog, click the "Data pipeline" tab in the left sidebar.
  2. Search for 'Engage' and select the destination, press Install.
  3. Enter configuration by selecting the blue gear icon.
  4. Enter the API information as requested, select save.

Now, as soon as the destination is enabled, PostHog will start sending your events to Engage in real-time.

Configuration

OptionDescription
public_key
Type: string
Required: True
Get your public key from your Engage dashboard (Settings -> Account)
secret
Type: string
Required: True
Get your secret key from your Engage dashboard (Settings -> Account)

FAQ

Is the source code for this destination available?

PostHog is open-source and so are all the destinations on the platform. The source code is available on GitHub.

Who created this destination?

We'd like to thank PostHog community members Francis Onyishi and Opeyemi Obembe for creating this. Thank you!

Who maintains this destination?

This destination is maintained by Engage.so. If you have issues with the destination not functioning as intended, please let them know!

What if I have feedback on this destination?

We love feature requests and feedback! Please tell Engage.so what you think! to tell them what you think.

What if my question isn't answered above?

We love answering questions. Ask us anything.

Questions?

Was this page useful?

Next article

Event Replicator

The Replicator app copies events from one PostHog instance to another, at the moment they are ingested. No changes are made to the events by this app if it runs in isolation. If this app is deployed in a chain then any changes made to the event data before the Replicator runs will also be copied to the new instance. Otherwise, no changes will be copied. Note : If you want to export previous ingested (old) events, use batch exports . Requirements The Replicator app requires two instances of…

Read next article