Global Targeting
Last updated
Last updated
You can enable user-level frequency capping to restrict the number of times a single individual is shown a survey. You can set the maximum number of impressions and the period for which the user won’t exceed the max number.
Check the box and then enter the number of maximum impressions to show and the number of days, hours or minutes (select time interval via the dropdown menu).
At the end of the period, the counter resets and the user will be eligible to see survey impressions again.
If you'd like a specific survey to ignore the frequency capping rules set at the account-level, you can check "Ignore frequency cap" in the survey's targeting configuration (in the "Advanced Settings" section). Please see our Targeting section for more details.
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.
Assumptions for this table:
Client Key is populated (e.g., upon login or on each pageview once the user was identified)
Frequency capping is turned on with a max of 1 impression per 7 days
You can also create a list of IP addresses to block on your account. This feature is typically used if you don’t want internal employees of your company answering surveys.
Pulse Insights will prevent Live surveys from displaying on those IPs for any survey in Live status. Draft surveys can still display while in Preview Mode so you can still QA surveys.
If you are using direct submission links and redirecting the user to a landing page (e.g. for surveys in an email), then you must whitelist the domain of the landing page here.
Type in the domain(s) you wish to whitelist (1 per row)
Click "Update"
| Scenario | Description | Behavior & Explanation |
|---|---|---|
Single User, Single Browser/Profile, But Two Accounts/Login IDs
User logs into Account 1
Device UDID is set to ABC
Client Key is set to 1234
User is served an impression.
User subsequently logs into Account 2 within the 7-day frequency cap period.
Device UDID is still ABC (same browser profile)
Client Key is set to 5678 (second account/login id)
The user is not eligible to be served another impression within the 7-day period, even with a second login/id.
The frequency cap considers both Client Key and Device UDID. Since the Device UDID has already been served an impression, no further impressions are allowed until the cap resets.
User logs into Account 1 with Device 1
Device UDID is set to ABC
Client Key is set to 1234
User is served an impression.
User subsequently logs into Account 2 with Device 2
Device UDID is set to DEF
Client key is set 5678
On the second login (different device, different account), the user is eligible to be served a second impression.
Because the user has two different client keys (1234 vs. 5678) and two different Device UDIDs (ABC vs DEF), the user is eligible to receive a second impression, even within the 7-day frequency cap.
Single User, Two Browsers/Profiles, Single Account/Login ID:
User logs into Account 1 on Device 1
Device UDID is set to ABC
Client Key is set to 1234
User is served an impression
User subsequently logs into Account 1 on Device 2
Device UDID is set to DEF
Client Key is set to 1234
On the second login (different device), the user will not be eligible to be served an impression.
The user has already met the frequency cap. The frequency cap is enforced because the Client Key remains the same across both devices, even though the Device UDID is different.
Single User, Two Separate Pulse Insights Platform Accounts (e.g., To Manage Multiple Websites Within A Single Company):
User 1 logs into Site A (Pulse Insights Console Account A).
Device UDID is set to ABC
Client Key is set to 1234
User is served an impression
User 1 logs into Site B (Pulse Insights Console Account B).
Device UDID is set to XYZ
Client Key is set 9876
User is served an impression
On the second login (different website, different console account, different UDIDs, different client keys), the user will be eligible to be served an impression.
Two separate console accounts have independent frequency cap settings and evaluations. Two separate websites will assign two separate Device UDIDs to the user. Two separate accounts/Login IDs will have two separate Client Keys for the user.
Single User with Long Time on Page Targeting Criteria Set:
User 1 logs in and is eligible for the survey but does not meet the time-on-page requirement.
Device UDID is set to ABC
Client Key is set to 1234
User is served an impression on page load.
Because the user didn’t meet the time requirements, the user does not see the survey.
User 1 logs in again within the 7-day window. On the second login, the user will not be eligible to be served an impression.
Because the user has met the frequency cap already, the user will not be eligible for a second impression until the period resets. Frequency caps are based on served impressions, which means that the user can meet the cap even if the user didn’t see the impression.
Two Users, Shared Device:
User logs into Account 1 on Device 1
Device UDID is set to ABC
Client Key is set to 1234
User is served an impression
User 2 logs into Account 2 on the same device (including browser profile)
Device UDID remains ABC
Client Key is set to 5678
On the second login (same device), User 2 will not be eligible for an impression on that device.
The user has already met the frequency cap. Because frequency capping evaluates both Client Key and Device UDID (ABC, which is the same across both devices), the user is ineligible to receive a second impression within the 7-day period.
Single User, Two Devices, Two Accounts/Login ID:
