Adding users to ProductLogz

You can control how your users are authenticated before they start interacting

Manual authentication

Users can manually authenticate themselves by entering their email and password or signing in via Google. This process is simple—users just need to click the Login/Signup button. A popup will appear, allowing them to either login or create an account if they haven't already.

Clicking on the button will open a popup where your users can either create account if not created already.

With this method, user accounts are stored and authenticated by Productlogz. However, if you prefer to streamline this process, you can eliminate the manual authentication step for users.

Automatically authenticating users

You can use the below Productlogz SDK Identify method to remove the manual authentication step from the user's side. This way, they are automatically verified when they click the feedback link from your product.

By integrating our JavaScript SDK, you can ensure that user feedback is linked to their accounts in your app.

Step 1: Add the link to your product

In your application, add the below link (replace href value) to your Productlogz feedback portal. Make sure it is prominently displayed so users can easily access it.

```
<a data-pl-link href="" target="_blank">
   Give feedback
</a>
```

Make sure you replace https://company.productlogz.com with your public board link ( or your custom domain link).

⚠️ Important: The data-pl-link attribute must be included. If removed, authentication will not work.

Step2: Add script tags

Place the following code in your application codebase, primarily at the root or in index.html.

Modify the values to pass your application's user data.

<script>
   window.ProductLogz('classify', {
      accountKey: <> // **required**,
      // NOTE: the 'user' is just used as a reference here, 
      // kindly replace it with your user's state.
      user: {
         alias: user.alias, // **optional**
         avatarURL: user.avatarURL, // **optional**
         createdAt: new Date(user.created).toISOString(), // **optional**
         email: user.email, // **required**
         id: user.id, // **required**
         name: user.name, // **optional**
         // **optional**
         companies: [
            {
               id: 'company-id',
               name: 'Company-Name',
               monthlyRevenue: some-number,
               createdAt: "2024-01-01",
            }
         ],
         // **optional**
         customFields: {
            title: 'Product Manager',
         }
      },
   });
</script>

Required Configuration

Account ID

• accountId [string] (Required)

  • Replace this value with your actual account ID, which can be found in the ProductLogz dashboard under Settings > Workspace Details.

User Fields

• id [string] (Required)

  • A unique identifier for each user in your system, ensuring their feedback is correctly linked to their account.

• email [string] (Required)

  • The user’s email, making it easier to identify them and follow up on their feedback.

• alias [string] (Optional)

  • A custom identifier for the user, useful if you want to reference them with something other than their email or user ID.

• avatarURL [string] (Optional)

  • A URL for the user’s profile picture, helping personalize their feedback.

• createdAt [string] (Optional)

  • The date and time the user was created in your system, useful for tracking feedback based on account age.

• name [string] (Optional)

  • The user’s display name, making interactions more personal and recognizable.

• companies [array] (Optional)

  • Associates a user with one or more companies, helping track feedback at an organizational level.

• customFields [object] (Optional)

  • Attach additional metadata to a user, such as role, subscription plan, or other relevant attributes for better context.

By implementing this setup, you can enhance the user experience while ensuring that their feedback is automatically linked to their account. 🚀

---

⚠️ Productlogz Identify doesn’t track admins, so if you’re testing, use a regular user account.