Choose and publish the review state
Use the live campaign URL, or publish the page to the Unbounce test domain when stakeholders need a shareable pre-campaign URL.
Paste a browser-accessible live or test-domain URL, send one review link, and collect contextual comments on the landing page reviewers can actually open.












Loved by1,250+Agenciesand companies in 100+ countries
Unbounce supports internal previews, published test-domain pages, variant testing links and live campaign pages. BugSmash reviews the browser-accessible URL chosen for the review round.
Before sending an Unbounce page for review, four documented boundaries matter:
An internal Builder preview can be opened before publishing from the Page Overview, Smart Builder or Classic Builder. It remains part of the Unbounce workspace rather than a documented public review link.
Unbounce documents publishing a page to an unbouncepages.com test domain when you need a test URL to share before using the live campaign domain.
A variant-specific URL opens one page variant in the browser, but conversions are not tracked through that link. Do not use it to evaluate conversion results.
Saving changes does not replace the version visitors already see. Republish the page when the updated version should appear at its published URL.
How it works
Use the live campaign URL, or publish the page to the Unbounce test domain when stakeholders need a shareable pre-campaign URL.
Paste that browser-accessible URL into BugSmash and share the resulting review link without granting every reviewer access to the Unbounce Builder.
Use the attached browser, operating-system, viewport and page context to update the page, then republish so visitors and reviewers receive the new version.
Attach feedback to the browser-accessible Unbounce page instead of describing the location in a separate message.
Review desktop, tablet and mobile viewport sizes while keeping Smart Builder and Classic Builder preview behavior distinct.
Keep the page URL, browser, operating system and viewport size with each website comment.
Collect frontend feedback without assigning Viewer, Author, Admin or Owner access to every external stakeholder.
Use the intended campaign or testing URL and label variant-specific links clearly because those testing links do not track conversions.
Add the BugSmash Feedback Widget when reviewers need to comment inside an authorized, logged-in or stateful experience.
Choose a URL by whether it is published, what version or variant it opens, and whether reviewers can reach it in their browsers.
| Your URL | Review by URL | What to do |
|---|---|---|
| Live Unbounce campaign URL | Works | Paste the published campaign URL that visitors use. |
| Published unbouncepages.com test URL | Works | Use the published test-domain URL for stakeholder review before moving to the campaign domain. |
| Variant-specific test URL | Testing only | Use it to open a particular variant, but remember that Unbounce does not track conversions through variant-specific URLs. |
| Internal Builder preview or unpublished page | Not a shareable test URL | Publish to the test domain when reviewers need a browser-accessible URL outside the Builder workspace. |
| Page behind application login or SSO | Use the widget | A pasted URL does not bypass application login or SSO. Install the Feedback Widget inside the authorized experience. |
| Local or otherwise inaccessible work | Use an alternative | Publish an appropriate browser-accessible state, use the Feedback Widget in the environment, or provide a static export reviewers can reach. |
Add the BugSmash script to a frontend where reviewers already have authorized access when a logged-in or stateful experience cannot be reviewed from a pasted URL. Unbounce user roles remain separate from frontend feedback.
Keep page building, published-page review, variant testing and stakeholder approval distinct while comments stay attached to the rendered landing page.

Review copy, layout and responsive presentation on the live campaign or published test-domain page.
See how
Use one browser review link for stakeholder comments while keeping Unbounce account roles limited to people who need workspace access.
See how
Identify the reviewed URL or variant and receive browser, operating-system and viewport context before republishing.
See howRoute an actionable website comment to the team with its page, selected location, browser, operating system and viewport context preserved.
Context stays attached from comment to completion.
Send to your workflow
The destination changes. The context does not.
Keep the Unbounce page beside campaign images, PDFs, videos, presentations and other launch assets, with feedback and approval in one project.

product-launch.mp4
Up to 40% offThis year marked our strongest period of growth to date. Revenue climbed 42% year over year while our customer base expanded across eleven new markets, driven by continued investment in product.

Operational efficiency improved as automated workflows reduced manual review time by nearly a third. Looking ahead, we plan to double down on infrastructure, deepen key partnerships, and ship the roadmap our customers have been asking for.

Unbounce documents preview as an internal Builder workflow. For an external test link, publish the page to the unbouncepages.com test domain and share that published URL.
Paste a browser-accessible live or published test URL and send a focused review link without opening the Unbounce Builder to every reviewer.
