We’re running redirect-based testing, but I’ve not...
# ask-questionsq
quiet-librarian-1778
10/08/2025, 6:00 PMWe’re running redirect-based testing, but I’ve noticed that our Facebook pixels (and other tags) are firing on both pages. What’s the best practice to prevent that from happening? We don’t have full control since we’re using a landing page builder, so going fully server-side isn’t an option...
b
billions-house-96196
10/08/2025, 7:25 PMIMO avoid client side redirect tests whenever possible. So many ways it could bite you. Could maybe put a timer delay on your pixels.
q
quiet-librarian-1778
10/08/2025, 7:35 PM@billions-house-96196 Yea, the issue is we are using a landing page building like kajabi. So we don't have server side access.... time delay. Hmmm.
quiet-librarian-1778
10/09/2025, 5:55 PM@strong-mouse-55694 Do you have any thoughts by any chance? 🙂 I don't remember having this issue with VWO. Maybe th mechanisms are different for how traffic is routed?
s
strong-mouse-55694
10/09/2025, 6:11 PMMerritt's advice is spot on, but I recognize the constraints.
Some other ideas:
• Minimize navigation delays if present. Are you setting a delay in the redirect? This is tricky to get right and requires some trial and error
• Conditionally fire the tracking events if possible. This would require some custom scripting.
• Some duplication may be unavoidable, so you'd need to dedupe on the analysis side.
• The big lift would be to move to edge evaluation, but that'd require a large infrastructure change that or may not be possible
q
quiet-librarian-1778
10/09/2025, 6:18 PM@strong-mouse-55694 In our case - since we don't own/host the landing pages. To use edge -- we would need to created a sub-domain -- and route traffic through there? Am I correct. We use kajabi.com.
Edge seems like it would solve the issues...
Conditional works - but we use the facebook pixel plugin with the platform kajabi. So we don't have full control on that as well 😕 I was able to do this with our own tracking - pageviews, etc.
quiet-librarian-1778
10/09/2025, 6:49 PM@strong-mouse-55694 Does the below look correct. We might be able to set this up...
Copy code
Step-by-Step Setup:
1. Keep Your Exact Same Domain
No change to your URL
Visitors won't notice any difference
All your links stay the same
2. DNS Changes Required
Instead of pointing directly to Kajabi:
<http://yourdomain.com|yourdomain.com> → Cloudflare → Worker (GrowthBook) → Kajabi
3. The Magic: Transparent Proxy
The Edge App runs as a smart proxy layer between your application and your end users Cloudflare Workers Edge App & SDK | GrowthBook Docs
Your Cloudflare Worker configuration:
tomlPROXY_TARGET = "<https://your-site.kajabi.com>" # Your Kajabi subdomain
# Your domain stays as <http://yourdomain.com|yourdomain.com>
4. What This Enables
Instant Redirects: Test different Kajabi pages/funnels
A/B Testing: Split traffic between different approaches
Personalization: Show different content based on user attributes
Feature Flags: Gradually roll out changes
No Kajabi Limits: Bypass Kajabi's redirect limitations
Important Benefits:
Invisible to Users: URL redirects happen behind the scenes (the public-facing URL does not change) Cloudflare Workers Edge App & SDK | GrowthBook Docs
Zero Downtime: Set up and test before switching DNS
Instant Rollback: Can disable anytime by changing DNS back
Keep Everything: All Kajabi features continue working normallys
strong-mouse-55694
10/09/2025, 9:40 PMIt's definitely feasible—but it's also a major infrastructure change. I'd likely try it first with a test Kajabi site + GrowthBook + Cloudflare setup to fine tune everything, and if it's working well, then move over. But it'd definitely eliminate your issues.
28 Views