Skip to main content
Here is a link to our implementation guide.
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.
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.
Yes, of course.Samsung reviews and approves each app.Remember: we never collect any user information and allow option-out at any time.
No, it will run in the background.
No.
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.
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.
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.
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 - this links directly to the API keys section. API keys section
  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
  3. Copy your key
    The generated key is shown once only - copy it immediately. New API key revealed
    Important: Once you close this dialog the key cannot be retrieved. If lost, delete and create a new one.
  4. Set the environment variable macOS / Linux - export in your shell:
    export SDK_API_KEY="<your-api-key>"
    
    To persist across sessions:
    echo 'export SDK_API_KEY="<your-api-key>"' >> ~/.zshrc
    
    Windows (PowerShell) - set for the current session:
    $env:SDK_API_KEY = "<your-api-key>"
    
    To persist for your user (survives reboots):
    [Environment]::SetEnvironmentVariable("SDK_API_KEY", "<your-api-key>", "User")
    
    Windows (CMD) - set for the current session:
    set SDK_API_KEY=<your-api-key>
    
    To persist for your user (survives reboots):
    setx SDK_API_KEY "<your-api-key>"