Skip to main content

Journey cannot detect my GA4 property although data exists

Comments

3 comments

  • Support
    • Journey Support Team

    kkr Are you seeing this error after selecting ‘mcbe-proxvc’ from the select property dropdown menu? As far as I know, the way the script is implemented shouldn't have any bearing on this.

    If there's a corresponding console error, or an error that's sent from an incoming xml request in devtools, feel free to send that along and we can take a look. 

    0
  • kkr

    I apologize for the delayed response.
    Yes, the error appears after selecting “mcbe-proxvc” from the property dropdown.

    I checked the browser developer tools and found the following console errors:

    __cmp never became available.

    >>> tokenResponse >> {
     iss: 'https://accounts.google.com',
     code: '[REDACTED]',
     scope: 'email profile https://www.googleapis.com/auth/analytics.readonly https://www.googleapis.com/auth/userinfo.profile https://www.googleapis.com/auth/userinfo.email openid'
    }

    GET https://publishers.grow.me/empty 404 (Not Found)

    [Violation] 'mousedown' handler took 167ms
    [Violation] 'focusin' handler took 178ms

    I have also checked the Network tab and did not see any obvious failed GA requests.

    Google OAuth authentication appears successful, and the analytics.readonly scope is granted.

    Please let me know if you need additional logs or screenshots.

    Thank you for your help.

    0
  • Support
    • Journey Support Team

    Hi kkr Thanks for sending that over!

    It looks like this error occurs when you are selecting a GA4 property that has an empty default_uri field. This can happen when the web data stream is not configured correctly. It shouldn't matter that the app stream was created before the web stream, but you should take a look to make sure that your URL is correct on the web stream and on the property. Additionally, can you confirm that the time zone for the property is set to (GMT-04:00)New York Time? This is a requirement for the property to work correctly with our dashboard.

    0

Journey is Self Supported

Our support staff is monitoring this forum everyday for bugs related to ad delivery, the display and functionality of the Journey dashboard, and any bugs related to the onboarding process. We are typically unable to assist with non-bug related issues like RPM performance expectations, issues setting up the ads.txt file, and questions already answered by our existing help docs. Read here for a more detailed breakdown of how Journey is self-supported and our recommendations for how to find answers to common issues.

Please sign in to leave a comment.

Powered by Zendesk