The quickstart is the shortest path from a new web account to a verified tracking link result. It keeps the setup sequence explicit so operators know which system owns identity, execution, source rows, and final evidence.
Start using Link Peeler by creating a web account, downloading and signing into the desktop client, selecting Google Sheets or platform API as the row source, running link resolution, and reviewing final URL evidence before any Google Ads script consumes the result.
The quickstart is the shortest path from a new web account to a verified tracking link result. It keeps the setup sequence explicit so operators know which system owns identity, execution, source rows, and final evidence.
Start using Link Peeler by creating a web account, downloading and signing into the desktop client, selecting Google Sheets or platform API as the row source, running link resolution, and reviewing final URL evidence before any Google Ads script consumes the result.
Use the public website for login, membership, desktop password setup, and billing state.
Register or log in on the website and confirm account access.
Website account anchors identity, plan state, and downloads.
Each topic page is shaped around extractable answers, operational risk, workflow steps, and next-page routing so searchers do not hit a dead end after the first answer.
Start using Link Peeler by creating a web account, downloading and signing into the desktop client, selecting Google Sheets or platform API as the row source, running link resolution, and reviewing final URL evidence before any Google Ads script consumes the result.
Use the public website for login, membership, desktop password setup, and billing state.
Register or log in on the website and confirm account access.
Website account anchors identity, plan state, and downloads.
A clean first run needs a trusted account, a local desktop runtime, a row source, and a place to inspect result state.
Use the public website for login, membership, desktop password setup, and billing state.
Install the local runtime that resolves redirects and pulls queued work outbound.
Start from Google Sheets for visible review or platform API mode for hosted state.
Keep final URL, conclusion, error, skip reason, and checked time visible.
Do not move into campaign mutation until operators have reviewed failed and skipped rows.
Let Google Ads scripts consume only verified state after the first run is trusted.
The quickstart is intentionally linear. Each step creates evidence for the next one.
Create account
Register or log in on the website and confirm account access.
Download desktop
Install the desktop client for the operating system that will resolve links.
Sign in locally
Attach the desktop to the same account so the account center can show device state.
Connect source
Choose Sheets or platform API and map the required source and result fields.
Resolve and review
Run link resolution, inspect conclusions, and exclude unsafe rows.
The goal is a first verified row that can be explained end to end.
Each topic page now repeats the core answer in several machine-readable shapes: risks, workflow checkpoints, and decision criteria. The content stays useful for humans while giving crawlers stronger entities and internal anchors.
Yes. Google Sheets is a common starting source, but platform API mode supports hosted row state when external systems need it.
Scripts should consume verified state. The desktop is the engine that creates that evidence by resolving links locally.
Run a small set of non-critical tracking rows and confirm final URL, conclusion, and checked time before expanding volume.
Open the setup doc for Google Sheets, Google Ads Scripts, or API Links depending on the next system you want to connect.