/
DMP Targeting - Cxense

DMP Targeting - Cxense

Owned by Sebastian Perez (Unlicensed)
Mar 07, 2018

Cxense is a Data Management Platform with which you can target campaigns loaded in e-planning to special profiles provided by Cxense -- based on audience data collected.


For the successful integration of both platforms two parallel processes are required: one developed by the Publisher + Cxense, and another developed by the Publisher + e-planning.

 

PROCESS 1: PUBLISHER + CXENSE

For the service to work, the Publisher must have access to a Cxense account. Additionally, he must implement the provided code in all the site’s pages where he wishes to track information.

 

Cxense example code:

<script type='text/javascript'>
    <!-- Cxense script begin -->
    // Synchronous load of cx.js library
    document.write('<scr' + 'ipt type='text/javascript' src='http' + (location.protocol === 'https:' ? 's://s' : '://') + 'cdn.cxense.com/cx.js'></scr' + 'ipt>');
</script>

<script type='text/javascript'>
   var user_id = readCookie('elpaisuser');
   if (user_id == null) user_id = 0;

   var cX = cX || {}; cX.callQueue = cX.callQueue || [];
   cX.callQueue.push(['setSiteId', ‘<site_id>']);

   if (typeof user_id !== 'undefined' && user_id != 0) {
      cX.callQueue.push(['addExternalId', {'id': user_id, 'type': ‘<prefix_provided_by_Cxense>'}]);
   }

   cX.callQueue.push(['invoke', function() {
        CX_SEGMENTS = cX.getUserSegmentIds({ persistedQueryId: ‘<id_provided_by_Cxense>' });

      var eplanning=''; // INIT
      eplanning = CX_SEGMENTS.join('|');

      // Deben tener jQuery, de lo contrario usen su funcion para actualizar la cookie
      $.cookie('cxSegmentos', eplanning, {
         expires: 180,
         path: '/'
      });
    }]);

   cX.callQueue.push(['sendPageViewEvent']);
</script>
<!-- Cxense script end —>

 

REFERENCES:

  • Information provided by Cxense.
  • Function to obtain the user´s id.
  • e-planning´s variable.
 

We strongly recommend to get Cxense assistance to complete this step.

 

PROCESS 2: PUBLISHER + E-PLANNING

To ensure the correct implementation of the DMP, the Publisher must notify e-planning’s team.

Your Account Manager can offer guidance regarding this matter. You can also contact the Technical Support Area to ask for further assistance.

 

Once the DMP is enabled, the Custom 'Segments' managed in Cxense (Clusters in e-planning) must be loaded in the Ad Server before using this provider for Campaign targeting.

Check this article to learn how to do it: Custom Clusters: Cxense

 

Also when this DMP is activated a new targeting option will show on the account*: 'Targeting for DMPs'.

*If another DMP provider was enabled before (i.e: Navegg, TailTarget) , just the new provider will appear on the list.

On the Add/Edit Campaign form, a new block will be included for the DMP configuration:



DMP Targeting:

 

 

Implementation

This functionality is only supported by AjaxV4 codes.

Our codes are already prepared to capture and send Cxense’s information in each impression to every user.

Once all previous steps have been appropriately followed, e-planning’s request will include the information sent by Cxense.


IMPORTANT!

This DMP is not supported by the Inventory Forecast yet, this means that if the campaign has this targeting option enabled and then the stock is checked. it will not be taken into account for the results.

 

What’s more...

You will be able to consult the reports, taking into account this new type of DMP Targeting:

  • Campaign Summary: DMP:

Every campaign will have a new tab in the Summary that will indicate information provided by the DMP, even if the campaign is not targeted with this option.
  

Keep in mind that the data will not be sumarized as the same user may have registered impression / click on more than one segment / cluster .



Related links:

- Custom Clusters: Cxense