Experiences Overview

Overview

Experiences are the elements UniSignIn shows on your pages: sign-up and account screens, walls and paywalls, newsletters, comments, polls, quizzes, recommendations, notifications, consent and adblock messages, AI summaries and more. See the experience library for every type.

Guides for each type

• Walls and account: Access Wall, Account Center, Sign-in Button, Data Form
• Preferences: Follow Button, Confirm Button, Toggle Switch
• Engagement: Comments, Poll, Quizzes, Reviews, Feedback, NPS, Countdown, Notifications
• Content: Story, Web Story, Live Blog, AI Summary

Create an experience

1. Go to Audience Operation > Experience and click New Experience.
2. Choose the experience type.
3. Fill in the settings and content. Most types let you set your brand colour and text.
4. Save the experience.

Use a default experience

Some types come with a ready-made default, so you don't have to create one. Choose it under Built-in defaults when you pick the experience in an Orchestration, or place it with its id in component code, for example <div data-exp="unisignin-button" data-exp-id="default-signin"></div>.

From an Orchestration, the sign-up wall, newsletter sign-up and recommendations go on the page's article, so target article pages. To change the text, colours or settings, create an experience of that type and use it instead. Answers to the default Feedback and NPS show in Results as Default Feedback and Default NPS.

Put it live

There are three ways to show an experience:

• Orchestration: choose where and to whom it shows, with rules on the page, context and reader profile, and A/B test variants. See Orchestration.
• Journey: show it the moment a visitor does something, such as scrolling halfway or reading their third article of the week, with Yes/No and random splits. See Journeys.
• Component code: place the experience in a fixed spot on your page with a container tag. See Set up experiences on your website.

Limit how often it shows

Set Show at most (times) and Per (Day, Week or Month) to stop a reader seeing the same experience too often, for example a newsletter box at most once a week. The limit applies when an Orchestration or a Journey shows the experience. Leave it empty for no limit.

When a reader skips or closes an experience, it stays closed as they move between pages.

Delete an experience

An experience that an enabled Orchestration or a live Journey uses can't be deleted. The message names them, so you can change or stop them first.

Measure

Each Orchestration has an insight page with users, clicks and click rate per experience. The Audience Overview shows how exposure to experiences relates to sign-ups, email subscriptions and paid subscriptions.

Personalise content

Experience text can include placeholders such as a tracked sign-up link, see Placeholders.