Phase 1 · MediaHawk → Pipedrive

MediaHawk Sync

Load MediaHawk call data — a call-log CSV parsed in the browser, or the calls pulled straight from MediaHawk — pull Pipedrive deals created in a date range, match by UK-normalised phone number, then push Origin / Campaign / PPC Keyword / GCLID back to Pipedrive. A CSV never leaves this page.

Correcting the Origin on many deals from a spreadsheet of email addresses? Use Bulk Origin corrections — a dry run first, then a logged update you can undo.

Step 1 — Load data & find deals

Load call data for enrichment (optional — a CSV, or straight from MediaHawk), then find deals by creation date. The action button always runs "Find Deals in Date Range" — the MediaHawk data tab only loads optional enrichment data.

Upload a MediaHawk CSV

Parsed in the browser — the file never reaches the server. Confirm the column mapping below.

Load from MediaHawk

Calls from to

Uses the call log the Calls module keeps (synced from MediaHawk first when the API key is configured). Defaults to the deal range starting one day earlier — the call usually precedes the deal. Loading replaces any CSV data.

Deal created from to

Defaults to yesterday. Keep the range tight — it exists to avoid overwriting GCLIDs on old deals.

Step 2 — Review & push updates

Rows start unchecked; choosing an Origin auto-selects the row. Only checked rows are pushed.

Select all 0 deal(s) selected Dry-run (no writes)

	Phone	Deal	Person	Created	Status	Origin	Campaign	PPC Keyword	GCLID

Update log

Deal field browser

Find the hashed API keys for the four custom fields. Configure them on the portal home under Settings → pipedrive (pipedrive.field_origin / _campaign / _keyword / _gclid).