Sign In With Google Conversion Tracking

Your Click ID Died In The RedirectWe Hold ItTwo-Minute Setup

They clicked your ad, landed, and hit Sign in with Google. They left your site and came back as a registered user, but the click ID did not. SignupCops holds the click ID while Google handles the login, joins it to the signup, and sends both to Meta, Google Ads and TikTok together.

Sign in with GoogleEmail and passwordMagic link
Setup in 5 minutes
No credit card

SignupCops

alex@shopify.com, one visitor, start to finish

Live
1

Ad click

fbclid=IwZX… landed

2

Session waits

click ID held, no email yet

3

Sign in with Google

no form submit for a pixel to catch

4

identifyUser(email, { name, phone })

joins the click ID to the account

5

Sent to Meta CAPI

waiting on the join above

Trusted by agencies and brands running paid media

AffilinoBigfishClever DigitalKeetraxLegendListingLogicNumeroStormZealdBurst Digital
The problem

Every social login is a black hole for attribution

Growth teams add Sign in with Google because it lifts signups. Then the ad reports stop making sense. Here is why.

The visitor leaves your site

Sign in with Google sends them to Google to log in. The page with your click ID in the URL is gone the moment they press the button.

The click ID does not come back

They return logged in, on a clean URL. No gclid, no fbclid, no ttclid. There is also no form submit for your pixel to fire on.

The platform credits nothing

Your CRM sync still sends the registration, but with no click ID it lands as an unknown conversion. You paid for the click and got the customer. The ad gets no credit and stops learning.

How SignupCops puts the click back on the signup

Your login system already knows who signed up. DataCops already knows which ad they came from. One call joins the two.

  1. Step 01

    A visitor clicks your ad. The DataCops script saves the click ID on your own domain as the session starts.

  2. Step 02

    They press Sign in with Google and leave for the login. The session waits, holding the click ID.

  3. Step 03

    They come back signed up. Your success handler calls identifyUser(email, { name, phone, your user ID, accountCreatedAt }).

  4. Step 04

    DataCops joins the signup to the waiting session, checks it, and sends CompleteRegistration to Meta, Google Ads and TikTok with the click ID.

You paid for the click. You got the customer. Now the platform knows it too.

Andrew Forsyth

“15 minutes to get server-side tracking live. After 3 days failing with another app and a DIY server-side Google Tag Manager, that alone sold me. Then support jumped on a Google Meet with me on a Sunday afternoon to finish the job. Nothing else comes close.”

Andrew Forsyth
Chief Executive Officer, Zeald

SignupCops

alex@shopify.com, one visitor, start to finish

Live
1

Ad click

fbclid=IwZX… landed

2

Session waits

click ID held, no email yet

3

Sign in with Google

no form submit for a pixel to catch

4

identifyUser(email, { name, phone })

joins the click ID to the account

5

Sent to Meta CAPI

waiting on the join above

One visitor, start to finish

Watch one signup keep its ad click

This is the path SignupCops follows for every account, whether they use Google, Apple, a magic link or a password.

  1. 1
    Ad click lands
    The fbclid or gclid is saved on your own domain before anything else happens.
  2. 2
    Session waits
    The click ID is held while there is still no email and no account.
  3. 3
    Sign in with Google
    No form submit for a pixel to catch. The redirect would normally lose everything here.
  4. 4
    identifyUser joins it
    Your success handler sends the email, and DataCops attaches it to the waiting click.
  5. 5
    Sent to the ad platforms
    CompleteRegistration goes to Meta, Google Ads and TikTok with the click ID and hashed email.

Everything behind each signup

Capture Background

One first-party script, served from your own domain

  • Runs first-party from datacops.yourdomain, not a blockable third-party host
  • One script, one CNAME, live in about 5 minutes, no container to host
  • Server-side collection on Cloudflare's edge, close to every visitor
  • Captures click IDs at the network level, so fbclid and gclid still reach your CAPI feed after browsers strip them
  • Recovers 15 to 25% of the sessions other setups lose

