General Settings

Order Total Logic​

↑ Back to top

The order total logic controls the output of the order total value, which is sent to the marketing pixels (Google Ads, Facebook Ads, etc.). This setting excludes statistics pixels, such as Google Analytics, that will always receive the full total cart value, including taxes and shipping.

Order Subtotal (default)​

↑ Back to top

The order subtotal represents the total minus the shipping costs, taxes, discounts, and if available, fees like PayPal or Stripe fees.

It is the default setting in the plugin.

Order Total​

↑ Back to top

The order total is what the customer paid and includes the shipping costs and taxes.

Profit Margin

↑ Back to top

The Pixel Manager will calculate the profit margin on the order and send that to the marketing pixels. It is the order total paid by the customer, minus shipping fees, taxes, discounts, and cost of goods for each product.

If the cost of goods has not been set on a particular product, the Pixel Manager will use a value of zero for that product.

Maximum Compatibility Mode

↑ Back to top

This mode detects specific settings that cause issues with the front-end output of this plugin and protects the output from being altered.

Over time and through many support requests we found certain third-party plugins that cause issues with our plugin. One common example is caching and minification plugins that are adjusting the output of our plugin, in some cases breaking the scripts and stopping the tracking pixels from working.

Obviously, this leads to hours of debugging, many support requests, and as a consequence, unhappy users.

Through thorough analysis, we identified the exact settings in those third-party plugins which cause those issues. The Compatibility Mode changes those settings to values that make the third-party plugins compatible with our plugin. We only do this with settings that are not essential to the working of the third-party plugins. In cases where we would have to disable essential functionality of the third-party plugins, we would not do this through the Compatibility Mode, but through displaying a warning notification in the back-end. The user would then have to decide how to proceed.

Exclude User Roles from Tracking

↑ Back to top

With this pro feature, you can exclude certain users’ roles from being tracked by the pixels.

PMW detects custom roles that were added to the shop. Those can be excluded from tracking too.

Order List Info​

↑ Back to top

The order list info displays information related to the Pixel Manager on the order list page.

Pixel Manager Column: The Pixel Manager column shows for which orders the conversion pixels have fired (green checkmark) or not (red circle). If you see two dots, then that order is not included in the analysis because the order creation was not triggered by the customer himself. That can happen when a shop manager creates an order for a customer.

Pixel Manager Filter: The Pixel Manager filter shows all orders of the past 30 days where the conversion pixels haven’t fired. It can help to detect a pattern and determine the cause, and why the conversion pixels haven’t fired.

Find out more about possible reasons, why the conversion pixels didn’t fire in this support article.

Scroll Tracker

↑ Back to top

The Scroll Tracker dispatches a scroll event when a certain scroll depth (in percent) is reached.

The scroll depth thresholds setting is a comma-separated list like so: 25,50,75,100

Currently, the scroll depth is automatically sent to Google Analytics (GA3 and GA4) as a custom event with the name scroll and the value of the scroll depth that has been reached.

Subscription Value Multiplier

↑ Back to top

By default, the conversion value for subscriptions transmitted to the paid ads conversion pixels only contains the value of the first subscription. But, a subscription may yield a much higher effective conversion value or customer lifetime value (CLV) because a subscription usually creates more than one automatic order in the future. Unfortunately, all those future conversion values can’t be captured by the paid ads conversion pixels because they don’t require checkout by the visitor using the browser.

Therefore, we implemented the subscription value multiplier into the Pixel Manager. It multiplies the subscription value to closely match the effective conversion value or customer lifetime value generated by a subscription.

The default value of the setting is 1.00. You can set any multiplier larger than 1.00.

How to determine an appropriate multiplier​

↑ Back to top

There is no general multiplier that can be used for all shops. The multiplier entirely depends on how long a subscription lasts on average for a specific shop.

A good approach is to average how often a subscription renews before the customer cancels it.

To calculate this, take the total count of subscription orders (initial and renewal orders) and divide it by initial subscriptions. This will give you an average number of times a subscription is renewed. And that is the number that you can use as a multiplier. Feel free to use a slightly lower number to stay on the more conservative side to account for fluctuations in the effective renewal multiplier over time.

Lazy Load the Pixel Manager

↑ Back to top

How it works​

↑ Back to top

When enabling lazy loading for the Pixel Manager, all tracking scripts will only be loaded after the first visitor interaction with the website. This will generally improve page speed scores on various page speed measuring services.

First visitor interaction is typically one of the following:

• Pressing a button on the keyboard
• Moving the mouse
• Using the mouse wheel
• Clicking a mouse button
• Touching a mobile phone screen

Once an interaction is detected on each page, all tracking scripts load.

Exceptions​

↑ Back to top

Pages

The exceptions are all cart and checkout pages. To ensure tracking works 100% accurately once a visitor enters the checkout funnel, the tracking scripts always get loaded immediately on those pages (cart, checkout, purchase confirmation pages)

Google Optimize

If you’ve enabled Google Optimize, then PWM Lazy Loading will not be enabled unless the Google Optimize anti-flicker snippet is activated as well.

The reason is, otherwise the PMW Lazy Loading will delay the loading of any running Google Optimize experiments on the page. This would visually load the pages before the experiments can be applied which would render the experiment results useless.

Risks​

↑ Back to top

Slow loading

There is a small risk that events don’t get tracked before or while tracking scripts get loaded.

We have minimized the risk wherever possible.

The user interaction detector should capture 100% of all interactions. We compiled the interaction detector with options that should make it work under the broadest range of conditions. But, there is a chance that under rare conditions (e.g., very old browsers), it doesn’t always work.

Loading the scripts introduces a short tracking delay (until the tracking scripts are fully loaded). Without any optimizations tracking scripts already load quite fast. The Pixel Manager preloads and caches the tracking scripts to improve load times even further.

JavaScript optimizers might break the lazy loader. We have tested the lazy loader with a range of JavaScript optimizers, and it works well. But not all JavaScript optimizers are the same, and we can’t test all of them. So you should test lazy loading the Pixel Manager in your setup properly before relying on it.

Google Optimize

Test​

↑ Back to top

Please test lazy loading the Pixel Manager in your setup properly. We have tested the lazy loader under various conditions, but we can only account for some possible setups. So you need to test the lazy loader on your system and setup before relying on it.