Dynamic accounts are only supported using legacy JavaScript implementations (H Code). These variables are not supported in current AppMeasurement libraries or tags in Adobe Experience Platform.
Dynamic accounts is an implementation feature that lets you determine what report suite to use based on criteria you define. If your organization requires more than one report suite but would like to use the same implementation between your sites, dynamic accounts is a good solution.
Adobe recommends sending data to a single report suite, then using virtual report suites to separate data if needed. See Global report suite considerations for more information.
3 variables are used to dynamically select a report suite.
dynamicAccountSelection
: Enable or disable dynamic account selection.dynamicAccountMatch
: Determines what value to observe. For example, the URL or a query string.dynamicAccountList
: Compares the values with dynamicAccountMatch
, and if a match is found, populates the account
variable.If dynamicAccountSelection = true
, the value within dynamicAccountMatch
is compared to dynamicAccountList
. If the values in dynamicAccountList
match, the report suite ID is included in the account
variable.
The account
variable can be set first, and acts as a default value in case any of the specified strings cannot be found. For example:
s_account = "examplersiddefault";
s.dynamicAccountSelection = true;
s.dynamicAccountMatch = location.hostname;
s.dynamicAccountList="examplersiddev=dev.example.com;examplersidprod=example.com";
If location.hostname
was neither dev.example.com
or example.com
, the hit would be sent to examplersiddefault
.
Multi-suite tagging can be used with dynamic account selection. For example:
s.dynamicAccountSelection = true;
s.dynamicAccountMatch = location.hostname;
s.dynamicAccountList="examplersid1,examplersid2=example.com";
If location.hostname
contains example.com
, the hit is sent to both examplersid1
and examplersid2
.