The Confirm Button asks readers one question with two buttons, such as "Get our morning briefing by email?" with Yes, please and Not now.
The answer is saved to a Yes/No profile field you choose, such as "Morning briefing". Create it in Data Management > User Data > Data Schema, or with the Create a field link in the experience. See Profile Fields.
Audience Operation > Experience and click New Experience.Next Step.| Setting | What it does |
|---|---|
| Question | What you ask the reader. Required. |
| Yes button | The text of the yes button. "Yes, please" if you leave it empty. |
| No button | The text of the other button. "Not now" if you leave it empty. |
| Ask again after (days) | How long the question stays hidden after a reader clicks the no button. 7 days for a new experience. |
| Saved to field | The Yes/No profile field you choose for the answer. Required. |
| Button colour | The colour of the yes button. |
Save Changes. The preview shows how the question looks.Place the question where it should appear, for example at the end of your articles. Copy the snippet from the experience, which fills in its ID, or replace EXPERIENCE_ID yourself:
<div data-exp="unis-confirm-button" data-exp-id="EXPERIENCE_ID"></div>
You can leave out data-exp-id. The question then uses the Confirm Button experience delivered to the page.
A yes sets the field you chose to Yes. The no button doesn't change the field. Use the field in Segments, for example the field equals Yes, to target the readers who said yes, or does not equal Yes to keep asking the others.
See the Confirm Button experience and Set up experiences on your website.
Identity, consent, audience, and subscription insights for publishers. A few emails a month, no spam.