Conversion tracking for Luma events

Architecture

What Luma actually lets you do

Luma's tracking is decent once you know its rules. Most of it requires Luma Plus.

1. Step 1

   GA4 via gtag, measurement ID only

   A G- or GT- ID works; a GTM container ID does not.

2. Step 2

   Purchase events with transaction ID and value

   Sent for paid and free registrations alike, which is the part to correct for.

3. Step 3

   Meta Pixel with three events

   PageView, CompleteRegistration for free events, Purchase for paid.

4. Step 4

   luma:purchase postMessage from embeds

   The button embed passes it to gtag and the dataLayer; the iframe embed needs a listener you write.

5. Step 5

   UTMs and click IDs via webhooks, API and Zapier

   No CAPI or Measurement Protocol from Luma, but this is exactly what a server build needs.

Diagnostic sequence

Checking a Luma setup

Five questions. On Luma, the first two explain most broken setups.

1. 1

   Is the account on Luma Plus?

   Without it the GA4 and pixel fields simply are not there.

2. 2

   Which embed is on your site?

   Iframe embeds need a listener, and most sites never added one.

3. 3

   How many GA4 purchases carry zero value?

   Those are free registrations counted as sales.

4. 4

   Was a GTM ID pasted into the GA4 field?

   Luma only takes gtag IDs; a container ID fails without an error.

5. 5

   Do webhook payloads carry UTMs and the click ID?

   Inspect one registration; it decides the server path.

Source-of-truth validation

How a Luma build is signed off

Tested with one real free registration and one real paid ticket, each from a tagged link.

• A free registration arriving as a registration, not a purchase, in GA4 and at Meta.
• A paid ticket recorded once, with Luma's transaction ID and the right value.
• An iframe-embed registration caught by the postMessage listener.
• A button-embed registration not double counted by that same listener.
• The webhook's click ID matched back to the original ad click.
• One event's guest list reconciled registration by registration.
• Repeated 30 days later, after more events have run.

Straight talk

When Luma's built-in tracking will do

Plenty of Luma hosts never need this. Signs you are one of them:

• If every event is free and promoted organically, an accurate registration count from Luma itself is all the measurement you need.
• If you run paid ads to one or two paid workshops a quarter, Luma Plus's pixel, with the free and paid split respected, may be enough.
• If you are not on Luma Plus and have no plans to be, decide that first; most of the tracking depends on it.