Parameter source=pcc results in loss of utm_campaign values in reporting
Hi all,
I am working through a tough one:
Webinar registration form is embedded in a HubSpot page, not using a HubSpot form
The query string for the landing page is being scraped and stored
Registrations are captured in the Webinar platform and then passed into HubSpot via Zapier, this includes the original query string from the landing page
In order to lump these sessions into a source of Paid Search, we need to include 'source=ppc' in the query string, since the referring domain info can be removed during this process and HubSpot's logic for Paid Search does not account for Bing.
HubSpot's traffic source conditions for Paid Search:
The "source" parameter contains the word "adword", "ppc", or "cpc"
The "gclid" parameter is present, as it is the Google click ID
The "utm_source", "utm_medium", or "utm_campaign" parameter is present and the referring domain is google.com
Unfortunately, what happens is the original utm_campaign value is being overwritten with just 'ppc'. Is this expected behavior? None of the documentation accounts for this, and we need to retain the original utm_campaign information.
One additional bit of detail: the leads that come in have the complete, original query string attached to them including the original value of for utm_campaign. The issue seems to be isolated to the actual Traffic Analytics reporting.