When you want Personalization to directly inject and display personalized content on your website, you can set a slot mode to trusted or untrusted. If your website requires content to be injected and displayed in your own customization (such as in a decoupled Drupal installation), you can set the slot’s mode to customized.
Users with ad blocking software in their browsers may not see content in Personalization slots. For more information, see Ad blocking and Personalization.
Personalization<iframe>.To alter the content replacement mode used on your website, perform the following steps to modify your Personalization configuration settings:
One or more slots can have a different setting than the website default. If you have a given slot that will always hold untrusted content on an otherwise trusted website, or vice versa, you can override the slot to have a non-default setting.
Within the embed code that you add to your page, add the following line to set a particular slot to always be trusted:
<div data-lift-slot="my-overridden-slot" data-lift-mode="[MODE]" />where [MODE] is trusted, untrusted, or customized.
Trusted content uses the style of your website by applying appropriate CSS and targeting. When you are using imported content that is not trusted, it does not use that CSS and its styling may not fit with the style of your website. You can apply an attribute to the slot, which applies a stylesheet:
<div data-lift-slot="my-slot-id" data-lift-css="http://mysite.com/custom_slot.css"></div>When rendering content in trusted mode, it is important to understand when styles should or should not be imported with the content as rendered by the view mode. In some cases, rendering the content in an untrusted iframe will require additional styling and scripting that should not be included in directly injected trusted content (or should be the responsibility of the Personalization website displaying the content).
In trusted content mode, Personalization renders markup only in <body> tags, which removes all styles and scripts included in the <head> tags that includes data-content-barrier-exclude="true" in its attributes. Content injected in untrusted mode will be injected as-is, with all markup included.
The intention with trusted mode is that the website receiving the injected content should control the styling and scripting of content, whether injected or rendered natively on the page. There are situations when the content for replacement is architected in a more component-based approach, and styles or scripts should be packaged with the content for use in either trusted or untrusted mode. In these cases, any styles and scripts necessary should be rendered in the <body> of the rendered view mode content.
For example, in untrusted mode, this markup is rendered:
<!DOCTYPE html>
<html lang="en">
<head>
<style>
.my-custom-style { color: #000000; }
</style>
<link rel="stylesheet" href="http://mysite.com/stylesheet.css" />
<script type="text/javascript" src="http://mysite.com/myexternaljs.js"></script>
<script>
var foo = 'bar';
</script>
</head>
<body>
<style>
.perfect { color: #39ff14; }
</style>
<script>
var perfect = 'check out that style';
</script>
<p class="perfect">My perfect content
<span data-content-barrier-exclude="true">Don't show this in trusted mode</span>
</p>
<div data-content-barrier-exclude="true">
<script type="text/javascript" src="http://mysite.com/myfooterjs.js"></script>
</div>
</body>
</html>However, if the content is trusted, only this section will be rendered:
<style>
.perfect { color: #39ff14; }
</style>
<script>
var perfect = 'check out that style';
</script>
<p class="perfect">My perfect content
</p>After setting a slot to customized mode, its content is now broadcast to the webpage instead of being injected into the webpage. To work with the content being shared (but not displayed), you must implement the following in your website’s code:
acquiaLiftContentCustomizable event to process the data, and customize your website. For details about how to implement this function, see JavaScript API events.AcquiaLiftPublicApi.customize(). For details about how to call customize(), see Personalization methods.With the slot included on a webpage, it will be monitored and tracked by Personalization, even if the content is not injected.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
When you want Personalization to directly inject and display personalized content on your website, you can set a slot mode to trusted or untrusted. If your website requires content to be injected and displayed in your own customization (such as in a decoupled Drupal installation), you can set the slot’s mode to customized.
Users with ad blocking software in their browsers may not see content in Personalization slots. For more information, see Ad blocking and Personalization.
<iframe>.To alter the content replacement mode used on your website, perform the following steps to modify your Personalization configuration settings:
One or more slots can have a different setting than the website default. If you have a given slot that will always hold untrusted content on an otherwise trusted website, or vice versa, you can override the slot to have a non-default setting.
Within the embed code that you add to your page, add the following line to set a particular slot to always be trusted:
<div data-lift-slot="my-overridden-slot" data-lift-mode="[MODE]" />where [MODE] is trusted, untrusted, or customized.
Trusted content uses the style of your website by applying appropriate CSS and targeting. When you are using imported content that is not trusted, it does not use that CSS and its styling may not fit with the style of your website. You can apply an attribute to the slot, which applies a stylesheet:
<div data-lift-slot="my-slot-id" data-lift-css="http://mysite.com/custom_slot.css"></div>When rendering content in trusted mode, it is important to understand when styles should or should not be imported with the content as rendered by the view mode. In some cases, rendering the content in an untrusted iframe will require additional styling and scripting that should not be included in directly injected trusted content (or should be the responsibility of the Personalization website displaying the content).
In trusted content mode, Personalization renders markup only in <body> tags, which removes all styles and scripts included in the <head> tags that includes data-content-barrier-exclude="true" in its attributes. Content injected in untrusted mode will be injected as-is, with all markup included.
The intention with trusted mode is that the website receiving the injected content should control the styling and scripting of content, whether injected or rendered natively on the page. There are situations when the content for replacement is architected in a more component-based approach, and styles or scripts should be packaged with the content for use in either trusted or untrusted mode. In these cases, any styles and scripts necessary should be rendered in the <body> of the rendered view mode content.
For example, in untrusted mode, this markup is rendered:
<!DOCTYPE html>
<html lang="en">
<head>
<style>
.my-custom-style { color: #000000; }
</style>
<link rel="stylesheet" href="http://mysite.com/stylesheet.css" />
<script type="text/javascript" src="http://mysite.com/myexternaljs.js"></script>
<script>
var foo = 'bar';
</script>
</head>
<body>
<style>
.perfect { color: #39ff14; }
</style>
<script>
var perfect = 'check out that style';
</script>
<p class="perfect">My perfect content
<span data-content-barrier-exclude="true">Don't show this in trusted mode</span>
</p>
<div data-content-barrier-exclude="true">
<script type="text/javascript" src="http://mysite.com/myfooterjs.js"></script>
</div>
</body>
</html>However, if the content is trusted, only this section will be rendered:
<style>
.perfect { color: #39ff14; }
</style>
<script>
var perfect = 'check out that style';
</script>
<p class="perfect">My perfect content
</p>After setting a slot to customized mode, its content is now broadcast to the webpage instead of being injected into the webpage. To work with the content being shared (but not displayed), you must implement the following in your website’s code:
acquiaLiftContentCustomizable event to process the data, and customize your website. For details about how to implement this function, see JavaScript API events.AcquiaLiftPublicApi.customize(). For details about how to call customize(), see Personalization methods.With the slot included on a webpage, it will be monitored and tracked by Personalization, even if the content is not injected.
If this content did not answer your questions, try searching or contacting our support team for further assistance.