• As you probably know, in WordPress you can have two different URLs for the “WordPress Address” and “Site Address”. Where Site Address is the front end public side and the WordPress Address is for the backend.

    In our case, the backend site address is different, and has /wordpress/ on the URL, while the frontend is just the naked domain.

    When I try to connect Monster to Google, it does not choose the frontend stream URL, instead it automatically generates a new V4 property using the backend URL.

    I assume this is wrong because I’m not trying to track WP backend activity in GA, I need to track the frontend site.

    I think Monster is automatically checking the wrong URL, using the WP Address instead of the Site Address when generating the V4 property.

    Since there is no way to select the correct stream, I had to enter the V4 code and API secret manually. But doing this means that all the dashboard statistics break.

    Please use the correct URL for the frontend of a site when checking the stream!

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support Tim H

    (@tharg3)

    Hi @guyinpv

    Thanks for reaching out.

    Do you by any chance have a multi-site installation? We’ve tracked down an issue that causes this exact thing to happen. We’re currently investigating and testing for a resolution.

    I apologize for any frustration that may have been caused by this.

    You may try editing the URL of the data stream after you have authenticated to it within MonsterInsights. Do note, that you should not reauthenticate MonsterInsights once the URL has been changed, as you may run into an error.

    Please ensure that you keep MonsterInsights updated for any fixes that will be rolled out.

    Thanks,
    Tim

    Thread Starter Guyinpv

    (@guyinpv)

    It is not a multi-site, but I can see how that confuses the issue even more for you!

    WP has those annoying and confusing functions. home_url() is the reference to the “Site Addres” which is the correct address for the frontend. While site_url() returns the “WordPress Address” where the backend lives and where you can always add “/wp-admin” to it to reach the admin area.

    Anyway, I hope to see an update to help with this!

    Thanks!

    Plugin Support Tim H

    (@tharg3)

    Hi @guyinpv

    That you’re not using a multi-site setup has made things more interesting! We think we have a solution for this, but it’s going to take a little time to iron out the wrinkles.

    In the meantime, there is a stop gap in manually changing the URL that is found within the data stream itself, as mentioned in my first reply above. I totally understand how annoying that it might be to change, but luckily, it’ll only need to be done the once.

    If you do change the data stream URL let me know if you run into any issues.

    Thanks!
    Time

    Thread Starter Guyinpv

    (@guyinpv)

    Hi,

    Just checking in if there are plans for an update or what the status is.

    I did not do the thing you said and rename the URL because the code we’ve been using already has data in it. I’m just waiting if there is a patch to Monster so it will use the right frontend URL.

    Thanks!

    Plugin Support Michelle D.

    (@devmich)

    Hi @guyinpv,

    Thanks for checking in. I’m sorry for the delay here. Our team is still looking into this, but we don’t quite have an update to share yet. We appreciate your patience!

    Thank you.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Linking wrong stream URL when WordPress has two site URLs’ is closed to new replies.