Cxense

Skip to end of metadata
Go to start of metadata

 

Cxense  provides a suite of unified and connected solutions that their customers and partners can leverage to effectively engage with their online audience. They do this by capturing and analyzing the context (the combination of many variables such as time and place, device, role, preferences, content, intention, event, activity and so on) in which content is consumed and produced; the context in which entities and concepts are used within the content; and perhaps most importantly, the context of the users themselves. Gigya enriches Cxense Analytics with personal, professional and social user information such as name, date of birth, address, education, skills, patents, favorite movies, Facebook likes etc.

Solution Overview

The integration between Gigya and Cxense has four basic steps:

  1. Deploy the Cxense analytics scripts
  2. Deploy the Gigya plugin code
  3. Update Data and Define Cxense DMP segments
  4. Import DMP segments

Deploying Cxense Analytics Scripts

You need to deploy the Cxense analytics scripts on all of the web pages for which you want to measure interactions.

Please coordinate this with your Cxense implementation manager.

Deploying Gigya Plugin Code

Cxense syncs with Gigya data based on a unique identifier with the following requirements:

  • The identifier can be up to 40 characters long
  • The identifier must only include alphanumeric characters.

If you are implementing an integration with Gigya for the first time, you may generate your own unique identifiers that comply with these requirements, and assign those to the Gigya users you create.

If you are already a Gigya customer, we recommend using the Gigya UID as the unique identifier for Cxense sync, however, since the default Gigya UID created does not comply with these restrictions, you need to contact your Gigya Implementation Consultant in order to have the UIDs of your current users converted to a format that complies with these restrictions. This may require involvement of Gigya Professional Services which may therefore incur charges for this service.

Once you have verified that your Gigya UID complies with the above requirements, in order to capture the Gigya UID and sync it with your Cxense account, the following script needs to be added to your web page in the onLogin handler.

 

<!-- Cxense script begin -->

<script type="text/javascript">
	var cX = cX || {}; 
	cX.callQueue = cX.callQueue || [];
	 
	function CxenseSync (res) {
	    var eid = res.UID;
		cX.callQueue.push(['setSiteId', '<site id>']);
	    cX.callQueue.push(['addExternalId', {'id': eid, 'type': '<YOUR_PREFIX>'}]); // Replace with your account prefix
	    cX.callQueue.push(['sendPageViewEvent']);
	};
	
	window.onload = function () {gigya.accounts.addEventHandlers( {onLogin:CxenseSync} ); }
</script>

<script type="text/javascript">
	(function() { 
		try { 
			var scriptEl = document.createElement('script'); 
			scriptEl.type = 'text/javascript'; 
			scriptEl.async = 'async';
			scriptEl.src = ('https:' == location.protocol) ? 'https://scdn.cxense.com/cx.js' : 'http://cdn.cxense.com/cx.js';
			var targetEl = document.getElementsByTagName('script')[0]; 
			targetEl.parentNode.insertBefore(scriptEl, targetEl); 
		} catch (e) {};
	} ());
</script>
    
<!-- Cxense script end -->

If, for any reason, you are unable to use the Gigya UID as your unique identifier (e.g. you may already be using the full Gigya UID for other purposes), you may use the Gigya email to sync with Cxense, however, it is up to you to ensure that the unique identifier you create out of the Gigya email address complies with the Cxense restrictions noted above.

Update Data and Define Cxense DMP Segments

Updating Gigya Data

Generic data such as browser type is automatically updated to Cxense in real time, however Gigya fields need to be synced over to Cxense in order to have them available to define segments.

Gigya fields are synced over to Cxense during the regular Data Extract process. This should be coordinated with your Gigya Implementation Consultant.

Once you have completed the update you can define your DMP segments in the Cxense Administration UI based on both generic data and Gigya data.

Defining Segments

To define a new segment, in your Cxense account, select the DMP tab and click Create Segment.

You must provide a name for each segment, and then you can specify the different criteria that define the segment. Once you save your segment, it will be assigned a unique ID.

When selecting criteria for segmentation, you should see Gigya data parameters (such as "age" or "like ID") entitled 1st Party Data alongside Cxense parameters . Note that you will only be presented with a field for segmentation if at least one user with a value for that field that has been synced to Cxense. For example, Facebook Likes will only be offered as an option for segmentation if at least one user with a value for Facebook likes has been synced to Cxense.

Cxense imposes a limitation on any text field that should be ingested to be up to 40 characters long.

 

 

You may also define several criteria as a group by specifying a Criterion Group.

With each change the UI updates the guage on the right to display the percent of records that match your set of criteria.

Once you have defined your segments, they can be referenced in advertising platforms such as Cxense Display, Google DFP and others.

Gigya data is not currently supported by Cxense content recommendations.

Import the DMP Segments

Coordinate file names and FTP locations with your Gigya Implementation Consultant, and then import the segments you want into the DMP or the Ad server you want to use. Some Ad servers are available in Cxense out-of-the-box; in other cases you may need to access your ad server through a private API access point.

Notes:

  • Flattened JSON Data: Any flattened JSON data (such as Gigya likes or favorites) should be transferred as a contiguous chunk for each user
  • Max. unique categories: Cxense limits the number of unique likes or favorites (i.e. categories) to 40. Customers with several entries in the same category (e.g. favorite.music) count as 1 category.