GPM / GPMGlobal profiles and antidetect details

Purpose

Extends Antidetect browser: link profiles correctly for GPMLogin, GPMGlobal, Hidemium, or Pionlogin, avoid mixed profile IDs, and verify the client opens the right profile during automation.

Before you start

• One supported antidetect app is installed on the same machine as KKClient.
• The app is connected to the Server.
• Facebook accounts already exist on the Website.

Quick differences

Software	Important note
GPMLogin	Common; may use a Private Server URL; classic GPM-style profile IDs
GPMGlobal	Separate license/package; UUID profiles — do not mix with GPMLogin IDs
Hidemium / Pionlogin	Follow KKClient fields and KKAuto docs

Do not mix IDs

Putting a GPMLogin ID into a GPMGlobal field (or the reverse) makes the client open the wrong profile or fail. Always pick the correct browser type in KKClient and the matching link field on the account.

On the Management Website

1. Open Facebook > Accounts.
2. Select an account → link the browser profile for your software.
3. Save. Confirm the displayed ID matches the antidetect app.

Some packages show a GPM profile inventory on the Website — use it to cross-check, not to replace creating profiles in the antidetect app.

In KKClient

1. Select the correct browser type (GPMLogin / GPMGlobal / …).
2. Enter API / URL per the vendor and your service info.
3. Connected → Start automation.
4. When a task is claimed, confirm antidetect opens the correct profile.

With proxies

If the account has a proxy assigned, confirm the browser session uses the network path you expect. Wrong proxy + wrong profile often appear together as login failures.

Notes

• One Facebook account per profile — do not share profiles.
• If you switch antidetect vendors mid-flight, update both Website and KKClient.
• Video lesson: D07 — Browser profiles.

See also

• Antidetect browser
• Run automation
• Install KKClient