Features

Everything needed to run link operations as infrastructure.

Link Peeler combines desktop execution, cloud row state, account controls, API-triggered workflows, and Google Ads update utilities in one product boundary.

Start free Download desktop

Tracking link resolution

Follow redirect chains, keep final URL evidence, and separate successful conclusions from skips and failures.

Google Ads suffix updates

External scripts can discover the active channel, read offer state, and update final URL suffixes safely.

Data Integration

Switch between Google Sheets and hosted platform API without rewriting the operational playbook.

API Links

Queue link-fetch jobs through signed API calls and let the desktop execute them through outbound polling.

Device awareness

Account pages expose desktop linkage and cloud-side device state for support and operations.

Quota and membership

Free plans validate small workflows. Pro unlocks unlimited offers and production integration paths.

Feature command deck

One product surface, four operating systems.

The feature set is organized around the control points that decide whether link work can move from a spreadsheet row to a production Google Ads change.

row contract

Rows become verifiable operating state.

Google Sheets or platform API rows carry tracking URL, expected destination, result fields, owner, schedule context, and row identity evidence before any downstream script acts.

coverage 6 source controls tied to one row.

source.selected -> identity.locked -> writeback.safe

Google Sheets Operator-owned review surface for rows, evidence, and final URL conclusions.

visible source

Platform API Hosted row and task state for external systems, portals, and repeat workflows.

managed state

Desktop resolver Local browser, proxy, device, and referer context for redirect resolution.

local execution

Signed API Links HMAC, timestamp, nonce, idempotency, quota, and queue gates for external triggers.

safe entry

Google Ads Scripts Campaign updates consume verified state instead of unresolved tracking URLs.

campaign handoff

Account center Plan, desktop devices, API key inventory, and workspace readiness stay inspectable.

operator control

Feature proof system

Each feature ships with an evidence contract, not only a UI control.

The product is strongest when every capability explains what it accepts, what it proves, what state it writes, and which downstream system is allowed to consume that state.

01 source ownership 02 desktop resolution 03 signed queue 04 result writeback 05 script handoff 06 account readiness

6 proof checkpoints before a campaign-facing system acts.

4 entry surfaces: Sheets, platform API, manual desktop, and signed API Links.

1 operating contract from raw row to verified destination state.

Source ownership Rows stay accountable before work starts.

Tracking URL, expected destination, row identity, source mode, owner, and schedule context define the job shape.

Redirect evidence Local execution turns raw URLs into inspectable conclusions.

The desktop records final URL, conclusion, checked time, error, and skip reason for each eligible row.

Queue safety External triggers must survive auth and replay controls.

API Links validate HMAC, timestamp, nonce, idempotency, quota, and task shape before a job exists.

Writeback contract Verified state returns to the active channel.

Sheets and platform API mode receive structured result fields instead of ambiguous notes or partial output.

Ads handoff Campaign scripts consume only reviewed state.

Google Ads utilities can filter rows by conclusion, final URL, freshness, and readiness before suffix updates.

Account readiness Operators see the production boundary.

Plan, desktop devices, API key inventory, and next best action stay visible from the account center.

Feature query map

Answer the product questions searchers ask before they trust automation.

The page now maps core buying and implementation questions to exact capabilities, so crawlers and operators can extract the feature story without depending on vague product claims.

Capability answer What features does Link Peeler include for link operations?

It includes desktop redirect resolution, Google Sheets and platform API state, API Links, Google Ads script handoff, device visibility, and account readiness.

Workflow answer Which feature keeps Google Ads scripts from reading unsafe rows?

Data Integration and verified result writeback give scripts final URL, conclusion, checked time, and readiness fields before campaign mutation.

Security answer Which feature protects external API-triggered link fetch jobs?

API Links use signed requests, nonce replay controls, idempotency keys, quota gates, and desktop outbound pickup.

Execution answer Which feature makes redirect resolution match operator context?

The desktop resolver follows links locally so browser, proxy, region, referer, and device behavior can match the workflow being tested.

Migration answer Which feature lets teams move beyond spreadsheets later?

Data Integration keeps Sheets and platform API mode behind one source contract so teams can migrate when volume or triggers grow.

Account answer Which feature tells a team what to do next after login?

The account command center shows plan state, device linkage, API inventory, readiness score, and the next best setup action.

Feature matrix

From row intake to external automation.

Operator workflow

Rows, schedules, proxy decisions, browser execution, result state, and final URL update scripts stay visible to the operator.

Platform workflow

Cloud APIs handle auth, quotas, idempotency, row state, external triggers, and desktop task pickup.

Deep feature coverage

The feature set maps to every fragile part of link operations.

Each capability exists because Google Ads and affiliate operations break when row identity, redirect context, destination evidence, or script contracts are implicit.

Row identity verification

Google Sheets writeback can verify row identity before updating result fields, reducing accidental writes to shifted rows.

Schedule-aware execution

Rows can carry frequency, method, and schedule context so repeat resolution is explicit instead of hidden in a cron job.

Platform queue mode

Hosted row state and task queues allow external API calls to trigger work without requiring direct access to a desktop machine.

Capability map

Which Link Peeler feature owns each operational risk?

Search and AI answer engines need clear, extractable claims. This map states what each feature does, what evidence it creates, and what downstream system can safely consume it.

Capability	Question it answers	Evidence created	Consumer
Tracking link resolutionFollows affiliate and paid traffic URLs through redirects in the desktop runtime.	Where does this link really land?Separates valid destinations, failures, skipped checks, and changed redirect behavior.	Final URL and conclusionStores destination, checked time, error or skip reason, and redirect result state.	Operators and scriptsTeams review the evidence before automation updates campaigns or offer records.
Data IntegrationKeeps Google Sheets and hosted platform API mode under one source contract.	Where should row state live?Lets teams start in spreadsheets and move to hosted state when triggers or volume increase.	Row identity and source modeRecords active channel, source fields, ownership, and writeback targets.	Desktop and relayBoth execution paths know where to read work and where verified results return.
API LinksAccepts external link fetch requests through signed web endpoints.	Can automation trigger work safely?Requests pass through HMAC signing, nonce replay checks, idempotency, and quota gates.	Queued task recordEach accepted request becomes a traceable job for desktop outbound pickup.	Internal tools and scriptsPortals, schedulers, and Google Ads utilities can create work without exposing desktops.
Account command centerSurfaces plan, device linkage, API key inventory, and workspace readiness after login.	Is this account production ready?Operators can see whether plan, desktop, source, and signed entry points are aligned.	Readiness stateShows next best action, production gates, device count, and API key visibility.	Support and operatorsTeams troubleshoot missing devices, plan limits, and API readiness from one page.

Feature FAQ

Questions teams ask before adopting Link Peeler.

Can Link Peeler work with an existing Google Sheet?

Yes. Google Sheets can remain the active source, while the desktop reads rows, resolves links, and writes verified results back to the sheet.

What is the hosted platform channel?

The hosted channel stores tracking rows and result state in Link Peeler cloud Postgres so external scripts and APIs can use a stable platform contract.

Can external systems trigger link fetch jobs?

Yes. API Links accept signed requests, queue work in the cloud, and let the desktop pick up jobs through outbound polling.

Does Pro change desktop behavior?

Pro unlocks production limits and integration surfaces. The desktop still executes local resolution, but it can operate against higher-volume hosted workflows.