Pineify Signals & Overlays: Access, Alerts, and Verification
Pineify Signals & Overlays requires TradingView authorization for the username submitted through Pineify. After access is granted, add the script to a chart and configure the alert conditions it actually exposes. TradingView runs created alerts on its servers; leaving your browser open is not a requirement for them to execute.
This guide covers access, alert configuration, and verification. It does not claim a tested win rate or certify the private indicator's internal calculations.
1. Request Access for the Correct TradingView Account
The Pineify application asks for a TradingView username when you request invite-only access. Submitting the request is part of the setup; purchasing an eligible plan does not tell the system which TradingView account should be authorized.
- Sign in to Pineify and open its invite-only indicator area.
- Confirm eligibility in the current account. The reviewed eligibility configuration includes Advanced, Expert, and Ultimate; consult current billing terms for prices and access duration.
- Open your TradingView profile settings and copy the username of the account you will use.
- Enter that username in Pineify's access dialog and submit.
- Read the result. A username-not-found response needs correction; a system error needs a retry or support follow-up. A success message confirms the request's reported outcome.
- Return to the same TradingView account, refresh, open the indicator menu, and check Invite-only scripts for Pineify® - Signals & Overlays™.
If it is missing, first compare the submitted username with the signed-in account. Save the request status when contacting support. Do not assume a fixed delivery time or that an email invitation is required.
2. Inspect the Script Before Interpreting Its Display
Record the script version, symbol and exchange, timeframe, session, and input values. Read its current description and inspect the settings available in the chart. An overlay color or arrow is a computed display, not a filled order.
The account-access code does not reveal the invite-only script's calculation source. This guide therefore does not assert that every signal combines three particular factors, that a specific EMA length is fixed, or that an ATR line is always present. Check the actual script rather than borrowing the behavior of another Pineify product.
If a displayed level is intended as a stop reference, decide how it becomes an order: when it is set, whether it can move, and which account or broker receives it. A line drawn on a chart cannot limit a loss by itself. The amount at risk also depends on quantity, contract value, currency, gaps, and execution.
3. Create an Alert From an Available Condition
TradingView distinguishes alert events exposed by scripts from running alerts created by users. Adding the indicator to a chart does not automatically create an active alert. Its official alert documentation also explains that an alert stores a copy of the script context when created.
- With the indicator on the intended chart, open Create alert.
- In Condition, select the indicator and inspect the choices offered. Use the actual condition names; do not assume separate Long, Short, or trend-change conditions exist.
- Where the chosen condition offers a frequency selector, choose the frequency that matches your rules. A close-based workflow should use Once Per Bar Close when available. For alerts driven by
alert()calls, frequency and message behavior can be controlled by the script. - Choose the notification channels shown for your account and set expiration if applicable.
- Give the alert a name containing the symbol, timeframe, and setup version. Save it, then check its active status in the alerts panel.
- After changing script inputs, symbol, timeframe, or version, recreate the affected alert so its saved context matches the intended setup.
No specific alert channel is guaranteed by this article. Use the options actually available in your TradingView account and verify delivery to the device or endpoint you intend to use.
Message Placeholders
Where the alert type supports placeholders, TradingView documents values including the following in its alert variable reference:
| Placeholder | Meaning |
|---|---|
{{ticker}} | Triggering instrument's ticker |
{{exchange}} | Exchange identifier |
{{close}} | Close value of the triggering bar at the alert event |
{{time}} | Opening time of the triggering bar, in UTC |
{{timenow}} | Current time when the alert fires, in UTC |
{{price}} is not a documented generic substitute for these price fields. With an intrabar alert, {{close}} is not necessarily the eventual completed candle close. Messages produced by alert() calls follow the script's message logic; do not assume a placeholder entered elsewhere will be expanded for every alert type.
4. Verify the Trigger and Delivery Separately
An alert can trigger successfully while its notification fails to reach a device. Use the alert log to separate those two cases.
| Observation | First checks |
|---|---|
| Indicator is absent | Account username, request result, eligibility, and chart refresh |
| Desired condition is absent | Script-selected condition list and current script instructions |
| No alert log entry | Active status, expiration, condition, timeframe, frequency, and runtime errors |
| Log entry but no phone notification | Selected channel, app sign-in, notification permission, and device connectivity |
| Alert differs from the visible chart | Saved alert context versus current inputs, symbol, timeframe, and script version |
| Old chart signals did not send notifications | Running alerts react to new events; historical markers are not a delivery history |
You can configure a separate simple price alert to check notification delivery, then remove it after testing. That checks the channel, not whether the indicator's signal logic is correct. TradingView's server-side execution also does not guarantee that a phone or third-party webhook recipient is always reachable.
5. Observe Realtime Behavior Before Using It as Evidence
For each new signal, save the bar time, alert time, direction, input settings, and a screenshot after the bar closes. Revisit the same chart after a reload. Investigate any moved or missing signal before relying on historical markers.
Waiting for a completed candle can reduce intrabar changes, but it does not prove every aspect of a script is non-repainting. Higher-timeframe data, past-positioned drawings, and historical recalculation can require separate checks. See TradingView's repainting explanation.
If you combine alerts from two timeframes, define the alignment rule in advance. “Both fired near each other” is not reproducible until “near” has a fixed time window and the status of the higher-timeframe bar is specified.
6. Keep Signals and Backtest Reports Separate
Adding an indicator does not automatically produce TradingView's strategy report. A strategy must define simulated orders, exits, sizing, and costs; TradingView describes that workflow in its strategy documentation. An indicator may display custom statistics, but their rules and scope must be inspected separately.
Pineify's Backtest Deep Dive is a separate trade-file analysis workflow. It accepts a TradingView trade CSV and analyzes imported trades. It cannot infer an invite-only indicator's complete trade rules simply from arrows on a chart. Check that the imported trade count, dates, P&L, and initial capital match the source report before using the analysis.
To measure a signal-based approach, specify an entry price convention, exits, costs, position size, and handling of overlapping signals. Record all qualifying trades, including losses. Report net expectancy, drawdown, average win/loss, and sample size alongside any win rate. No universal target win rate is established here.
Frequently Asked Questions
Must I keep TradingView open for alerts to run?
No. TradingView executes created alerts on its servers. Notification delivery still depends on the selected channel and the receiving device or service.
Do chart changes update an existing alert?
Changes to the chart or script inputs do not update the alert's saved context automatically. Recreate the affected alert with the intended configuration.
Does Signals & Overlays automatically place trades?
A plotted signal or notification is not itself a live broker order. Any separate execution integration needs explicit configuration and verification.
What historical win rate should I expect?
This guide establishes no verified win rate. A percentage requires specified trading rules, a dated sample, execution assumptions, and a complete trade record.
Why does the indicator not create a backtest report?
Indicator displays and strategy order simulations are different. Use a strategy with explicit trading rules for a strategy report, and import its supported trade file into a separate analysis tool when needed.