Connect Testing-tool signals
Pass AXO audience labels to an existing testing tool.
All connectors · Checked against AXO’s implementation in October 2026.
Prepare access
Use an owner or admin account in AXO and confirm the selected site. Have permission to authorize the external account or create its server credentials. Keep secrets in the connector’s protected configuration.
| Setting | Value to prepare |
|---|---|
tool selection | Enable at least one supported tool. |
segment_attribute | Attribute name beginning axo_; default axo_segment. |
propensity_attribute | Optional axo_ attribute for high/medium/low propensity. |
Connect
Open Integrations, find Testing-tool signals, and open its setup. Enter the fields above and save with Connect (or Save changes for an existing connection).
- Enable Optimizely Web, Adobe Target at.js, VWO, Kameleoon, or Dynamic Yield.
- Create the matching custom attributes/dimensions in your testing tool. Dynamic Yield uses an axo_signal event instead.
- Install the testing tool on the same page. Save the connector and target its attributes in that tool.
Verify the result
There is no server test. Check the receiving tool’s preview/debug view. Propensity needs a trained site model and a prior scored page in the visit.
Record the AXO integration or trigger result and the receiving system’s result. A saved configuration, credential check, and completed delivery establish different things. Use a controlled destination for a test that writes data or sends a message.
Fix a failed connection
Optimizely Feature Experimentation and Adobe alloy are not written by this adapter. AXO does not measure causal lift for decisions the other testing tool makes.
For a saved catalog connector, open Health to read the latest error, then repair the settings through the setup method on this page. Pause delivery while correcting an unintended destination. Reconnect OAuth when its grant is revoked; for key-based connections, save the replacement key, verify it, then revoke the old key at the provider.
Next: create an event-triggered action, or implement a webhook receiver.