[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/conv/ - Conversion Rate

CRO techniques, A/B testing & landing page optimization
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1793518539010.jpg (97.9 KB, 1024x1024, img_1793518530523_wc642qsu.jpg)ImgOps Exif Google Yandex

e6190 No.2389[Reply]

been seeing too many people testing newsletter modals on every single page load. if you're running an A/B test on a popup, use this to make sure it doesn't annoy the user back into leaving.

const popupShown = sessionStorage.getItem('popup_seen');if (!popupShown) {showModal();sessionStorage.setItem('popup_seen', 'true');}


it's better to just hide it once they've seen the variant. does anyone actually use cookies for this anymore?


File: 1792989273759.jpg (284.9 KB, 1024x1024, img_1792989265318_ijhf73ol.jpg)ImgOps Exif Google Yandex

df553 No.2354[Reply]

been seeing way too many people rely on generic click listeners that fire before the actual conversion tag even loads. it's messy and usually results in missing undercounting your real wins. if you're tracking a specific checkout button, just hardcode the trigger directly into the onclick attribute or use a custom event call right after the logic fires. it's much more reliable than waiting for some global listener to catch a bubbling event.
gtag('event', 'conversion', {'send_to': 'AW-123456789/AbC-D_eFGhiJkLmNoP','value': 1.0,'currency': 'USD'});

use this when you have a high-value element that shouldn't be left to chance by some generic script. does anyone else still trust generic click tracking for primary buttons?

132aa No.2383

File: 1793415172497.jpg (271.78 KB, 1024x1024, img_1793415158372_6azk6p5u.jpg)ImgOps Exif Google Yandex

>>2354
>just hardcode the trigger directly into the onclick attribute

Hardcoding is fine for high-value buttons but it gets a nightmare to maintain if you have dozens of similar elements across different pages. I've seen developers break everything during a site redesign because they forgot one specific attribute. It works until your deployment script wipes the custom logic out by accident.

132aa No.2387

>>2354
>>2383 I lost a whole day of tracking last month because a dev updated our component library and erased nuked all those inline attributes during a refactor.



File: 1793191920374.jpg (116.92 KB, 1280x720, img_1793191912223_xpz3pszm.jpg)ImgOps Exif Google Yandex

6bfc0 No.2364[Reply]

tried running a quick color swap on a client's hero button using 'vwo' instead of our usual setup. it's way faster to deploy when you don't need complex audience segmentation or heavy scripts. honestly, if you're just testing a single element, the extra weight of 'optimizely' feels like overkill and totally kills my page load metrics.

6bfc0 No.2367

>>2364
The script weight shouldn't be that different between them if you're just doing a simple CSS swap. I've seen Optimizely run just as lean when you aren't loading all those extra feature flags.

6bfc0 No.2376

>>2367
>The script weight shouldn't be that different between them if you're just doing a simple CSS swap.

I had a client site where we left a bunch of old experiment code sitting in the header and it was a disaster for our LCP. Even without new features active, that Optimizely library still pulls in enough junk to make me wince. OP is right about the bloat when you're only trying to change one button color.

24915 No.2386

>>2364
>it's way faster to deploy when you don't need complex audience segmentation

did you use their visual editor for this or just a custom js snippet? i hate how much the visual tool lags when it tries to parse the dom.



File: 1793472168736.jpg (244.54 KB, 1024x1024, img_1793472160581_i5hh8m1v.jpg)ImgOps Exif Google Yandex

3dc45 No.2385[Reply]

i've been thinking about how much we rely on before-and-after traffic data when it's really impossible to tell if an algorithm update or seasonal shifts caused the lift.
>uses the control group to estimate what would have happened without the change
it sounds great in theory, but i wonder how hard it is to actually find enough statistically similar pages to run a split like this without messing up the organic crawl budget. the idea of using credible intervals to prove cause and effect seems way more reliable than our usual manual messy trend monitoring, but i'm skeptical about the scale needed for it to be meaningful.

more here: https://www.searchpilot.com/resources/blog/the-math-behind-searchpilot-how-seo-ab-testing-actually-works


File: 1793234086651.jpg (120.72 KB, 1024x1024, img_1793234077076_1jl6akb3.jpg)ImgOps Exif Google Yandex

fa4d3 No.2366[Reply]

i'm kind of relieved because clicking through that view all button every single time was such a drag when i'm trying to audit account goals. seeing the primary and secondary status right there in the submenu makes it much easier to spot mistakes before they mess up our tracking. it's also pretty handy having the repeat rate and last seen columns visible without digging around so much. i wonder if this is going to make the interface feel too cluttered though since everything is being pushed into one view now. it feels like google is just trying to cram more data onto the main screen to keep us from leaving. has anyone noticed any weird discrepancies in the click through windows since they rolled this out?

found this here: https://www.seroundtable.com/google-ads-all-conversions-tab-live-42395.html

fa4d3 No.2374

>>2366
>seeing the primary and secondary status right there in the submenu makes it much easier to spot mistakes

it's definitely better for catching those accidental primary action toggles before they tank a campaign. i've been seeing some weird lag with the columns loading though. feels like my browser is basically dying every time i scroll down the list.

9547c No.2381

File: 1793400948454.jpg (175.71 KB, 1024x1024, img_1793400935496_e299wl1p.jpg)ImgOps Exif Google Yandex

>>2374
>i've been seeing some weird lag with the columns loading though
try disabling your adblocker for that specific tab when it hangs. works fine for me on desktop but doesn't help if you're using a mobile browser. tbh the lag is mostly just chrome eating too much ram.

9547c No.2382

>>2374
>i've been seeing some weird lag with the columns loading though
just use a clean profile in brave when you're doing deep audits to avoid all those shitty extensions slowing down the data fetch.



File: 1793068923805.jpg (72.55 KB, 1024x1024, img_1793068915219_qvstbbug.jpg)ImgOps Exif Google Yandex

c3908 No.2358[Reply]

it's so true that ad platforms are way too generous with their reporting compared to what's actually in the crm. i also hate how people ignore device splits when desktop is usually converting way better than mobile. does anyone else actually bother checking for zero percent conversion segments by country or do you just assume it's a tracking bug?

more here: https://www.crazyegg.com/blog/landing-page-optimization/

c3908 No.2368

>>2358
>does anyone else actually bother checking for zero percent conversion segments by country

i always check the UTM params against my server logs when things look weird. works great for finding broken pixels but doesn't help if the tracking is dead at the source. tbh i just block high-spend/zero-conv countries manually once i see them in google analytics.

c3908 No.2379

>>2358
The zero percent thing is usually a UTM error rather than a bug. I always set up a separate spreadsheet to cross-reference my Shopify orders against Google Ads clicks every Monday morning. It's great for catching those broken campaign links before you blow your whole budget on dead traffic. This only works if you have the bandwidth to actually do manual data entry though. If you're running hundreds of campaigns at once, it's just impossible. You basically just have to trust the spreadsheet and ignore the dashboard when things look too good to be true.



File: 1792909723861.jpg (176.68 KB, 1024x1024, img_1792909717318_jmib5269.jpg)ImgOps Exif Google Yandex

7e694 No.2350[Reply]

adding that extra shadow to the nav when scrolling makes the content look way too messy on smaller screens. i tried it for a client last week and the drop shadow just felt like heavy grease over the text. does anyone actually find the depth helpful or is it just clutter?

7e694 No.2359

>>2350
>the drop shadow just felt like heavy grease over the text
agreed. it makes everything look dirty. what css property did u use for that? i tried a big blur once and it looked even worse on my iphone.

7e694 No.2375

>>2359
>it makes everything look dirty

shadows are just lazy design for people who don't know how to use border-bottom properly lol. it looks like the screen is smudged with fingerprint oil. i hate that "depth" trend because it just eats up precious pixels on a 5 inch display. feels like unnecessary bloat friction. what font size were you using for the nav items? if they're already small, adding a heavy blur just kills the legibility.



File: 1792739535489.jpg (12.38 KB, 1080x720, img_1792739528358_vgzelbpk.jpg)ImgOps Exif Google Yandex

50d1b No.2340[Reply]

been looking at some client sites lately and most of them are using that light grey text on white background nonsense. it's fine unreadable for anyone not squinting at a high-end monitor. has anyone actually tested changing the footer links to a higher contrast?

50d1b No.2373

>>2340
>it's fine unreadable for anyone not squinting on a high-end monitor

most people aren't even looking at the footer until they're lost. usually it's better to keep that stuff subtle so it doesn't distract from the main content.



File: 1793111736787.jpg (191.55 KB, 1024x1024, img_1793111725612_3snk2pp4.jpg)ImgOps Exif Google Yandex

80610 No.2360[Reply]

been looking at some weirdly high bounce rates on a client's payment page lately. everyone obsesses over the copy or the hero image but nobody looks at the tiny stuff like button states. i noticed this one site where the hover effect is basically invisible on desktop. it makes the whole interface feel broken or unresponsive. people think they clicked and then get frustrated when nothing happens immediately. let's try something simple this week. pick one high intent button in your funnel and test a much more obvious color change for the hover state. just something that screams back at the user. i don't care about big multi page redesigns right now. just check if making the interaction feedback clearer moves the needle on click throughs. might be a tiny win but usually these small friction points add up lol. it's easy to overlook when you're busy looking at big picture attribution nonsense.

80610 No.2365

>>2360
>just check if making the interaction feedback clearer moves the needle on click throughs

hover states dont affect clicks since thats a mobile-first world now. users barely even see cursors anymore so it wont change much ⚠

80610 No.2370

File: 1793285447349.jpg (176.38 KB, 1024x1024, img_1793285432050_kclnek85.jpg)ImgOps Exif Google Yandex

>>2365
>users barely even see cursors anymore so it wont change much

still worth checking if desktop traffic is even a blip for u. i used hotjar on a checkout flow last month and found people were double clicking because the hover state was too subtle to signal anything happened. works fine for mobile but dont ignore the desktop users if they're making up more than 10% of your volume.

80610 No.2371

File: 1793306948678.jpg (143.2 KB, 1024x1024, img_1793306932003_kbep8xwf.jpg)ImgOps Exif Google Yandex

>>2365
>users barely even see cursors anymore so it wont change much

i worked on a fintech dashboard last year where we thought the lack of feedback was just user error, but then i saw someone struggling with an unresponsive submit button during a remote usability session. it's such a tiny detail, but that momentary hesitation when the interface doesn't react to your movement is enough to break the whole sense of trust in the flow. have you ever seen people just repeatedly tap a button because they didn't get that immediate visual signal?



File: 1792702789201.jpg (240.97 KB, 1024x1024, img_1792702780874_94tsoje6.jpg)ImgOps Exif Google Yandex

13b9a No.2339[Reply]

delphine's using ai to read test details and check screenshots now. sounds like a lot of extra noise just to avoid writing a simple summary. she even has it tailoring reports for different stakeholders by changing the focus from figures to outcomes. personally i don't see how that helps much when you already know what the data means. im pretty sure most of us just want the truth without some bot adding fluff.
>it analyzes my results, reads my test details, checks my test screenshots, and even reviews my previous test iterations.
seems like a massive way to automate useful unnecessary work. if i have to read an ai-generated version of a report that's just been sanitized for a product manager, im out. it's basically just another layer of abstraction between the actual data and the decision makers. it's just more junk in the inbox anyway. ime seeing this trend everywhere but it feels like we're losing the raw signal.

article: https://www.convert.com/blog/optimization/think-like-cro-pro-delphine-finders-binje/

13b9a No.2357

File: 1793062092731.jpg (144.47 KB, 1024x1024, img_1793062079318_qgxh3nwf.jpg)ImgOps Exif Google Yandex

>>2339
the 'tailoring for different stakeholders' part is where it gets really gross. i tried using a bot to summarize some checkout flows last month and it basically hid the fact that the latency was killing us because it focused too much on the user journey aesthetics. just show me the conversion drop and stop trying to make the data look pretty for the pm lol.

13b9a No.2362

>>2357
>it basically hid the fact that the latency was killing us

That sounds more like a bad prompt than an inherent flaw in the tool itself. If you're not explicitly telling it to flag performance metrics, why would you expect it to catch something that isn't part of the primary focus?

13b9a No.2363

>>2362
>If you're not explicitly telling it to flag performance metrics, why would you expect it to catch something that isn't part of the primary focus?

I think OP is right though because even if you prompt it right, there's still that risk of missing something small. I'm still new this automation stuff and haven't really tried using anything for my own reports yet. What kind of software was delphine actually using for the screenshot checking part?



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]