I would like to inquire about hubspot public app certification

Developer Support APIs & Integrations
,
1

I am developing a hubspot public app.
I was able to receive the authentication token by installing the pulic app on the user.

And the user was able to run the public app and receive data from the user through Worlflow.

How should we distinguish between the users who installed the pulic app and the users of the data we received through Worlflow from the same user?

I am inquiring because there is no authentication-related information Starter in the data I received through Worlflow.

2

@davidcho wrote:

I am developing a hubspot public app.
I was able to receive the authentication token by installing the

editing app

on the user.

And the user was able to run the public app and receive data from the user through Worlflow.

How should we distinguish between the users who installed the pulic app and the users of the data we received through Worlflow from the same user?

I am inquiring because there is no authentication-related information Starter in the data I received through Worlflow.

Distinguishing between users who installed your public app and those whose data you receive through Workflow without authentication information can be tricky, but here are some possible approaches:

1. Unique identifiers:

  • Workflow Trigger Token: If your Workflow includes a trigger action initiated by the public app itself, the trigger token associated with that action can be used to identify app users. This assumes the trigger token is unique per user and not shared across Workflow runs.
  • Custom User Property: Add a custom user property in HubSpot specific to your public app install. This property could be set during the app installation process and later checked in your Workflow logic.
  • Device/Session ID: If available, you could utilize device or session IDs from the data received through Workflow. While not foolproof due to potential sharing across devices, it can offer some level of distinction.

2. Data analysis:

  • User behavior comparison: Analyze user activity patterns in the publicly available app data and Workflow data. App users might exhibit distinct behavior compared to those whose data you passively receive through Workflow.
  • Data source comparison: Check for differences in the format, content, or structure of data coming from the public app and Workflow. App users might directly submit data in a specific format, while Workflow data might be automatically generated.

3. Combination of approaches:

Combining any of the above methods can provide a more robust solution. For example, analyzing user behavior while utilizing unique identifiers like custom user properties can yield better accuracy.

Additional considerations:

  • Workflow permissions: Review the permissions granted to your Workflow in HubSpot. If it has access to user contact information, you might be able to identify app users based on email addresses or other unique identifiers present in Workflow data.
  • Privacy concerns: Be mindful of user privacy when implementing any identification strategies. Ensure transparency and proper disclosure regarding data collection and usage.

Remember, the most effective approach will depend on your specific use case and the data available within your public app and Workflow. Experiment and test different methods to find the best fit for your needs.