This message was deleted.

I checked both our

sign_up

and

experiment_joined

events via Big Query and it seems like more than 50% of `sign_up`s did not have a corresponding

experiment_joined

event

As in when you join or group by these events on

id

there are 50% of

id

with at least one

sign_up

event who do not have a corresponding

experiment_joined

event? Just ruling out that there's some issue with

sign_up

events firing too often.

• I am confident in the queries we are running for

sign_up

events and they include the same pre-conditions of the A/B experiment

To confirm, they are querying the same table?

• in our

trackingCallback

, we push an

experiment_joined

event with the

experiment_id

and

variant_id

to our GTM data layer, which, in turn, sends a GA event

Are there any differences (besides the fact that the tracking callback is getting called within the GB SDK) between this and how you track sign up events? Is it the case that you expect every single

id

that fires a

sign_up

event to also fire an

experiment_joined

event?

Hi @helpful-application-7107, thank you for your reply! Shortly after posting this message, I went and checked again all of our pre-conditions, where I found a bug that made all our non-UK sessions not be bucketed into experiments 🤦‍♂️ The good news is that we are now seeing about the same amount of `sign_up`s as

experiment_joined

events. For the 0.5% that is missing, we are assuming it's people with cookies disabled, or in-app browsers that do not handle our cookie. To quickly answer your questions, yes, we have all events in the same table(s) in BigQuery, the events were fired in the same way, and we were expecting everyone that had a

sign_up

event through a specific flow, to have a corresponding

experiment_joined

event. I appreciate you for jumping on my questions and offering help, thanks again! 🙌