Passing GA4 Client and Session IDs From WordPress Forms to Salesforce

What was happening

The site had a working form-to-CRM handoff, but the lead record did not consistently include the identifiers needed for possible GA4 session-level investigation. The requirement was to propagate the existing analytics identifiers alongside the ordinary submission, not to build a separate CRM or claim that analytics could automatically identify a person.

Why the obvious solution was not enough

A GA4 client ID identifies a browser or app instance, while a session ID identifies a session; neither alone proves marketing attribution or uniquely identifies a person. Values may be unavailable because analytics has not initialized, the browser blocks storage, or consent has not been granted. The website, Zapier mapping, and Salesforce field configuration all need to agree on the destination of each value.

How the solution works

1. Identify the two GA4 values required for the integration and add compatible destination fields in Salesforce.
2. Extend the existing WordPress Gravity Forms capture so forms can carry the available client and session identifiers through the normal submission path, subject to the site's analytics and consent controls.
3. Keep the identifier fields separate from contact details and avoid fabricating placeholder values when analytics identifiers are unavailable.
4. Update the Zapier mappings so each identifier travels to its corresponding Salesforce lead field rather than being merged into unstructured notes.
5. Apply the mapping consistently across the site's relevant form variations instead of fixing only one landing-page form.
6. Validate the complete submission-to-Zapier-to-Salesforce field path and coordinate CRM field visibility with the Salesforce administrator.

What should be verified before shipping

• Inspect the hidden form fields using synthetic test values only; never publish actual visitor identifiers or lead records.
• Submit representative forms and confirm that the intended values appear in Gravity Forms, Zapier task history, and the correct Salesforce fields.
• Test when analytics is unavailable or consent has not been granted; the form must remain functional and must not invent an identifier.
• Check multiple form templates and language variants so the mapping remains consistent.
• Verify destination field permissions and placement on the Salesforce Lead layout with the CRM administrator.
• Confirm any subsequent GA4-to-CRM analysis has an explicit, privacy-reviewed matching method instead of assuming the identifiers themselves provide complete attribution.

What changed

The two Salesforce destination fields were created, and the relevant Gravity Forms workflows were updated to pass GA4 client and session identifiers through Zapier. Adding the fields to the Salesforce Lead layout and confirming downstream record visibility remained an administrative follow-up. No improvement in attribution accuracy or marketing ROI is asserted without separate analysis.

Reusable lesson

Analytics-to-CRM integration starts with correct field ownership and consistent handoffs. Preserve the identifiers that are actually available, verify each boundary, and distinguish data capture from the later analysis needed to interpret it.

How I would evaluate this today

The business, industry, website, CRM records, field API names, actual analytics identifiers, and internal configuration are intentionally excluded. Identifier handling must follow the deployed site's consent, privacy, and data-retention requirements.