Extensions Payload

Browser Profiles support injecting Chrome Web Store extensions into the browser.

Why Use Extensions?

Use Case	Description
Ad blockers	Block ads to speed up page loading
Custom extensions	Inject custom functionality
RTILA extension	The RTILA extension is auto-injected

Configuring Extensions

1. Go to Browser Profiles.
2. Create or edit a profile.
3. In the Extensions Payload section, enter extension URLs, one per line:

https://chromewebstore.google.com/detail/ad-blocker/abcdefghijklmnop
https://chromewebstore.google.com/detail/custom-ext/bcdefghijklmnopq

4. Save the profile.

How It Works

1. When the Visual Builder is launched for a project using this profile:

   1. RTILA downloads each extension from the Chrome Web Store.
   2. The extension is extracted.
   3. The extension is injected into the browser.

2. The extensions are available for the duration of the session.

Supported Extension Sources

Currently, only Chrome Web Store extensions are supported.

Limitations

Limitation	Description
Chrome Web Store only	Only Chrome Web Store extensions are supported
Download required	Extensions are downloaded each time the profile is launched
No extension settings	Extension settings are not persisted between sessions

Tips

Tip	Description
Use ad blockers	Blocking ads speeds up page loading significantly
Limit extensions	Each extension adds overhead. Use only what you need.
Test extensions	Verify extensions work with your automation before relying on them