Manage Conversions

Manage Conversions lets you define the customer journeys Wheremore should measure and the page interactions that complete each stage.

Overview

Configuration has three parts:

1. Define Path Info — name the journey, choose its type, website, value and schedule.
2. Add Pages — create and order the required steps.
3. Configure Zones — identify the element or supported form submission that completes each step.

A path is ready for reliable measurement only when every required step has at least one working zone.

Access and scope

Manage Conversions is workspace- and website-aware.

• The active workspace controls which websites are available.
• A path belongs to one selected website.
• Step pages must be tracked pages belonging to that website.
• The user must have access to the website in the active workspace.
• Markets and search groups are not used.

Changing workspace reloads the available websites and paths.

Before you begin

You need:

1. The website assigned to the active workspace.
2. The Wheremore pixel installed.
3. Tracking enabled.
4. Cookie or Cookieless mode selected.
5. Every required page added in Manage Session Tracking.
6. Current captured HTML for the pages you will use.

If a page is missing from the selector, add or import it through Manage Session Tracking, allow capture to finish, then return to Manage Conversions.

Quick start

1. Open Manage Conversions.
2. Confirm the active workspace.
3. Select Create New Path.
4. Enter the path name and conversion type.
5. Select the website.
6. Add and order the conversion steps.
7. Choose Zero Value or Fixed Value.
8. Set the status and active dates.
9. Save the path.
10. Expand its conversion steps.
11. Select Configure zone or Edit zone for each step.
12. Pick and test the relevant element, or configure a HubSpot form submission.
13. Save each zone.
14. Confirm the path reports All zones configured.
15. Test the journey on the live website.

Create a conversion path

Select Create New Path to open the path drawer.

Path Name

Enter a clear internal name, such as:

• Newsletter signup
• Request a demo
• Product enquiry
• Completed checkout

The name is used in conversion reports and should describe the completed outcome.

Primary Conversion Type

Choose the closest type:

• Lead Generation
• Purchase
• Signup
• Download
• Subscription
• Contact
• Custom

When using Custom, enter a custom conversion-type name.

Website

Select the website on which the journey occurs. The website must be available in the active workspace.

A path cannot contain steps from different websites.

Target Conversion

Use Target Conversion to store the path’s intended conversion target where applicable. It provides planning context and does not itself change how events are detected.

Description

Describe what the path measures, who it is for and what counts as success. This helps other users understand why the path exists.

Add conversion steps

Each step needs:

• a clear step name; and
• one tracked page.

For example:

More than one step can use the same page when different elements represent different milestones.

Add a step

1. Enter the step name.
2. Select the tracked page.
3. Select Add Step.
4. Repeat for each required stage.

Reorder steps

Use the step controls to place the steps in the order visitors must complete them.

The order matters. Wheremore only advances an active path when an interaction matches its next incomplete step.

Save the updated path after reordering.

Remove a step

Removing a saved step also removes zones associated with that step. Historical conversion records can retain limited identifiers even when their original configuration is deleted.

Review the path before confirming removal.

Choose a value source

Zero Value

Choose Zero Value for non-revenue goals. Wheremore records the conversion with a value of zero.

Fixed Value

Choose Fixed Value when every completed path should receive the same configured value.

Enter a non-negative amount and select:

• USD
• EUR
• GBP

The configured amount is not a live order value.

Status and schedule

Active

An active path can process eligible interactions during its date range once its zones are configured.

Inactive

An inactive path retains its configuration but does not advance from new activity.

Use Inactive while building or testing a path.

Active From and Active To

Set the dates during which the path should accept progression. The end date must be on or after the start date.

Progress is evaluated within the active schedule. Starting a new schedule provides a clean measurement window for the path.

Save and review the path

After saving, the path card displays:

• status;
• number of pages or steps;
• primary conversion type;
• value source and value;
• active date range; and
• zone-configuration status.

Expand Conversion Steps to review the ordered milestones.

All zones configured means every step has at least one zone. It does not prove that every selector or form event works on the live page; complete the testing process as well.

Configure a conversion zone

Select Configure zone for a step, or Edit zone for an existing configuration.

The Zone Editor opens the captured page and provides Desktop, Tablet and Mobile views.

Zone Name

Use a name that describes the action, such as:

• Main demo button
• Pricing enquiry link
• Newsletter submission
• Checkout confirmation

Description

Explain what the visitor is expected to do and why the action represents this step.

Category and Subcategory

Categories help describe the interaction, such as Navigation, Content, Form, Media or Ecommerce.

Category and subcategory are optional. Choose Custom when the available labels do not fit, then enter the custom name.

These labels provide reporting context; the selector or form identity performs the actual match.

Pick a page element

For a click-based zone:

1. Select Desktop.
2. Choose Pick element.
3. Select the intended element in the captured page.
4. Review the generated selector.
5. Select Test.
6. Repeat for Tablet or Mobile when those layouts use a different element.
7. Save the zone.

Desktop, Tablet and Mobile

Desktop is the base selector. Tablet and Mobile can inherit it when the same selector works across layouts.

Use a device-specific selector when:

• responsive markup changes;
• navigation changes into a mobile menu;
• a different button is rendered;
• the element moves into a different component; or
• the inherited selector fails its test.

Reveal hidden

