Monetization

What this page is

Connections → Monetization is the list of donation services the app can listen to: one card per service, saying whether it is connected and carrying the buttons that set it up, stop it or wipe it. Whatever any of them sends arrives as the same donation event, so alerts, the fundraising goal, the auction, the carousel, statistics, scenarios and voice over all react to it. The event still names the service the money came from, so parts of the app can be told to skip some of them: an alert card has Donation platforms, the fundraising goal Count donations from, and a scenario's donation trigger its own Count donations from.

The app only listens. Money goes from the viewer to your donation service and stays there — strAImer never handles the payment and takes no cut, and none of the services here cost credits.

Setting up a service

1. Open Connections → Monetization. Seven services can appear here: DonationAlerts, DonatePay, Streamlabs, StreamElements, DonateX, Trula and StreamEngine.
2. Only DonationAlerts and DonatePay come with the app. The other five have to be installed from Module Catalog → Add-ons first — until then they have no card in the list at all, and a list with nothing installed reads "No connector modules are installed. Add one from the Module Catalog."
3. On a card that has never been set up the button carries the service name, as in Connect Streamlabs. It switches the module on and opens that service's own settings page.
4. What that page asks for differs. DonationAlerts signs you in through the browser with Authorize via Browser and wants nothing else; the six others take a token or a dashboard link that you paste and store with Save Settings. Step by step, each has its own guide: "DonationAlerts Settings", "DonatePay Settings", "Streamlabs Settings", "StreamElements Settings", "DonateX Settings", "Trula Settings" and "StreamEngine Settings".
5. DonatePay, DonateX and Trula also carry an Accept donations switch, StreamEngine an Accept payments one. With that switch off nothing arrives, however good the token is — the badge on their page reads Disabled.
6. A card that is set up shows the account name, a badge — Connected, Connecting..., Sign-in required, Not receiving or Error — and its buttons: Configure, Disconnect, and the bin, Remove connection. In two of those states — Sign-in required and Not receiving — the first button reads Reconnect instead and opens the same settings page. Signing in again cures both: Not receiving means the connection is alive and events stopped anyway, and restarting the app does not fix that.
7. A service that has not named your account says so on the card rather than guessing: "Account name appears after the first donation" (Streamlabs), or "This service does not report the account name" (Trula, StreamEngine).
8. The connection panel at the top of the window keeps a Donations group. A service joins it once it is set up, showing the same state as its card.

Stopping and removing

Disconnect only stops the module: the token stays stored, and Connect starts it up again. The bin, Remove connection, also erases everything that service had saved, the token included — after it, setting up begins from an empty field. Neither one uninstalls the module; it stays in the catalog, and its card stays in the list.

Donations that do not come from this page

• Twitch bits become donations by themselves, in the unit BITS, with nothing to switch on. The Twitch connection lives under Connections → Channels, and for the sums to mean anything you say what one bit is worth — see "Currency Rates".
• YouTube Super Chats and paid stickers arrive the same way, from the YouTube connection under Connections → Channels.
• StreamEngine is on this page, but it sells actions rather than transfers: the alert says what was bought, not only what it cost.

Currency of the amounts

Amounts arrive in the currency the service sent them in, and the Currency Rates module converts them into your base currency. The base currency is one setting for the whole app, on Settings → Localization. With Currency Rates off nothing is converted, and a 1000 KZT donation adds 1000 to a goal counted in dollars. Both pages have their own guides, "Currency Rates" and "Localization".

Which sum shows up where is worth knowing. An alert prints the amount and the currency exactly as the platform sent them, so an alert can read "1000 KZT" on a dollar-based setup, and the Stream: Events tile on the Control Panel does the same. The fundraising goal, the auction and statistics count in the base currency.

What is not possible

• No money moves through this page. Every service on it is read-only — it reports donations and nothing else. Payouts, refunds and the donation page itself stay on that service's own site.
• A service cannot be given a currency of its own. The base currency is one for the whole application, chosen from a list of fourteen.
• Kick sends no donations at all: its connection carries chat and stream events only.
• A donation that arrived while the app was closed will not fire alerts, goals or the auction afterwards — they react only to what happens while the app is listening. DonationAlerts is the single exception, and only for Statistics: it fills missed records into the history without replaying anything on screen.
• Donations, amounts and history are not shown here. These cards are about access; the money is on Statistics.