feat(autocapture): fetch page actions from remote config

[Dogfalo]

Summary

• Remote config for key analyticsSDK.pageActions is fetched now after plugin initialization, this requires fetchRemoteConfig to be enabled.
• It is designed to be non-blocking and doesn't slow down initialization of the plugin.
• Fixed an error where the wrong operator name was used for checking Element Text in the Labeled Event definition evaluation

Checklist

• Does your PR title have the correct title format?
• Does your PR have a breaking change?:

[promptless]

📝 Documentation updates detected!

New suggestion: Document remote configuration support for pageActions in autocapture

[cursor]

Bug: Remote Config Overwrites Local Data, Triggers Not Updated

The remote configuration for pageActions has two issues. First, the recomputePageActionsData function performs a shallow merge, causing undefined values from remote config (e.g., for labeledEvents or triggers) to overwrite existing local pageActions properties, resulting in data loss. Second, while recomputePageActionsData reassigns the evaluateTriggers function, existing event tracking subscriptions (e.g., trackClicks) retain a reference to the original function. This prevents remote config updates from being applied to active event processing.

packages/plugin-autocapture-browser/src/autocapture-plugin.ts#L185-L199

Amplitude-TypeScript/packages/plugin-autocapture-browser/src/autocapture-plugin.ts

Lines 185 to 199 in 249dd07

	// Function to recalculate internal variables when remote config is updated
	const recomputePageActionsData = (remotePageActions: ElementInteractionsOptions['pageActions']) => {
	if (remotePageActions) {
	// Merge remote config with local options
	options.pageActions = {
	...options.pageActions,
	...remotePageActions,
	};
	// Recalculate internal variables
	groupedLabeledEvents = groupLabeledEventIdsByEventType(Object.values(options.pageActions.labeledEvents ?? {}));
	labeledEventToTriggerMap = createLabeledEventToTriggerMap(options.pageActions.triggers ?? []);
	// Update evaluateTriggers function
	evaluateTriggers = generateEvaluateTriggers(groupedLabeledEvents, labeledEventToTriggerMap, options);

Fix in Cursor • Fix in Web

---

Comment bugbot run to trigger another review on this PR
Was this report helpful? Give feedback by reacting with 👍 or 👎

[daniel-graham-amplitude]

Nitpick: this try -> catch block isn't necessary. If the error gets thrown from inside of 'then' it will be caught by 'catch'.

[daniel-graham-amplitude]

Does the remote config endpoint allow us to return analyticsSDK: { browserSDK, pageActions} instead of calling these 2 separately?

[daniel-graham-amplitude]

Could this function be moved into a helper function? It looks like it does the same thing as evaluateTriggers from autocapture-plugin.ts

[daniel-graham-amplitude]

Just to confirm, this means that:

1. if the fetch fails, it will fallback to the hardcoded configuration?
2. up until the fetch is complete, it's going to use the hardcoded config?