Fingerprint identity

Fingerprint identity

How PowerOps generates a profile's device identity as one set, keeps it the same on every open, and changes it only when you ask.

Guide · 1 min read

Generated as a set

PowerOps generates a profile's identity fields together as one set, and the profile presents as Windows 11. Fields generated together agree with each other, which is what a real device looks like.

It stays the same every open

The identity is stored with the profile and applied on every open. A site that saw the profile yesterday sees the same device today. Nothing rotates unless you ask for a new fingerprint.

Editing one field changes one field

Edit a field and only that field changes. The rest of the stored set stays exactly as it was. That makes a small correction possible without disturbing an identity a site already knows.

New fingerprint rotates the identity

Generating a new fingerprint replaces the whole set at once, and PowerOps says so before it does. Sites will see a different device on the next open. Use it when you want a fresh identity rather than a corrected one.

• Work with proxiesAdd and test proxy endpoints, assign them to profiles in bulk, and match each profile's timezone and locale to its route.Next guide
• Add, test and assign a proxySave a proxy once in your workspace's proxy library, test it, and assign it to the profiles that should use it. Each profile gets its own copy, and PowerOps checks it again when the profile opens.Next guide
• Add extensions to your profilesKeep the extensions your team uses in one library, add them from the Chrome Web Store or a package file, and choose which profiles run each one.Next guide