How to Set up Goal Tracking on Wisepops?

Official setup documentation checked September 6, 2026. The validation checklist below is editorial guidance, not a client implementation report.

The thank-you page (or whatever page completes the goal) must have the same Wisepops setup code, on the same website in the app. Cross-subdomain works if the code is shared. The requirements specify the same domain and support cross-subdomains, while later troubleshooting mentions multiple domains. Confirm a cross-domain implementation with Wisepops before relying on it; shared code alone does not prove it works.

Step 1: attribution

Open Settings → Goals. Set:

• currency
• attribution window (how long after a campaign interaction a conversion still counts)
• the model (display vs click). See how conversions are attributed for the vendor's rules.

Step 2: create a goal

Open Goals in the left menu → Add goal.

URL method. Good for thank-you / order-confirmation pages. You enter a string. The conversion fires if the page URL matches or contains that string, so checkout fires on /eshop/checkout and /sales/checkout. Optional: a fixed revenue value. Same value for every conversion.

JavaScript method. Use this when the amount varies, or the conversion happens without a page change. Name the goal, pick JavaScript snippet, save. Wisepops shows the snippet. Replace the placeholder revenue: 100 with a static number or a dynamic value from your thank-you page. You can fire it through Google Tag Manager.

Shopify app. Orders and revenue are tracked automatically. Skip to step 3 if that is the only goal.

Step 3: assign the goal to a campaign

One goal can sit on many campaigns. One campaign can have only one goal.

• Popups, bars, embeds: Goal icon in the left menu of the editor.
• Notifications: Goal step at the top of the notification editor.

If goal tracking is off on the campaign, conversions will not attribute even when the snippet fires. Events that happened before the goal was saved do not backfill.

Validate the goal before relying on reports

Use a controlled test and record the goal, campaign, action time and expected value. Do not assume a request in the browser’s Network panel proves correct campaign attribution. Inspect the configured goal and resulting report too.

A URL containing checkout can identify the start of checkout rather than a completed order. Choose a success condition that represents the event you actually want to measure. For JavaScript goals, use the snippet generated for your goal and replace example revenue values before launch.

If revenue is missing, check campaign goal activation, saved configuration, setup-code coverage and the attribution window. Record any ambiguity about repeat events or domain scope for support rather than changing several settings at once.

A recorded or attributed conversion does not establish incremental impact. Use an appropriate comparison design when the question is whether the campaign caused additional outcomes.

Legacy wisepops("goal") users: create a new goal in the app, then remove the old snippet once the new analytics look right.

Related: A/B tests, Wisepops help.