Hi Windsor support,
We need 17 custom Pardot Prospect fields exposed on our Pardot connector so we can pull them into BigQuery.
We’ve tried adding them to the fields= parameter using three naming conventions, all rejected with “Unexpected field(s)”:
Plain Pardot name (e.g. Lead_Source, utm_source, GCLID)
Salesforce API name (e.g. Lead_Source__c, utm_source__c, GCLID__c)
Prefixed to match your standard fields (e.g. prospect_lead_source, prospect_utm_source, prospect_gclid)
The fields we need, with Pardot field name and API name:
Field Pardot name API name
Lead Source Lead_Source Lead_Source__c
Form Source Form_Source Form_Source__c
UTM Source utm_source utm_source__c
UTM Medium utm_medium utm_medium__c
UTM Campaign utm_campaign utm_campaign__c
UTM Content utm_content utm_content__c
UTM Term utm_term utm_term__c
Last UTM Source last_utm_source last_utm_source__c
Last UTM Medium last_utm_medium last_utm_medium__c
Last UTM Campaign last_utm_campaign last_utm_campaign__c
Last UTM Content last_utm_content last_utm_content__c
Last UTM Term last_utm_term last_utm_term__c
GCLID GCLID GCLID__c
FBCLID FBCLID FBCLID__c
Travel Circle New Travel_Circle_New Travel_Circle_New__c
Travel Circle Member Travel_Circle Travel_Circle__c
Travel Circle Signup Circle_Signup Circle_Signup__c
Two things that would help us plan:
Can these be exposed, and if so what naming should we use in the fields= parameter once they are?
Will they be available for historical backfill? We need to re-run a backfill from 2022-11-01 to present so the fields populate for existing prospects, not just going forward.
Account: tiaan@acuto.io (Solos team). The connector is our Pardot Prospects task writing to BigQuery.