Track sign-ups in your app (incl. Google & Microsoft SSO)

When the action you care about happens inside your own software – someone creating an account – you usually want one Lead event sent to LeadJourney, with the new user's name and email, attributed to the ad click that brought them. This guide shows exactly how, including Google and Microsoft sign-up, which the automatic form listener can't catch on its own.

Why the automatic form listener isn't enough

LeadJourney's script fires a Lead automatically when it sees a standard <form> submit. That covers your plain email/password sign-up form. It doesn't cover Google or Microsoft sign-up, because that flow never submits a form on your page:

• The visitor leaves your site to accounts.google.com / login.microsoftonline.com, approves, and is redirected back to your callback. There's no <form> submit for the script to catch.
• The account is often created server-side on that callback, where there's no browser to read from at all.
• An SSO button click is ambiguous – it could be a login, not a new sign-up. You only want the event on a new account.

So for sign-ups you send the Lead event yourself, exactly once, the moment a new account is created. It's three small pieces: a server route that holds your secret, one call after sign-up succeeds, and – for SSO – carrying the click ID through the OAuth state parameter.

Before you start

Grab your Conversion API credentials from Settings → Events → Conversion API:

• Your Postback URL – looks like https://api.leadjourney.io/api/v1/postback/<your-id>.
• Your Postback Secret – starts with pb_…. Treat it like a password; it stays on your server and is never exposed to the browser.

Make sure a Lead event exists in the Events Manager – every workspace has one by default.

Step by step

// app/api/lead/route.js
export async function POST(req) {
  const d = await req.json();

  await fetch(
    "https://api.leadjourney.io/api/v1/postback/YOUR-POSTBACK-ID",
    {
      method: "POST",
      headers: {
        "Authorization": "Bearer YOUR_POSTBACK_SECRET",
        "Content-Type": "application/json",
      },
      body: JSON.stringify({
        type: "Lead",
        click_id: d.click_id,
        tag: d.tag,
        firstname: d.firstname,
        lastname: d.lastname,
        email: d.email,
      }),
    }
  );

  return Response.json({ ok: true });
}

fetch("/api/lead", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    click_id: localStorage.getItem("clickId"),
    tag: "app_signup",          // your campaign / source tag – a fixed word is fine
    firstname: /* see table below */,
    lastname:  /* see table below */,
    email:     /* see table below */,
  }),
});

Carry the click ID through Google / Microsoft SSO

For SSO there's one extra thing to solve: getting the click ID from before the redirect to your callback after it. localStorage may be gone by the time the account is created – the callback can run server-side, or land on a different subdomain.

1. When the user clicks "Continue with Google / Microsoft", pack the click ID into state:

const clickId = localStorage.getItem("clickId") || "";

// Pack the click ID into `state`. Add your own CSRF token here too if you use one.
const state = btoa(JSON.stringify({ clickId, csrf: yourCsrfToken }));

// Google – Microsoft is the same idea with login.microsoftonline.com/common/oauth2/v2.0/authorize
const url = new URL("https://accounts.google.com/o/oauth2/v2/auth");
url.searchParams.set("client_id", GOOGLE_CLIENT_ID);
url.searchParams.set("redirect_uri", REDIRECT_URI);
url.searchParams.set("response_type", "code");
url.searchParams.set("scope", "openid email profile");
url.searchParams.set("state", state);

window.location.href = url.toString();

2. On the callback, after the account is created, decode state and send the Lead:

// `state` comes back exactly as you sent it
const { clickId } = JSON.parse(atob(stateFromCallback));

await fetch("https://your-app.com/api/lead", {
  method: "POST",
  headers: { "Content-Type": "application/json" },
  body: JSON.stringify({
    click_id: clickId,
    tag: "app_signup",
    firstname: profile.given_name,   // Microsoft: profile.givenName
    lastname:  profile.family_name,  // Microsoft: profile.surname
    email:     profile.email,        // Microsoft: profile.mail
  }),
});

Verify it's working

1. Open your app from a tracked link (one carrying lj_* parameters, e.g. a test ad URL or a link built with the UTM Builder) so a click ID is stored.
2. Create a test account – once via the form, once with Google, once with Microsoft.
3. In Settings → Events the Lead event's Total count goes up and its status turns Active.
4. To inspect a single call (status code, payload, whether the click ID matched), open the API Postbacks log.

FAQ

Related articles