Events and users
Users and revenue credit
Identify signed-in users, who gets their revenue, and what you see for each user.
Tell Dropplink who is signed in, so a user's events and revenue go to the creator who brought them, even when they reinstall, switch phones or buy on your website. Needs the SDK at version 0.2.0 or later.
Identify a user#
Call identify as soon as someone signs up or logs in, with your own user ID: the one your backend already uses, like a
database ID or UUID.
Dropplink.identify(userId = user.id, email = user.email, phone = user.phone)Dropplink.identify(userId: user.id, email: user.email, phone: user.phone)await Dropplink.identify(user.id, email: user.email, phone: user.phone);Dropplink.identify(user.id, { email: user.email, phone: user.phone });- Call it on every launch for a signed-in user, not only at login. Calling it again with the same ID does nothing, and it also covers users who logged in before you added the SDK.
emailandphoneare optional. They're hashed (SHA-256) on the phone and only the hash is sent, so plain values never leave the device and aren't stored. Pass the phone with its country code, like+919876543210; one without it is left out.- The user ID must not be an email or a phone number. Those are refused, so use an opaque ID. Sequential IDs (
1,2,3) work, but random ones are harder to guess. - Use the same ID on your server. Purchases you send with
POST /v1/s2s/eventsfind the user by this ID.
Log out#
Dropplink.logout()Dropplink.logout()await Dropplink.logout();Dropplink.logout();Events after logout carry no user and are credited to the install. Like events, identify and logout are saved on the phone and
sent in order, so events tracked right after a login always arrive with that user.
Who gets a user's revenue#
First touch. The first creator whose link brought the user, through any install that later identified as them, gets their revenue. Later installs from other links don't take it away. That stops someone reinstalling a regular user's app from their own link to claim their purchases.
Won back. Credit moves to another creator only when that creator's link brings back a user who had been inactive for your re-engagement window, and only for revenue from then on. Set the window in Settings → Project details → Attribution windows: 7 to 180 days, 30 by default.
Test devices that log in as many accounts
An install that identifies as more than 3 different users in one day is flagged, and from then on it can't set or move anyone's credit. That's normal for a QA phone. Use a fresh install, or a different phone, for each test user whose credit you want to check.
What you see for each user#
Paste an install ID into Install debugger in the dashboard. Alongside how the install was attributed, it shows:
User and revenue credit
Latest events: the install's last 50 events, newest first.
The dashboard never shows email or phone: only their hashes reach Dropplink, and the debugger leaves even those out.
Reports across all users
Totals per link, channel and creator (installs, sign-ups and revenue) are coming to the dashboard next. Today, use the Install debugger to check individual users while you integrate.
Deleting a user's data#
When someone deletes their account or asks for their data to be removed (DPDP, GDPR), call
DELETE /v1/s2s/users/:userId from your server. Their events and identity are removed;
installs stay as anonymous counts, so creator totals don't change.