Metric 1: users that buy (purchases, binomial)
Met...
# ask-questionsr
rapid-ghost-5775
09/27/2022, 7:47 AMMetric 1: users that buy (purchases, binomial)
Metric 2: product revenue (sum)
Metric 3: duplicate of metric 2, with 1 addition: use denominator: metric 1)
Now, in the results, the denominator matches metric 1, but the numerator does not match Metric 2.
Am I missing something?
f
fresh-football-47124
09/27/2022, 7:50 AM
Hi Jules
fresh-football-47124
09/27/2022, 7:52 AM
The numerator is not matching? 909 and 915 - or do you mean it should use the revenue instead?
r
rapid-ghost-5775
09/27/2022, 7:53 AMI'd expect RPU to be Product Revenue / Users that purchase.
The Users match, but the Product revenue doesn't
f
fresh-football-47124
09/27/2022, 7:55 AM
@future-teacher-7046 would be able to help better, I’ll let him know
f
future-teacher-7046
09/27/2022, 10:43 AM
Are all of the metrics selecting from the same table?
r
rapid-ghost-5775
09/27/2022, 10:46 AMYes.
rapid-ghost-5775
09/27/2022, 10:48 AMThe revenue query uses a 2nd table in the DWH to fetch "official" revenue
Copy code
with x as ( select .. from GA4 left join DWH using(transactionid) )
select user, timestamp, value from xrapid-ghost-5775
09/27/2022, 10:50 AMI then used: duplicate metric
And selected a Denominator (users that purchase)
rapid-ghost-5775
09/27/2022, 12:47 PM@future-teacher-7046 I found the error, it's on my side.
rapid-ghost-5775
09/27/2022, 12:51 PMWe send/use "transactionid" on 3 events, and I used the timestamp of the first one, not the "one with the event name purchase" - so the timestamp >= clause was leaving the users out sometimes.
A few milliseconds can make the difference.
rapid-ghost-5775
09/27/2022, 12:57 PMThanks for allowing me to show the SQL in the interface. It's all neat and tidy now.
31 Views