SmartTarget and Profiling and Personalization are not the same although at a very very basic level it may appear you can force them to do the same thing.
Profiling and personalization will allow you do display specific Component Presentations (attached to the page) to be displayed on the page if the profile logic is met.
SmartTarget integrates with the ...
You can indeed implement all of those things, by simply having some good triggers based on ADF claims. You should try very hard to make it generic, though, as one of the biggest benefits of SmartTarget over something like P&P is that the SmartTarget user is in control and doesn't have to involve developers every time they want to do a new Promotion.
@Manas, What I understand from your question is you are facing issue while incrementing the value of tracking key. To increment the tracking key value, you don't need to read the component visit/Page visit value. I can see some issue in your code, which seems to be a major issue in not updating the tracking key value. No need to use trackingKey.SetKey(...
You can get the value using the following:
var waiPage = new WAIPage(pgModel.Id, this.HttpContext.ApplicationInstance.Context);
//For Storing the Tracking Key
Tridion.ContentDelivery.Web.WAI.TrackingKeys trackingKey = new TrackingKeys(waiPage.User);
//retrieving cond from page.componentPresentation.Conditions
if (cond is KeywordCondition)
The commonest cause of null reference exceptions coming from Tridion Content Delivery code is incorrect configuration. This usually means that an expected XML element or attribute can't be found. (I imagine if they checked the result of every XPath, things would be better.) I would suggest the following:
Schema validate your configuration files - the ...
It's all just text. Tridion doesn't care whether it's emitting a head or a body. There's no reason why a component presentation can't be used in the head of a web page.
Regarding TCDL tags, it really doesn't matter whether these originate in the page or the page template, as long as they are correctly present in the output by the time the TCDL is ...
Is the component presentation stored in the broker database?
The code you are listing
will not be executed by the ComponentPresentationAssembler if the source is in the database; DCPs with ASP.Net server side code must be located on the filesystem for their code to be executed (in an SDL Tridion Content Delivery ...
Maybe depends on the environment because in previous versions of Tridion (2011) there were differences in the behaviour of the Profiling between "aspx" and "jsp" pages.
When the page is first loaded, it checks for a "request....
Answering your first question: Yes. you can use Custom Characteristics without tracking keys.
Second i have never tested but AFAIK it should be published DCP and dropped on page as Bjorn mentioned in your last post. can't you just try?
As far as I know, the (legacy) Personalization & Profiling functionality is not exposed through SDL Web 8 CIL APIs, but only in the (deprecated) in-process APIs.
Note that Experience Optimization (and to some extent Context Expressions) functionality is considered the successor of Personalization & Profiling functionality. But, admittedly, neither ...
To start with there are two types of personalization: Implicit and Explicit
Implicit will use Categories and keywords
Explicit will use Java or .net to set Customer Characteristics using WAI module.
More information can be seen in below post which have full code for my working module.
Target Groups based Content
I know that a while back the out of the box activate tracking TBB did not work, for which I created a fixed version as part of some generic TBBs on Tridion World. I would have expected that this had been fixed in more recent versions though (what version are you using?), however to be honest I have not done anything with P&P for years so I couldn't tell ...
It's been a while, but I seem to have 'solved' my issue when I started working on it again - I've opened up the Web App log file for a fresh peek and I noticed this ERROR suddenly after the CD WAI gets initialized.
ERROR LicenseReader - Could not find the license file file:/c:/windows/system32/inetsrv/cd_licenses.xml
Yep, all kinds of wrong.
As you might ...
The exception is being thrown in the constructor of WAIPage. The constructor accepts an HTTPContext as a parameter. If this parameter is null, this will cause the problem you are reporting.
It's a real shame that your Tridion license won't allow you to simply decompile Tridion.ContentDelivery.Web.WAI.WAIPage and look at its constructor. I've found that ...