How to Set up Goal Tracking on Wisepops?

The 2023 version of this page only documented wisepops("goal", name, value). That snippet still exists as the JavaScript method. It is not the whole feature.

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. Cross-domain does not, unless both properties are the same Wisepops website.

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.

How do you know it is working?

On the JS path, Chrome DevTools → Network, look for a request whose query includes the goal event (the older docs looked for _.gif?e=g). Reporting lives in the campaign analytics, not a separate "Reporting" mystery page. If revenue is zero despite purchases: confirm the goal was on, the thank-you page has the same setup code, and the attribution window covers the purchase.

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.