Skip to main content

Plan External Scripts and Storefront Measurement - Article

Coordinate developer-managed scripts and Storefront measurement with the correct audience, placement and operational evidence.
Updated: 14 Nov 2026
5 min read

Summary

External scripts can connect the platform experience with an organization’s measurement or supporting web services. They run code in the page, so configuration belongs with a qualified developer and a clear business owner. Define the purpose, audience and expected evidence before choosing script type, placement or scope.

Use this article to:

  • Plan a specific external-service or measurement outcome
  • Understand script type, placement and audience choices
  • Distinguish Storefront interaction data from learning evidence
  • Verify a scoped implementation and maintain ownership

Define the business question first

A training provider may want to understand which Storefront searches reveal unmet demand or which catalogue view visitors use. Another organization may need an approved supporting web service on a specific audience route. Start with the question or function, not a collection of scripts copied from other sites.

For an illustrative partner offer, useful questions might be “Which product-training terms do visitors search for?” and “Does the audience find the intended catalogue view?” Those questions are different from “Who completed the training?” External web measurement and native learning analytics prove different things.

Work with the appropriate technical owner

The external-script facility is developer-managed. Open Settings → Third party integrations → External scripts where access is delegated, and coordinate creation or changes with the responsible developer and Eurekos as appropriate.

The list provides Add script. A script is a maintained configuration record, not an HTML embed inside one Course page. It can affect the page experience for its configured audience and should have a named purpose, source owner and change/removal plan.

Do not add provider code simply because a field accepts it. Confirm the intended service, supported integration route and information-handling requirements with its owner. A customer-facing business administrator can define the need without becoming responsible for writing or debugging JavaScript.

Understand the configuration choices

ChoiceWhat it controlsPractical consequence
Script type: ExternalLoads a script from its full URLThe external source and its continuing availability become dependencies
Script type: InlinePlaces the supplied code in the pageThe maintained code belongs to this configuration record
Script attributesAdds supported attributes for an external scriptUse the provider/developer’s agreed attributes
Render as noscriptWraps supported inline content for the no-JavaScript caseIt is a distinct fallback mechanism, not normal script execution
Placement: Header or FooterChooses the page head or body placementUse the placement required by the approved implementation
Insert at top of bodyPlaces a body script at the start rather than the endReview with the developer when the service needs that position
DisabledExcludes the script from loadingA controlled way to stop that configured script
Roles and OrganizationsLimits the intended audienceEmpty Roles includes every role; empty Organizations applies no organization filter

Leave Roles empty to apply the script to every role, or select the roles that should receive it. Leave Organizations empty to apply no organization filter, or select the organizations and suborganizations whose members should receive the script. A role selection does not remove an organization restriction.

Selecting a parent organization includes its suborganizations. Selecting specific suborganizations targets those branches, including their own child organizations. For example, select a regional partner organization to include its local branches; select one branch when the service should be limited to that branch and its descendants.

Scripts normally do not run for anonymous visitors. An organization-scoped script can run before sign-in when the visitor arrives through that organization’s Invite by email, QR invite or Custom URL, or through an Activity description shared using Share on behalf of Organization. Test the actual entry route as an anonymous visitor as well as with a signed-in account.

Where Page visibility is available, choose All pages, Only selected pages or All pages except selected pages. Use Page addresses for the selected-page choices: enter one path per line without the website domain. Use * for multiple subpages. For example, enter storefront and storefront/* on separate lines to include both the Storefront itself and its subpages; the wildcard alone covers only the subpages. Combine page targeting with the intended role and organization scope, then test an included page and an excluded page.

Keep Storefront measurement precise

The Google Tag Manager extension supports catalogue-search information including catalog_search_text, catalog_search_tags and catalog_view_mode. Agree the supported setup and event configuration with Eurekos and the measurement developer before implementing it.

Use the configured provider’s preview/debug evidence to verify that a specific supported interaction produces the expected parameters. A script appearing in a page is not proof that a measurement event reached the destination, and a catalogue-search event does not prove enrollment, payment or completion.

If the purpose is native participation or learning-performance analysis, use the relevant Eurekos report. External measurement can complement those reports with discovery or web-interaction context, but it should not replace their record definitions.

Maintain a scoped implementation

Record which audiences and entry routes should receive the script and why. Test a person inside the scope and someone outside it, as well as the relevant anonymous route. Review performance and the actual page behavior with the developer before scaling the configuration.

When an external provider changes its code or service requirements, revisit the configuration and outcome evidence. Disabling a script record is different from deleting external data, withdrawing every provider authorization or changing a learner’s training access.

Verify the configuration

Scenario or checkExpected result or evidence
Intended page and audienceThe approved script loads in the correct placement
Person outside a configured scopeThe audience boundary behaves as designed
Relevant anonymous organization routeActual visitor behavior is checked separately
Supported Storefront interactionProvider debug evidence shows the intended event and parameters
Native learning result is requiredThe appropriate Eurekos report supplies that evidence
Script is disabled in a controlled changeThat configured script stops loading without assuming unrelated service changes

Troubleshooting

ProblemWhat to check
A script does not runDisabled state, type, code/URL, placement and audience scope with the developer
The audience is broader than intendedEmpty Roles/Organizations selections and hierarchy inheritance
Anonymous behavior differs from an administrator testThe actual organization-context entry route and visitor state
Code loads but measurement is absentProvider event configuration and debug evidence for the supported interaction
Search data is being treated as completion evidenceUse native learning records for completion and external measurement for its defined interaction
An external update changes page behaviorCoordinate the source change and the maintained implementation owner before broad reactivation

Third Party Integrations

FAQ