A live Audience project is already in field. Completes are arriving, but slower than the study needs. Closing the project and starting over would split the report. Waiting it out would miss the deadline. Sample Boost is the control for that moment: invite more respondents without relaunching, and keep every complete in the same Audience project.<\/p>\n\n\n\n\n\n
Once an Audience project is live, the remaining completes still have to arrive under the original targeting, qualifications, quotas, and survey settings. Creating a second Audience project to speed things up splits reporting, close actions, and later reconciliation<\/a> across two records. Closing the live project so you can start again throws away the operational advantage of staying in field. The practical problem is not a lack of settings. It is the lack of a way to add respondent traffic while the original Audience project stays open.<\/p>\n\n\n\n Teams then choose between three weak options: wait, relaunch, or manage leftover completes as a separate Audience project. None of those keep one live project, one report, and one close action.<\/p>\n\n\n\n Research operations teams asked for a way to finish remaining completes on a live Audience project without creating a second project to manage. The product decision was to keep the researcher on one Audience project and let the platform invite more respondents in the background.<\/p>\n\n\n\n That is why Sample Boost, also called Project Push, creates another project in the backend for only the remaining required responses. Existing collection continues. Responses are combined in the original Audience project. Closing that Audience project closes every associated backend project with it.<\/p>\n\n\n\n Sample Boost lets you increase traffic to a live Audience project without closing or relaunching it. You start the action from the Projects page with Push Project, then choose whether to keep the current CPI or raise it.<\/p>\n\n\n\n What does not change is the Audience project you manage. Targeting, qualifications, quotas, and survey settings stay the same. CPI changes only when you select Push at Higher CPI. You do not get a second Audience project, a split report, or a new close workflow.<\/p>\n\n\n\n Use Sample Boost when the project is progressing slowly, is not collecting quickly enough, or you want remaining completes sooner while keeping the same project settings.<\/p>\n\n\n\n After you confirm a push, the platform creates another project in the backend. That backend project uses the same targeting, qualifications, quotas, survey settings, and other configurations, and it requests only the remaining required responses. You keep working in the original Audience project while associated backend projects collect in the background.<\/p>\n\n\n\n Push at Same CPI launches a backend project at the current CPI and the same settings. It is available for the first two pushes on a project.<\/p>\n\n\n\n Push at Higher CPI launches a backend project at a CPI that is at least 10% higher than the current CPI. For example, if the current CPI is $2.00, the minimum for a higher-CPI push is $2.20.<\/p>\n\n\n\n After the first two pushes, Push at Same CPI is no longer available. Any further boost must use the higher-CPI option.<\/p>\n\n\n\n The original Audience project stays active. Associated backend projects keep collecting until you close the Audience project. Responses from all of those backend projects are combined in the same Audience project. Audience also tracks the backend project associated with each response, so reconciliation can still run after field.<\/p>\n\n\n\n A specialized-sample study is live and behind pace on remaining completes. The research operations manager does not want a second Audience project and does not want to change targeting. They open the Projects page, hover over the live project, and click Push Project.<\/p>\n\n\n\n If this is one of the first two pushes, they can choose Push at Same CPI and keep the current price. If those two same-CPI pushes are already used, they choose Push at Higher CPI and set a CPI at least 10% above the current value. After they confirm, the platform creates another project in the backend for the leftover completes. Reporting stays in the original Audience project. When the team later closes that project, every associated backend project closes with it.<\/p>\n\n\n\nWhy did we build Sample Boost?<\/strong><\/h2>\n\n\n\n
What is Sample Boost and what does it change?<\/strong><\/h2>\n\n\n\n
How does Sample Boost invite more respondents?<\/strong><\/h2>\n\n\n\n
How do you start a push from the Projects page?<\/h3>\n\n\n\n
\n
What is the difference between same CPI and higher CPI?<\/h3>\n\n\n\n
What happens after you confirm the push?<\/h3>\n\n\n\n
What does Sample Boost look like on a live project?<\/strong><\/h2>\n\n\n\n