Introduction
Integrating ValueFirst as your SMS Service Provider (SSP) in WebEngage enables you to send SMS campaigns directly from the WebEngage platform. Follow these steps to set up the integration:
Pre-requisites
- ValueFirst Account: Ensure you have an active ValueFirst account. If you don't have one, request an HTTP account for SMS. Once you receive your login details, proceed with the integration.
- IP Whitelisting: Confirm that your IP address is whitelisted by ValueFirst to allow API requests.
- Principal Entity ID (PE ID): For sending messages to users in India, obtain a Principal Entity ID by registering on a Distributed Ledger Technology (DLT) portal as per TRAI regulations.
Configuration
Integration Steps:
Select SSP:
- In your WebEngage dashboard, navigate to Data Platform > Integrations > SMS Setup (Configure) > SMS.
- From the list of available SSPs, select ValueFirst.
- To create an RCS campaign using a ValueFirst sender in MoEngage, you must have pre-approved templates with ValueFirst. These templates can be created through the ValueFirst platform under the Approved Templates section.
- You can create the same template in MoEngage. For more information, refer to Add Templates
Name Your Configuration:
- Assign a user-friendly name to this configuration for easy identification during campaign creation.
- For example: "ValueFirst - Promotional Campaigns" or "ValueFirst - Transactional Messages".
Add Username & Password:
- Enter the username and password provided by ValueFirst for your HTTP account.
- These credentials authenticate API requests from WebEngage to ValueFirst.
Add Principal Entity ID:
- If you're sending messages to Indian users, input your PE ID obtained from the DLT registration.
- This ensures compliance with TRAI regulations for SMS marketing in India.
Add SSP:
- After entering the required details, click Add SSP to complete the integration.
- This ensures compliance with TRAI regulations for SMS marketing in India.
- platform under the Approved Templates section.
- This step ensures that identical messages are not blocked, allowing for consistent campaign delivery.
- Create a test SMS campaign in WebEngage and send it to a group of internal users to verify the integration.
Disable Duplicate Message Checking:
Testing the Integration:
Monitor the delivery and receipt of these test messages to ensure everything is functioning correctly.