Permission: Campaign entities

First layer messages allow you organization to create a consent experience whereby end-users can accept, reject, and/or make individual choices on vendors and purposes (or navigate to a privacy manager on the property).

In this article, we will cover how to edit a first layer message on an individual property.

  Note: If your privacy manager satisfies all necessary regulatory requirements, the first layer message is an optional configuration.

However, rather than configuring all the requirements into a privacy manager (which can lead to a very large, not user-friendly privacy manager), Sourcepoint strongly recommends a "dual layer approach" using both the first layer message with a link to the privacy manager.

Click Messages on the left-hand panel and select a regulatory regime (GDPR Messages, U.S. Privacy Messages (Legacy), or U.S. Multi-State Privacy Messages).

Click Web/Webview from either subsequent menu.

  Note: When building a message for the GDPR regulatory regime, you will have the option to select either a Web/Webview message for either TCF or Standard.

Screenshot 2023-11-13 at 5.57.44 AM.png

Use the property field in the upper right-hand corner to select a property for which you will edit a first layer message.


Ensure the First Layer tab is selected and then click the Edit icon inline with a first layer message. You can only edit first layer messages whose status is DRAFT.


From the subsequent page, apply any edits to the first layer message and click Save Message when finished. Click here for more information on how to navigate the first layer message builder.


  Note: If the first layer message is currently included in a message campaign, you will need to relaunch/refresh the campaign to push the charges into the environment. Once the campaign is relaunched/refreshed, Sourcepoint will create a new environment-specific version of the message with a static message ID. 

Click here for more information on how to relaunch/refresh your campaign.

Was this article helpful?
0 out of 0 found this helpful



Article is closed for comments.