[{"data":1,"prerenderedAt":19},["ShallowReactive",2],{"blog-post-en-manage-multiple-browser-profiles-broma":3},{"slug":4,"lang":5,"title":6,"summary":7,"date":8,"tags":9,"tag_slugs":14,"thumbnail_url":15,"translations":16,"body":17,"asset_base":18},"manage-multiple-browser-profiles-broma","en","Managing Multiple Browser Profiles in Broma for Safe Multi‑Account Workflows","Learn how to create, switch, and maintain isolated browser profiles in Broma, ensuring each task runs with its own cookies, logins and extensions for reliable multi‑account automation.","2026-10-31",[10,11,12,13],"broma","browser-profiles","automation","operations",[10,11,12,13],"https:\u002F\u002Fblog-api.bromaapp.com\u002Fapi\u002Fblog\u002Fposts\u002Fmanage-multiple-browser-profiles-broma\u002Fthumbnail.svg?lang=en",[5],"## Why Isolate Browser Profiles?\n\nWhen you run repetitive web tasks, each account often needs its own set of cookies, saved logins, and browser extensions. If all actions share a single profile, data from one account can bleed into another, causing:\n\n- Accidentally posting to the wrong store.\n- Losing session state when a page reloads.\n- Triggering anti‑bot mechanisms that look for multiple accounts from the same browser.\n\nIsolating profiles gives you a clean, self‑contained environment for every task, which improves reliability and reduces the risk of account bans.\n\n## Benefits of Profile Isolation\n\n- **Credential safety** – each profile stores its own login cookies, so you never reuse a password across accounts.\n- **Extension hygiene** – add a price‑tracker extension to one profile without it interfering with another.\n- **Testing flexibility** – run the same workflow against different site layouts (e.g., mobile vs desktop) by switching profiles.\n- **Auditability** – logs show which profile performed each action, making troubleshooting easier.\n\n## Setting Up Profiles in Broma\n\n### Step 1: Create a New Profile\n1. Open Broma and go to **Profiles** → **New Profile**.\n2. Give the profile a descriptive name, e.g., `Amazon_Seller_A`.\n3. Choose a platform (Chrome, Edge, Firefox) – Broma uses the underlying engine of the selected browser.\n\n### Step 2: Configure Cookies, Logins, and Extensions\n1. After creation, click **Edit**.\n2. Use the **Import cookies** button to paste a cookie string exported from the target site, or manually add them via the **Add cookie** dialog.\n3. For login steps, add a **Navigate** action followed by a **Fill form** action that enters the username and password. Save the workflow as part of the profile so it runs automatically when the profile is activated.\n4. Install any required extensions by toggling the **Enable extension** switch; Broma will launch the browser with that extension already loaded.\n\n### Step 3: Assign a Proxy (Optional)\nIf the site restricts requests by IP, configure a proxy in the profile settings. Enter the proxy address, port, and authentication details. The profile will now route all traffic through that IP, keeping each account’s traffic separate.\n\n## Switching Between Profiles During a Workflow\n\nBroma lets you insert a **Run on profile** action. This tells the workflow to:\n\n1. Activate the chosen profile.\n2. Execute the subsequent steps.\n3. Return to the original profile when finished.\n\nTypical pattern:\n- **Open page** (profile‑agnostic URL).\n- **Run on profile** → *Select `Amazon_Seller_A`*.\n- **Click** the dashboard link.\n- **Run on profile** → *Select `Amazon_Seller_B`*.\n- **Loop** through steps for each profile.\n\nThis approach eliminates the need to manually change profiles between runs, making the workflow fully automated.\n\n## Real‑World Example: Managing Multiple E‑Commerce Seller Accounts\n\n### Scenario Overview\nA seller operates three Amazon storefronts, each with its own login, pricing rules, and inventory. The goal is to:\n\n- Check the current buy‑box price on each storefront every 6 hours.\n- Record the price in a Google Sheet.\n- Send an alert if the price drops below a threshold.\n\n### Building the Workflow\n1. **Create three profiles** – `Amazon_A`, `Amazon_B`, `Amazon_C` – each pre‑filled with the respective seller login.\n2. **Start a new workflow** called *Price‑Monitoring*.\n3. Add an **Open page** action with the Amazon Seller Central URL.\n4. Insert a **Run on profile** action and select `Amazon_A`.\n5. Inside that sub‑workflow:\n   - **Click** the *Inventory* tab.\n   - **Wait for element** with selector `\u002F\u002Fspan[contains(@class,\"price\")]` (see code block below).\n   - **Read text** → store in a variable `priceA`.\n   - **If** `priceA` \u003C `threshold` → **Send email** (using a mail action).\n6. Add another **Run on profile** for `Amazon_B` and repeat steps 5‑6.\n7. Add a final **Run on profile** for `Amazon_C`.\n8. End the workflow with a **Log** action that records the timestamp and each price.\n\n### Code Block – Robust Price Selector\n```javascript\n\u002F\u002F XPath that survives minor class name changes\nxpath = \"\u002F\u002Fspan[contains(@class, 'price')]\u002F\u002Ftext()\"\n```\n\nThe expression uses `contains` to match any class that includes the word *price*, making it resilient when Amazon updates its HTML.\n\n### Running the Workflow\nSet the schedule to **Every 6 hours** in the **Scheduler** tab. Broma will launch each profile in turn, execute the actions, and write a detailed log entry for each run. You can view the log per profile, making it easy to spot which account triggered an alert.\n\n## Maintaining Profiles When Pages Change\n\nEven with robust selectors, a site redesign can break a workflow. Follow these practices:\n\n- **Use stable attributes** such as `data-testid`, `id`, or `name` whenever possible.\n- **Add fallback selectors**: if the primary XPath fails, include a secondary one separated by a pipe (`|`).\n- **Test after each site update**: run the workflow manually on each profile and verify that the read‑text step returns a value.\n- **Version your profiles**: when a major UI change occurs, duplicate the profile, make adjustments, and keep the original as a backup.\n\n## Scheduling and Logging\n\nBroma’s built‑in scheduler lets you set:\n\n- **Frequency** (every hour, daily, weekly).\n- **Start time** and **timezone**.\n- **Run limit** (stop after N attempts).\n\nEach scheduled run creates a **log entry** that includes:\n- Profile name.\n- Start and end timestamps.\n- List of actions executed.\n- Any errors with stack traces.\n\nYou can export logs as CSV for further analysis or feed them into a monitoring dashboard.\n\n## Troubleshooting Common Issues\n\n| Issue | Likely Cause | Fix |\n|-------|--------------|-----|\n| Profile fails to load cookies | Cookie import error or missing `domain` attribute | Re‑export cookies from a fresh browser session and re‑import. |\n| Selector not found | Element’s class or ID changed after a site update | Update the XPath\u002FCSS selector; use `contains` or a more generic attribute. |\n| Proxy authentication error | Wrong credentials or proxy blocked | Verify proxy details in profile settings; test connectivity with a simple request. |\n| Email not sent | SMTP settings incorrect | Check Broma’s mail action configuration; use a test email address. |\n\n## Quick Checklist\n\n- [ ] Profiles created with correct login data.\n- [ ] Each workflow references the appropriate profile via **Run on profile**.\n- [ ] Selectors use stable attributes or `contains` logic.\n- [ ] Schedule set and a test run logged without errors.\n- [ ] Alerts and logging configured for the specific use case.\n\n## Conclusion\n\nIsolating browser profiles in Broma gives you the same reliability that a dedicated RPA server provides, but without the overhead of cloud services or code. By creating dedicated profiles for each account, you keep cookies, extensions, and proxies separate, which prevents cross‑contamination and reduces the chance of account bans. The step‑by‑step setup, profile‑switching actions, and robust selector strategies make it straightforward to build repeatable, maintainable workflows for e‑commerce sellers, marketers, and anyone who needs to manage multiple web identities from a single Windows desktop.\n","https:\u002F\u002Fblog-api.bromaapp.com\u002Fapi\u002Fblog\u002Fposts\u002Fmanage-multiple-browser-profiles-broma\u002Fassets",1794729622751]