> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bright-sdk.com/llms.txt
> Use this file to discover all available pages before exploring further.

# FAQ

<AccordionGroup>
  <Accordion title="How do I implement the Samsung TV SDK?">
    Here is a [link](https://docs.bright-sdk.com/integration-guides/tizen-integration) to our implementation guide.
  </Accordion>

  <Accordion title="Which Samsung versions are supported?">
    Our SDK works well on TV models with Tizen 6.5 and above, and emulator with Tizen 7. It could work on previous versions, but that is yet to be validated.
  </Accordion>

  <Accordion title="I have many apps on Samsung TV. Which ones will generate the highest revenue for me?">
    First, you are more than welcome to implement the Bright SDK in all of them.

    For revenue prioritization purposes, we suggest implementing the Bright SDK for Samsung on apps that have users in the highest paying countries and/or have the best retention so you can maximize your revenue.
  </Accordion>

  <Accordion title="Does the Bright SDK comply with Samsung's rules and restrictions?">
    **Yes, of course.**

    Samsung reviews and approves each app.

    <u>Remember:</u> we never collect any user information and allow option-out at any time.
  </Accordion>

  <Accordion title="Will the Samsung Tizen SDK interfere with watching TV or using other apps?">
    **No**, it will run in the background.
  </Accordion>

  <Accordion title="Will my app generate money even while the Samsung TV is turned off?">
    **No.**
  </Accordion>

  <Accordion title="Should my application have sound in it?">
    While recommended to include sound in your app, it is not mandatory.

    We do recommend that in case the app does not include sound, you specify it when submitting for Samsung’s review.
  </Accordion>

  <Accordion title="Multiple apps with different SDK versions on the same Samsung/Tizen TV cause conflicts. Is that a known issue?">
    Yes, this is a known limitation being worked on. Apps using very different SDK versions on the same device can cause initialization failures.

    **Update to the latest SDK version to minimize this.**
  </Accordion>

  <Accordion title="My dashboard shows 0 active devices even though users opted in. Why?">
    The app needs to pass the self-check and Bright Data review before devices start counting. Also check that the app status is set to "Active/Approved" in the dashboard.
  </Accordion>

  <Accordion title="How to obtain BrightSDK API Key?">
    The BrightSDK tools authenticate with the releases API using an API key. Follow these steps to create one.

    1. **Open API Keys**\
       Log in to the [BrightSDK Control Panel](https://bright-sdk.com/cp/settings/company_profile#api_keys) - this links directly to the **API keys** section.
       ![API keys section](https://raw.githubusercontent.com/BrightSDK/bright-sdk-integration/main/docs/img/auth_step2_api_keys.png)
    2. **Create a new key**\
       Click **+ Add**. Choose an expiration (e.g. *One year*), give the key a descriptive name, then click **Generate key**.
       ![Key creation dialog](https://raw.githubusercontent.com/BrightSDK/bright-sdk-integration/main/docs/img/auth_step3_key_creation.png)
    3. **Copy your key**\
       The generated key is shown **once only** - copy it immediately.
       ![New API key revealed](https://raw.githubusercontent.com/BrightSDK/bright-sdk-integration/main/docs/img/auth_step4_key_revealed.png)
           <Warning>
             **Important:** Once you close this dialog the key cannot be retrieved. If lost, delete and create a new one.
           </Warning>
    4. **Set the environment variable**
       **macOS / Linux** - export in your shell:
       ```bash theme={null}
       export SDK_API_KEY="<your-api-key>"
       ```
       To persist across sessions:
       ```bash theme={null}
       echo 'export SDK_API_KEY="<your-api-key>"' >> ~/.zshrc
       ```
       **Windows (PowerShell)** - set for the current session:
       ```powershell theme={null}
       $env:SDK_API_KEY = "<your-api-key>"
       ```
       To persist for your user (survives reboots):
       ```powershell theme={null}
       [Environment]::SetEnvironmentVariable("SDK_API_KEY", "<your-api-key>", "User")
       ```
       **Windows (CMD)** - set for the current session:
       ```cmd theme={null}
       set SDK_API_KEY=<your-api-key>
       ```
       To persist for your user (survives reboots):
       ```cmd theme={null}
       setx SDK_API_KEY "<your-api-key>"
       ```
  </Accordion>
</AccordionGroup>