Manage Conversions

Use Manage Conversions to define the journeys Wheremore should measure, such as starting an enquiry and submitting a contact form. Open the Conversion paths page to create a path, configure its steps and actions, and control when it is enabled.

A path is an ordered journey. A step is a milestone on one tracked page. An action, also called a zone, identifies the element click or supported form submission that completes that milestone.

You configure the page and its actions together in the path builder. The captured page appears beside the step editor so you can select elements directly.

Before you begin

Use the workspace containing the website you want to measure. You need access to that website, and the required pages must be available in Manage Session Tracking.

For visitor activity to be recorded, the website needs the Wheremore pixel and the appropriate tracking and consent configuration. Creating a path does not install or enable website tracking.

Element picking requires captured HTML for the page. A screenshot alone does not provide selectable elements. If captured HTML is unavailable, you can configure a selector manually or use a supported HubSpot form submission identity, then test on the actual website.

Each path belongs to one Domain. Its steps can use different pages on that domain, and several steps can use the same page.

Find and review paths

The list provides All, Active and Disabled tabs, Search paths, and filters for conversion type and domain.

Each row shows the path name, type, step and page counts, configured value and controls. For example, 3 steps · 2 pages means three ordered milestones across two distinct tracked pages.

Select the path name or arrow to expand its steps. Select a step to edit it directly, or select Edit to open the path builder. Finish setup opens a path that still needs configuration.

The on/off switch shows whether the path is enabled. A Starts date or Ended warning identifies a schedule that is not currently open. An enabled path still needs working actions, an eligible schedule and visitor tracking before it can record conversions.

A lack of warnings in the list is not proof that tracking works. Review the actions in the builder and test the journey on the website.

Create a path

1. Select + New path.
2. Enter a name in Name this path, such as “Request a demo”.
3. Select Domain and choose the website. If only one domain is available, it is selected automatically.
4. Select Type and choose Lead generation, Purchase, Signup, Download, Subscription, Contact or Custom. For Custom, enter a custom conversion type.
5. Review Value, Active and More as described below.
6. Select Save draft to keep the path disabled, or continue adding steps.

A draft requires a path name, type and domain. It can be saved without steps, or with steps that do not yet have actions. New paths start disabled.

The domain is locked while the path has steps or a step editor is open. Choose the correct website before building the journey.

Value

Open Value and choose:

A fixed value must be non-negative. It is a configured amount, not a live order total.

Schedule

Open Active to set Active from and Active to. New paths default to today through the same date next year. The end date cannot be earlier than the start date.

The schedule and enabled status are separate. Check both when a path is not recording activity.

Description and target

Open More to add a Description and Target conversions. The target provides planning context for the reporting period; it does not change which visitor interactions complete the path.

Add a step and pick an element

1. Select + Add step 1, or the next numbered Add step button.
2. Under Choose page, search for and select a tracked page.
3. Wait for the captured page to load.
4. Under Action, select Pick element in the action card.
5. Move your pointer over the page preview. The picker highlights the element under the pointer.
6. Click the intended element. This selects it for tracking; it should not follow a link to another page.
7. Enter an Action name, such as “Header enquiry button”.
8. Review Category and subcategory. Picking may suggest values; change them if they do not describe the action correctly.
9. Under Check other devices, review the Mobile and Tablet selections using the workflow below.
10. Add a Description if useful, then enter the milestone name under Step name.
11. Select the numbered Add step button at the bottom of the editor.

The step now appears in the builder. It has not yet been saved to the path: use Save draft, Save path or Activate path when ready.

For an existing step, the confirmation button is Apply step. Cancel step changes discards the edits in that open step editor.

A step name is used in reports. If you leave it blank, it receives a name such as “Step 1”. An action name identifies the individual element or form; an unnamed action uses the step name when saved.

While picking

The editor collapses to give the preview more space. Use Cancel picking, or press Escape while the main builder has keyboard focus, to stop without cancelling the whole step.

On smaller screens, Editor and Preview switch between the two panels. Starting the picker opens the preview; selecting an element or cancelling returns to the editor.

After selection, use Change element to replace the main target. Use Reveal hidden for elements present in the capture but hidden behind a menu, tab or similar component. Revealing an element does not prove it is reachable in the real visitor journey.

The preview is a captured copy, not the live website. Third-party embedded frames cannot be explored as though their internal controls were ordinary elements in the captured page. For supported HubSpot forms, use submission tracking instead.

Check desktop, mobile and tablet selections

After choosing an element, Check other devices appears beneath the selection. Desktop shows Selected. Mobile and Tablet show whether each selection has been checked and whether it uses the desktop selection or a separate selection.