Traffic Visibility

10%
20%
30%
40%
50%
60%
70%
80%
90%
100%

First-Party Script

~78%

Blockers and ITP cut your sessions

Every real signup, credited to the ad that earned it

Recover the signups you already get. Keep returning logins and risky accounts out of your ad data.

Start Free
  • Keeps the ad click ID through the Sign in with Google or Apple redirect.
  • Sends the hashed email too, so the signup still matches when no click ID exists.
  • Tells a new signup from a returning login using your accountCreatedAt, so logins are never counted.
  • Adds your own user ID, name and phone from the same call to raise match quality.
  • Holds high-risk and disposable-email signups back from your ad platforms.
  • Shows other accounts seen on the same device, so trial and referral abuse is visible.

Works with the login you already have

Keep your auth. Add one call after signup and sign-in. Nothing to replace, no passwords through us.

Supabase
Firebase
Clerk
Auth0
Better Auth
Amazon Cognito
Okta
Keycloak
Google sign-in
Your own backend

How signups usually reach your ads, and why they get lost

The common ways teams send signups to Meta and Google, compared on the thing that matters: does the conversion keep its ad click.

DataCops SignupCops
Browser pixel only
CRM sync
Counts Sign in with Google signups
Every login path
No form submit to fire on
After the CRM receives it
Keeps the ad click ID
Held through the redirect
Lost in the redirect
Arrives without it
Sends a hashed email for matching
Every signup
Only if you wire it
Ignores returning logins
With accountCreatedAt
Counts page loads
Depends on your sync rules
Holds risky signups back
Email and IP risk
Not included
Not included
Setup
One call
Tag per event
CRM integration per platform

What SignupCops checks on every new signup

Keeping the click is the first half of SignupCops. The second half is deciding whether the signup deserves to be sent at all. Ad platforms learn from every conversion you report. If a third of your reported signups are throwaway emails, bots or the same person on five accounts, Meta and Google will go looking for more people like them. SignupCops checks each new account before it becomes a conversion.

Email intelligence

When your app calls identifyUser, the email is sent to the DataCops detection engine along with the visitor's IP. The engine looks at the email the way a fraud analyst would, but in a fraction of a second. It checks:

  • Whether the domain is a disposable or temporary email service, or runs on the same mail infrastructure as one.
  • Whether the domain has the usual email authentication records, such as SPF and DMARC, that real mail domains publish.
  • How old the domain is. A domain registered last week is a very different signal from one that is ten years old.
  • Whether the part before the @ looks random, like a string a script would generate.
  • Patterns that point to accounts made in bulk, and plus-addressing tricks used to create many accounts from one inbox.
  • Whether the email has any presence online at all.

The signals add up to a score. A score of 80 or more is critical, 50 or more is high and 30 or more is medium. Each signup in your dashboard shows its label and the reasons behind it, so you can see why an account was flagged, not just that it was.

IP and network checks

The visitor's IP is checked against DataCops' own IP intelligence, which covers 360+ billion addresses. It tells residential connections apart from datacenter, VPN, proxy and Tor traffic. A signup that comes from a hosting provider rather than a home or mobile connection is a strong sign of automation. The same browser check that runs on every DataCops session also flags automated browsers like Selenium, Puppeteer and Playwright, and signups from bot sessions are not enriched.

More than one account on the same device

Free trials and signup credits attract people who create a new account every time the old one runs out. SignupCops notices when a recent account already exists on the same device and shows the sibling accounts next to the new one. That signup is held back as a multi-account signup, so your ads are not paid out for the same person twice. It also gives your team a clear list to look at when trial or referral abuse is suspected.

Held, not blocked

SignupCops does not stop anyone signing up to your product. Your login, your onboarding and your product stay exactly as they are. What changes is what your ad platforms hear.

