Currently the session is identified after the first identify(0xA) call.

What happens if in the same session there are are multiple identify calls:

• identify(0xA)
• identify(0xB)

Will the second call be skipped?

  /**
   * Emits an identify event with current wallet address.
   * param {Address} params.address
   * returns {Promise<void>}
   */
  public async identify({
    address,
    providerName,
    rdns,
  }: {
    address: Address | null;
    providerName?: string;
    rdns?: string;
  }): Promise<void> {
    if (this.session.isIdentified())
      return logger.warn("Identify: Wallet already identified in this session");

    this.session.identify();
    await this.trackEvent(Event.IDENTIFY, {
      address,
      providerName,
      rdns,
    });
  }

All the events seem to have 00 seconds:

Screenshot 2025-04-08 at 18.54.44.png

This can result in an unexpected order of events:

https://app.formo.so/teams/94f54b87-0209-4411-90dc-0e24a186c729/projects/formo.so/profiles/0x94b305f3c18232799333cb6dc3d0b6f8ad8f4fd9

For this user we get the following events:

Screenshot 2025-04-04 at 13.38.37.png

The order is unexpected: why is disconnected wallet before connected wallet? Check if the disconnected wallet event has the same or older timestamp than the identified and connected wallet event

Show event seconds in the activity feed "10:44:15 PM"

Screenshot 2025-04-08 at 18.56.00.png

Currently we call identifyAll() in init() but this is illegal apparently.

🚫 Most analytics tools do NOT automatically call identify() on page visit

// Automatically resolving from backend or cookie without consent
analytics.identify(userId); // 👎 Not safe if user hasn’t logged in

If you auto-identify users (GET /user) without login the moment someone connects a wallet (or even worse, when they visit), you could:

• De-anonymize someone without consent
• Violate GDPR/CCPA if you're tying public address → private profile
• Expose someone’s full profile in the network tab

So, until you call identify(userId) manually (typically after login/signup), the user is tracked anonymously.

✅ TL;DR:

• Most tools do NOT call identify() automatically
• They DO track anonymous activity with a unique, persistent anonymous ID
• You must manually call identify(userId) once the user logs in or signs up

Preferred flow:

// 1. User connects wallet
const address = "0x123...abc";

// 2. Verify ownership (e.g., connect wallet, sign message, SIWE)
const verified = await siweLogin(address);

// 3. Fetch backend-issued user ID
const user = await fetch(`/user?address=${address}`, {
  headers: { Authorization: `Bearer ${verified.token}` }
});

// 4. Identify using stable user ID
analytics.identify(user.userId, {
  address,
  ens: user.ens,
});