Open the PBX Ideate dashboard
Go to Insights > Test Ideas to open the PBX Ideate dashboard.
Dashboard tabs
The dashboard organizes ideas into four tabs:- All Ideas: every idea PBX Ideate generates across your analyzed pages.
- Favorites: ideas you’ve starred.
- Used in Campaign: ideas you’ve already launched as an experiment.
- Archived: ideas you’ve archived.
Define project context
By default, PBX Ideate analyzes a page using only what it can see on the page itself. It has no way to know your brand voice, target audience, or business constraints unless you tell it. Project context lets you describe the parts of your brand that stay the same from analysis to analysis, written once and applied automatically to every future analysis for that project, without you repeating it each time you add a page.- Click the ⋮ menu next to Add page in the dashboard header.
- Select Project context.

- In the Define project context modal, select a project from the list on the left, or search for it by URL. Kameleoon labels a project Empty in the list until you save context for it.
- In the text box, describe your brand voice, target audience, offer and differentiators, vocabulary to use or avoid, and any hard constraints PBX Ideate should never break. You can enter up to 5,000 characters.
- Click Save context.
- Click Done to close the modal.

Add pages for analysis
Add one or more URLs to queue them for analysis.- Click Add page to open the Analyze pages modal.
- Enter a URL in the Page URL field.
- Select the version to analyze: Desktop (default) or Mobile.
- Optionally, enter an Analysis prompt to direct this specific analysis. You can enter up to 5,000 characters.
- Click Add to list to queue the page. It appears in the list of pages to analyze on the right, so you can queue several pages before running any analysis.
- Repeat steps 2 through 5 for each additional page you want to queue.
- Click Start analysis to launch the analysis for every queued page.

- Which region of the page to focus on, for example the hero call-to-action (CTA) or the content above the fold.
- Which visitor segment matters most, for example returning visitors or mobile users.
- The KPI you’re optimizing for, for example add-to-cart rate rather than page views.
- Which analytics inputs to include or exclude from the analysis.
- What you’ve already tested on this page, so PBX Ideate doesn’t repeat it.
- The main goal you want PBX Ideate to focus on.
- How bold you want the proposed variations to be.
Hypothesis generation isn’t instant. Analysis takes approximately 10–15 minutes, and the page card shows its status while the analysis runs.
Manage your pages
Each page card has a ⋮ menu with Analyze again and Delete. If a page’s analysis failed, Kameleoon replaces the menu with direct Retry and Delete buttons, since those are the only relevant actions at that point.
- Analyze again: re-runs the analysis on a page that already completed. Consumes 1 analysis from your quota, the same as a new page. Analyze again replaces all existing ideas for the page (including any you’ve favorited or archived) with the newly generated ones. You can’t undo this action, so favorite or otherwise record any idea you want to keep before you run it.
- Retry: re-runs a page whose analysis failed. Retry is free and doesn’t consume a quota credit.
- Rename: hover over the page title and click the pencil icon to edit it inline. Confirm with the checkmark icon or cancel with the X icon.
- Delete: removes the page and its ideas.
- Still in the 30-day cooldown: the tooltip reads “To keep results relevant, each page can be analyzed once every 30 days.”
- Basic plan’s annual quota exhausted: the tooltip reads “You’ve reached your annual analysis limit: you won’t be able to analyze this page until your quota resets or you upgrade to Premium,” with an Upgrade to Premium link.
Read your ideas
Kameleoon numbers each idea (Idea 1, Idea 2, and so on) so you can reference it in team discussions. An idea card shows:- Impact Score: a 0–10 score that Confidence AI generates from a model trained on more than 20,000 historical experiments. Five proportional dots next to the score (filled green, unfilled grey) give an at-a-glance read.
- High confidence (8–10): strong evidence, proven patterns, and a clear mechanism.
- Moderate confidence (5–7): a reasonable hypothesis that’s partially supported.
- Low confidence (1–4): a speculative mechanism or an unsupported pattern.
- Status badge (for example, Draft): shows the status of the idea’s linked campaign in PBX Build.
- A ⋮ menu with View details, Add to favorites, and Archive.
Favorite and archive ideas
Click the ⋮ menu on an idea card and select Add to favorites or Archive. The same menu also has a View details option, which opens the idea’s side panel, the same panel you get by clicking the card itself.
- Favoriting an idea keeps it in All Ideas and also surfaces it in Favorites.
- Archiving removes an idea from All Ideas and Favorites; it then appears only in Archived.
- Unarchiving returns an idea to All Ideas, and back to Favorites too if you’d favorited it before archiving.
- You can’t favorite an idea directly from the Archived tab. Unarchive it first, then favorite it.
Test idea vs. hypothesis view
Use the view toggle above the idea list to switch how ideas group:
- Test idea (default): every idea appears as its own card.
- Hypothesis: ideas group under the hypothesis they support, with an explicit if-then structure. The page thumbnail appears once, at the hypothesis header level, using the first idea’s screenshot. Nested idea cards underneath don’t repeat the thumbnail.

Filter your ideas
Open the filter sidebar to narrow the idea list by:- Project.
- Device version (Desktop or Mobile).
- Campaign status (whether you’ve already used the idea in a campaign).
- Impact Score (a range slider with numeric inputs for precise filtering).
Explore an idea in detail
Click an idea card to open its side panel. The panel has three sections. Hypothesis: the full reasoning behind the idea, as an if-then statement covering the optimization focus (Lever) it addresses, the behavioral insight behind it, the UX observation that surfaced it, and the best practice that supports it.

