Share how Replo can make their product better for you and your team.
Use Case for Google Shopping - Dynamic Page/Product update depending on product source.
The main challenge is figuring out how to dynamically generate the Replo landing pages for each product, rather than having to create a new page for each one manually. They have a large number of products (around 250) included in their Google Shopping campaigns, all in the same ad group. They want to do A/B testing on the landing pages for these Google Shopping ads, where 50% of the traffic goes to their standard product page and 50% goes to a modified landing page they create in Replo. The goal is to test different product page designs to see which one performs better in terms of conversion rate across an aggregate of the products, rather than just testing one product at a time. They don't want to do individual tests for each product, as that would be too much work. They want to be able to do a single test that applies across all the products in their Google Shopping campaigns.
Reviewed
Ability to Opt our store Out of Replo Analytics
We’d like to remove the Replo Pixel firing on our site so we know it won’t slow down our site. While we’ve been told by the Replo product team the pixel won’t create any slowing effect, we still would like the control to make the decision for ourselves.
Reviewed
Group Metrics by URL Keyword on Deep Dive Page
I’d like to request a feature that allows filtering by “URL contains” on the Deep Dive page. Specifically, I’m looking to view aggregated analytics—such as CVR, RPV, total sessions, etc.—for all landing pages that share a common word in their URL slug. For example, I want to see these metrics for all pages that contain the word “gummies” in the URL. While the Overview page currently allows filtering by URL contains, it only shows stats for individual pages, not a combined view. Having the ability to see average performance metrics across a group of pages would be incredibly valuable for analyzing trends and optimizing landing pages. This could also be a helpful feature for other merchants who want to track performance across similar page types. Thanks!
Reviewed
Add "Week" View to Analytics Charts
Currently can view by day (or hour on short timeframes). Weekly view would help smooth out trends
Reviewed
Add Notes to Analytics Dashboards
Similar to how Google Ads does it. This would be helpful for helping teammates understand when things changed with the store/funnel setups. Or just helping someone remember something for themselves.
Reviewed
A/B Testing & Analytics Graphs Should Include Published Page Milestones
Would be great if Page Analytics included the dates new page versions were published and other significant milestones. This would help understand how variations and trends in the graph results correspond with changes made on the Replo Pages themselves.
Reviewed
Export Replo Analytics
Allow to export data from Replo Analytics - would be in the format of a csv to begin. Possibly more formats down the line. If there are any specific format requests, please reply in the thread here!
Reviewed
Replo Analytics: Add an option to /not/ compare timeframes
Would like to have the option to not compare dates. Sometimes it adds too much visual noise to the charts with data I’m not interested in. When trying to set a shorter timeframe so you only see the comparison line during the first point(s) on the x axis you get hit with an error.
Reviewed
Replo A/B Testing - testing on existing urls/domains!
A/B testing is great, however not being able to run the experiments on existing urls is a big blocker. Any existing campaign cannot be tested on without changing links. Which makes using this feature pretty much obsolete. Would be amazing if this was possible :) BEST KNOWN WORKAROUND So let's say you have AD1 sending to URL1 and that's the setup you're not trying to mess up because of social proof. And let's say the Replo A/B test you setup uses TestURL_1 which splits traffic to VariantA_URL and VariantB_URL. The workaround requires a few things: URL1 and VariantA_URL and VariantB_URL will have to be different URL1 must be a /pages/ page on Shopify (not the homepage or a product, etc) From there you can setup a Shopify Redirect to redirect traffic sent to URL1 to TestURL_1. So the new chain look like: 1) AD1 sending to URL1 -> notice no change here 2) Shopify Redirect Action from URL1 to TestURL_1 -> the "workaround"3) TestURL_1 which splits traffic to VariantA_URL and VariantB_URL -> standard setup of a Replo A/B Test. This redirect operation is outlined here.
Planned
Ability to track CTR of a button
this simple step should be your priority ability to mark certain CTA buttons as a "goal" and then show us % of people that clicked on the CTA button to proceed to the next page