Documentation / Product / Integrations / Iterable

Iterable: Configure Webhooks

Lytics highly recommends setting up Iterable system webhooks for real time event capture of your events. This will allow Lytics to get real-time activity data such as clicks, opens, bounces etc. on your Iterable campaigns.

Lytics requires that webhooks are enabled to use Iterable Experiences as part of Lytics Orchestrate because it allows for the collection of reporting metrics for your Iterable Experiences.

Note: If you are running a continous import from Iterable and using webhooks, some user activity data may be captured twice.

To set up system webhooks to go to Lytics, you will need to have a Lytics API token ready, you can read how to generate a new API token if you do not already have one. Then follow these steps:

  1. Log into your Iterable account.
  2. Navigate to Integrations > System Webhooks.

    iterable integration webhook create

  4. In the Endpoint URL box, enter: where YOUR_API_TOKEN is your Lytics API token which can be generated in your account settings.

    iterable integration webhook create2

  5. Set the Auth Type to NoAuth by clicking the NoAuth radio button.

  7. Then scroll to the far right edge and click the EDIT button.

    iterable integration webhook edit

  8. Click the Enabled checkbox.

  9. Select the events you'd like to send data to Lytics by clicking on their respective checkboxs. The available options for Webhook events are:

    • Triggered Send
    • Blast Send
    • Push Send
    • SMS Send
    • Email Open
    • Push Open
    • Email Click
    • Hosted Unsubscribe Click
    • Email Complaint (i.e. Spam)
    • Push Uninstall
    • SMS Received
    • Email Bounce
    • Push Bounce
    • SMS Bounce
    • Email Subscribe
    • Email UnSubscribe
  10. Click SAVE.

    iterable integration webhook save

After saving the changes to the webhook, the selected events will be sent to your Lytics account in real-time. Events collected via the webhook are processed and mapped in the same way that activity data via the import workflow is mapped, reference the fields table for a full list of user fields.