Google Analytics Integration

This topic contains 8 replies, has 4 voices, and was last updated by  James Simone 8 years, 8 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #168375

    James Simone
    Buyer
    Post count: 18

    Hi – I’ve been reading about the intricacies of integrating this element of the app – I’ve just stumbled across one as well: the authorized redirect callback.

    I set it (using Google’s suggestion) to domain/oauth2callback, but that gave an error – could you provide the callback I should be using?

    FYI, here’s google’s direction:

    “For use with requests from a web server. This is the path in your application that users are redirected to after they have authenticated with Google. The path will be appended with the authorization code for access. Must have a protocol. Cannot contain URL fragments or relative paths. Cannot be a public IP address.”

    Thanks.

    James.

    #168469

    Guust
    Moderator
    Post count: 29970
    #168861

    James Simone
    Buyer
    Post count: 18
    This reply has been marked as private.
    #168863

    Paolo
    Site Admin
    Post count: 31206
    #168872

    James Simone
    Buyer
    Post count: 18

    Resolved – sort-of: went back and re-configured the Oauth2 client.

    The previous {“error”:{“errors”:[{“domain”:”global”,”reason”:”insufficientPermissions”,”message”:”User does not have sufficient permissions for this profile.”} error message has now been replaced with {“error”:”Login failed”}.

    …the Oauth2 client looks to be configured properly still
    – any ideas what’s going on with this {“error”:”Login failed”} error?

    James.

    #168942

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    Hi James,

    I would need FTP to debug that one.

    Thanks,

    Stiofan

    #169077

    James Simone
    Buyer
    Post count: 18
    This reply has been marked as private.
    #169267

    Stiofan O’Connor
    Site Admin
    Post count: 22956

    It’s still coming back as unauthorised client, you had a space in your client secret so it was actually throwing a 404 error but it’s still unauthorised. I would try again from the beginning if that does not work the only way i think we can solve is for either you to trust us with your google login or to create a new google account to let us test.

    Thanks,

    Stiofan

    #169423

    James Simone
    Buyer
    Post count: 18
    This reply has been marked as private.
Viewing 9 posts - 1 through 9 (of 9 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount