Sourcepoint's webOS solution supports version 3+.
Sourcepoint's web-based webOS solution enables your organization to launch an OTT message campaign and collect end-user consent on webOS OTT devices.
Requirements
In order to successfully utilize Sourcepoint's webOS solution your organization will need to satisfy the following requirements:
- OTT property with configured message campaign
- webOS SDK (webOS IDE and emulator)
- Access to Sourcepoint's webOS SDK
Import project
Clone the webOS SDK into your local workspace directory and import the repo into Project Explorer pane.
Configure client details
The cloned files will allow your organization to demo an OTT message tied to a Sourcepoint controlled property. In this section, we will cover the necessary steps to edit the details of the cloned files to surface your organization's OTT message campaign.
Replace the accountId and propertyHref parameters in the index.html file with your account specific information.
<script>
function _typeof(t){return(_typeof="function"==typeof Symbol&&"symbol"==typeof Symbol.iterator?function(t){return typeof t}:function(t){return t&&"function"==typeof Symbol&&t.constructor===Symbol&&t!==Symbol.prototype?"symbol":typeof t})(t)}!function(){for(var t,e,o=[],n=window,r=n;r;){try{if(r.frames.__tcfapiLocator){t=r;break}}catch(t){}if(r===n.top)break;r=n.parent}t||(function t(){var e=n.document,o=!!n.frames.__tcfapiLocator;if(!o)if(e.body){var r=e.createElement("iframe");r.style.cssText="display:none",r.name="__tcfapiLocator",e.body.appendChild(r)}else setTimeout(t,5);return!o}(),n.__tcfapi=function(){for(var t=arguments.length,n=new Array(t),r=0;r<t;r++)n[r]=arguments[r];if(!n.length)return o;"setGdprApplies"===n[0]?n.length>3&&2===parseInt(n[1],10)&&"boolean"==typeof n[3]&&(e=n[3],"function"==typeof n[2]&&n[2]("set",!0)):"ping"===n[0]?"function"==typeof n[2]&&n[2]({gdprApplies:e,cmpLoaded:!1,cmpStatus:"stub"}):o.push(n)},n.addEventListener("message",(function(t){var e="string"==typeof t.data,o={};if(e)try{o=JSON.parse(t.data)}catch(t){}else o=t.data;var n="object"===_typeof(o)?o.__tcfapiCall:null;n&&window.__tcfapi(n.command,n.version,(function(o,r){var a={__tcfapiReturn:{returnValue:o,success:r,callId:n.callId}};t&&t.source&&t.source.postMessage&&t.source.postMessage(e?JSON.stringify(a):a,"*")}),n.parameter)}),!1))}();
</script>
<script type="text/javascript">
window._sp_queue = [];
window._sp_ = {
config: {
isOTT: true,
accountId: CLIENT_ACCOUNT_ID,
baseEndpoint: 'https://cdn.privacy-mgmt.com',
propertyHref: 'PROPERTY_NAME',
gdpr: { }
}
}
</script>
<script src="https://cdn.privacy-mgmt.com/unified/wrapperMessagingWithoutDetection.js"></script>
Note: To add a button/link that will resurface your privacy manager and allow end-users to directly manage their consent preferences on an ongoing basis you will need to add an OTT/CTV JavaScript code snippet to your index file. Click here for more information.
Run webOS emulator
Turn on your webOS emulator.
Once the emulator is running, navigate back to the webOS IDE to the Target Configuration pane and connect to the emulator machine.
| Field | Input |
| Name | Enter a name for the device. Choose a name that can easily identify the device. |
| Host |
|
| Port |
|
| Username |
|
You do not need to enter the Password and PrivateKey. When you use real TV, enable the Developer Mode before connecting the target.
With the connection to your emulator made, right-click the project folder in the Project Explorer window and click either Run As/Debug As > webOS Application.
If successful, your OTT message campaign will be surfaced in the simulator.