Use Reveal hidden when the target exists in the captured page but is hidden behind a menu, tab, modal or responsive state.

Confirm that the element is also reachable during a real visitor journey.

Manual selectors

You can enter a CSS selector manually when the picker cannot identify the correct element.

Use the most stable selector available. Prefer a unique ID or durable data attribute over a long position-dependent selector.

Always test a manual selector before saving. A selector can stop matching after a website redesign.

Use multiple zones for one step

A step can have several zones when different actions should complete the same milestone.

For example, a contact step might accept:

• the header Contact button;
• an in-page Request a demo button; or
• a mobile sticky enquiry control.

Each is saved as a separate zone record with its own element, path and step context.

Do not duplicate an identical zone. Wheremore absorbs a true repeated submission of the same zone configuration, while a genuinely different selector can be saved as another zone.

Any matching zone can complete the step, but one interaction advances that path by no more than one step.

Track a HubSpot form submission

Use Form submission tracking for a supported embedded HubSpot form when its fields or submit button are not directly or reliably selectable.

Find the HubSpot Form ID

The Form ID is a UUID in this format:

4a51e838-9f74-453b-acbd-557137ffe89c

It can usually be found in the HubSpot form embed configuration or the form’s HubSpot settings.

Configure the form zone

1. Open the step’s Zone Editor.
2. Enter the zone name and description.
3. Enable Form submission tracking.
4. Enter the HubSpot Form ID.
5. Save the zone.

Wheremore applies the form identity across Desktop, Tablet and Mobile.

The zone matches a supported completed HubSpot submission event. It does not treat an ordinary click on the submit button as proof of successful submission.

HubSpot requirements

• The Wheremore pixel must be current and active on the page.
• The tracked page must contain the intended HubSpot form.
• The Form ID must be the exact UUID for that form.
• The visitor must satisfy the website’s tracking and consent rules.
• The path must be active and the form zone must be the next eligible step.

Edit or delete a zone

Edit

Use Edit zone to change its name, description, classification, device selectors or HubSpot Form ID.

Reload the path after saving and confirm the details and selectors persist.

Delete

Deleting a zone removes that matching configuration. If it was the step’s only zone, the path is no longer fully configured.

Deleting one zone does not delete other different zones assigned to the same step.

Test a path

Use a fresh browser session and follow the real journey.

Cookieless test

Complete every step in one session.

Cookie-mode test

After granting the required consent:

1. complete an early step;
2. close or end the session;
3. return in a later eligible session; and
4. complete the remaining steps.

Allow background processing to finish before checking reports.

Test Desktop and Mobile separately when their selectors differ.

Recommended workflow

1. Create the path as Inactive.
2. Add only meaningful milestones.
3. Put the steps in the required order.
4. Configure Desktop selectors first.
5. Test inherited selectors on Tablet and Mobile.
6. Add device-specific selectors only where needed.
7. Use HubSpot submission tracking for supported embedded forms.
8. Add alternative zones where either action legitimately completes the same step.
9. Confirm every step has at least one zone.
10. Activate the path and test it on the live website.
11. Review the first events before relying on conversion-rate reporting.

Troubleshooting

No websites appear

• Confirm the active workspace.
• Confirm the website is assigned to it.
• Confirm your account has website access.

A page is missing

• Add it in Manage Session Tracking.
• Confirm it belongs to the selected website.
• Allow HTML capture to complete.
• Reload Manage Conversions.

The picker cannot load the page

• Confirm captured HTML exists.
• Refresh the page capture in Manage Session Tracking.
• Confirm the live page is publicly reachable.
• Check whether the page depends on scripts that are unavailable in the safe editor preview.

The selector test fails

• Reveal hidden content if appropriate.
• Pick the element again.
• Prefer a stable ID or data attribute.
• Add a device-specific selector where responsive markup differs.
• Refresh the captured page after a website redesign.

The path does not show All zones configured

Expand the steps and find one without a saved zone. Configure at least one zone for every step.

A HubSpot submission is not recorded

• Confirm Form submission tracking is enabled.
• Confirm the Form ID is the exact UUID.
• Confirm the current pixel is installed.
• Confirm tracking and consent conditions are satisfied.
• Confirm the path is active and within its date range.
• Confirm the form step is the next incomplete step.
• Allow the conversion processor to run.

A later step was not accepted

The earlier required step may be incomplete. Paths advance sequentially, so completing a later page or zone does not bypass an earlier step.

A Cookie-mode path does not continue later

• Confirm the visitor granted the required consent.
• Confirm Cookie mode is enabled.
• Confirm the durable visitor cookie remains available.
• Confirm both visits used the same website identity context.
• Confirm the path remained active.

A Cookieless path does not continue later

This is expected across different sessions. Complete the journey in one session or use Cookie mode where appropriate.

The path stopped after changing tracking mode

Mode changes can make active paths inactive. Review the path against the new identity model and reactivate it deliberately.

What should I do next?

• Read Understanding Conversion Tracking for identity, progression and attribution concepts.
• Use the Conversions Dashboard to review results.
• Use Session Replay to inspect unsuccessful journeys.
• Use Page Engagement around zone locations.
• Use User Behaviour Analysis for aggregate friction patterns.
• Use the UTM URL Builder for consistent campaign attribution.