Forum Replies Created

  • In Google Tag Manager, each individual event and the parameters associated with it aim to record what the user is doing on your site. The User Properties, on the other hand, reflects who the user is. This means you would typically include the user ID under User Properties, and the action the user has taken (i.e., whether or not they have signed up for email updates) under Event Parameters for the ‘create_account’ event. So, in simple terms, you list ‘who is doing it’ under User Properties and ‘what they are doing’ under Event Parameters.

  • Rajesh

    Member
    26 June 2023 at 9:19 pm in reply to: Multiple 'begin_checkout' events detected in GA4 without GTM tag

    There could be a few different reasons for the ‘begin_checkout’ event appearing twice. One common reason is if you have the Google Analytics code installed in two different places on your website. Since you’re using a GA plugin, it’s also installing the GA code. Therefore, you have to make sure that it’s not hard-coded somewhere else in your site’s header or footer (through a theme option or another plugin).

    Another possibility could be conflicting plugins. Sometimes, different plugins may use similar methods to track the same event, which results in duplications. Check to see if any other analytics or tracking plugins could be causing the duplication. Deactivate them one by one to pinpoint any potential cause.

    These fixes aren’t too technical and could potentially correct the issue. However, if the problem is still there, I’m afraid more detailed technical investigation might be required, which should probably be done by someone with web development expertise. They may need to check the actual site’s JavaScript code and see what’s triggering the ‘begin_checkout’ event. It’s also possible that there’s some obscure bug or issue specific to GA4. I advise passing these possibilities to your web developer client if it’s still not resolved after initial checks.

  • Sure thing, pal! From what I understand, you’re trying to debug in GA4 and your internal filter seems to affect your visibility in the Realtime reports. Normally, GA Realtime does include dev traffic, so your findings aren’t strange. Try setting up a testing property (separate from your main one) to isolate your dev/debug traffic. Happy debugging!

  • The issue you’re facing with GA cross-domain tracking seems to be a common hurdle when dealing with multiple website setups. Considering the nature of cookies and how they attach themselves to a specific domain, when a user is journeying from your Squarespace site over to the Booqable checkout, it’s likely that the cookie from the originating site is not being carried over to the Booqable session, hence the absence of any trailing _ga or _gl parameters in your URL.

    The baffling part is that when the user’s journey is reversed from Booqable back to Squarespace, the cookies seem to keep up with this transition. This behavior could be due to the way Booqable is handling or forwarding these cookie values back to Squarespace.

    You’ve already explored a couple of options from shuttling back and forth between sites to manual setups. It seems that the only component that’s showing up in the URL when you use a button on your Squarespace website is the _gl, but it’s not quite what you’re looking for.

    Your manual setup approach could be the right direction – ensuring both your Squarespace and Booqable platforms are correctly configured to handle these cookies. It’s unfortunately not always as straightforward as the guides suggest. Clear tutorials on this specific issue can be hard to find, especially considering the nuances of individual website setups and CMS choices.

    Broadly, it certainly seems like a JavaScript-related issue or something amiss in the handoff between Squarespace and Booqable. Since you’ve tried many things already, perhaps considering a consultation with an independent developer or an specialist might provide more insightful troubleshooting or solutions.

  • The person is explaining what they did to use an API from Google Analytics. Firstly, they successfully logged into a user account using Google and generated a token. Secondly, they tried to retrieve a list of account summaries that the user can access, but got stuck because they couldn’t find the required key. They provided the code they used and asked if anyone knows where they can find this key. Lastly, they want to carry out a query using a command, providing the snippet of the command they used, and asked if it is correct or not. They also asked if anyone can help find the key for the second query. They concluded by stating they used several resources, providing links to these resources.