21

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 ...


13

What you propose is definitely the approach I would take... Remove the "publish to SmartTarget" TBB from the Component Templates to make sure items don't end up there again... Create a set of "delete" operations for Fredhopper (probably scripted to make sure I don't copy/paste the wrong URIs) Drop this file in the "incoming" folder of Fredhopper I was ...


13

The problem was found in my smarttarget_conf.xml file, I had recently added some new claim variables and have failed to correctly close one of the XML nodes. I've ensured the XML is correctly formed and the website now loads perfectly.


11

The shortest possible SmartTarget promotions implementation with JSP tags is as follows. This indeed looks a lot like the TCDL tags. source <smarttarget:query siteEditTagName="span" publication="tcm:0-72-1"> <smarttarget:promotions region="Homepage Banners" maxItems="1"> <smarttarget:itemTemplate> <...


11

By default you will not see SmartTarget promotions in Fredhopper. Fredhopper users should not change the SmartTarget promotions in the Fredhopper GUI, so they are hidden. If you are doing some troubleshooting or just are curious, you can change a setting in the SmartTarget extension in Fredhopper to enable the listing in the Fredhopper GUI. Just add a file ...


10

There's no reason why you still can't use the TBB's. I'd recommend using them in the event you wish to move away from the DD4T mvc framework in the future. Simply output your content as REL and transform the TCDL tags yourself when you return your content from the broker.


10

This problem can be resolved by simply checking the cd_deployer_conf.xml file within the deploying application, the incorrect property <TCDLEngine> <Properties> <property Name="aspnet.tagprefix" Value="smarttarget" /> Should become: <TCDLEngine> <Properties> <property Name="aspnet.tagprefix" Value="tridion" /> ...


10

We Can achieve this using the following option in the FH/ST server : http://[host]:[port]/fredhopper/sysadmin/reload-config.jsp?select=trigger-types although, the person who taught me that, told me that we need to be very careful with that administration console, we can mess up the entire environment Thanks Marc!


10

Another way of doing this would be to write a number of mvc html helpers that would use the smarttarget query api to fetch promotions etcetera. The flow would be something like get parameters from the html helper (promo name, nr of items, region name,...) construct a smarttarget query send a query and receive xml with results. I believe the results are tcm ...


10

Usually, the installation package contains some sample configuration xml files. For smarttarget, you can find it here in your installer package : Content Delivery\configuration\samples\smarttarget_conf_sample.xml. You should put that file in your odata config directory, rename it, and make the necessary adjustments for your environment.


10

You choose the field you wish to order on, as well as ascending/descending preference, on the "Filtering and Ordering" tab of a Promotion. Note that for a field to show up there, it needs to be a live attribute within Fredhopper ('added to the navigation index'). For more information, see the following pages in the documentation: Filtering and ordering ...


9

