On google analytics traffic is registring as direct traffice

  • Posts: 58
  • Thank you received: 0
5 years 4 months ago #301143

-- url of the page with the problem -- : aditya.iconvm.com.au/
-- HikaShop version -- : 4.0.1
-- Joomla version -- : 3.9.1
-- PHP version -- : 7.2.7
-- Browser(s) name and version -- : Mozilla firefox

Hi Support,
I have this issue with hikashop google plugin all works well with google analytics plugin comes with Hikashop. Unfortunately the traffic source is coming as direct. Please refer to the screen shoots.
w = website
g = google
w1-g1
w2-g2
w3-g3
w4-g4

Any help be appreciated.

Thanks
Aditya

Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 26007
  • Thank you received: 4004
  • MODERATOR
5 years 4 months ago #301155

Hello,

Please details the "traffic" you're talking about and please provide details about your GA plugin settings.

Regards,

Jerome - Obsidev.com
HikaMarket & HikaSerial developer / HikaShop core dev team.

Also helping the HikaShop support team when having some time or couldn't sleep.
By the way, do not send me private message, use the "contact us" form instead.

Please Log in or Create an account to join the conversation.

  • Posts: 58
  • Thank you received: 0
5 years 3 months ago #302252

Hi,
Sorry for late reply,
We for traffic coming from facebook, paid clicks, etc.

Thanks
Aditya

Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 81540
  • Thank you received: 13071
  • MODERATOR
5 years 3 months ago #302280

Hi,

We replied in private by email in order to send you a modified version of the plugin.

Please Log in or Create an account to join the conversation.

  • Posts: 58
  • Thank you received: 0
5 years 3 months ago #302795

Hi Team,

The issue is that Hika Shop transactions are appearing as Direct transactions in Google Analytics.

This is being cause by multiple redirects occurring on the confirmation page. Can you please let us know how to remove this?

Images attached for reference.

Attachments:

Please Log in or Create an account to join the conversation.

  • Posts: 81540
  • Thank you received: 13071
  • MODERATOR
5 years 3 months ago #302889

Hi,

The redirects are normal and cannot be avoided.
But I don't see the link between the redirects and the fact that the transactions would appear as direct transactions ?
Also, did you try the new plugin version which now handles the campaigns ? It should normally help.

Please Log in or Create an account to join the conversation.

  • Posts: 58
  • Thank you received: 0
5 years 3 months ago #302908

Hi Nicolas,
Thanks for your response.

We tried the new version and it now logs the transactions as (Other) in Google Analytics. This is still incorrect. It needs to log whichever channel the user arrived by i.e Paid Social, Paid Search, Organic etc.

We need a work around for the redirect, it is not normal to have 2 redirects before the confirmation page. If it cannot be removed then is there an alternative? This issue is causing us to capture incorrect data in Google Analytics.

To answer your question, what is the link between redirects and direct transactions? Redirects can often keep GTM code from launching and properly identifying the traffic as having come from a paid search campaign. For example, if your ad leads to www.mydomain.com/index.html , but you've created a 301, 302, or JavaScript redirect from that URL to www.mydomain.com/page2.html , the campaign information that was originally appended to the landing page is lost upon redirection.

The browser is redirecting before the java script call from the code can be made.

For more information please refer to the following:
support.google.com/analytics/answer/1034383?hl=en
support.google.com/analytics/answer/1009614

Please Log in or Create an account to join the conversation.

  • Posts: 81540
  • Thank you received: 13071
  • MODERATOR
5 years 3 months ago #302920

Hi,

Your links explain that having a redirection on the landing page is a problem because the referer data and the utm parameters are lost when the javascript is loaded and so it doesn't from which source the user came as the utm parameters in the URL are not available anymore.
However, this is not a problem with what we're talking about here because the checkout pages are not landing pages.

Having redirects in a checkout (because of many things) is totally normal. For example, if you access a step of the checkout where you have a login/registration view and you're already logged in, it will redirect you to the next step of the checkout.
That's something which is done on any website's checkout, even Amazon.
Disabling the redirects will make the checkout wrok strangely for your customers and that's not something you want anyways.
Tracking the customers sohuld be feasible even with redirects as long as the redirect don't happen on the landing page which is apparently not the case on your website.
So again, I don't think that your problem comes from the redirects.
It must be something else.

Can you please check what data you have in the column order_payment_params of the hikashop_order table for the new orders you got since you updated to the 4.0.2 ?
You can check on that via your phpmyadmin.
That will tell us if the source is properly found and stored with the order so we'll at least know if the problem happens before the order is created (during the checkout), or after (when the order is confirmed and the data is sent to GA).

Please Log in or Create an account to join the conversation.

Time to create page: 0.073 seconds
Powered by Kunena Forum