PostHog Transformations: Save Visitor IPs to Person Properties
Save a visitor’s IP from a browser event when privacy settings allow it, then map that value into later server-side conversions.
Read moreSave a visitor’s IP from a browser event when privacy settings allow it, then map that value into later server-side conversions.
Read moreGive every campaign consistent UTM names and verify the results in PostHog. Capturing a parameter alone does not guarantee the channel classification you expect.
Read moreConvert each transaction at an explicit rate date, then reconcile refunds and duplicate IDs; for experiments, revenue per participant includes nonbuyers, unlike average order value.
Read moreCheckout events can reach PostHog under a different identity from storefront visits. Verify that link before using purchases to judge an experiment.
Read moreShorter questions, quick answer choices, and conversational wording replaced a longer, problem-focused form; the changes were tested as one package.
Read moreTwo easier application forms drew more submissions and prompted concerns from sales teams. Merging duplicated booking steps raised completion while keeping qualification questions.
Read moreOffering a session about two minutes after registration drew more joins. At entry, the default 27-second automatic start led a manual redesign and no waiting room.
Read more