Integrations
Connect destinations from Admin → Integrations. Credentials are encrypted at rest and never exposed in the dashboard after saving. All integrations support a Test action, a soft-delete with 30-day restore window, and a live health log.
Meta Conversions API (CAPI)
Server-side conversion forwarding to Meta – bypasses browser-level ad blockers and iOS privacy restrictions. AXO hashes PII (email, phone) with SHA-256 before transmitting and automatically maps fbp / fbc cookies from the tag. Supports test event codes for QA validation in Meta's Events Manager.
Google Enhanced Conversions
Server-side enhanced conversion reporting to Google Ads. PII is SHA-256 hashed per Google's spec. AXO captures gclid automatically via the tag and includes it in the conversion payload for attribution. Test event codes are supported.
Email & Messaging (Klaviyo, Braze, Resend)
AXO can fire profile and event data to your ESP via Triggers. For Klaviyo: provide your private API key; AXO will track events and update profile properties. For Braze: provide your REST endpoint and API key. For Resend: provide your API key and a from-address for transactional emails. These are the destinations used by the Abandoned Cart and Welcome New Customer play templates.
Salesforce CRM Sync
Bidirectional Salesforce sync, set up on the Admin → Salesforce screen – also reachable by clicking the Salesforce connector in Integrations. Contact and Opportunity fields are pulled into AXO profiles as crm_attribute values, available as segment predicates. The sync runs on a scheduled cron and can also be triggered manually. The CRM Sync page provides a contact-level view with validation, currency input, and data enrichment.
Testing-tool signals (Optimizely, Adobe Target, VWO, Kameleoon, Dynamic Yield)
Already running a testing tool? Turn on Testing-tool signals and the tag writes the visitor's AXO segment – plus a high / medium / low propensity tier on sites with a trained propensity model – into that tool as its own visitor attribute, so you can target the tool's experiences on it. Optimizely Web gets a custom attribute, Adobe Target (at.js) an in-page profile attribute, VWO a user-scoped custom dimension (or a visitor attribute in Data360 workspaces), Kameleoon custom data, and Dynamic Yield an axo_signal custom event. Attribute names are yours but must start with axo_; create them in the tool first. Same rules as ad audience signals: nothing is written without consent or when the tool isn't on the page, one write per pageview and verdict, and the tool's own render is never held. AXO does not measure lift for decisions made inside these tools – the scorecard reports only AXO-rendered decisions against AXO's holdout.
Webhooks
Configure a generic webhook destination to receive real-time events. Every delivery is HMAC-SHA256 signed – verify the X-VibeTag-Signature header (a hex digest of the raw body, keyed by the secret you set on the integration – always set one, because without it the signature falls back to your public site_id and proves nothing) on your endpoint; the X-VibeTag-Event header carries the event type. Supported event types: visitor events (profile.identified, segment.changed, conversion, add_to_cart, abandon_cart, pageview, click) plus control-plane events for agents and automations (experiment.ended, experiment.shipped, experiment.guardrail_paused, variant.watchdog_disabled, trigger.fired, lead.captured, call.completed, generation.finished, crawl.completed, campaign.launched, campaign.paused, campaign.closed, stall.found). Payload shapes and a verification snippet are in the ingestion & webhooks reference. Webhooks can be used to fan events out to any downstream system not covered by a native integration.