The attributes (fields) in Fredhopper have a maximum size which you probably exeeded. An attribute cannot exceed the max character length of 32K. Most likely you have hit this limit. Logs Check the Fredhopper logs on the indexer instance and the xmlloader log in particular. You can expect an error message like this: 2015-01-09 14:59:55,963 ERROR [XML-...


8

There is not yet a release compatible with 2013 SP1. It's coming soon - estimated somewhere in Q2.


8

I've resolved the issue. I had installed FAS version 7.5.1.0 (107777), I should have been using 7.5.0.16. Version 7.5.1.0 is not used for 'on-premise' installations. Thanks Peter Kjaer @ SDL for sitting with me to resolve this :)


8

I suspect there may be more than one issue behind the symptoms you describe. To get past your brick wall, consider the following: From your last log we see that there is a service being called (most likely a soap or rest web service): at System.Data.Services.Client.DataServiceRequest.Execute[TElement](DataServiceContext context, QueryComponents ...


8

Claim to trigger mapping The first problem is in the mapping. You should map the "group" instead of the claim. So you want to map the "group" taf:claim:usertype to the prefix user. Try this mapping: <taf_claim_usertype>user</taf_claim_usertype> This way the claim taf:claim:usertype:prof will be mapped to the trigger url-param user_prof. ...


8

So to me this looks like it's supposed to be a JSON object: Start Region: { title: "MainContent", allowedComponentTypes: [ { schema: "tcm:6-195-8" template: "tcm:8-288-32" } ], maxOccurs: 10 } Except for one thing -- you missed a comma between the schema and template. Will fixing that make it work? Really just pulling this out of ...


8

Finally I have resolved my issue, the problem was a configuration in the Publication Targets. I created 2 similar Publication Targets (Previsualization and PrevisST), both had the same webservice_preview url,and both use the same URLs to access but only PrevisST had filled Targeting layer. When I tried to modify my page from XPM, the default target selected ...


7

You can also query Fredhopper directly via the query web service -passing the various facets you wish to query on. Fredhopper will return results that contains several components such as a breadcrumb, facetmap, item lister and promotions. You can then render these as you wish. Cheers


7

Fredhopper: SDL Fredhopper is a Customer Experience Management tool which provides a seamless, targeted and fully personalized website experience to the end users. The SDL Fredhopper enables the marketing team to target a specific segment of customer with all the right products or content which suits them best. SmartTarget: SmartTarget is an add-on for SDL ...


7

Your JAVA website will use the SmartTaget tag library, or if you like the SmartTarget API, to get the content for a specific SmartTarget region. SmartTarget will also take care of the SmartTarget markup for Experience Manager. In a JSP page you could add some JSP tags to define the SmartTarget region on the page. SmartTarget will do the rest. See a minimal ...


7

Apart from the approach Stephan202 mentioned: If you're using the deployment agent, you can use it's "capture" functionality to capture the complete configuration, and restore that when needed.


7

The Service Account Email, doesn't need to be the one you use to log on google analytics pages. The Service Account Email is the one you use to generate de .p12 file. Then in Google Analytics Admin of the site you want to use, this Account Service Email, must be granted in the "User Management" tab. With at least "Read and Analyze" permission. Like in the ...


6

You need to use fh:user:date as the claim uri. You also need with Tridion 2013 to enable claim forwarding for that claim. You can do this in the cd_ambient_conf.xml by adding <Claim Uri="fh:user:date"/> within the GloballyAcceptedClaims element. However, this is not enough, because the date format generated by the FootprintDate control is not ...


6

As far as my knowledge is concerned, you can only get an IP address from the ADF and you would need some IP-To-Location third party APIs to show the physical location mapped to this IP - I would certainly recommend using some paid service like: MaxMind ip2location I have worked with these two and results are 98% accurate (as per their claim; I have seen ...


6

If SmartTarget is an option, then I'd definitely go for it. This is probably the easiest integration point. This is +/- what you'd have to do: Create an ADF cartridge that reads the user's group memberships and adds this as an ADF claim (perhaps in a comma separated list?) Configure trigger-types.xml to use this claim Create promotions that trigger if the ...


6

The capture-import command (and pretty much all other commands!) should be run from the fredhopper installation directory, not from the bin directory.


6

I currently do not have access to the LiveContent documentation page, so the following information is from the top of my head: SmartTarget 2014 installations that use an on-premise installation of Fredhopper are advised to use FAS 7.5.0.16, which is contained in fredhopper-7.5-revision-13 (i.e., not fredhopper-7.5-revision-14, which contains FAS 7.5.1.0). ...


6

Like when digging a tunnel it might be helpful to troubleshoot this issue from two ways. Or maybe from multiple ends. From the Tridion CD side If you publish a SmartTarget enabled DCP and the publishing process is succesfull the SmartTarget deployer has deployed the DCP to Fredhopper and the DCP is processed in the Fredhopper indexer instance. Are you sure ...


6

You could put the content out using REL and transform the TCDL tags yourself. when you return your content from the broker. EDIT I agree with the process Harald discusses above - I have tested and confirm you can get the Component Presentation HTML - BUT any dynamic component links are not available (it doesn't go through the Tridion REL engine) - it ...


Only top voted, non community-wiki answers of a minimum length are eligible