TOFU Acquisition Strategy
Want to back the stream? The «داعم» membership on YouTube is EGP 60 a month: badges, emoji, and I answer your questions first on stream. Become a supporter
The gist
The stream documents wide-ranging practical work on Burnish, a GEO application for Shopify merchants intended to measure store and product visibility in AI answers and recommend catalog improvements. The session focused on rebuilding and simplifying onboarding, polishing the scan page, report-wait experience, and mobile UX, and reviewing plan selection, Shopify billing, and data-processing consent. In parallel, it developed a Meta/Facebook acquisition funnel built around a free report and signals such as scan started, scan completed, and lead, with a recurring view that the mid-funnel and user journey should be improved before ads run. The work also covered clean-state testing and troubleshooting 500 errors, scan failures, deployments, Turnstile, tracking events, Stripe redirection, and Supabase, Cloudflare, Railway, and GitHub integrations; several causes and outcomes remained unresolved, and end-to-end verification was not shown as complete. Performance testing found that reducing sampling depth did not deliver the expected speedup in one attempt, leading to discussion of progressive results and a clearer waiting experience. Audience questions and broader discussions covered home-hosted databases, building Shopify apps through vibe coding, learning programming with AI, GEO versus SEO and AEO, dropshippers as a possible audience, and personal comparisons of Codex, Claude, and agent workflows. The indexed topics also cover separate discussions of Shopify-app market economics and saturation, D2C and Egyptian market strategy, cash flow and AI-tool spending, internet and OBS troubleshooting, digital-access constraints, digital-nomad visas, and asynchronous communication. The supported conclusion is that clear value, low-friction onboarding, reliable funnel behavior, and sound measurement should precede advertising scale; final product readiness, several bug causes, and the best landing-page and consent structure remained open.
183 moments from the stream
- 0:00:54
Designing the Meta Ads Acquisition Infrastructure
Plans a top-of-funnel acquisition journey that collects a Shopify store URL and business email to generate an AI report, supported by a landing page, Meta Pixel, conversion optimization, and backend work. It also explains why delayed lead conversion requires estimating long-term value, and argues that an unsupported reservation request should be replaced with a concrete early-adopter benefit.
- 0:08:59
Balancing Creativity and Conversion in a Portfolio Website
A portfolio-site critique praises its non-linear presentation, visual character, and demonstration of coding skill, while warning that cursor delay and playful interactive sections may distract visitors or impede action. Whether those effects are appropriate depends on whether the goal is showcasing craft or converting visitors into clients, with mobile behavior also raised as an open concern.
- 0:15:05
Sequencing Facebook and LinkedIn Ad Work
Plans to begin with Facebook Ads before later considering LinkedIn Ads, after first reviewing part of the application.
- 0:15:35
Reviewing Onboarding Before Testing the Full Application
A plan to uninstall the application, experience onboarding from the beginning, and compare the current implementation with the expected journey before examining the rest of the product. The discussion argues that onboarding should be simple, smooth, and pleasant to reduce early churn, and merits a dedicated review even though parts of it were developed indirectly.
- 0:21:01
Testing Burnish Onboarding from a Clean Install State
Discusses testing the onboarding flow through an uninstall and reinstall, while noting that uninstalling alone may not recreate a true first-install state. Because the product was still an unlaunched MVP, resetting session and shop data was considered as a possible way to make onboarding QA repeatable, alongside a request for more proactive agent guidance before carrying out the steps.
- 0:22:38
Reviewing Pixel Setup and Advertising Category Policies
The discussion reviews Burnish Pixel setup and conversion-related options, noting that certain categories are subject to special advertising policies and that the speaker does not believe the project falls within them, while leaving the settings subject to verification.
- 0:26:40
Running SQL Through Codex and Supabase MCP and Troubleshooting Access
The speaker explains that a Supabase integration in Codex could technically let the agent run an SQL query, but criticizes the agent for treating a database reset as inherently risky despite the product not yet being launched. Later, he questions why Codex cannot reach Supabase even though the integration had already been configured and used.
- 0:30:16
Maintaining Focus Across Multiple Apps
The speaker noted that managing several applications at once can divide attention and make the work harder.
- 0:33:44
Testing Shopify Apps and Meeting Google Merchant Requirements
A participant described building a functioning Shopify store with payments to test code and satisfy Google Merchant requirements, with later policy-violation testing planned. The speaker discussed development versus real stores and the regulatory complexity of building themes.
- 0:39:23
Install Tracking and Custom Conversions for Facebook Ads
The speaker explained that user installs are recorded in the database while Facebook signals are used for campaign optimization. He proposed custom conversions for CTA clicks and in-product scan actions so the ad system can understand funnel stages and deeper conversion signals.
- 0:42:24
Supabase Tool Discovery and Coding-Agent Proactivity
The speaker described an experience in which a coding agent initially failed to discover an available Supabase connection and tools, then found them after additional prompting. He framed this as a tool-access problem and expressed the opinion that Codex was more reactive and less proactive than Claude in moving work forward.
- 0:50:16
Working with Codex and Its Terse Response Style
The speaker says Codex handles most of his coding work effectively, but sometimes ends with a short sentence and leaves the user to take the initiative—a style he considers workable but occasionally frustrating.
- 0:50:57
Diagnostic Hypotheses for a Pre-Onboarding 500 Error
After mentioning deletion of a Supabase session, the speaker reports a 500 error immediately upon installing the application, before onboarding began. He proposes two hypotheses for investigation—the development environment was not started, or the latest application version was not deployed—but no diagnostic result is captured.
- 0:55:58
Dated Observation About New Shopify Apps
The speaker reacts to a stated figure of 750 new Shopify apps on Friday, May 8, 2026. The captions do not establish the figure’s source or counting method.
- 0:58:49
No Available Option to Remove a Gateway Connection
The work session includes an instruction to disconnect and remove a gateway, followed by the observation that the interface offers no remove, disconnect, or delete option. The gateway’s name is unclear in the captions, and no later outcome is shown.
- 1:05:30
Direct Integration vs. Shopify’s Facebook Ads Onboarding
A comparison of Shopify’s easier Facebook Ads onboarding with a direct implementation that offers more control. The discussion explains how custom conversions can be defined from user behavior—such as visiting multiple pages and reaching a certain scroll depth—then used as funnel signals to understand what may lead to a sign-up.
- 1:08:20
Deploying Conversion API Configuration
A brief practical update on adding Conversion API access configuration to the hosting environment and starting a deployment, as part of recurring work with APIs, environment variables, and secrets. Sensitive configuration details are omitted.
- 1:13:48
Improving DPA Links and the Consent Flow
The review requested placing the data processing agreement link beside the AI engine names, replacing the Grok link that returned a 404 with the correct one, and disabling Continue until the merchant accepts Burnish’s use of subprocessors for catalog analysis. These were requested changes, not confirmed completed work.
- 1:26:34
Privacy Wording and Deployment Variables
The discussion asks whether the consent-page data-retention wording should be refined for Shopify review. It then mentions configuring Meta-related environment variables on Cloudflare Pages, while the other setup details remain unclear in the available captions. The available captions do not establish the final wording decision.
- 1:39:10
Manual Deployment vs. Railway CLI
The discussion examines Cloudflare not updating and the consent page reverting after a manual Railway deployment, prompting a question about how that differs from deployment through the Railway CLI. Following another deployment, the captions state that Meta Pixel is live on the website.
Got a question about something in this stream?
Ask in the group