Campaign-to-Pipeline Attribution

The problem

Marketing reports from the ad platforms, sales reports from the CRM, and the numbers rarely agree. Analysts export spend and engagement by hand into spreadsheets or the warehouse, so attribution is always days behind. Nobody trusts the pipeline number in the Monday meeting.

How it runs on Neblex

A cron schedule pulls spend and performance from Google Ads at whatever cadence you choose. Poll-based change detection watches HubSpot campaigns and contacts, catching inserts, updates, and deletes through cursors and content hashing, so removed or renamed campaigns do not linger in your reporting.

Transforms and field mapping shape both sources into a common model, and chunked batch processing with checkpoints loads the data into Google BigQuery. Because every SQL database connector runs arbitrary SQL, the flow runs the join and attribution queries in BigQuery as a step, then writes summarized attribution back to HubSpot.

If a load fails partway, the run resumes from its last checkpoint instead of starting over, and a failed run can be replayed from the exact step that broke. Bulk replay recovers up to 200 failed runs at once after a fix.

Step by step

1. 1
   Pull ad spendA cron schedule fetches Google Ads spend and performance for the reporting window.
2. 2
   Detect CRM changesPoll-based change detection picks up new, updated, and deleted HubSpot campaigns and engagements.
3. 3
   Transform to one modelTransforms and field mapping align both sources on shared campaign and contact keys.
4. 4
   Load into BigQueryChunked batches with checkpoints write the data, so partial failures resume cleanly.
5. 5
   Compute attribution in SQLAn arbitrary SQL step runs the attribution queries directly in BigQuery.
6. 6
   Write back to HubSpotSummarized attribution lands on campaigns so marketing and sales read the same numbers.

Platform capabilities used

• Cron schedules
• Poll-based change detection
• Chunked batch processing with checkpoints
• Arbitrary SQL on database connectors
• Transforms and field mapping
• Bulk replay

Common questions