Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

titleNew Name: Marketing Cloud Personalization

Interaction Studio (formerly Evergage) is now known as Marketing Cloud Personalization. The new name reflects our mission and vision for innovation in Salesforce Marketing Cloud. We wish we could snap our fingers to update the name everywhere, but you can expect to see the previous name in various places until we replace it.

Server-side campaigns integrate Interaction Studio testing and personalization at the server-to-server level. While Interaction Studio handles the campaign logic, a developer is required to write the code to call the appropriate APIs and provide Interaction Studio with the necessary information about the website visitor.

titleServer-Side Campaigns

Server-Side campaigns that leverage Server-Side templates are only available to Interaction Studio customers using the Campaigns & Templates system. Customers using Interaction Studio Classic will continue to leverage Server-Side Classic campaigns.

titleThis Article Explains

This article provides a business user-level overview of process to create a server-side campaign. Developers can find a detailed, step-by-step, guide on building a server-side campaign from a template on Interaction Studio's developer documentation site.

titleSections in this Article

Table of Contents

How Does It Work?

  • Your server calls the Interaction Studio server-side API and provide information about the visitor (ID, context, action, etc.).
  • With that information, Interaction Studio handles the campaign logic and uses a JSON payload to return recommendations, user attributes, or other campaign data specific to that visitor.
  • Your server handles the JSON, builds the message to show the visitor, and calls the appropriate action tracking APIs to track campaign impressions and clicks.

Create a Server-Side Campaign in Interaction Studio

Process Overview

Building and executing a server-side campaign is typically a close collaboration between a business user and a developer. Here is a breakdown of the responsibilities:

  • Business User:
    • Create the campaign and define the campaign type (rules based or A/B/n)
    • Apply campaign targeting logic at the campaign and experience levels
    • Configure control group allocation
    • Apply server-side templates to the campaign experiences and complete the template configuration
    • Track campaign stats in the campaign statistics report (once the campaign is live)
  • Developer:
    • Build server-side templates that a business user can access
    • Configure API calling patterns that map to the campaign's authentication and identity requirements
    • Configure end systems to render Interaction Studio's JSON response payload
    • Ensure campaign stats are passed back to Interaction Studio to populate the campaign statistics report

Create a Server-Side Campaign

  1. Login to Interaction Studio.
  2. Select Server-Side > Server-Side Campaigns from the left navigation.
  3. Click New Campaign in the top right corner.

titleDefault Campaign Rule

When you create a new server-side campaign, you will see that a default rule of channel: Server is applied. While you can remove this rule, it is important that you understand the implications doing so has from an identity and authentication perspective.

Since removing the rule will impact how the API calling patterns are configured for the campaign, prior to removing the rule you should review the Server-Side campaign identity and authentication requirements

Select the Campaign Type

There are two campaign types. A/B Test campaigns split traffic randomly into different groups based on percentages you define. Each group sees a different campaign experience. Rule Based Test campaigns follow the rules you define to determine which experience to show to each visitor. For example, using a rule-based test, you could target a segment of visitors who had not been to your site in 30 days and show them experience 1, then show experience 2 to visitors who had been to your site in the last 24 hours.

  1. The default campaign type is A/B Test.
  2. Click > next to A/B Test.
  3. Toggle between A/B Test and Rule Based Test to change the type.

Create Campaign Experiences and Apply Additional Targeting Logic

For both rules-based and A/B/n tests, you can configure multiple campaign experiences. An A/B/n test will randomly split users into groups that see a different experience while a rules-based test will follow the targeting logic outlined in each experience. If a user in a rules-based campaign qualifies for multiple experiences, the experience higher in the list will correspond to the higher priority experience.

titleCross-Channel Campaigns

It is possible to configure a Server-Side campaign to extend across multiple channels and applications. Depending on the campaign rules, authentication and user identity requirements will differ depending on how you configure the campaign.

If you plan to build a single campaign that extends across multiple channels/applications, work closely with your development team and review the Create Application Specific Experiences section of the Server-Side Templates developer documentation which outlines the implications of going across channels.

Apply Server-Side Templates

Once you have configured your campaign experiences, it is time to apply templates. Once you select your template, you will be able to complete the inputs that the template developer has made available.

  1. Click Add Template at the left, under Experience 1
  2. In the Select Template window, select the template you want to apply to your campaign. The template list only includes published Server-Side templates (not web templates).
  3. The template appears under Experience 1.
  4. Configure the inputs available, which vary by template.

Test and Publish the Campaign

To test your campaigns, work with your campaign developer and use a tool like Postman to preview campaign response data. Detailed testing instructions are included in the Server-Side Templates developer documentation.