Data Integration

Run offer rows from Google Sheets or a hosted platform API without changing the operating model.

Teams often begin with a spreadsheet, then grow into API-triggered work and hosted row state. Link Peeler treats both modes as first-class data channels so scripts and the desktop can keep one workflow contract.

Start free Download desktop

Direct answer

What does Data Integration do in Link Peeler?

Data Integration lets an account choose whether offer rows are operated from Google Sheets or the hosted Link Peeler platform API. The active channel controls row intake, task creation, result writeback, and Google Ads script consumption without forcing operators to redesign the entire workflow.

Source router

Make the row source visible before scripts, API callers, or operators touch it.

Data Integration is the control layer that tells Link Peeler where rows live, where results return, and how downstream automation should discover the active channel without rewriting the workflow.

Channel selector

Which source should own row state right now?

Switch modes to see how ownership, automation depth, and migration readiness change when a workflow starts in Google Sheets, moves to platform API mode, or supports both through discovery.

source ownership

Data Integration starts by choosing who owns the row state.

Google Sheets is strongest when operators need a visible spreadsheet as the source, while Link Peeler still owns desktop resolution and verified writeback.

96 operator visibility

58 automation depth

72 migration runway

01 Google Sheets mode

Keep rows in an operator-owned spreadsheet while Link Peeler performs desktop resolution and verified writeback.

02 Platform API mode

Store rows and results in the hosted platform when external systems need stable API access.

03 Active channel discovery

Google Ads scripts can discover the active channel before reading offer state.

04 Writeback semantics

Result fields, conclusions, skips, failures, and identity checks stay part of the channel contract.

05 Upgrade path

Free validates small workflows; Pro unlocks higher-volume hosted integration surfaces.

06 Desktop continuity

The desktop remains the local execution engine across both source modes.

Integration lifecycle

Data Integration keeps the source switch explicit.

A source switch should not require rewriting every script. Link Peeler keeps channel selection at the account level and makes the active mode discoverable.

01 Decide

Pick the channel

Choose Sheets for spreadsheet-owned operations or platform API for hosted workflows.

02 Configure

Connect runtime settings

Set row fields, identifiers, and execution parameters for the selected channel.

03 Execute

Run desktop resolution

The desktop reads tasks, resolves links, and creates result state.

04 Sync

Write back results

Results return to the same active channel for operators and scripts.

05 Evolve

Move to hosted state

Teams can move from Sheets to platform API as automation depth increases.

Channel contract

The data channel is a production contract, not a storage preference.

A strong integration page needs to make every row boundary explicit: source ownership, identity, desktop execution, result writeback, consumer discovery, and the moment hosted state becomes the right operating model.

01 / Ownership Choose where the row is authoritative.

Sheets works when operators inspect and edit rows directly. Platform API mode works when multiple systems need hosted state.

02 / Identity Keep row identity stable across sorting and syncing.

Tracking URL, expected destination, row ID, owner, and campaign context stay attached before desktop work begins.

03 / Execution The desktop remains the redirect engine.

The active channel decides where work is read and written, while local desktop resolution keeps browser, region, proxy, and referer assumptions intact.

04 / Writeback Result state returns to the same active channel.

Final URL, conclusion, checked time, error, skip reason, and diagnostics must be available where scripts and operators expect them.

05 / Discovery Consumers discover the current source.

Google Ads scripts and API utilities should ask which channel is active before reading rows or preparing campaign mutations.

06 / Migration Hosted state should be an upgrade path, not a rewrite.

Teams can keep the same row contract while moving higher-volume or externally triggered work into platform API mode.

Sheets vs platform API

Choose the source based on operational maturity.

Google Sheets is often the fastest way to begin. Platform API mode is the better fit when multiple systems need reliable programmatic access.

Decision point

Google Sheets mode

Platform API mode

Best for

Google Sheets: small teams, manual review, operator-owned spreadsheets.

Platform API: hosted row state, external triggers, production automation.

Ownership

Sheets stay close to the operator and are easy to inspect.

Platform API centralizes state for scripts, accounts, and external systems.

Scale

Sheets are practical for validation and moderate operational workflows.

Platform API is better for continuous jobs and higher-volume integration.

Script contract

Scripts can become sheet-specific over time.

Scripts discover the active channel and read stable row state.

Data Integration query map

Answer the source-mode questions before teams hard-code a spreadsheet or API assumption.

The page includes compact, extractable answers for search engines and AI answer systems: what Data Integration does, when to use each mode, how scripts stay source-aware, and when migration becomes necessary.

Definition answer What does Data Integration do in Link Peeler?

Data Integration lets an account operate offer rows from Google Sheets or the hosted platform API while the desktop keeps the same link resolution and verified writeback workflow.

Mode answer Should link operations start in Google Sheets or platform API mode?

Start in Sheets when human review and spreadsheet ownership matter. Use platform API mode when external triggers, higher volume, or multiple consumers need hosted state.

Script answer How can Google Ads scripts support both Google Sheets and platform API mode?

Scripts should discover the active channel, read the shared row identity and result fields, and avoid binding campaign mutations to one storage implementation.

Migration answer When should a team move from Sheets to platform API mode?

Move when workflow ownership shifts from one operator sheet to hosted production state with external jobs, audit requirements, repeated triggers, or more consumers.

Writeback answer What result fields should the active source receive?

The active source should receive final URL, conclusion, checked time, error, skip reason, diagnostics, row ID, and enough context to audit downstream automation.

Desktop answer Does changing the data source change desktop execution?

No. The desktop still resolves tracking links locally. The source mode changes where tasks and results are read and written.

Operating contract

A source switch is safe only when every consumer reads the same contract.

Data Integration keeps spreadsheet workflows, hosted API workflows, API Links, and Google Ads scripts attached to the same row language so the site can explain both the current product and the migration path.

Source contract

The account names the active source, row owner, expected row identity, and the fields that must exist before link work enters the queue.

Execution contract

The desktop pulls or reads work from the active channel, resolves the redirect in local context, and records the evidence needed for downstream use.

Consumer contract

Google Ads scripts, API Links, and internal tools discover the active channel and consume verified row state instead of assuming one storage path.

Data Integration FAQ

Questions about Google Sheets and platform API modes.

Can a team start with Google Sheets?

Yes. Sheets mode is designed for teams that want to keep the spreadsheet as the operating surface.

Why move to platform API mode?

Move to platform API mode when hosted state, external triggers, or programmatic access become important to the workflow.

Does switching modes change the desktop?

The desktop still resolves links locally. The selected data channel changes where rows and results are read and written.

Can Google Ads scripts support both modes?

Yes. Scripts can discover the active channel and consume verified row state from the configured source.