Segment integration performance question

[sk-roofr]

I'm using several integrations (around 5–6) with Segment. Since some of them are heavy—like Google Tag Manager—they noticeably slow down the initial load. I know there are techniques to load Google Tag Manager asynchronously, but I don’t think that’s possible when it's loaded through Segment.

I’m aware that Segment supports buffering, so events can be sent later. However, Amplitude needs to load early in order to identify the user and fetch A/B testing data.

Is there a way to load one of the integrations separately and inject it into Segment later? Also, are there any known tips or tricks to improve page load performance when using multiple Segment integrations?

[silesky]

Hey @sk-roofr

Is there a way to load one of the integrations separately and inject it into Segment later?

Sorry, all destinations must be declared on analytics.load(), we don't currently support lazy registration of destinations, like we do other types of plugins. 😢

Also, are there any known tips or tricks to improve page load performance when using multiple Segment integrations?

The one optimization I can recommend is that you can save the cost of the destination network requests by installing destinations through npm.

Note: the destinations are still just a wrapper around other externally-loaded scripts (GTM, etc), so you will still incur the cost of loading those destinations, but can help with network qeueing-based perf issues.