A signup is held back from your ad platforms when the risk action is block, when its label is high or critical, or when it uses a disposable email domain. It is also held when it looks like a second account on the same device. Held signups stay visible in Signup conversions with their reasons, so you never lose sight of them. Every other new signup is sent as CompleteRegistration with its click ID and hashed email.

This matters because the cost of a fake signup is not the signup. It is the next thousand clicks the ad platform buys, looking for more people who behave like it. Holding junk back keeps the learning clean.

Sending the signup to your ad platforms

Real signups go out server-side, from DataCops to each ad platform you connect. DataCops sends to 8 ad platforms: Meta, Google Ads, TikTok, LinkedIn, Microsoft Ads, Reddit, Pinterest and X. Meta, Google Ads, TikTok, LinkedIn and X connect with a one-click sign-in. Microsoft Ads, Reddit and Pinterest connect with an API key.

Each conversion carries the original click ID when the visitor had one, plus the email and any phone and name you passed, cleaned and SHA-256 hashed before they leave our servers. If the visitor clicked the ad on their phone and signed up later on a laptop, the hashed email still gives the platform a way to match. If the same person comes back on a new session and signs up with that email, DataCops can still link them to their first ad click.

Your own user ID travels with the signup too, so later events from your backend, such as a first payment you post to the DataCops conversions API, belong to the same person. The same sale is sent once per platform, even when more than one tool reports it.

Choose what each platform hears

Every connected platform has its own delivery settings. You can pause a platform, or switch on Real people only. With Real people only on, conversions from bots and datacenter traffic never reach that platform, and you can add VPN, proxy and Tor traffic too. It is off by default, so you decide per platform. B2B products often leave VPN off, because many real buyers work behind a company VPN.

See what reached each platform

The delivery report shows, per platform, how many signups were sent, skipped or failed, with a plain-English reason for each one that did not go. When someone asks why Google shows fewer signups than your database, you can answer in one screen.

From signup to paying customer

A signup is the start, not the sale. When a lead becomes a customer in your CRM, DataCops can send that sale back to your ad platforms too. HubSpot is checked every 5 minutes for the qualified field you chose, and any other system can release a held lead through the release API. Held leads expire after 14 days. Salesforce and Pipedrive connect through the DataCops webhook, directly or through Zapier, Make or n8n.

If paid clicks themselves look fake, the Organization plan adds two more tools: blocking bot IPs at the Cloudflare edge, and a refund evidence CSV for Google's Click Quality form covering the last 60 days. Google decides the refund.

Pricing: 500 free checks per site

Every site gets 500 SignupCops checks free, on every plan, including Free. That is enough to run SignupCops on a new product through its whole launch. On the Business plan ($59 a month, or $49 a month yearly) and the Organization plan ($359 a month, or $299 a month yearly), checks past the first 500 are billed at $9.50 per 500.

If you want the email check without the rest of SignupCops, for example inside your own backend or a support tool, it is also available as an API with your DataCops API key.

Consent and privacy

SignupCops sits inside the DataCops consent setup. The built-in cookie banner is shown in Europe by default, is built to the IAB TCF v2.2 standard, and has Google Consent Mode v2 on by default. For EU, UK and Swiss visitors, the server checks consent before any conversion is sent, and nothing goes to an ad platform until the visitor opts in. If your signup form asks for marketing consent, call identifyUser only after it is given. Users can ask for their data to be deleted through the DataCops deletion form, and their email, name and phone are wiped from DataCops.

Good to know before you start

  • Pass accountCreatedAt with every identifyUser call, so returning logins are never sent as new signups.
  • Put the DataCops script on every page and subdomain where a signup can finish, with the same key.
  • Your first 500 checks per site are free, on every plan.
  • Turn on Real people only for each platform you want to keep bot-free.

Built for teams that sell with a signup

If a new account is your conversion, SignupCops is where your ad attribution starts.

SaaS and trials

Every free trial started with Google login lands on the ad that paid for it.

