The published result of a SmartTarget enabled page(below) has properly resolved the TCDL tags, but does not, however, evaluate the SmartTarget user controls at runtime. The below code is rendered to the page, minus the Page Language declaration, as is and unevaluated.

<%@ Page Language="C#" %>

<SmartTarget:promotions region="ST" var="promotion" maxItems="1"> 
                    <tridion:ComponentPresentation pageURI="tcm:3151-18143-64" componentURI="${item.componentUri}" templateURI="${item.templateUri}"/> 

        <br>Fallback content goes here.</br>


The web.config for the app is as follows

    <globalization fileEncoding="utf-8" requestEncoding="utf-8" responseEncoding="utf-8" culture="en-US"/>
        <add tagPrefix="asp" namespace="System.Web.UI" assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
        <add tagPrefix="asp" namespace="System.Web.UI.WebControls" assembly="System.Web.Extensions, Version=, Culture=neutral, PublicKeyToken=31BF3856AD364E35" />
        <add tagPrefix="tridion" namespace="Tridion.ContentDelivery.Web.UI" assembly="Tridion.ContentDelivery" />
        <add tagPrefix="SmartTarget" namespace="Tridion.SmartTarget.Web.UI" assembly="Tridion.SmartTarget" />

<validation validateIntegratedModeConfiguration="false"/>
<modules runAllManagedModulesForAllRequests="true">
    <add type="Tridion.ContentDelivery.AmbientData.HttpModule" name="Tridion.ContentDelivery.AmbientData.HttpModule" /> 

The relevant snippet from my smarttarget_conf below shows that the case of the ST user controls is valid and matching.


Another possibly related issue deals with the session and smart target cartridges delivered with SmartTarget. When I add those cartridges the app completely breaks with no error and renders a blank html page. This issue combined with the non-evaluation of the SmartTarget controls lead me to believe I may have a corrupt SmartTarget download.

Is there something else that anyone can think of that I might be missing here? Also let me know if there is any other information or configs I can provide to help the diagnosis.

2 Answers 2


Looks like you've asked it to render JSP tags but your site is running ASP.NET. You should change the Target Language of your Publication Target to ASP.NET and republish.

  • Took me a second to figure out how you discovered this... then saw it - attribute case. Well spotted.
    – Nuno Linhares
    Aug 5, 2014 at 10:56
  • There's also a "var" attribute and no "runat=server" attribute (the latter being the real reason why it doesn't work), but yeah :) Aug 5, 2014 at 13:45
  • @PeterKjaer the target language on my publication target is ASP.NET. Aug 5, 2014 at 13:53
  • 1
    Your deployer_conf can force a language too - check the <TCDLEngine> section in it
    – Nuno Linhares
    Aug 5, 2014 at 14:02
  • 1
    @NunoLinhares That was it! The one thing I managed not to check. This is a POC application in a sandbox and I obviously copied a deployer from a java app instead of .NET. It also appeared that either the session or smarttarget cartridge was corrupt in the SmartTarget download. I re-downloaded and installed the new cartridges and the call to Fredhopper is now being made. Aug 5, 2014 at 15:37

Here's the steps I'd take to troubleshoot your issue:

  1. configure your log file to capture your smart target events (documented here) - you can see the request made to SmartTarget plus you'll see any errors reported
  2. use the preview tool within the business manager to test that your triggers are working correctly.
  3. Write a bit of code to check that your expected values exist in the ambient data framework, i've dropped an example here

Once you've done these three, perhaps update your question with more information to help solve it, or if you solve it, please provide the answer for every one else.

  • I have already been through steps 1 and 2, but stopped there when I realized from the logging that the call to ST wasn't happening. This is when I realized the user controls were not being evaluated. I'm still trying to solve that issue. Aug 5, 2014 at 14:16
  • ah well, i'll leave the info there, might be useful to someone one one day :)
    – johnwinter
    Aug 5, 2014 at 14:38
  • Totally agree. These are the defacto steps I take as should anyone in debugging SmartTarget. When they have their deployers correctly setup, unlike I did here :) Aug 5, 2014 at 15:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.