Feature request: allow passing custom attributes to initialize method (web)

[Frank3K]

Description

In the Intercom JavaScript SDK, it is possible to pass additional properties to the boot method, not just the appId, as is currently done in intercom_flutter_web. This could allow developers to initialize Intercom with more user-specific data.

For reference, here’s an example of how the boot method can accept additional properties:

Intercom('boot', {  
    app_id: 'abc12345',  
    email: 'john.doe@example.com',
    created_at: 1234567890,
    name: 'John Doe',
    user_id: '9876'
});

Source: Intercom SDK Documentation: boot Method

Currently, the intercom_flutter_web package only passes the appId during boot, as shown here:

intercom_flutter/intercom_flutter_web/lib/intercom_flutter_web.dart

Lines 62 to 66 in 6e332b7

	globalContext.callMethod(
	'Intercom'.toJS,
	'boot'.toJS,
	updateIntercomSettings('app_id', appId).jsify(),
	);

Feature Request

Would it be possible to add support for passing additional properties to the boot method? While I know it’s possible to inject these properties using window.intercomSettings, I’d prefer to handle this within Flutter for consistency.

[deepak786]

You can use updateUser API to pass the additional data and custom attributes.

[Frank3K]

You can use the updateUser API to pass the additional data and custom attributes.

Yes, I’m aware of the updateUser option. However, in our use case, some data is already available during the application's bootstrap, so it would be beneficial to submit this information directly during the initialization of Intercom. This would avoid an additional ping request to Intercom, making the initialization more efficient.

I’ve tried calling updateUser immediately after awaiting the initialize method, but unfortunately, the updateUser call does not seem to send a ping request in that case. I'm still investigating the cause—it could be due to Intercom not being fully initialized at that point, or perhaps the call is being debounced.

Would you be open to a PR that adds this functionality, allowing properties to be passed during the initial boot as described in the feature request?

[deepak786]

If we allow passing some additional data only from the web during the initialization then it will be inconsistent with other platforms (Android and iOS). So I don't recommend this.

The ideal way is to chain the updateUser call after the initialize.

[Frank3K]

If we allow passing some additional data only from the web during the initialization then it will be inconsistent with other platforms (Android and iOS). So I don't recommend this.

The ideal way is to chain the updateUser call after the initialize.

Thanks for your answer. I understand. I'll try to debug why the immediate updateUser does not fire.