Introduction
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
library_add_check |
Prerequisites - Ensure you have access to a Seen Campaign. - Ensure MoEngage Connected sources is available for your account |
In the following example, we’ll send users’ data to SEEN for video generation, and receive a unique landing page link and a unique, personalized thumbnail back to MoEngage for distribution.
This example uses a Connector Campaign to send data to SEEN, and Connected Sources to receive the data back to MoEngage.
If you have multiple video campaigns with SEEN, repeat the process to connect Braze with all video campaigns.
Step 1: Create connector campaign on MoEngage
To create a connector campaign on MoEngage,
1. Navigate to Create Campaign >> Connectors >> Custom
2. On step 2 of the campaign, add -
Key | Value |
---|---|
Method | POST |
Webhook URL |
https://api.seen.io/v1/campaigns/<campaign_slug>/receivers/ Get your campaign_slug from SEEN to call the correct endpoint. |
Headers |
Authorization: Token {token} Content-Type: application/json
You will receive your Authentication Token from SEEN. |
Body |
Follow the SEEN API documentation for the exact request body. You can select raw and copy paste the request. |
3. At this point, your campaign should be ready to test and send. You can also test your connector configuration using the Test functionality available on Step 2 of Create Connector Campaign
Rate limit
The SEEN API currently accepts 1,000 calls per hour.
Step 2: Create a connected source on MoEngage
On your SEEN dashboard,
- Create new custom attribute fields for landing_page_url and email_thumbnail_url. These are the two attributes we will be using in this example.
- Create a connected source on MoEngage. Reach out to your CSM or support team to create connected source - provide your config and get a valid endpoint.
- Paste the endpoint on your Seen CallBacks. Follow the Seen documentation for more details.