Hi @tcrewes1
The getQueryParam plugin is not inherently restricted to full-page loads. However, it is not SPA-aware either. It reads the query string from the URL at the time it is executed.
In an SPA, URL changes through history.pushState() or history.replaceState() do not trigger a full-page reload. Therefore, the plugin will not automatically execute again to capture the updated query parameters.
Try using the below flow maybe it could be of an help
-
Create a Data Element using Core → Query String Parameter and specify the required parameter (e.g., utm_source).
-
Create a rule with Core → History Change as the event to detect SPA route changes.
-
Configure an Adobe Analytics action to set the required eVar using the Query String Parameter data element.
-
Trigger the Track State / Send Beacon action after setting the variables.
If the SPA uses custom routing, you can alternatively use a custom event triggered by the application after the URL is updated.
One important point is ensure that the data element is evaluated after the URL changes and that its storage duration does not cause stale values to be returned.