MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Use of audiences ... how many web parts targeted on a single site

  Asked By: Grace    Date: May 25    Category: MOSS    Views: 803

With MOSS .. has anyone used MOSS Audiences extensively? For example,
a department wants to target content to geographic groups (audiences).
Now in the edit mode this would be ugly, but what impact on
performance, etc. if there are literally dozens of web parts (usually
content editors). on a site so that user "X" sees only those targeted
to him/her?

So there could be 16 audiences, thus 16 web parts on the page, each
targeted at a single audience, so user X from geography X sees only
webpart X?

This assumes that these geographies exist in AD. I know that part, I'm
more interested on hits on performance.




1 Answer Found

Answer #1    Answered By: Faith Delgado     Answered On: May 25

My usage of audience  targeting hasn't really fallen under the scenario that you
describe (where each audience has its own web  part that is designed for that
particular audience), but more along the lines of using content  aggregation web
parts (like CQWP) that apply audience filtering so that the information that you
see in 1 web part  is targeted  (aka personalized) to the end user  based upon the
audience(s) that the end user belongs to in addition to the normal filtering
defined in the web part content. This concept can be used to drive both list
based information (like top 5 related audience targeted news stories) or content
based (like related ad banners).

We have used this pretty extensively with large groups  of audiences  (as well as
many audiences) and several targeted web parts  on main pages with no noticeable
performance hit (as compared to normal web parts). While we have not done
specific performance  analytics against this particular metric, there was nothing
noticeably slower. I think that the audiences having to be compiled helps with
this tremendously (as opposed to real-time audience compilation for a page
request, which would be more convenient).