Ackee - tracking.js missing

[girish]

@jlx89 said in Ackee - tracking.js missing:

Feb 15 20:36:34 [Ackee] › warning /tracking.js?ver=1.0.0 not found

Also, the file name is tracker.js and not tracking.js . It's located in /app/code/dist/tracker.js which you can see using the Web Terminal

[JLX89]

@girish Thanks for following up on this. So I found part of the issue, which was related to an outside system. I've gone ahead and fixed that and this issue has fixed itself.

I'm working to see why information isn't flowing in from the trackers. Do you know if there is a way to see if Ackee is actually receiving traffic from the tracking codes? I have updated the CORS information per the documentation and the code seems to be loading fine on the sites.

Thank you!

[marcusquinn]

@jlx89 Does your browser have privacy tracker blocking or submit donotfollow preferences?

[JLX89]

@marcusquinn Thanks for replying. I actually disabled it, but it seems to have taken around 48 hours to actually start pulling data in. I think I'm good to go now, thanks again!

[MelodyKH3]

For anyone else who is trying to add Ackee to a Wordpress install. "SoapBerry" defaults to "tracker.js" but it should be 'tracking.js'

Adding this here because its the first result on google and it seems that's originally the problem this OP had.

[girish]

@melodykh3 you mean the other way around ? I do see that https://wordpress.org/plugins/soapberry/#description has a screenshot that defaults to tracking.js . I reported it here - https://wordpress.org/support/topic/ackee-tracker-file-should-be-tracker-js/

[JLX89]

@melodykh3 Yes, this was a portion of the issue -- an outside hosted WordPress website using SoapBerry was hitting the server with the default tracking.js. I went into the plugin and changed the file name.

The other issues seems to have resolved over time with updating the CORS Headers in the env file. It ended up taking a good 72 hours for everything to work out.

[humptydumpty]

Ackee & Soapberry work fine if you set it to use tracker.js, add the CORS headers in the env file and restart the app. The tracking worked immediately for me on multiple WP installs except one. There's some kind of conflict with the caching plugin (WP-Rocket) and I haven't looked into it yet.

[JLX89]

@humptydumpty Yeah, I ended up figuring it out but it took some time. So I did also notice, if you're using bunny.net CDN, you need to include the tracker.js to be excluded from the CDN.

[humptydumpty]

@jlx89 Thanks for the tip. That's the CDN that I'm using and it's with the site that I'm having trouble with