1. Select Check beside Mobile or Tablet. The preview switches to that device and turns off Reveal hidden.
2. Review the highlighted element in the captured layout.
3. Select Use this element if it is the intended control. If it is not, select Pick a different element, then click the correct control in the preview.
4. Confirm that the device shows Checked in preview. Select Review if you need to inspect it again.
5. Repeat for the other device and for each alternative action in the step.
6. Add or apply the step, then save the path to retain the selections.

Use this element requires exactly one visible match. If there is no visible match or several visible matches, pick the intended element instead. On smaller screens, the review controls also appear above the preview.

Not checked means the selection has not been confirmed in the preview; it does not mean tracking is disabled for that device. A device without a separate selection uses the desktop selection. A device with a separate selection keeps using it even if it needs review. Confirming the desktop match for Mobile or Tablet saves an explicit selection for that device, even when the underlying selector is the same.

Changing a device selector clears its confirmation. Testing an unchanged, previously checked selector preserves confirmation only when it still has one visible match. Testing alone does not mark an unchecked device as checked. If a later review finds no single visible match, check the selection again.

These checks concern the captured layout. Test the actual website too, especially responsive menus and mobile-only controls. HubSpot form submission uses the form ID and does not need separate device selections.

Classify each action

Category and subcategory help AI conversion analysis understand the action’s purpose. They describe each action, rather than the path as a whole.

For example, a navigation button might use Navigation and Button, while a submitted enquiry form might use Form and Submission.

1. Choose the category that best describes the action.
2. Choose its subcategory.
3. If you choose Custom, enter both the custom category and custom subcategory.
4. Check the classification separately for every alternative action.

You can save a disabled draft with classification still incomplete. Activation requires valid actions with Category and subcategory throughout the path.

Classification does not decide whether an action occurred. The selected element or supported form identity provides the matching configuration. Labelling a submit-button click as Submission does not turn it into proof of a successful form submission.

Add alternative actions to one step

Once the step has a usable action, select + Add alternative action to configure another way of completing the same milestone. Give each action a clear name and its own classification. Use its Edit or Remove control to manage it.

Any one of these actions completes the step. The visitor does not need to perform them all.

For example:

Putting the Name and Email fields in one step would make them alternatives. It would not mean that both fields must be filled in. A field click is also not proof that the field contains a valid answer.

One interaction advances a path by no more than one step. If the same element is used in two steps, a separate eligible interaction is needed for the later step. Review the duplicate-element warning before keeping that configuration.

Track a HubSpot form submission

Use this when the milestone is a successful supported HubSpot submission, rather than a click on its submit button.

1. Choose the page containing the form.
2. Open Advanced settings in the action card.
3. Under What counts, select HubSpot form submission.
4. If the form is detected in the capture, select Use beside it. Otherwise, enter its exact HubSpot form ID.
5. Review the action name, description and classification. Form and Submission are appropriate for a completed form submission.
6. Add or apply the step, then save the path.

The form ID is a UUID, for example 4a51e838-9f74-453b-acbd-557137ffe89c . It must be the ID of the intended HubSpot form, not its page address.

Submission tracking uses the form identity across Desktop, Tablet and Mobile; it does not require separate element selectors. A warning that the ID was not found in the capture is a reason to verify it on the website. A correctly formatted ID alone does not establish that submission tracking is working.

The installed Wheremore pixel must support the form event, tracking and consent conditions must be satisfied, and the form must be the next eligible step in the path.

Advanced selectors

Open Advanced settings for a click action to review its Desktop selector. A CSS selector is a rule identifying an element on a page, such as #enquire  or a[href="/contact"] .

Enter and test a selector

1. Enter the selector in Desktop selector.
2. Select Test.
3. Review the result and highlighted match.
4. If it matches the intended element, add or apply the step and save the path.

Found in captured page confirms a match in the capture. If several elements match, the preview uses the most visible match; narrow the selector if this could identify the wrong control.

Not found in captured page and No capture available do not establish whether the selector works on the current website. When offered, Use anyway lets you retain the selector without verification. Test it on the website before relying on the path.

An invalid selector must be corrected. Partly entered actions are not silently discarded: finish the selector or form ID, or explicitly Remove the unfinished action before applying the step. Saving an incomplete draft does not preserve a half-entered action inside an open editor.

Edit device selectors manually

Use the preview’s Desktop, Tablet and Mobile controls to inspect the captured layouts.

Tablet and Mobile use the desktop selector by default. In Advanced settings, select Use a different element when a layout needs its own target, then use Pick on mobile or Pick on tablet, or enter and test its selector. Use Check other devices to review an unchecked selection explicitly.

Select Use the desktop selector to remove the separate selection and its device-check confirmation. Review the inherited selection again through Check other devices.

Save, activate and disable

Finish or cancel the open step editor before saving the path.

Activation requires at least one step, usable actions and complete classification for every alternative action. Unverified selectors still need real-world testing even if the configuration can be activated.

If Mobile or Tablet selections are unchecked, the activation confirmation includes a reminder. This does not block activation: those devices use their current selection, or the desktop selection where no separate one is set. Review them and test the real journey before relying on the results.

Saving an enabled path temporarily disables it while its actions are saved. If saving fails, the path can remain disabled and some changes may already have been saved. Read the error, correct the affected step and use Retry saving. After a connection failure or interrupted save, reopen the path and check its saved details and enabled status.

To disable a path from the builder, select Enabled, then Save draft to persist that change. The list’s on/off switch saves a disable action directly. Switching on a disabled path from the list opens the builder so you can review it and select Activate path.

Use ← Conversion paths to return to the list. Unsaved edits can trigger a leave-without-saving warning. Save before refreshing, changing workspace or leaving the page if you want to retain the work.

Edit, reorder or remove saved work

Open Edit, then select the step you want to change.

• Drag step cards into the required order. With a step card focused, Alt + Up Arrow or Alt + Down Arrow also changes its position. Save the path afterward.
• Use Change beside the selected page to replace it. Changing the page removes the previous page’s actions when the path is saved; configure new actions for the replacement page.
• Use Remove within an action card to remove that alternative. Apply the step and save the path. Removing its only action leaves the step incomplete.
• Use Remove step to remove a milestone and its actions when the path is saved.
• Use More → Delete path…, or the list’s three-dot menu, to delete the path after confirmation. Deletion removes its configuration and cannot be undone. Previously recorded conversions are retained, although their deleted configuration is no longer available for editing.

Use More → Discard draft to abandon a new, unsaved path.

Test the real journey

1. Activate the path and confirm its schedule includes the test date.
2. Open the actual website in a fresh test session and satisfy its tracking and consent requirements.
3. Complete the steps in order, using the intended controls.
4. For HubSpot submission tracking, successfully submit the form; do not stop at clicking its button.
5. Allow background processing to finish, then review the conversion reports.
6. Repeat with alternative actions and device-specific targets where relevant.

A later step does not bypass an earlier incomplete step. Cookie-backed journeys can continue across eligible sessions when visitor identity is available. Cookieless progression stays within one session. See Understanding Conversion Tracking for identity and progression rules.

Troubleshooting

My domain or page is missing

Confirm the active workspace and website access. Add missing pages through Manage Session Tracking and allow capture to finish. The page-selection help opens that workflow in a new tab. Return to the page chooser, using Change beside the selected page if needed. If the list is still stale, save the draft and reload Manage Conversions.

I cannot see or use the picker

Open a step and choose a page. Look for Pick element inside its Action card. Picking is unavailable while the preview loads or when usable captured HTML is unavailable. If an element is already selected, use Change element.

Use Reload preview if offered. If only a screenshot is available, obtain an HTML capture or configure a manual selector. For a form-submission action, use the HubSpot form ID rather than the element picker.

The element is hidden, or clicking follows a link

Use Reveal hidden if the element exists in the capture but is hidden. Select Pick element before choosing the target. Picking should show a highlight and prevent navigation.

If the overlay is absent or a link changes the preview, stop and reload the captured page before trying again. Do not assume the element was selected. If it persists after reloading the page and current scripts, report the affected page and action.

Activation is unavailable

Apply or cancel the step currently being edited. Then check that every step has a valid action and every alternative has Category and subcategory. For Custom, complete both custom names. Also check the path name, type, domain, value and dates.

Existing actions could not be loaded

Reload the path before editing or saving. The builder blocks those operations when saved actions are missing from its loaded data, so that an incomplete view does not overwrite your configuration.

A previously working action no longer matches

The site may have changed since its last capture or since the selector was configured. Refresh the capture through Manage Session Tracking, reload the preview and use Change element, or correct and test the selector. Use Review or Check for Mobile and Tablet; within that device review, Pick a different element changes its target. Save the updated step and path.

I cannot confirm a device selection

Use this element is unavailable unless the current device preview contains exactly one visible match. Device checks turn off Reveal hidden so hidden controls do not count as visible matches. Select Pick a different element to choose the intended control. If the capture is missing or outdated, obtain a current HTML capture and reload the preview. Test the control on the live website as well.

No conversion appears after testing

Check the enabled status, schedule, installed pixel, tracking and consent conditions, and the order of completed steps. Verify the target selectors or exact HubSpot form ID on the real website. Allow background processing to complete before checking again.

Continue with analysis

Use the conversion reports to review completed journeys and step progression. See Conversion Path Flow for the journey view and Conversion Performance AI Analysis for interpretation of conversion evidence. Action names, descriptions and classification provide useful context, but they do not replace recorded visitor activity.