Identifying Users
This is the single most important thing you'll add by hand — and it's just one line. Identifying a user tells Signal Sparrow who an anonymous visitor really is, so their earlier visits can be connected to the payment they make later in Stripe.
Why it matters so much
A visitor might click your ad today and pay next week. Without a shared clue, those two moments look unrelated. When you call identify with their email, Signal Sparrow can stitch the whole journey together:
Clicked a Google ad → browsed your site → signed up → paid in Stripe
The more visitors you identify, the more of your revenue gets traced back to its source — which directly raises your match rate.
When to call it
Call identify as soon as you know a person's email — typically:
- Right after they sign up.
- When they log in (in case they signed up on another device).
Calling it more than once is harmless, so it's safe to call on every login.
How to call it
- HTML snippet
- React SDK
- Next.js SDK
<script>
if (window.rp) {
rp.identify('user@example.com');
}
</script>
import { identify } from '@signalsparrow/sdk';
// After signup or login:
identify('user@example.com');
'use client';
import { useIdentify } from '@signalsparrow/next';
const identify = useIdentify();
// After signup or login:
identify('user@example.com');
Your customers' privacy is protected
The email address is hashed (scrambled into an unreadable code) before it ever leaves the browser. Signal Sparrow and the ad platforms match on that scrambled value — the raw email is never exposed. You stay in control of your customers' data.
Matching works best when the email you identify with is the same one on the customer's Stripe record. If they check out with a different email, the two may not connect.