Best Practices & Tips

A reliable workflow is one you can explain and verify. Start with one demo account, one symbol and one known message. Add complexity after that path behaves as intended.

Before the first trade

Check the complete setup0 of 6

The intended demo trading account is connected.The License ID in the message belongs to that connection.The symbol matches the broker’s exact name, including any prefix or suffix.Trade size and stop/target units match the message and EA settings.The TradingView event type matches the method used by the script.There are no duplicate old alerts or unintended duplicate EA instances.

For this visit only. Your progress resets when the page reloads.

Use Test alert for the first connection check. Then test your own script separately: a working webhook does not prove that a strategy’s conditions or sizing are correct.

Change one thing at a time

When updating a message, change one parameter, inspect the new result and keep the previous working version. This makes it easier to tell whether a difference came from the code, alert, EA setting or broker.

If you change…	Check next
License ID or connected account	The destination account shown in the Portal and MetaTrader
Symbol or mapping	The resolved broker symbol in the received message and order
Risk or target values	The actual volume and stop/target prices
Script code, inputs, symbol or timeframe	Delete the old TradingView alert and create a new one using the updated setup
Close on Reverse or pyramiding	A fresh entry, an opposite signal and repeated same-direction signals on demo

Keep alert names useful: include the script, symbol, timeframe and intended destination. A name such as SuperTrend · EURUSD · 15m · Demo is easier to investigate than several alerts with the same default name.

Compare logs in the right order

1. TradingView Alerts log: did the condition trigger, and what message was sent?
2. PineConnector Signals log: was that message received, and how was it processed?
3. MetaTrader Experts and order history: what did the terminal and broker do with it?

Compare the message, not only the chart arrow

A chart marker, a simulated strategy fill and a broker trade are different events. Follow the alert message through the logs before deciding which part failed.

Use Missing signals when the chain stops, Errors for a reported code, and EA settings when the result differs from the message’s intended size or handling.

Keep symbols and units explicit

{{ticker}} and syminfo.ticker use TradingView’s symbol; neither guarantees your broker uses the same name. Verify suffixes and mappings before expanding to more symbols or a watchlist.

Similarly, a legacy risk=1, sl=10 or tp=20 needs the matching EA settings to explain its meaning. Read the Syntax reference for the exact parameter you use. Do not infer units from a number or from another person’s example.

Understand what runs where

TradingView runs created alerts on its servers. In a self-hosted PineConnector setup, MetaTrader and the EA still need to be running and connected on your computer or VPS. Closing the TradingView browser window is different from shutting down the machine that runs MetaTrader. TradingView alert behaviour

Use the VPS setup guide if you manage a remote machine. Review your broker’s instrument specifications, market hours and automation rules for the actual account; a hosting or broker recommendation does not establish those requirements for you.

Treat backtests and repaints as separate checks

A good-looking historical chart does not confirm that live signals arrive at the same points. Review repainting, alert frequency, data feeds and simulated order timing before relying on a script’s history.

• Use TradingView’s repainting guide to understand why historical and real-time output can differ.
• Use TradingView’s strategy guide for the broker emulator, order timing and backtesting limits.
• Observe real-time demo behaviour after creating the alert. Historical markers are not replayed as newly sent alerts.

Learn or adapt Pine Script

Add alerts to your scriptComplete strategy and indicator examples, followed by dynamic messages. Automate without code accessFind out which alerts the script author already provides. TradingView Pine Script documentationOfficial language guides and explanations. Select the version used by your script. Pine Script language referenceLook up exact functions, arguments and built-in variables. PineConnector library by ZenAndTheArtOfTradingA published helper library for composing alerts. Review the library version, generated message and EA requirements before adopting it.

Optional learning resources

The original recommendations page also points to Pine Script Mastery and TradeSearcher. These are external learning/discovery resources, not requirements for using PineConnector or evidence that a strategy will work for your account. Review current pricing and terms on the provider’s own site.

If you hire a coder, provide your intended entries, exits, broker symbol format, sizing rules and a demo acceptance test. Ask for editable source and clear instructions on which TradingView alert type to create. Do not share account passwords as part of a script-editing brief.

When asking for help

Include the script/alert method, symbol, timeframe, the time of the event, the relevant Signals log entry and the full error text. Explain what you expected and what happened. Remove passwords, secrets and unnecessary account details from anything you share publicly.

Open PineConnector Support when you need help tracing the result. Keep repeated tests on demo until the cause is understood.