This build adds campaign tracking to the existing demo-request workflow and a small Campaign Performance report. The automation was tested with form submissions. The report uses a separate synthetic dataset to demonstrate how enquiries and sales outcomes can be compared by campaign.
Marketing needs to understand which campaigns bring enquiries and which of those enquiries progress into sales opportunities and customers. Tracking the source only against a contact can lose that detail when the same person enquires more than once.
This build saves campaign details against each individual enquiry. It extends the existing lead-management process without adding another qualification process.
The demo-request form includes an optional Campaign ID field. Marketing creates a prefilled form link for each campaign, so prospects do not need to know or type the identifier. In Google Forms, this field remains visible and editable.
A Campaigns reference tab holds each Campaign ID, Campaign Name and Channel. When a submission arrives, the Zap uses its Campaign ID to retrieve the matching details and includes them in the new enquiry-log row.
The CRM stores the contact. The enquiry log stores each separate request, including the campaign that brought it. Reusing an existing contact must still create a new enquiry record.
Marketing launches a tracked campaign. A prospect requests a demo. Marketing manually records the known campaign against the enquiry, and the existing lead-management process handles the request. Sales records qualification and sales outcomes. Marketing then combines the campaign, enquiry and outcome records to prepare a performance report.
The issue is the manual recording and reporting work. Campaign tracking itself is already a normal marketing activity.
Marketing maintains the campaign reference and distributes the relevant prefilled link. A prospect submits the demo request. The automation saves the campaign details against that enquiry and continues through the existing lead-management process.
Sales remains responsible for recording the outcome of each enquiry. Looker Studio reads the reporting sheet and updates the campaign view when its data refreshes. No Looker Studio action is required in the Zap.
The completed prototype demonstrates campaign capture and reporting separately. An enquiry-level sales record feeding the live report remains an improvement.