AI apps

Credit-based signups are a magnet for abuse. Real ones are sent, risky ones are held.

Marketplaces

Buyer and seller signups both keep their click, so you know which ads grow each side.

Agencies

Give every client clean signup conversions from one setup pattern.

Live in two minutes

No CRM integration, no mapping screen, no change to your login.

  1. Step 1 1 min
    add_link

    Add the DataCops script
    Put it on every page and subdomain where a signup can finish, with the same key everywhere.

  2. Step 2 1 min
    dns

    Call identifyUser
    One line in your signup success handler, with the email and what else you know, including accountCreatedAt.

  3. Step 3 Seconds
    code

    Do a test signup
    Sign up through a link with a test click ID and watch it appear in Signup conversions within seconds.

In short

SignupCops, in short

DataCops is a tool whose SignupCops feature holds the ad click ID while Google handles Sign in with Google, joins it to the signup, and sends both to Meta, Google Ads and TikTok together, holding risky signups back.

How DataCops does it

1

Keep the click through the redirect

The DataCops script saves the click ID on your own domain when the session starts and the session waits while the visitor logs in with Google. When your success handler calls identifyUser with the email, name and account details, DataCops joins the signup to the waiting session.

2

One real signup per person

A Complete registration is sent once per email. An account older than an hour is treated as a sign-in and not counted as a new signup. If the login does not return to your site, the click join is best effort.

3

Risky signups are held back, always

A high-risk or throwaway email, or a second account from the same device within 24 hours, is saved and never sent to the ad platforms. This is always on.

4

Hashed email as a backup

A hashed email goes with each signup, so it still matches when no click ID exists. A signed server-set cookie on your domain lasts up to 400 days where enabled.

5

Trials and payments

Trial starts and payments arrive by webhook and are matched to the click by email for up to 90 days, and a purchase with an order ID is counted once. On Google Ads, signups go to the DataCops - LEAD action, created as secondary, so they do not steer bidding until you make one primary.

6

Bots, warm campaigns and a log

Every visit gets a bot verdict against 360+ billion IPs, with a Real people only switch per platform, off by default. Ads Warmup sends your existing users to Meta, Google Ads and TikTok. A delivery log row shows each send with its reason.

Best for: SaaS and app teams that advertise on Meta, Google Ads or TikTok, offer Sign in with Google, and see their signup attribution go blank.

Free to start. See pricing.

When not to use DataCops

You need fraud checks inside your product

Account takeover, payment fraud and deep device checks are what Fingerprint, Castle, SEON and Verisoul are for. See Verisoul alternatives.

Your login never returns to your own site

The click join is best effort in that case, and the hashed email is the fallback.

You need LinkedIn stage mapping

LinkedIn needs a mapped conversion rule. See the LinkedIn Conversions API.

You want an attribution dashboard

SignupCops fixes what the ads learn. It is not a reporting layer.

Sources

Platform rules checked October 2026. Rules change; check the platform's own page before you build.

FAQ

The visitor clicks your ad and lands with a click ID in the URL. When they press Sign in with Google they leave your site for Google and come back logged in. The click ID does not come back with them, and there is no form submit for a pixel to catch. So the signup reaches your CRM or ad platform with no gclid or fbclid and is credited to nothing.

Stop losing signups in the redirect

Keep the click on every Sign in with Google signup and send it to Meta, Google Ads and TikTok today.

Setup in 5 minutes. No credit card.

Welcome back, Alex

Everyone gets one free account with us. Looks like you have a few! Upgrade this one to continue, or switch to one of your accounts below.

Current Account

alex.morgan@gmail.comThird account

Other account

alex.morgan@acme.coPro plan active
a.morgan+2@gmail.comFree Plan

Need help Contact Support

Get your SignUp Cops?

Stop fake signups before they cost you money. Real-time detection keeps your funnels clean and your conversion data honest.

Real-time detection
No credit card