Frequently Asked Questions

Find answers to the most important questions about ControlPlay

We've collected the most common questions about ControlPlay and answered them clearly for you.

General

For Streamers

Monetization, Coins & Channel Points

For Viewers

Security & Transparency

Technical Questions

Troubleshooting

Disclaimer

ControlPlay is currently in Beta. Features, availability, integrations, and prices may change. Actual compatibility always depends on the individual game, PC, streaming, and network setup. For further questions, please contact our Support.

Privacy Settings

We use cookies and similar technologies on our website. Some are essential for the operation of the site, while others help us improve this website and your experience. Personal data may be processed (e.g. IP addresses), for example for personalized content or usage measurement.

Some services process data in the USA. By consenting, you also agree to data processing in the USA pursuant to Art. 49(1)(a) GDPR. The CJEU considers the USA a country with inadequate data protection by EU standards. There is a risk that US authorities may process your data for surveillance purposes without effective legal remedies available to you.

There is no obligation to consent. You can adjust or revoke your settings at any time. If you are under 16 years of age, you need the consent of your parent or guardian.

Privacy Policy

Essential Cookies

These cookies are required for the basic functions of the website and cannot be disabled. They do not store personally identifiable information.

controlplay_cookie_consent

1 year 1 month 1 day

Stores your cookie consent preferences.
controlplay_session

2 hours

Identifies your active browser session.
XSRF-TOKEN

2 hours

Protects against cross-site request forgery attacks.
cp_ref

1 month 2 days

Stores a referral code from the link you used to visit the site, so the referral can be credited at sign-up.

More details

Analytics & Statistics

These cookies help us understand how visitors interact with the website by collecting and reporting information anonymously.

_ga

2 years 2 months 2 days

Main Google Analytics cookie used to distinguish visitors.
_ga_ID

2 years 2 months 2 days

Used by Google Analytics to persist session state.
_gid

1 day

Used by Google Analytics to identify the user.
_gat

1 minute

Used by Google Analytics to throttle the request rate.
FPID

2 years 2 months 2 days

Server-side first-party identifier cookie (HttpOnly). Replaces the client-side _ga cookie for more reliable visitor identification via server-side Google Tag Manager.
FPLC

20 hours

First-party linker cookie for cross-domain tracking in server-side Google Tag Manager. Contains a hashed value of the FPID and is readable via JavaScript.

More details

Marketing & Third-Party

These cookies enable enhanced features and personalized content. Without these cookies, some features may not be available.

_gcl_au

3 months 6 days

Used by Google Ads for conversion attribution. Stores a unique identifier for matching ad clicks to conversion events.
_gcl_aw

3 months 6 days

Set by Google Ads Conversion Linker, stores the Google Click ID (GCLID) for conversion measurement after clicking a Google ad.
_gcl_dc

3 months 6 days

Used by Google Ads Conversion Linker for click information from DoubleClick/Display campaigns.
_gcl_gs

3 months 6 days

Used by Google Ads Conversion Linker to store Google ad click information.
_gac_ID

3 months 6 days

Used by Google Ads for click tracking with auto-tagging enabled. Contains campaign-related information.
_fbp

3 months 6 days

Meta browser ID used for ad attribution and measurement.
_fbc

3 months 6 days

Meta click ID used for ad attribution when arriving from a Facebook ad.
_ttp

1 year 1 month 3 weeks 5 days

TikTok browser ID used for ad attribution and measurement.
_tt_enable_cookie

1 year 1 month 1 day

Used by TikTok to check whether the browser supports cookies.
ttclid

1 month 2 days

Stores the TikTok Click ID appended to the landing page URL when clicking a TikTok ad. Used for conversion attribution.
_twclid

1 month 2 days

X (Twitter) click ID cookie. Stores the X Click ID (twclid) appended to the URL when clicking an X ad. Used for conversion attribution and ad measurement.
_rdt_uuid

3 months 6 days

Reddit pixel browser ID. Stores a unique identifier to attribute website visitor events to Reddit ad campaigns and optimize ad delivery.

More details

Frequently Asked Questions

General

What is ControlPlay?

Who is ControlPlay for?

What types of interactions are available?

Which platforms are currently supported?

Is ControlPlay free?

Is ControlPlay currently in Beta?

For Streamers

How do I install and activate ControlPlay?

What hardware is required?

What are the system requirements?

Can I control which actions viewers can trigger?

Can I use ControlPlay without Game Actions?

Does ControlPlay work with OBS, Streamlabs, and other tools?

Does ControlPlay work with all PC games?

Does ControlPlay work with console (e.g. PS5)?

What is the latency for actions?

Is there an emergency stop?

Monetization, Coins & Channel Points

How does the Bits-in-Extensions revenue share work?

Which interaction options can viewers use?

What are Channel Points packages?

Do I have to use the Channel Points feature as a streamer?

For Viewers

How can I trigger actions?

What actions can I perform as a viewer?

Do I need a Twitch account?

Can I trigger every action as often as I want?

Will other viewers see what I trigger?

What happens if an action fails?

Security & Transparency

Do I always maintain control as a streamer?

What access does ControlPlay have to my system?

What data is collected?

What security measures does ControlPlay have?

Could ControlPlay be used as a cheat?

Technical Questions

How does ControlPlay work technically?

Why does ControlPlay use an HID Device?

Is there a public API or developer access?

Troubleshooting

What can I do if inputs aren't being triggered?

What can I do if an overlay isn't visible?

Who can I contact with questions?

Disclaimer