Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with Fresh URL & HubSpot #13

Open
Corgin opened this issue Nov 29, 2017 · 8 comments
Open

Issue with Fresh URL & HubSpot #13

Corgin opened this issue Nov 29, 2017 · 8 comments

Comments

@Corgin
Copy link

Corgin commented Nov 29, 2017

Hello,

I am using the Wistia Fresh URL on our HubSpot hosted website but it seems to be interfering with the HubSpot analytics. Is there any way of checking for definite whether or not it is interfering? And is there any way to solve it?

I have used to following script to ensure it waits for HubSpot to read the UTM parameters but it doesn't seem to make any difference.

<script> var _freshenUrlAfter = ['googleAnalytics', 'hubspot']; </script> <script src="//fast.wistia.net/labs/fresh-url/v1.js" async></script>

Be glad if you could help...
Gavin

@mrdavidjcole
Copy link
Contributor

Hey Gavin, thanks for the report! Can you share a little more info about what's going wrong? It would be super helpful if you could share an example URL (including the UTM params that you expect HubSpot to do something with).

@Corgin
Copy link
Author

Corgin commented Dec 1, 2017

Hello,

I ran a test yesterday by clicking on this post we published to LinkedIn - https://www.linkedin.com/feed/update/urn:li:activity:6341917271912386560/

I clicked on the link and doubled checked the UTM parameters were there when it opened it up in Chrome. They then disappeared once the page had finished loading.

Before I clicked on the link, there were 8 visits from direct traffic and 1 from organic search. When I checked again later, there was 9 direct traffic and 1 organic search. However, there should have been 1 showing for Social Media > LinkedIn.

Hope this helps,

Gavin

@mrdavidjcole
Copy link
Contributor

Hey @Corgin, it looks like the problem might be that you have the Fresh URL script included too high up in your page's HTML. (See the instructions https://github.com/wistia/fresh-url#how-do-i-use-it, which specify to include it at the bottom of your page).

It's currently in the <head> section at the top. Can you try moving all the way to just before the closing </body> tag, at the very bottom, and let us know if that fixes the problem?

@Corgin
Copy link
Author

Corgin commented Dec 12, 2017

Hello @mrdavidjcole - I have now updated the code but I still seem to be having the same problem.

@Corgin
Copy link
Author

Corgin commented Jan 11, 2018

Hello @mrdavidjcole - Do you have an update on this?

@mrdavidjcole
Copy link
Contributor

Hey @Corgin, it looks like although you did move the Fresh URL script down to the bottom of the page body, you removed the script to tell it to wait for HubSpot (and Google Analytics). I'm not seeing this anywhere on your page now:

<script> 
  var _freshenUrlAfter = ['googleAnalytics', 'hubspot'];
</script> 

You'll want to include that directly before the Fresh URL script, like this:

<script> 
  var _freshenUrlAfter = ['googleAnalytics', 'hubspot'];
</script> 
<script src="//fast.wistia.net/labs/fresh-url/v1.js" async></script>

Can you try adding that back in and let us know if that resolves the issue for you? Thanks!

@Corgin
Copy link
Author

Corgin commented Jan 19, 2018

Hello @mrdavidjcole, I have done that now but it's still not working. If I click on a LinkedIn post and open it in Chrome it removes the UTM parameters from the end of the URL correctly but it just shows as direct traffic in HubSpot. If I click on a LinkedIn post and open the webpage in the LinkedIn app, it doesn't remove the UTM parameters from the URL but it does show correctly in HubSpot.

I may just remove the Fresh URL code altogether because I'd rather better analytics.

@Corgin
Copy link
Author

Corgin commented Jan 23, 2018

Hello @mrdavidjcole, I have removed the code from our website now but I would very much like the issue to be solved if possible. Do you have any ideas why it may not be working for us? Thanks, Gavin

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants