Adobe Campaign Classic
Configure Adobe Campaign Classic as an SSP (SMS service provider)
Adobe Campaign Classic is a part of Adobe Experience Cloud Solution presented for cross-channel campaign management for businesses to create consistent customer journeys on all touch points and experience high customer engagement through personalized marketing communications. Using Adobe Campaign Classic, you can design and orchestrate targeted and customized campaigns in multiple channels.
Setting up a campaign with Adobe Campaign Classic through Lemnisk is entirely different from setting up a campaign with other SMS service providers (SSPs) which involves the following steps.
Workflow
This Adobe Campaign Classic configuration with Lemnisk for SMS engagement is documented by assuming that Adobe Campaign Classic sends SMS engagement via the SMS vendor Infobip. The configuration setup may vary if the SMS engagement from Adobe Campaign Classic is set up with any of the other SMS vendors.
Step 1: Configure Adobe Campaign Classic with Lemnisk
Go to > Campaigns > Channels > SMS
Click on the "+" icon.
Select "Adobe Campaign Classic" from the client list.
Provide the following information to configure Adobe Campaign Classic with Lemnisk.
Client: Choose Adobe Campaign Classic from the list of SSPs.
Name: Enter connection name.
Server URL: Enter the server URL of Adobe Campaign Classic.
Username: Enter the username of your Adobe Campaign Classic account
Password: Enter the password of your Adobe Campaign Classic account
Step 2: Map Lemnisk Macros with Adobe Campaign Recipient Schema
To send SMS engagement through Adobe Campaign Classic via Lemnisk, the details of the user like First name, Last name, Age, etc. must be mapped with the recipient's parameters in Adobe Campaign Classic from Lemnisk. Only the parameters that are available in the Lemnisk will be updated in the Adobe Campaign Classic. If any of the parameters gets added/updated in Lemnisk, the same will be updated in the Adobe Campaign Classic while the other parameter remains unchanged.
Map the parameters with Adobe Campaign Classic by following the steps shown below.
Click the "+Add Mapping" Button displayed under Adobe Campaign Parameter Mapping.
Match the Adobe recipient parameters with the macros in Lemnisk.
The recipient information between Lemnisk and Adobe Campaign Classic will always be in sync.
Step 3: Verify Your SMS Configuration ( Optional )
Once the configuration is saved, you can test your SMS configuration by using our Try It Out option.
Click on the TRY IT OUT tab.
In To, enter the mobile number along with the country code to which you wish to send the SMS.
In Select a Template, Add a DLT-approved text message template. The Template Id will be automatically fetched from the Adobe Campaign Classic.
Click Send Text SMS. You can see the API response in the Response section.
Step 4: Set up your campaign with Lemnisk
Once you configure Adobe Campaign Classic with Lemnisk, you can set up your engagement with the following steps.
Go to > Campaign > Segment
Create a new segment or select an existing segment. To create a new segment, Check here.
Select the channel SMS and click + Add Engagement.
General
Engagement Name: Give a unique name for your engagement.
Label: Add a Label to your engagement.
Choose SMS Client: Choose your SMS client as Adobe Campaign Classic.
Add a Goal
Goal Type: Set your goal type from the dropdown with the use cases Page, Track, and None
Configure Template
Select a template: Select an SMS delivery created at Adobe Campaign. You can search for it via the delivery code or label. You can only use the SMS deliveries that are in Target Ready and Being Edited states. You cannot change any delivery configurations from Lemnisk. You can only preview the delivery details from Lemnisk by dragging the pointer to the preview section.
Content Template ID: Content template ID will be automatically fetched from Adobe Campaign Classic.
Template Message: Template message will be reflected based on the configuration from Adobe Campaign Classic.
Step 5: Schedule your engagement delivery
Schedule the engagement based on your use case (later or trigger). Please note that trigger immediate use cases will not be supported with Adobe Campaign.
Points to Note
No more than 50,000 API calls can be made from Adobe Campaign Classic in a single day. This limit may vary according to the plan you subscribe to.
Lemnisk do not support defining workflow variable like TargetData
Do not define any target population while creating a delivery. The targets will be defined by Lemnisk.
Trigger-immediate use cases are not supported. This is because Adobe Campaign Classic receives data from Lemnisk and triggers the communication. Other use cases, like triggering after a particular time or event, can be supported.
Last updated
