Switch from Sourcepoint "Legacy" to "Multi-Campaign" implementation

This guide is intended for websites, having integrated Sourcepoint’s Consent Management Platform on their own. If you receive the CMP via the Ströer TagManager, you can ignore this document.

An in-depth guide for implementing the “Multi-Campaign” features is available from Sourcepoint directly: https://docs.sourcepoint.com/hc/en-us/articles/1500012033481
However, there a some technical steps necessary, that are not directly evident from the documentation. To ease the migration process, please consider the following tips.

The first part of the migration process, is changing the URL of Sourcepoints main script to a new one. This should be done, before making any changes inside the Sourcepoint UI. Sourcepoints documentation suggests to start with the UI, but this will lead to losing consent functionality on your website for extended periods of time.

Instead, start by locating your configuration of Sourcepoint inside your website. This will look similar to this example:

<script>
	window._sp_queue = [];
	window._sp_ = {
		config: {
			baseEndpoint: "https://cdn.privacy-mgmt.com",
			accountId: 375,
			targetingParams: {}
		}
	}
</script>
<script src="https://cdn.privacy-mgmt.com/wrapperMessagingWithoutDetection.js"></script>

In most cases, the “baseEndpoint” property and script “src” will use a subdomain of your own website. If this is the case, please re-use your own (sub)domain instead of “https://cdn.privacy-mgmt.com/”

The property “targetingParams” is optional and may contain further key value combinations, if you are using targeting in your Sourcepoint Scenarios. If you do not use it until now, remove / ignore it.

Take the following steps:

Append the configuration with a new “gdpr” property, and include your “targetingParams” and all its key value combinations as child property.
Change the script “src” path to “/unified/wrapperMessagingWithoutDetection.js”

It should look similar to this example:

<script>
	window._sp_queue = [];
	window._sp_ = {
		config: {
			baseEndpoint: "https://cdn.privacy-mgmt.com",
			accountId: 375,
			gdpr: {
				targetingParams: {
					exampleTargeting: "removeMe", //example for documentation purposes, do not use on your website
					yourTargeting: "whateverYouUseOnYourWebsite" //example for documentation purposes, do not use on your website
				}
			}
		}
	}
</script>
<script src="https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js"></script>

In most cases, the “baseEndpoint” property and script “src” will use a subdomain of your own website. If this is the case, please re-use your own (sub)domain instead of “https://cdn.privacy-mgmt.com/”

The property “targetingParams” is optional and may contain further key value combinations, if you are using targeting in your Sourcepoint Scenarios. If you do not use it until now, remove / ignore it.

Please make absolutely sure that your configuration includes the “gdpr” property. Even if you use no targeting and the property will be empty, Sourcepoints “Multi-Campaign” will not work if the “gdpr” property is missing.

We highly recommend testing this configuration on a staging / test site, before continuing.

Make sure not to test on your “localhost“, since Sourcepoint will only work correctly on a valid (sub)domain relating to your website.
When testing your new configuration, all consent features on your website should still work as before. If you encounter any errors, contact your Sourcepoint support.
If all went well, roll out your new configuration to your live website, before continuing.

2.) Start switching your Property to “Multi-Campaign” in Sourcepoint UI

Make sure you have tested and live-deployed your new configuration.

Since there are a few more steps necessary to change each Property fully to “Multi-Campaign”, switch your Properties one by one and not all at once as suggested by Sourcepoint “Enable multi-campaign on property group”

Instead, follow the instructions of Sourcepoints documentation “Enable multi-campaign on individual property“ https://docs.sourcepoint.com/hc/en-us/articles/1500012033481#h_01F6JAQAKW7BC0S14W7VJX5YFH
After enabling Multi-Campaign for one of your properties, continue with the next step.

3.) Change your exiting “Partitions” and “Scenarios” to use “Campaign Types”

Inside the Sourcepoint UI, we will need to change your “Scenarios”, “Partition Sets” and finally starting a new “Campaign”. Each of these require a new “Campaign Type”, that marks it as “GDPR Compliance”.
Start by changing your “Scenarios” first.

Click on the Property you just changed to “Multi-Campaign”.
Navigate to the “Scenarios” tab

Some or all of your scenarios will show a message in red, “No Type”. Before you can use these scenarios in a new campaign, you have to change the type to “GDPR Compliance”.

Click on “Set Type”. A small drop down box will appear.
Select “GDPR Compliance” and click “Update”
Repeat these steps for every “Scenario” you like to use in the future

Switch to the “Partition Sets” tab and repeat the above steps.
Be aware that you can only change the type on “Partitions” that contain “Scenarios” you already switched. Otherwise, you will receive an error message prompting you to do so.

4.) Create a new “Stage Campaign”

We will now create a new “stage campaign”, that will allow you to test all functionality without impacting your live website directly.

You could theoretically continue with creating a “Public Campaign”. This will put your changes directly live, without any testing. Do so on your own discretion.

Navigate to your Properties “Campaigns” tab.
Click “New Campaign”. A small form will appear asking you to fill in a “Name”, “Type”, “Partition Set” and “Environment”
Name your Stage campaign
Select type “GDPR Compliance”
Select a Partition Set of your choosing
Select the environment “Stage”
Select priority “1”
Click the “Create” button

You are now able to test your new Stage Campaign on your website. See Sourcepoints documentation https://docs.sourcepoint.com/hc/en-us/articles/1500011973962-Campaign-environments#h_01F6HYASZFMZPTR4ND3VW7MFDK on pointers how to do so.
If you encounter any errors during the process or if your consent layer is not showing up on your website, please contact your Sourcepoint Support.

Should everything have worked out, without errors, continue with the next step.

5.) Promote your “Stage” campaign to “Live”

The next step will leave your website shortly (~30 seconds) without any consent functionality. Neither consent layer, advertisements nor consent interfaces will be available.
All users will be prompted to give their consent anew. Unfortunately, there is no way around this.

Navigate to your Properties “Campaigns” tab.
Under “Public Campaigns” (to your right) you will see your currently running live campaign.
Click “End Campaign” on your public campaign
Click and hold your mouse button on the white box of your “Stage” campaign.
Drag and drop your “Stage” campaign to the right into the “Public” campaign area
A prompt will appear, asking you to confirm that your stage campaign should be delivered to your users.
Click “Yes”

Your stage campaign will now appear under “Public Campaigns”. This change will be processed by Sourcepoints server in around 15-30 seconds.
Afterwards you are finished with this property, no further steps are necessary.

If any errors or problems come up, please contact your Sourcepoint Support immediately.

1.) Include “gdpr” property in Sourcepoint config, before switching

2.) Start switching your Property to “Multi-Campaign” in Sourcepoint UI

3.) Change your exiting “Partitions” and “Scenarios” to use “Campaign Types”

4.) Create a new “Stage Campaign”

5.) Promote your “Stage” campaign to “Live”