Tailor AIINTEGRATION Β· GA4
Your experiments should show up where your team already looks.
Last updated March 1, 2026
Most optimization tools keep results in their own dashboard. Your team does not check that dashboard. They check GA4. Tailor sends experiment events, conversion data, and variant performance directly to Google Analytics 4, so results appear in the reports your team already uses.
The problem
Experiment results stuck in a tool nobody checks. Results need to appear in GA4 where the team makes decisions.
What this covers
How Tailor fires GA4 events, experiment dimensions, conversion tracking, and practical reporting patterns.
The gap
Experiment results live in a silo
Teams run experiments but results live in a tool that only the person who set up the test ever opens. The marketer who needs to justify budget looks at GA4, not the testing tool. The VP who approves next quarter's spend looks at GA4. The agency partner sending weekly reports pulls from GA4.
The gap shows up the same way in most GA4 setups:
We don't meaningfully have access or have GA4 incorporated into our workflow.
Google ad group aggregation is a material limitation.
It's really hard to get per-page performance information in Google Ad Manager.
Analytics and alerting pain is bigger than landing page pain for us.
Setting up conversion goals for Google Ads is a huge pain.
The optimization tool might be producing real lift. But if the results do not appear where your stakeholders are already looking, that lift is invisible. And invisible lift does not get budget renewed.
How it works
How experiment data reaches GA4
Tailor pushes a tailor_experiment event to the dataLayer on each page load where an experiment is active. The event includes the experiment ID, variant group (control or treatment), ramp stage, and ramp percentage. If you use Google Tag Manager, you can forward this event to GA4 as a custom event with those values as event parameters.
Tailor fires events when:
- A visitor is assigned to an experiment (fires tailor_experiment with experimentId, experimentGroup, rampStage)
- The experiment variant is rendered on the page
- A conversion goal is triggered (form submit, CTA click, or custom event you define)
You map these dataLayer values to GA4 event parameters in GTM. Once configured, experiment data flows into your GA4 reports alongside your existing data.
"Every time we launch a new experiment, someone has to manually create the conversion event in GA4." With Tailor, the dataLayer event fires automatically for every experiment. You set up the GTM trigger once.
Data flow
What gets sent to GA4
Here is a breakdown of the data that flows from Tailor into your GA4 property:
Experiment ID and variant label
Sent as custom dimensions so you can filter and segment by experiment in any GA4 report.
Conversion events with experiment attribution
Each conversion carries the experiment context, so you can attribute conversions to specific variants.
Page-level metrics by variant
Standard pageview and engagement metrics flow with experiment dimensions attached.
Revenue events (if configured)
When you track revenue in GA4, experiment attribution carries through to revenue reporting.
This data works with GA4's built-in exploration reports, segments, and audiences. No additional GA4 configuration is needed. Events appear in the Events report automatically.
Where to look
Use Tailor's dashboard, GA4, or both
Tailor has its own analytics dashboard at app.tailorhq.ai that shows experiment results in real time: traffic per variant, conversion rates, and statistical significance. For many teams, this is enough.
The GA4 integration is for teams that need experiment data in the same place as their other marketing metrics. Common reasons: your VP reviews GA4 weekly, your agency pulls GA4 reports, or you want to build GA4 audiences from winning experiment variants for remarketing.
You can also set conversion goals in Tailor that reference events already tracked in GA4. For example, if you track "trial_signup" in GA4, you can select that as Tailor's experiment goal. Tailor then measures lift against that event without requiring you to duplicate tracking code.
See GA4 integration in action
Read the analytics integration setup docs.
Reporting patterns
How teams actually use this
Patterns we see from teams that have connected Tailor to GA4.
Exploration reports by experiment
Build a GA4 Free Form exploration filtered by experiment ID to compare variant performance side by side. This is the most common starting point.
Audiences from winning variants
Create GA4 audiences based on visitors who saw a winning experiment variant. Use those audiences for remarketing in Google Ads.
Google Ads conversion loop
Use Google Ads conversion import from GA4 to close the loop: ad click to experiment variant to conversion. This connects ad spend directly to experiment results.
Landing page report comparison
Compare Tailor experiment data against your existing GA4 landing page reports to see how personalized pages perform relative to your baseline.
Cross-domain tracking
If your checkout or signup flow lives on a different domain, ensure GA4 cross-domain tracking spans both domains so experiment attribution carries through.
"We were exporting CSVs from the testing tool and pasting them into Google Sheets every Monday." GA4 integration eliminates that manual step by putting experiment data where the team already reports.
Prerequisites
Before you start
Make sure you have the following to send Tailor experiment data to GA4:
- A GA4 property with admin or editor access. You need permission to view events and optionally register custom dimensions.
- The GA4 measurement ID (starts with G-) and a working gtag.js installation on your site, either via a direct script tag or Google Tag Manager.
- Tailor installed on your site. The GA4 integration sends events from the Tailor script, so Tailor must be running before events can flow to GA4.
- Google Tag Manager (recommended but not required). GTM makes it easier to manage consent mode, event forwarding, and debugging without code changes.
No GA4 API keys or service accounts needed. Tailor fires events using the standard gtag format that your existing GA4 property already understands.
Troubleshooting
Common issues
Events not appearing in GA4 Real-Time reports
GA4 Real-Time reports show events within seconds, but they require at least one active user on the site. If you do not see events, check that your GA4 tag is firing (use Google Tag Assistant or GTM Preview mode). Also confirm that consent mode is not blocking the events. Cookiebot and similar tools can suppress analytics events until the visitor accepts cookies.
Duplicate events from GTM and inline script
If you have both a gtag.js script tag in your page head AND a GA4 Configuration tag in GTM, events may fire twice. Use one or the other, not both. The most common setup is a single Google Tag in GTM. Check your page source and GTM container for duplicate GA4 measurement IDs.
Custom dimensions not populating
Tailor sends experiment ID and variant label as event parameters. For these to appear as dimensions in GA4 Explorations, you need to register them as custom dimensions in GA4 (Admin > Custom Definitions > Create Custom Dimension). Events will still appear in the Events report without this step, but custom dimensions enable filtering and segmentation.
24-48 hour delay for some GA4 reports
GA4 Real-Time shows data immediately, but standard reports (Explorations, Engagement, Conversions) can take 24-48 hours to fully process. If you added Tailor today and do not see data in standard reports, check Real-Time first to confirm events are flowing, then wait for standard reports to catch up.
Consent mode blocking experiment events
If you use Cookiebot, OneTrust, or another consent management platform with GA4 consent mode, experiment events may be blocked until the visitor grants analytics consent. This is expected behavior. You will see lower event counts in GA4 compared to Tailor's built-in analytics because Tailor can track events without cookie consent.
QA
Verify experiment data is flowing to GA4
Follow these steps to confirm that Tailor experiment events are reaching your GA4 property:
- 1Open your site in Chrome and trigger an active Tailor experiment (visit a page with targeting rules you match).
- 2Open GA4 and go to Reports > Realtime. You should see active users within 30 seconds.
- 3In the Realtime report, scroll to "Event count by Event name." Look for Tailor experiment events (e.g., tailor_experiment_view or your configured event name).
- 4Click into the event to verify the event parameters include experiment ID and variant label.
- 5If you use GTM, open GTM Preview mode (tagassistant.google.com) and navigate your site. Verify that Tailor events appear in the GTM event stream and that your GA4 Configuration tag fires.
- 6For Explorations, wait 24-48 hours, then build a Free Form exploration filtered by experiment ID to confirm data is available for analysis.
If events appear in Realtime but not in standard reports after 48 hours, check that GA4 data retention is not set to a very short window (Admin > Data Settings > Data Retention).
FAQ
Frequently asked questions
Stop checking two dashboards. See experiment results in GA4.
Connect Tailor to your GA4 property and see variant performance where your team already reports.