TagPipes Companion for Chrome Add to Chrome →

Analytics

The Loyalty Sign-Up Is Your Most Valuable Form. Are You Measuring It?

The sign-up is the identity moment

Most of what happens on a restaurant website is anonymous. A guest browses the menu, finds a location, maybe places an order as a guest. Then, at the loyalty sign-up, they tell you who they are and agree to hear from you.

That's the most valuable form on the site, and it's often the least measured. Three things need to be recorded at that moment: where the guest came from, a way to connect them to their orders, and the choice they made about marketing. Miss any of them at sign-up and you can't rebuild it later. The checks below are our practice framing, not measured findings.

Record the source at sign-up

If you want to know which campaigns recruit members, the campaign has to be written down when the member joins. Two common ways to do it:

  • Hidden fields on the form. Capture the campaign tags from the landing URL (source, medium, campaign) into hidden fields, so they're saved with the member record in the loyalty system.
  • An analytics event at sign-up. Fire a sign-up event when the form succeeds, so analytics credits the session's source. GA4 has a recommended sign_up event for this.

Ideally you do both. The hidden fields keep the source with the member forever; the analytics event lets you compare sign-ups with everything else the campaign did. If you're tagging links to the sign-up page from email, the naming rules in What Did That Email Sell? apply here too.

Join loyalty to online orders

Members are only half the picture. The value of a loyalty program shows up in the orders members place afterward, and that means the loyalty profile and the online order need a shared key.

In practice that's the member ID. When a signed-in member places an order, the member ID should travel into the ordering flow and land on the order record. Without that join you can count members and you can count orders, but you can't connect them, so "repeat orders per member" becomes a guess.

Check it the simple way: sign up as a test member, place a test order while signed in, and see whether the order shows up against the member in the loyalty system and in the order export. If the ordering flow runs on a separate domain, test the hop specifically. One Store, One Key covers the same handoff problem for store IDs.

Store the consent choice with the record

The third thing to record is the guest's choice: what they agreed to, and when. Store it with the member record at the time it's made, not reconstructed later from a default.

This post describes what to record, not what any law requires of you. Which choices you need to ask for, and how, is a question for your counsel.

What you can report once it holds

Once source, member ID and choice are all captured at sign-up, a few reports become possible that usually aren't:

  • Members by recruiting campaign. Which channels bring in sign-ups, from the hidden fields.
  • Repeat orders per member. From the member ID on each order.
  • Repeat orders by recruiting campaign. The one that matters: which channels recruit guests who actually come back, not just guests who join.

That last report is what lets you stop judging a loyalty campaign by sign-up count alone. A channel that recruits fewer members who order often can be worth more than one that recruits many who never return.

Where restaurant sites start

Recording the choice only works if the site waits for it. Our Website Privacy Index suggests most restaurant sites aren't set up that way yet. In the restaurant edition, 131 of 31,167 restaurant sites scanned January to November 2026 were Gated (0.4%, about one in 238).

The report defines Gated as: "Consent platform detected, Consent Mode v2 observed, no tracking seen before consent or after denial." That's what the scanner observed on one public page load, not a judgment about any site. The other end of the scale is larger: 25,689 restaurant sites (82.4%) had no consent platform and no privacy preferences link detected.

Why Restaurant Websites Score Worst On Privacy explains why the vertical starts there, and Your Own Orders vs Marketplace Orders covers why the guest data you collect yourself is worth getting right.

A five-question self-check

  1. Is the campaign source captured on the member record at sign-up?
  2. Does the member ID reach the ordering flow and land on the order?
  3. Does the purchase event fire once per order, with its value?
  4. Is the guest's choice stored with the record, at the time it was made?
  5. Do marketing tags wait for that choice before they fire?

If any answer is no or don't know, start there. Book a data and tracking audit and we'll walk the sign-up and ordering path with you, or request a free privacy scan to see what loads on your site before a guest chooses. We review each request within 48 hours.

Source: Rawsoft Website Privacy Index, 47,506 sites scanned and 47,420 scored, January to November 2026. Most of the index is restaurant, hospitality and ecommerce sites, and the report itself says it is not a sample of the web as a whole. Every figure describes what an automated scan could observe on a public page.

More from the Website Privacy Index: Do cookie banners work? · Consent Mode v2 adoption · Ecommerce privacy index

Rawsoft provides technical implementation and analysis, not legal advice. Please confirm any regulatory interpretation with your counsel.

Get new research by email

New posts and Website Privacy Index findings, sent to your inbox. No spam, unsubscribe anytime.

We only use your email for this list. See our Privacy Policy.

About Rawsoft

Rawsoft is an Atlanta-based digital data agency specializing in analytics implementation, privacy and consent management, and media tracking for enterprise brands.

Add Rawsoft as a preferred source on Google

More from the blog

Analytics

One Store, One Key: Fixing Location-Level Reporting for Restaurant Brands

Location reports disagree because every tool names your stores differently. Agree one location key and pass it everywhere before you build another dashboard.

November 2026Read

Analytics

Your Own Orders vs Marketplace Orders: The Guest Data You Never Get Back

A marketplace order and an order on your own site can be the same meal. Only one of them leaves you a guest you can market to. What each channel lets a restaurant measure.

November 2026Read