Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A/B testing based on git branches #331

Open
zappys opened this issue Dec 21, 2019 · 36 comments
Open

A/B testing based on git branches #331

zappys opened this issue Dec 21, 2019 · 36 comments
Labels
feature-request New feature or request

Comments

@zappys
Copy link

zappys commented Dec 21, 2019

Can we setup A/B tests using git branches ?
We are thinking to move from netlify to amplify-console but this is holding us back.

You can see how netlify implements this here: https://docs.netlify.com/site-deploys/split-testing/#run-a-branch-based-test

Is there any way we can setup a split test with ampify-console ?

@kahdojay kahdojay added the question Further information is requested label Dec 23, 2019
@swaminator swaminator added feature-request New feature or request and removed question Further information is requested labels Dec 26, 2019
@rallona
Copy link

rallona commented May 4, 2020

Hi!! Any improvement related with A/B testing? I need it working on amplify.

@Munsterberg
Copy link

Any progress on this?

@alexkates
Copy link

+1

@HeinrichTremblay
Copy link

This feature would be great! For Gatsby based projects, the A/B testing approach by using git branches is the one officially recommended in their docs with Netlify. Here's the link: https://www.gatsbyjs.org/docs/ab-testing-with-google-analytics-and-netlify/

@karimjp
Copy link

karimjp commented Sep 7, 2020

Any updates?

@kylekirkby
Copy link

I'd also love for this feature to be added!

@intonumbers
Copy link

I would also be highly interested in this feature!

@avnerkhan
Copy link

Me too! This would. be a great feature to have.

@Uri-CyberWrite
Copy link

+1 on this feature, A/B testing based on git branches on top of AWS Amplify would be an amazing feature to have!

@maximussinclair
Copy link

Yes please!

@redixhumayun
Copy link

+1 on this feature.

@Erick-Suarez
Copy link

+1

3 similar comments
@Belrald
Copy link

Belrald commented Jan 14, 2021

+1

@MarwanNakhaleh
Copy link

+1

@carlotamolintr
Copy link

+1

@raunaqss
Copy link

+1 (would pay for this feature in AWS Amplify Console)

@afontcu
Copy link

afontcu commented Apr 21, 2021

We are thinking to move from netlify to amplify-console but this is holding us back.

This is our situation as well. So, +1

@bajcmartinez
Copy link

+1

@raunaqss
Copy link

This would be unreal

@mark-04
Copy link

mark-04 commented Jul 8, 2021

+1

2 similar comments
@gwidonw
Copy link

gwidonw commented Aug 2, 2021

+1

@marvinbernd
Copy link

+1

@SimonHoiberg
Copy link

+1 🔥

Like, seriously.
I got it working by hacking around the lambda@edge functions Amplify create, but a UI to set this up would be AMAZING!

Come on, Amplify team! Please, give it to us 🤩

@NickEast12
Copy link

+1

@Pijuli
Copy link

Pijuli commented Apr 12, 2022

🤔🤔🤔

@woolimi
Copy link

woolimi commented May 5, 2022

Any news about it ?? please, we really need this 🙏

@tmosmant
Copy link

tmosmant commented Jun 8, 2022

@SimonHoiberg can you share how you hacked the lambda@edge functions? We don't find them in our AWS console.

@SimonHoiberg
Copy link

@SimonHoiberg can you share how you hacked the lambda@edge functions? We don't find them in our AWS console.

Lambda Edge functions are created in the us-east-1 region (N. Virginia).
Go to that region and then find the Lambda Edge functions under the Lambda section.
They'll have the description "Default Lambda@Edge for Next CloudFront distribution".

It's horrible though. There's a ton of code, and it took us quite a long time to find out how to alter it in the right way.
I don't have the actual code anymore to share, unfortunately.

But let's use this occasion to push the AWS Amplify team once again 👊
We want this inbuilt!

@jd-carroll
Copy link

@SimonHoiberg do you think what I am trying to do in #2812 would also work for your use cases?

@mkarsene
Copy link

Its like the amplify team is asleep at the wheel. Thought AWS was customer first... :P

@kaaroIndus
Copy link

Any workaround for this? I came across running these manually using middlewares. Nothing as neat as linking branches to the split. Would have to maintain the alternatives versions of each file.

@BenjaminJameson
Copy link

+1

@ghost ghost added the e2e-cypress-tests Cypress/E2E test step issue label Jan 27, 2023
@hanna-becker
Copy link

We'd also love to see an A/B testing solution for Amplify!

@iandesj
Copy link

iandesj commented Sep 15, 2023

+1

1 similar comment
@arpitSB
Copy link

arpitSB commented Jan 22, 2024

+1

@mauerbac mauerbac removed the e2e-cypress-tests Cypress/E2E test step issue label Mar 5, 2024
@tettoffensive
Copy link

So is there no way to do A/B or multivariant split testing with amplify using 302 redirects? Normally we've done this in an .htaccess file on non-amplify projects with something like this:

RewriteCond %{REMOTE_ADDR} ([02468])(?!.*\d)
RewriteRule ^$ /r [R=302,QSA]

I was hoping that the condition (The condition for a URL rewrite or redirect rule, such as a country code.) might support something.

I guess my best option is to use client side javascript to handle the test?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request
Projects
None yet
Development

No branches or pull requests