HomeGuidesAPI Reference
Submit Documentation FeedbackJoin Developer CommunityLog In

Personalizing content

This topic explains how to personalize content using a headless approach for content recommendations through the Content Delivery API.

How do you add content personalization to a headless solution where the tracking does not hit a controller in the presentation layer?  You can use a headless approach for content recommendations through the Content Delivery API. To do this you need to implement compatible tracking and calls to the recommendation API. See Tracking.

In a headless scenario, you can also customize the DefaultContentModelMapper and replace it with your own. See Customizing data returned to clients and Serialization.

Example: Customizing DefaultContentModelMapper

You can manipulate with personalization by customizing the DefaultContentModelMapper.

  1. Create a new class where your CustomContentModelMapper inherits from DefaultContentModelMapper. Register it with ServiceConfiguration and in DependencyResolverInitialization (this is an example from an Alloy site).
public void ConfigureContainer(ServiceConfigurationContext context)
{
  //Implementations for custom interfaces can be registered here.

  context.ConfigurationComplete += (o, e) =>
  {
    //Register custom implementations that should be used in favour of the default implementations
    context.Services.AddTransient < IContentRenderer, ErrorHandlingContentRenderer > ()
      .AddTransient < ContentAreaRenderer, AlloyContentAreaRenderer > ()
      .AddTransient < IContentModelMapper, CustomContentModelMapper > ();
  };
}​
  1. With CustomContentModelMapper: 
[ServiceConfiguration(typeof (IContentModelMapper), Lifecycle = ServiceInstanceScope.Singleton)]
public class CustomContentModelMapper: DefaultContentModelMapper
{
  public CustomContentModelMapper(IContentTypeRepository contentTypeRepository, ReflectionService reflectionService, IContentModelReferenceConverter contentModelService, IUrlResolver urlResolver, IEnumerable < IPropertyModelConverter > propertyModelConverters): base(contentTypeRepository, reflectionService, contentModelService, urlResolver, propertyModelConverters)
  {}

  public override ContentApiModel TransformContent(IContent content, bool excludePersonalizedContent = false, string expand = "")
  {
    var personalization = System.Web.HttpContext.Current.Request.Params["personalization"];
    return base.TransformContent(content, string.IsNullOrWhiteSpace(personalization) ? excludePersonalizedContent : Boolean.Parse(personalization), expand);
  }
}​

In this way, you can take advantage of personalization parameters in your request.

📘

Note

The DefaultContentModelMapper is currently marked as internal, so there is a risk of unadvertised breaking changes when customizing this.


Did this page help you?