Introduction

Seen is a personalization video platform that allows companies to create and build videos around their customers to deliver a more engaging experience. With Seen, you can design a video around your data, personalize it at scale in the cloud, then distribute it where it works best.

This integration is built and maintained by Seen. For assistance, reach out to your Customer Success Manager at Seen.

Use Cases

Seen offers automated video personalization across the entire customer journey. Common uses include onboarding, loyalty, sign-ups and conversion, and win-back and anti-churn.

Integration

Prerequisites

A Project must be created and published in the Seen Platform before you set up the integration.
Ensure MoEngage Connectors and Flows are available for your account.

In the following example, you send user data to Seen for video generation, and receive a unique video player link and a personalized email thumbnail back in MoEngage for distribution. This example uses a Connector step in a MoEngage Flow to send data to Seen, and a Seen webhook to post the result back to MoEngage as a custom event — ready to use across email, SMS, push, and more. If you have multiple video campaigns with Seen, repeat the process to connect MoEngage with each one.

Step 1: Send Data to Seen

Navigate to Engage → Flows and create a new blank Flow in MoEngage.
Give your Flow a name, add a Connector step to the canvas, and configure it as follows:
Field Value
Webhook URL https://next.seen.io/v1/projects/{project_id}/data — find your Project endpoint in the Run tab of your Seen Project.
HTTP Method POST
Body type JSON

Field	Value
Webhook URL	`https://next.seen.io/v1/projects/{project_id}/data` — find your Project endpoint in the Run tab of your Seen Project.
HTTP Method	POST
Body type	JSON

Use the payload below as a starting point. Adjust the fields to match the personalizations in your Seen Project.

{
  "user_id": "{{UserAttribute['ID']|default('MOE_NOT_SEND')}}",
  "first_name": "{{UserAttribute['First Name']|default('MOE_NOT_SEND')}}"
}

Add the following request headers:
Header Value
Authorization Bearer {token}
Content-Type application/json
You can create an API token in your Seen Platform account under Settings → API → OAuth2.
Test the Connector with a specific user using the Test section at the bottom of the Connector step.
If everything works as intended, activate the Flow.

Header	Value
Authorization	`Bearer {token}`
Content-Type	`application/json`
You can create an API token in your Seen Platform account under Settings → API → OAuth2.

Step 2: Set Up Your Webhook in Seen Platform

Navigate to your Project in the Seen Platform.
Open the Run tab and click Add Webhook.
Configure your webhook to post the result back to MoEngage (see Step 3 for the full configuration).

Step 3: Receive Data Back from Seen

First, create an authorization configuration in MoEngage so Seen can authenticate its callback.

In MoEngage, navigate to Settings → Advanced Settings → Authorization Configuration.

Click + Add Auth Config and fill in the following fields:

Field	Value
Name	Seen API
Token type	JWT
API URL	`https://next.seen.io/oauth2/token`
Method	POST
Body type	FORM
grant_type	`client_credentials`
client_id	`<YOUR_SEEN_CLIENT_ID>`
client_secret	`<YOUR_SEEN_CLIENT_SECRET>`
Find your Client ID and Client Secret under Settings → API → OAuth2 in your Seen workspace.

Click Send test & continue.
In the Access token field, select access_token.
Click Decode Access Token. In the expiry field that appears, enter access_token.exp (Unix Epoch).
Set Preferred prefix to Bearer.
Click Save.

Next, configure the webhook in the Seen Platform webhook editor to POST back to MoEngage:

Field	Value
URL	`https://api-01.moengage.com/v1/event/{YOUR_MOENGAGE_WORKSPACE_ID}`
Authentication	Basic Auth (Username = MoEngage Workspace ID, Password = MoEngage Data API Key)
Content-Type	`application/json`

Replace 01 in the URL with your workspace’s data center number.

Use the payload below as a starting point for the Seen webhook body. Replace Player link and Email thumbnail link with the dynamic output references available in the Seen webhook editor:

{
  "type": "event",
  "customer_id": "user_id",
  "actions": [
    {
      "action": "seen_video_generated",
      "attributes": {
        "seen_campaign": "onboarding",
        "seen_player_link": "Player link",
        "seen_email_thumbnail_link": "Email thumbnail link"
      }
    }
  ]
}

Click Create to save the webhook.

Step 4: Verify the Integration

In MoEngage, navigate to Segment → Search Users and open your test user’s Event Activity.
Confirm that a seen_video_generated event appears with the following attributes populated:
Attribute Description
seen_player_link A link to the user’s personalized Seen video.
seen_email_thumbnail_link A personalized video thumbnail for use in email.

Attribute	Description
`seen_player_link`	A link to the user’s personalized Seen video.
`seen_email_thumbnail_link`	A personalized video thumbnail for use in email.

Once confirmed, you can reference these attributes in any MoEngage campaign:

{{EventAttribute['seen_player_link']|default('MOE_NOT_SEND')}}
{{EventAttribute['seen_email_thumbnail_link']|default('MOE_NOT_SEND')}}

​Introduction

​Use Cases

​Integration

​Step 1: Send Data to Seen

​Step 2: Set Up Your Webhook in Seen Platform

​Step 3: Receive Data Back from Seen

​Step 4: Verify the Integration

Introduction

Use Cases

Integration

Step 1: Send Data to Seen

Step 2: Set Up Your Webhook in Seen Platform

Step 3: Receive Data Back from Seen

Step 4: Verify the Integration