nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Livesite Targeting, Segmentation

SPrakash

Hi,

I am using Teamsite 6.7.1 with Site publisher. I like to know how the concepts of Targeting, Segmentation and Taxanomy to be used for a site. I did checked the documentation and havent found much information about these concepts.

One more thing there are ILog Rules in Livesite. How these ILog rules has to be used in the Site.

Can any one who used these concepts eloborate a bit about how we can use these concepts together for a site.

Regards,
Prakash

Find more posts tagged with

Comments

Migrateduser

Segmentation - segment/segregate your customers(Male, Female, from NY City, from Bangalore...)

Based on the above, you will end up with 'n' number of segments. So without having to maintain/manage 'n' different websites and associated sitemaps/site navigation you will be able to present 'n' website experiences, for example user from NY City will see en_US pages where as a Bangalore user can have Kannada content served to him(just an example, this particular usecase can be achieved without segmentation also)

When you use segments you are at the site level implicitly using "targeting", ie.. your users are seeing something tailored for their segment(Male users home page will have a Corvette as their home page background, where as Female users can have pretty pink bunnies...)

Another type of targeting is 'content' targeting, that is a single component will render something different for Males .vs. Females. Corvette for Males, Pink bunnies for Females.

The content ofcourse is rendered inside a component, and the component can be attached with rules, such as

If user is "male" show Corvette
If use is "female" show Pretty Pink Bunnies

These business "rules" are defined in iLog and consumed by LiveSite.

For Taxonomy, consider a promotion component for Corvettes and Pretty Pink Bunnies. So you can create a Taxonomy with two nodes "Macho" and "Cute", so tag content with "Macho"(Corvette.jpg) or "Cute"(Pretty Pink Bunnies.jpg). Now you can write a rule such as

If User is Male and from NY City show content tagged with "Macho"
If User is Female and from San Francisco show content tagged with "Cute"

So when a Male logs in the promotion component will say "Corvette.jpg" and Pretty Pink Bunnies when a Female user logs in.

SPrakash

Hi,

Thanks for your detailed explanation.

I have tried creating Segments in TS 6.7.1 by setting rules. It also updates the site map for that particular site and it is taking the start page as the preview page.

My doubt is when we create a segment, for a site which has different pages, is it possible to show different pages based on the rule.

One more doubt, i have created content rules and taxonomies. I am not able to understand how i can use them practically. Is the content rules relate to the Internal Datum Content Rule? Whether the rules created from the ILOG can be used in creating the segments as well.

Regards,
Prakash

Migrateduser

when you create a new segment, it 'forks' the 'Primary' segment in Sitemap, and you can add whatever new pages/nodes to the new segment, which are absent in the Primary.

The way segments work is that when the user logs in the correct 'start' page for the particular segment will be shown, for Ex. in Primary the start page could be start.page, whereas for a NY City segment, the start page could be nystart.page(just associate the start node in the NY City segment to nystart.page), there by showing different 'Home' pages for different segments.

Once you have a taxonomy(Category/Content Type) and you have created Content rules like:
If the gender of the user is male
then
add content from category 'macho' and add it to the context

where 'macho' is a Category taxonomy node.

Once this rule is created in the context of a site, and your component has a 'Content Rule' Datum, you component properties will allow you to add the above rule(s) to the component. In TS 6.7.1 SP1, take a look at an example component name 'Simple List.component', which just shows the vpath of tagged content, For ex: if you had Corvette.jpg tagged with 'macho' the above rule will just show the vpath of Corvette.jpg, or if the 'user' is not a male , then it will show every thing except Corvette.jpg, this is just the default behavior of the external in that component.

Rules are generally same for Segments and Content Rules, but you can have rules appear only in Segment and not in Content Rules and vice versa. It depends on which of the iLog project you extend.

SPrakash

Thanks for the reply.

I have created a segment and changed the start page for that segment in the sitemap for that particular site. If i deploy the sitemap to the runtime and logged in the runtime, all the segmentation rules for that site will be automatically applied and based on the rule it satisfies, that segments start page will be displayed.

Similarly, the content rules can be set to a component with the content rule datum, add it to the page and deploy the site to the runtime, based on the rule, the component will be displayed to the users in the Runtime.

Please let me know whether my understanding is correct.

Unfortunately i dont have Runtime configured and the deployment is failing to the development server and the DB schema is not getting updated for the taxanomies.

Whether the content categories and dataypes in the taxanomies relate to the normal templates we create in Teamsite.

Regards,
Prakash

Migrateduser

Hey Prakash,

Content Categories & content types are the 2 OOB base taxonomies shipped with Livesite.the Content Type and content category data type is an extension of Taxonomy Node.

Content type and content categories data type will be used by Livesite to tag contents.

Please specify the error message you are getting while deploying to the development server.

Thanks

Vinay

SebPRG

Hi Guys, im using TS 7.1 and enabled Segmentation, i created 2 segment (English & French), where i set the start page for each segments ?

Thank

ToggleSeriesVisibility.rptdesign

SebPRG

I based my condition on each segment on the name of the page

English: if page name contains ENG
French: if page name contais FRA

No matter what, its always the Primary segment that is displayed in my left menu ...

Thank