Sending Events to Analytics Platforms
Send Tailor experiment data to Amplitude, Google Analytics, Segment, Microsoft Clarity, and other analytics platforms
Overview
Tailor can send a tailor_experiment event (which test the visitor is in and which page they saw) to your analytics platforms so you can track performance and build funnels in your existing workflow. There are three ways to set this up: the toggle-based approach (recommended), a cookie your own code reads for in-house analytics, or a manual callback for advanced use cases. Conversions are not sent this way; Tailor measures those itself.
Tailor sends experiment data to GA4 with a single switch in Settings. Tailor can also hook onto JavaScript events that fire to GA4 and use them as Tailor conversion goals. Full GA4 data import into Tailor analytics is available upon request. Amplitude data import is available today.
Toggle-Based Setup (Recommended)
The easiest way to send experiment events to your analytics platform. No code required. Just flip a toggle in your Tailor settings.
- Go to Settings β Your connections β Analytics
- Under Your analytics tools, toggle on the platforms you use (Amplitude, Google Analytics, Segment, or Microsoft Clarity)
Requirement: Your analytics provider script (e.g., Amplitude SDK, GA4 tag, Segment snippet, Clarity tag) must already be installed on pages where the Tailor script is installed.

Once enabled, Tailor sends a tailor_experiment event with the five event properties to the selected platforms on every page load where the visitor is in a test. No callback code needed.
When it fires. On a site with a consent tool, Tailor waits for the visitor to accept cookies, then waits up to 30 seconds for the platform's SDK to appear on the page. Nothing is sent for holdout visitors, preview links or the editor, so your analytics sees a clean comparison between the pages in the test.
Microsoft Clarity works a little differently: instead of event properties, each visitor's Clarity session gets a tailor_<testId> tag set to the page they saw (control, variant-1, and so on), plus a tailor_experiment event. Filter recordings and heatmaps by the tag to compare pages, or by the event to find every session that was in a Tailor test.
Manual Callback Integration (Advanced)
Most customers use the toggle-based setup above and don't need this section. The manual callback is for teams that need custom event formatting or want to send to unsupported platforms.
If you need full control over event formatting or want to send to a platform not listed above, you can configure a custom callback in the Tailor init script. Choose your analytics platform below to see the implementation code:
How the callback fires. With analyticsProvider set, the callback waits for cookie consent and for that platform's SDK, like the toggle does. If the toggle for the same platform is also on, the toggle wins and the callback is skipped. Without analyticsProvider, the callback runs as soon as the test is served, with no consent wait, so gate it yourself if your site needs to. Either way it is skipped for holdout visitors, preview links and the editor.
<!-- Begin Tailor AI Script -->
<script src="YOUR TAILOR SCRIPT HERE" async></script>
<script id="tailor-init-script">
(window.TailorQueue || (window.TailorQueue = [])).push(function() {
Tailor.init({
analyticsProvider: 'amplitude',
experimentInitCallback: function (tailorEvent) {
amplitude.track('tailor_experiment', {
experimentId: tailorEvent.experimentId, // Unique ID for each test
experimentGroup: tailorEvent.experimentGroup, // 'control', 'variant-1', 'variant-2', ... ('treatment' carries the same value for older integrations)
rampStage: tailorEvent.rampStage, // 'in_experiment', or 'fully_ramped' once one variant is at 100%
rampPercentage: tailorEvent.rampPercentage // Share of visitors this variant gets, 0-100
});
}
});
});
</script>
<!-- End Tailor AI Script -->Available Event Properties
The toggles and the cookie send exactly these five properties. The manual callback receives them on its tailorEvent argument, plus the extra fields listed below the table.
| Property | Type | Description |
|---|---|---|
| experimentId | string | Unique ID for each test, named after the page it started on |
| experimentGroup | string | The page the visitor saw: "control" is the original, "variant-1", "variant-2" and up are the variants. Tests created before variants were numbered report "treatment". |
| rampStage | string | "in_experiment" while visitors are split between pages, "fully_ramped" once one page gets 100% |
| rampPercentage | number | Share of visitors the visitor's own page gets, 0-100 |
| guestId | string | Tailor's id for this browser |
The manual callback's tailorEvent also carries, when available:
treatment: the same value asexperimentGroup, kept for integrations written before the renametreatments: every page in the test, each with itsnameandfractionof visitors (0 to 1)enrichmentData: the visitor's company enrichment, when your account has enrichment on and a match was found
Example Funnel Analysis (in Amplitude)
Once your Tailor AI experiments are sending events to Amplitude, you can create funnel analyses to compare conversion rates between the control and each variant. Here's an example of a funnel analysis comparing test variants:

Key setup steps in Amplitude:
- Navigate to the "Funnel" analysis type
- Add the
tailor_experimentevent as your first step - Filter by
experimentIdto select your specific test - Group by
experimentGroupproperty (shows "control" and "variant-1", "variant-2" and so on) - Add your conversion event(s) as subsequent steps (e.g., "Element Clicked", "Form Submitted")
- Analyze the conversion rate differences between variants
Pro tip: Use the rampStage property to filter for users in the "in_experiment" stage to ensure you're only analyzing users who were actually exposed to your experiment.
Custom Event Names
When using the manual callback, you can customize the event name by changing 'tailor_experiment'to any name that fits your analytics naming convention. For example:
ab_testexperiment_startedtailor_split_test
Troubleshooting
Toggle-based setup: If you're using the toggle-based setup and events aren't appearing, verify your analytics provider is installed on the same pages as Tailor, and that its SDK loads within 30 seconds of cookie consent. Test in a normal browser window: nothing is sent for holdout visitors, preview links or the editor.
Cookie: If the cookie is missing, check that the visitor is in a test and has accepted cookies. It is written in the browser after the page loads, so your server first sees it on the visitor's next page.
If you're using the manual callback and encounter issues, verify that:
- Your analytics platform is properly initialized
- The tracking function names match your platform's API
- No errors appear in the browser console related to analytics
- Events appear in your analytics platform's real-time or debug view
