Extension Configuration
Settings below are only available in Pro Mode
Below are the configuration settings available for Apollo QAX. You configure the settings below in the Launch extension configuration.
Apollo QAX in the Launch Extension Catalog
All settings must be saved and built into a relevant launch property library to take effect.
This option allows you to enable or disable the extension for libraries in any or all of the 3 launch environments.
Apollo QAX includes an optional integration with Airbrake for logging errors.
Requirement:
This option requires the Airbrake JS Notifier extension to also be installed in the Launch property.
Airbrake is a paid tool for use with a subscription.
The configuration to enable the Airbrake Integration with Apollo QAX requires the Airbrake Project ID and Project Key.
The Project ID and API Key can be retrieved from the Airbrake project settings (top right)
These settings effect how QAX validates Adobe Analytics.
- Maximum eVar: Should be set to match the available number of eVars for the company. 75, 100, 250
- Local Storage Type: Sets the location where configuration and other settings will be stored in the clients browser.
- Hosted Config Version (Read Only) Displays the version of the Apollo test case configuration file that QAX will retrieve. It is important to ensure the last version published by Apollo is the version that QAX will retrieve when the extension runs.
Simple on off options for various AArdvark validations.
Simple on off options for various AArdvark validations with one exception.
- List Currency Events: This list appears when you enable "Validate currencyCode for currency events". This list should only include events which are configured in Adobe Analytics as currency events.
Simple on off options for various AArdvark validations.
Simple on off options for various AArdvark validations with one exception.
- List Product Syntax Merchandising eVars: This list appears when you enable "Validate the setting of product syntax merchandising eVars". This list should only include eVars which are configured in Adobe Analytics as product syntax merchandising eVars.
Last modified 2yr ago