lonfirebrand

Are you testing from multiple browsers or machines?
Google sets a cookie and assigns the user to a specific variant in a specific experiment.
I did hit that page from 3 different browsers and got the 1st variant in all three cases.
Looking at the console log, everything appears to be firing OK, just always getting 0 for chosenVariation.

Unfortunately, I don’t see the immediate problem.
GTM has been problematic for client-side experiments for a couple of versions now. (Why we have the little hack to run the experiment.)

Google is pushing everyone (and GTM users in particular) to Google Optimize.
It’s actually quite slick. You get a visual editor to build your content variations. If you’re already running GTM, it’s simple to set up and it works in a very similar fashion to GTM.

If you can’t use Optimize for some reason, let me know and we can try to dig deeper into what’s going in your particular install of the WordPress plugin.

If you’re using Google Tag Manager, it would be easy to add a new pageview event to generate an event in the same format as the ScrollDepth events.
So see which users didn’t scroll, you could create a custom segments of session that don’t include category “Scroll Depth.”

The percentages are hard-coded in the library.
You can use the Event Handler field to put in your code to send Google Analytics events.

But, 10% increments make it hard to see trends in your data. It is more common to track specific targets (end of article, footer) and see how often visitors see them.

Cool. Can’t take credit. We just make it easy to use in WordPress.
Rob Flaherty https://scrolldepth.parsnip.io/ maintains the main JavaScript library.

ScrollDepth posts regular GA Events.
You should be able to watch in the real-time event monitor and pick the event you wish to use as your goal.

Let me know if you have further questions.
Can’t create a walk-through today (pretty busy here), but if a tutorial is needed, it might make for a good blog post ??

I wonder if it’s fighting with your sticky header function:

jQuery(window).scroll(function() {
if (jQuery(this).scrollTop() > 1){  
	jQuery('header').addClass("sticky");
  }
  else{
	jQuery('header').removeClass("sticky");
  }
});

I just checked a few of our sites running ScollDepth in different configurations, and I’m not seeing any errors like that.

On the suspicion it might be a PHP name-space issue, I reviewed the code for possible conflicts.
There is only one global variable, and all the functions have a wp_scroll_depth_ prefix.
So we should be OK on name collisions.

• Are you running a third-party theme?
• Is there a link where we could see the issue?
• Do you have a list of other plugins you are running?

Thanks.

Looks like cs.marinsm.com is a tracker script from
https://www.marinsoftware.com/
Their page has your error. As well as multiple Facebook pixels. ??

MARINSM.COM does not have valid certificate. So that would be the ERR_INSECURE_RESPONSE when fetching from secure page.

So now I’m really puzzled and want to get to the bottom of this.
The ScrollDepth jQuery plugin is included in the WordPress plugin, so there’s no external links there that could have an incorrect protocol (ssl/non).
In fact, the only external links are in the documentation and instructions.

That’s everything I can think of. If you could provide more information or a links, I’d be glad to look further.

Hi, cbquest
Do you know what resource it’s trying to load?
I grepped the source for all our plugins for “marinsm” and that string does not appear.
I’m wondering if it might be a CDN thing.

Sorry for the delay in responding.

It’s not recommended to host analytics.js locally:
https://support.google.com/analytics/answer/1032389?hl=en

I don’t see the Google Analytics tracking snippet when I view source for that page.
I quick peek into the minified JS and don’t see any Analytics-related stuff there either.
But you should not load Google Analytics via an external JS script anyways.

If you’ve renamed the GA object, you may need to set that in the plugin settings.

I see you’re running smooth-scroll and infinite scroll plugins.
I’ve not tested it with these sorts of plugins. But it should work.

I’d double-check the installation to make sure Google Analytics and jQuery are installed.

Let me know if you have more information to help us track down the problem.
Thanks.

If you’re using Google Tag Manager, you might want to look into the timer trigger.
https://www.simoahava.com/gtm-tips/timer-trigger/

Interesting thought, darmenti.

I don’t actually maintain the scroll-depth javascript. Just the WordPress implementation.
The official home:
https://scrolldepth.parsnip.io/

And github issues:
https://github.com/robflaherty/jquery-scrolldepth/issues
You could certainly request the feature there.

Changing the noninteraction might have unexpected issues.
It seems to affect time-on-page and other numbers as well.

I don’t know a way to mix noninteraction and interaction events for scroll-depth.
If you’re more concerned about the bounce rate, you could turn off the percentage tracking and specify specific elements to trigger. (Visibility) Then you could set noninteraction to false. When a visitor scrolled to that element, it would prevent that page from being counted as a bounce.

ScrollDepth just tracks scrolling and visibility.
For tracking clicks, I recommend implementing Google Analytics via Google Tag Manager.
GTM has built-in methods for adding multiple forms of click and form tracking.

Sorry for the delayed response.

An item named “#postend” is an HTML element with an ID of “postend.”
Such as:
<div id="postend" class="footerthing">
This might be something in your theme, it could be created with a plugin, or it might be something you enter using the WordPress editor or Customizer.

To track that element, enter its CSS Selector (# for ID, . for class) in the dashboard setting under Elements to Track.

The naming requirements are just those of CSS selectors.

Excellent. I don’t have a GTM test site set up for this at the moment.
Would you be willing to try a beta for the next release?

Hi, Erik Molenaar,
Could I ask what method you are using to include your Google Analytics?
(Universal Analytics code, classic Analytics code, a plugin, Google Tag Manager, etc.)

Thanks so much

Thanks for the head-up, Erik Molenaar

It certainly could be our plugin.
According to what Jaren L saw on your site:

The variation needs to be chosen at least before your final GA tracking call. In my test visit to the site, the only GA tracking call occurred before the experiment API loaded, so the experiment was not included in the tracking beacon.

Have a look at this section for tips on synchronizing the API calls or what to do when you can’t guarantee the order: https://developers.google.com/analytics/solutions/experiments-client-side#implement-send

I didn’t notice this in our internal testing, but I’ll look into it.
It’s entirely possible the calls are being made in the wrong order.

If it’s something we’re doing wrong, I’m terribly sorry about that.
I’ll post our findings on this thread when I have an update or new information.