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

UTM Params not being passed when signing up with Google from landing page(s) #6

Open
tythorsen opened this issue Dec 12, 2024 · 0 comments
Assignees

Comments

@tythorsen
Copy link

tythorsen commented Dec 12, 2024

TL;DR(W): We have a marketing site landing page with a Sign up with Google button for which we're failing to pass our UTM params. We need to add some code to the marketing site JS to ensure they are passed correctly.

Background

@jsnyder18 and @mjtay10r in marketing (with an assist from @morrismatts) have identified a gap in our conversion tracking. You can view Josh's original Loom video to get some additional context.

Basically, we have one landing page (www.close.com/get-started) that allows visitors to sign up with Google in addition to a normal signup form that pre-populates the in-app signup form.

Image

Signups that use the form work fine. Signups that use the Google OAuth option are missing UTMs. This is due to the fact that the button on this page is linking directly to our Google signup url https://app.close.com/auth/google/sign-up/?app_platform=web and we expect UTMs to be appended to the URL in this scenario.

Proposed Solution

When users sign up with Google in the app, we have some logic in js/components/guest/utils.ts that appends a few things like analytics context and UTM values as search params before redirecting to Google. We need to port a simplified version of this code into Webflow for the marketing site.

  • The app has a few abstractions to handle different types of providers and OAuth types. We can directly address the Google signup case.
  • We should probably write our solution using a global click handler that targets any link to the Google OAuth URL so that marketing can easily add this functionality to other landing pages in the future.
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