Targeting
Survey Triggers, Widget types, and a number of targeted web pages impact the number of responses you will get.
Last updated
Survey Triggers, Widget types, and a number of targeted web pages impact the number of responses you will get.
Last updated
While Pulse Insights has advanced targeting capabilities, using all capabilities in tandem can result in overly high setup & QA overhead with limited data capture.
If the user is on a URL containing “Products,” and scrolls 50%, THEN show a survey.
Once a visitor has answered the questions, you do not need their answers again! By default Pulse, surveys do not refire once a visitor has answered the questions.
Additionally, you can also choose "do not refire" once a user as closed a survey. Don't be a pest! If a visitor has closed the survey, they have indicated that they do not want to answer.
Surveying the same person multiple times may skew your results.
An exception to the rule: If a survey is set up as an informational flag to answer a visitor's questions or to help direct them to information, you may want it to show every time.
Without a frequency cap, a visitor sees the survey every time they visit AND meet the targeting conditions, until they’ve clicked the ‘X’ or answered the survey.
Think of frequency caps as the last prevention to over-surveying, as they can be used in combination with other restrictions like widget type, survey triggers, and sample rates.
Pulse recommends setting a frequency cap. Frequency caps are set account-wide, will apply to every survey, and can be set to any amount.
Pulse recommends setting a frequency cap of 1 or 2 impressions per day.
Impression frequency capping is based on Served Impressions, not Viewed Impressions. If a survey is served, but isn't viewed due to unmet targeting conditions, the served impression still counts towards the cap.
You want to get a representative read of the site as a whole.
You want to compare results across all pages.
If it is important for many visitors to see the survey.
To use an inline survey here, your tech team will need to create a container/div.
You’d like a representative to read across a subset of pages
You want to compare results across all pages.
To use an inline survey here, your tech team will need to create a container/div.
You want to understand the UX of a specific page
You want to know more about the content on one specific page or part of a page.
You want to know about one piece of content or design & would like to put a survey right next to that piece of content.
Inline surveys must be targeted at one page at a time, and are best for asking about objects or content they are placed near.
You should only pick one!
Impression frequency capping is based on Served Impressions, not Viewed Impressions. Certain targeting rules, such as "On Page Behavior" targeting may impact frequency caps. Even if a survey isn't viewed due to unmet targeting conditions, the served impression still counts towards the cap.
You can set a delay based on how far down the webpage a user scrolls.
You might consider how your widget interacts with the user’s experience.
We recommend using between 10 - 20% scroll to trigger your survey unless you are hoping to trigger near a specific piece of content. For example, perhaps you want to make sure someone read a piece of content that is about 20% down the page. Then we recommend setting the scroll percentage at roughly 30%.
You can set a timed delay before your survey shows.
Consider how your widget interacts with the user’s experience. For example, if you’ve chosen an inline format, you probably do not need to delay showing the survey. If you’ve chosen an overlay, you may want to give the visitor a few seconds to absorb your page’s content before triggering your survey.
We recommend 5 seconds or less. On average visitors, spend about 5 seconds on a webpage, so we recommend keeping the time low.
You can trigger your survey based on the number of pages your visitor has seen. This can be a good option if you’d like to capture visitors that have come in through the homepage, but explored your site a bit.
We recommend 3 page views or less.
Pulse can trigger your survey by targeting a visitor’s exit behavior.
We recommend turning on the on exit behavior trigger when trying to capture visitors that are leaving your site.
You can set your survey to show immediately or on page load which means that the survey show as the page loads. This is a great option for inline surveys.
We recommend turning on the on page load trigger when your goal is to capture high response rates quickly.
You can use a button click or an object in view to trigger a survey. Pulse will work with your tech team. They will send an event, which Pulse will use to trigger your survey.
Pulse will work with your tech team. They will send an event, which Pulse will use to trigger your survey.
