Problem/Motivation

When clicking a Google Ads link, the gclid (https://support.google.com/google-ads/answer/9744275?hl=de) is transfered into Posthog to let it know where the lead came from. Posthog stores it in the tracked user data.

If we have client-side events, we have that data available, but for the (generally more reliable) server-side events, in our case Drupal Commerce checkout complete conversions we don't have them, because the PHP session doesn't know about the client session?

I guess we'll end up finding a solution for this to make this work?
#3500561: Identify / Synchronize anonymous users client / server side

It seems without that data no conversions will ever be persisted. Posthog says:

Emtpy 'gclid'. Skipping ...

in the GA destination plugin testing area.

https://www.reddit.com/r/GoogleTagManager/comments/1e0wc1a/is_anyone_suc...

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

anybody created an issue. See original summary.

anybody’s picture

Issue summary: View changes
grevil’s picture

anybody’s picture

Assigned: grevil » anybody

I'll check if this works now with recent fixes!

anybody’s picture

Status: Active » Postponed

Ok it seems the ID is only stored with person profiles enabled... I'll check this in detail soon.

anybody’s picture

grevil’s picture

Yes this is fixed through #3558453: Add a new setting to allow person profiles (even for logged out users) and also has posthog cookies support:

  1. The user accesses the page (cookieless_id is tracked).
  2. The user accepts cookies (new id is generated).
  3. The GCLID is saved inside "$session_entry_gclid" after consent given.

But on consent denied, we unfortunately can not track the gclid, since posthog doesn't allow identifying users which have consent denied.

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.