Crisper22 min read6 views

What Crisper sends to Google Analytics 4, field by field

Every GA4 event and field Crisper sends, when each one appears, which to register as custom dimensions or metrics, and how to read bot and AI traffic.

The short answer

Crisper sends supported page, lead, booking and store events to Google Analytics 4, with campaign, form and order details when available. This guide explains when each field applies and how to register it. Bot, AI and ad-blocker signals are included when available; verify them in your property before building reports.

  • Verify campaign fields first; register form_id if your forms supply it. Allow 24–48 hours for reporting.
  • If you sell online, add payment_type, new_customer and the cart and discount fields.
  • A standard GA4 property allows 50 event-scoped custom dimensions and 50 custom metrics, and registration does not fill in past data.
  • Never register click IDs, session IDs or visitor IDs. Google reserves some of those names anyway.
  • Field list checked against Crisper's live tracking setup and Google's documentation on 28 October 2026.

Ask an assistant

ChatGPTClaudePerplexity

FREE AUDIT

NO LOGIN

Check what Meta and Google can count on your site

  1. Your site
  2. Crisper
  3. Meta and Google count it

Enter your website to see how good its tracking is, and whether Meta is likely restricting it.

Run a free audit

What does Crisper send to GA4?

Crisper sends three kinds of data to GA4, and only one of them needs work from you. GA4 handles the first two itself; the third is extra parameters whose reporting definitions you choose after verifying collection.

GA4's automatic data

Examples
Page views, sessions, engagement time, device, country, Session source / medium
What you do
Nothing. Use GA4's standard reports.

Fields GA4 already understands

Examples
value, currency, transaction_id, tax, shipping, coupon and items on store events
What you do
Nothing. They fill the monetization reports and predefined dimensions such as Transaction ID and Order coupon.

Crisper's extra fields

Examples
first_session_campaign, form_id, cart_total, device_bot and the rest of this guide
What you do
Register the ones you will use as custom dimensions or custom metrics.
Three kinds of GA4 data. Only the third needs registering.

An event parameter is a detail attached to one event, such as the form ID on a lead. A custom dimension makes a parameter available to group or compare events in reports. A custom metric makes a numeric parameter available for calculations. A user property describes the visitor rather than one event. Google's overview of custom dimensions and metricssupport.google.com has the full definitions.

This guide covers sites installed with Crisper's standard tracking, which loads from your own tracking subdomain and is more resistant to ad blockers. Each connected integration has its own event mappings. Verify delivery in the platform you want to report on. If your site runs its own Google Tag Manager container, its field list can differ, so check Realtime before registering anything.

Which events reach GA4, and what triggers them?

The standard web tag is configured to send page_view on page loads; receipt still depends on the installation. Other events depend on the tools your site uses. If a tool isn't on your site, its events never appear, and that is expected.

page_view

Sent when
Any page loads
Where you see it
Every site

generate_lead and submit_application

Sent when
A GoHighLevel, ClickFunnels or Heyflow form is submitted, a Typeform thank-you page loads, or your site sends its own lead event
Where you see it
Lead and booking sites

schedule

Sent when
A Calendly or GoHighLevel booking is completed
Where you see it
Booking sites

contact

Sent when
Someone taps a phone, email or WhatsApp link
Where you see it
Sites with those links

tf_form_loaded, tf_form_started, tf_form_submitted

Sent when
A Typeform embed loads, is started, or is submitted
Where you see it
Sites with Typeform

cf_form_loaded

Sent when
A ClickFunnels form appears on the page
Where you see it
ClickFunnels pages

view_item, select_item, add_to_cart, view_cart, remove_from_cart, begin_checkout, add_payment_info, purchase

Sent when
A shopper takes that step in your store
Where you see it
Online stores

submit_application, then purchase when the booking has a price

Sent when
An Acuity appointment or order is confirmed
Where you see it
Acuity sites

Any other event name

Sent when
A custom event you or Crisper added, for example with custom events set up through an AI assistant
Where you see it
Varies by site
Events Crisper's standard tracking sends to GA4, checked 28 October 2026.

The shared GoHighLevel, ClickFunnels, Heyflow and matching thank-you-page triggers send both generate_lead and submit_application for the same action. Custom and booking events can follow different paths. Mark only one of them as a key event in GA4, or your key event count doubles.

The shared store-event mappings do not generate GA4 events for collection and product-list views, searches, or the contact, address and shipping steps of checkout. Additional tracking on your site may still send these events to GA4. A few sites also have events set up for them alone, such as scroll depth or a booking thank-you page; ask us about any event name you don't recognize.

To see what your own property receives today, open Reports > Realtime overview in GA4, view a product or submit a test form in another tab, then click that event in the Event count by Event name card. The parameter names listed there are the ones you can register.

Which fields come with which events?

Each Crisper field rides on some events and not others. A missing or empty value can show as (not set) in a report. Some request keys can also be present but empty; that does not make them meaningful values.

Standard fields GA4 reads on its own

page_location, page_referrer, page_title, language, screen_resolution

Sent on
Web events when the browser supplies these values
Where it shows in GA4
Predefined dimensions such as Page location, Page title and Language. Nothing to register.

value, currency

Sent on
Events that carry a value, mostly store events
Where it shows in GA4
Event value, and Purchase revenue on purchase

transaction_id, tax, shipping, coupon

Sent on
purchase
Where it shows in GA4
Transaction ID, Tax amount, Shipping amount, Order coupon

items with item_id, item_name, item_brand, item_category, item_variant, price, quantity, index, discount

Sent on
Store events with products
Where it shows in GA4
Item reports: Item name, Item ID, Item brand, Item category, Item revenue and more

item_list_id, item_list_name

Sent on
Store events from a product list, when the store sends them
Where it shows in GA4
Item list name and ID
Fields GA4 recognizes without any setup.

Google lists the parameters it collects with every web eventsupport.google.com and the fields each store event usesdevelopers.google.com. The shared container does not explicitly configure enhanced measurement events such as scroll, outbound click, file_download, form_start and view_search_results. Their availability also depends on your Google tag and GA4 stream settings, which were not inspected here.

Shopify stores also send item details GA4 doesn't know, inside items: item_sku, variant_name, item_url, compare_at_price, and item_selling_plan_id and item_selling_plan_name for subscriptions. To report on one, register it as an item-scoped custom dimensionsupport.google.com. A standard property has 10 of those, so pick the one or two you'd filter by, such as item_sku or item_selling_plan_name.

Where the visitor came from

first_session_source, first_session_medium, first_session_campaign, first_session_campaign_id, first_session_term, first_session_content

What it holds
The UTM values from the visitor's first tagged visit in this browser, with a configured storage lifetime subject to browser limits and renewal
Sent on
Every event, once the visitor has arrived on a link with UTM tags
Register as
Event-scoped custom dimensions

last_session_source, last_session_medium, last_session_campaign, last_session_campaign_id, last_session_term, last_session_content

What it holds
The UTM values from the most recent tagged visit, with a configured 30-day lifetime that can be renewed
Sent on
Every event, once the visitor has arrived on a link with UTM tags
Register as
Event-scoped custom dimensions

session_session_source, session_session_medium, session_session_campaign, session_session_campaign_id, session_session_term, session_session_content

What it holds
This visit's source: UTM tags first, otherwise the referring site, otherwise (direct) / (none)
Sent on
Every event
Register as
Optional. GA4's own Session source / medium usually covers it.

crisper_session_id

What it holds
Crisper's ID for the current visit
Sent on
Every event
Register as
Don't register

fbclid, fbc, fbp, gclid, gbraid, wbraid, ttclid, ttp, crisperclid

What it holds
Ad click and browser IDs used to match conversions to ads
Sent on
When the link or a cookie has them
Register as
Don't register
Acquisition fields. The doubled word in session_session_source is the real parameter name.

Type session_session_source exactly as written when you register it; the doubled word is part of the name. The first and last fields fill only from tagged links, so a visit from Google search or an untagged link sets the session fields but never the first or last ones. Tag your ad and email links with the UTM builder so they fill; how UTM parameters work explains each part.

First campaign is per browser, not per person. Switching devices, clearing cookies or browser restrictions can reset the history. The current setup also renews selected cookies on the server, so a requested lifetime is not a guaranteed retention period. Chrome caps individual cookie expiry at 400 daysdeveloper.chrome.com; Safari has its own tracking-prevention ruleswebkit.org.

GA4 has its own First user source, the source by which GA4 first acquired the usersupport.google.com. Crisper's first_session_* and last_session_* fields are plain values on each event instead, so you can put the first and the last campaign side by side on the same lead without GA4's attribution rules in between.

Store and order details

ecomm_pagetype

What it holds
The page type the store reports, such as product, category, basket or other
Sent on
Store events
Register as
Event-scoped dimension

collection_id

What it holds
The collection a product was picked from
Sent on
select_item
Register as
Event-scoped dimension, if you compare collections

cart_quantity

What it holds
Number of items in the cart or order
Sent on
Store events that carry products
Register as
Custom metric, Standard

cart_total

What it holds
Cart total before discounts
Sent on
begin_checkout, add_payment_info, purchase
Register as
Custom metric, Currency

sub_total

What it holds
Order subtotal on purchase; on other events it repeats the event value
Sent on
Store events with a value
Register as
Custom metric, Currency, if you need the subtotal

discount_amount

What it holds
Discount given, in money
Sent on
purchase
Register as
Custom metric, Currency

discount_percentage

What it holds
Discount given, in percent
Sent on
purchase
Register as
Custom metric, Standard

discount

What it holds
The discount code
Sent on
purchase
Register as
Skip. GA4's Order coupon reads the same code from coupon.

payment_type

What it holds
Payment method, such as creditCard
Sent on
add_payment_info, purchase
Register as
Event-scoped dimension

new_customer

What it holds
true for a first-time buyer, false for a returning one
Sent on
purchase
Register as
Event-scoped dimension

value, currency, transaction_id, tax, shipping, coupon, items

What it holds
Standard order fields
Sent on
Store events
Register as
Don't register. GA4 already reports them.
Store fields, from a Shopify store's data. Other store platforms send similar fields; confirm in Realtime.

These fields come from your store, so a site without a store never sends them. Google also advises against registering a parameter that already has a predefined dimensionsupport.google.com, such as transaction ID, because it uses a slot and adds nothing.

Forms, bookings and contact clicks

form_id

What it holds
The Typeform form's ID
Sent on
tf_form_loaded, tf_form_started, tf_form_submitted, and the lead events on a Typeform thank-you page
Register as
Event-scoped dimension

embed_id

What it holds
Which embed of that Typeform on your site
Sent on
The same Typeform events
Register as
Usually skip

phone_number

What it holds
The link that was tapped: a phone number, email address or WhatsApp link
Sent on
contact
Register as
Skip. Email links put an address in it.
Form and contact fields.

The standard mappings do not intentionally attach a Typeform ID to purchases, Calendly or GoHighLevel bookings, or GoHighLevel and ClickFunnels forms. Custom implementations or persistent data-layer values can differ; do not assume a form ID describes every event that happens to carry it. In a report by form_id their leads show (not set); compare them by event name and page instead. GA4's own form_start and form_submit events also use a parameter called form_id, for the HTML form's ID, so if another GA4 tag on your site sends those, one form_id dimension holds both kinds of value.

Visitor quality

device_bot

What it holds
true when the visit scored 50 or more for bot signals, otherwise false
Sent on
Where the request supplies the signal; reporting verification pending
Register as
Event-scoped dimension after receipt is verified

device_bot_score

What it holds
A score from 0 (human-like) to 100 (bot-like)
Sent on
Where the request supplies the signal; reporting verification pending
Register as
Event-scoped dimension after receipt is verified

user_ai

What it holds
true when the visit was detected as coming from an AI tool
Sent on
Where the request supplies the signal; reporting verification pending
Register as
Event-scoped dimension after receipt is verified

user_adblocker

What it holds
Whether an ad blocker was detected on a request that reached tracking
Sent on
When the signal is supplied; reporting verification pending
Register as
Event-scoped dimension after receipt is verified

user_ai_name

What it holds
The AI platform's name, when it could be identified
Sent on
When a platform name is supplied; reporting verification pending
Register as
Event-scoped dimension after receipt is verified
Bot, AI and ad-blocker fields. How to read them is below.

If you used the previous AI parameter names

The current AI names are user_ai and user_ai_name. The bot and ad-blocker names have not changed, and this update does not rename any GA4 events.

ai_traffic

Current parameter
user_ai

ai_traffic_source

Current parameter
user_ai_name
AI parameter names changed on 28 October 2026.

If you registered an old name, keep that definition for any history it already contains. Once you verify receipt of the new name, create a new Event-scoped definition for it and use that definition in future explorations. Google does not let you change a saved definition's event parameter or scopesupport.google.com. Renaming its display label does not retarget it, and a new definition does not combine or backfill the old data.

Request details and contact fields

In the incoming request details for an event, you may see keys such as ep.user_data.email, ep.user_data.phone_number and ep.user_data.address.0.first_name. The ep. prefix is a transport prefix for an event parameter, not a separate dashboard variable. The current GA4 forwarding setup explicitly excludes these keys and the mapped contact-address fields. They may still be available in incoming request details when your Crisper logs expose them.

Incoming request details and GA4 reports serve different purposes. The current exclusions do not establish what Google retained from older requests or from other tags on your site. Do not register email, phone or other personal contact details as custom report dimensions; Google's guidancesupport.google.com distinguishes acceptable analytics data from personally identifiable information.

IDs and setup labels

Leave these alone: crisper_cid (also added as a user property by the server; a fallback visitor ID that different visitors can share), database_cid (your store's customer ID for signed-in shoppers), ta_event_id, ta_integration_method, ta_web_container_id and ta_web_container_version. They are IDs or setup labels, and Google advises againstsupport.google.com custom dimensions for unique IDs per user or per session.

The server also sends integration_method, server_container_version and server_container_id as diagnostic event fields. They are useful for support checks, not part of the recommended custom-definition starter set.

Google also reserves some names outright. gclid, currency and customer_id can't be usedsupport.google.com for custom dimensions, and user_id can't be used as a user property dimension.

How do I register a custom dimension or metric in GA4?

Register a field once and GA4 reports it for every event that carries it from then on. Do it as soon as you know you'll use the field, because GA4 does not fill in the days before.

Step 1: Confirm the field arrives

  1. In GA4, open Reports > Realtime overview.
  2. In another tab, do what sends the event: view a product, submit a test form or tap a phone link.
  3. In the Event count by Event name card, click the event.
  4. Find the parameter name in the list that opens.

Done when you can see the parameter, spelled exactly as in this guide, on the event. Google suggests this Realtime checksupport.google.com before you create the dimension.

Step 2: Create an event-scoped custom dimension

  1. Click Admin.
  2. Under Data display, click Custom definitions.
  3. Open the Custom dimensions tab and click Create custom dimension.
  4. Dimension name: a readable name, such as First campaign. Use spaces or underscores, not hyphens.
  5. Scope: Event.
  6. Description: optional, for example "First UTM campaign from Crisper".
  7. Event parameter: the parameter name, such as first_session_campaign.
  8. Click Save.

For an item field such as item_sku, follow the same steps with Scope set to Item (Google's item-scoped stepssupport.google.com). Done when the dimension appears in the Custom dimensions list. You need the Editor role or higher, and you can't change the scope or the parameter after saving (Google's stepssupport.google.com).

Step 3: Create a custom metric for numbers

  1. In Admin > Custom definitions, open the Custom metrics tab.
  2. Click Create custom metric.
  3. Metric name: such as Cart items.
  4. Event parameter: such as cart_quantity. Custom metrics are event-scoped; there is no scope choice to make.
  5. Unit of measurement: Standard for counts and percentages, Currency for money. For Currency, choose cost or revenue classification only if it matches what that metric actually measures.
  6. Click Save.

Done when the metric appears in the Custom metrics list. Google's custom metric stepssupport.google.com list every unit option.

Step 4: Wait a day, then check

Google says custom dimensions and metrics become usable after 24 to 48 hourssupport.google.com, and a newly registered parameter can show (not set) for the first 24 hourssupport.google.com. Events from before you registered don't gain the dimension; registration is not retroactiveanalyticsmania.com, although previously exported raw data may contain parameters independently of custom-definition registration.

Done when an exploration the next day lists real values for the new dimension, such as campaign names under First campaign.

Which fields should I register first?

Start with the fields that answer a question you already ask. A standard property allows 50 event-scoped custom dimensions, 25 user-scoped ones and 50 custom metricssupport.google.com, and the starter set below uses well under half.

Any site running ads

Register
first_session_source, first_session_medium, first_session_campaign, last_session_source, last_session_medium, last_session_campaign
As
Event-scoped dimensions

Sites with Typeform

Register
form_id
As
Event-scoped dimension

Online stores

Register
ecomm_pagetype, payment_type, new_customer
As
Event-scoped dimensions

Online stores

Register
cart_quantity (Standard), cart_total and discount_amount (Currency)
As
Custom metrics

Online stores that filter by SKU or sell subscriptions

Register
item_sku or item_selling_plan_name
As
Item-scoped dimension

Every site, once Realtime shows them

Register
device_bot, device_bot_score, user_ai, user_ai_name, user_adblocker
As
Event-scoped dimensions
A starter set to choose from. Register only fields you have verified and intend to report on.

Add the content, term and campaign ID versions later if you use those UTM parts. Three mistakes cost you data:

  • Registering a week late. That week stays without the dimension in reports.
  • Registering IDs. crisper_session_id or a click ID has a new value on almost every visit, which pushes report rows into the (other) rowsupport.google.com.
  • Reading `(not set)` as zero or as human. It means a report value is unavailable, which can reflect missing collection or registration and processing timing.

If you reach the limit, Google makes you wait 48 hourssupport.google.com after archiving a dimension before you can add a new one.

How do I read bot, AI and ad-blocker signals in GA4?

Crisper configures bot, AI and ad-blocker labels for measurement. Bots and AI traffic continue forwarding. The signals describe requests that reached tracking; they do not count every blocked visit or every crawler on your website.

As checked on 28 October 2026, all five signal names are in the published configuration and appeared in a small sample of outgoing GA4 requests. The AI platform name was empty in that sample. This confirms the forwarding path, not collection in every client property. Verify populated values in your property before using them in reports; registration alone does not create missing data.

device_bot = true

What it means
The visit scored 50 or higher: likely automated or suspicious

device_bot = false

What it means
The request scored below 50; this does not prove a human visitor

device_bot_score = 0 to 100

What it means
Higher is more bot-like. 0 is a real score, not missing data.

device_bot or device_bot_score = (not set)

What it means
No reportable value is available, for example because collection or registration was missing. It does not mean human.

user_ai = true

What it means
The visit was detected as coming from an AI tool, such as an AI assistant or an AI browser

user_ai = false

What it means
A negative AI flag was supplied; not proof of a human visitor

user_adblocker = true

What it means
An ad blocker was detected on this request

user_adblocker = false

What it means
No ad blocker was detected; not a guarantee that nothing was blocked

user_adblocker missing or (not set)

What it means
Unknown for this event; keep it separate from false

user_ai_name = a name

What it means
The AI platform, when it could be identified

user_ai_name = (not set)

What it means
No platform value is available; do not infer a human or non-AI visit
How to read these signals once GA4 collection is verified.

An AI referral does not automatically mean a bot visit. Read user_ai alongside source/medium and bot signals, but do not use them alone to decide whether a person clicked an assistant link or an autonomous agent fetched the page. Detection is incomplete.

After collection is verified, use an event-based comparison: Event name as rows, device_bot or user_adblocker as columns, and Event count as values. Keep missing values visible. Do not treat event counts as unique visitors or interpret the ad-blocker flag as a measure of all traffic lost to blocking.

For a score distribution, register device_bot_score as an Event dimension and use Event count against its values. If you also need numeric calculations, first verify that GA4 receives a number, then create a custom metric with Event parameter device_bot_score and Unit of measurement Standard. A sum of scores is not a bot count; an average needs the number of events carrying a valid score as its denominator, not all events.

What reports can I build with these fields?

Each report below is a free-form exploration. Build one once and it updates every day; the same steps build a custom report for Facebook ads in GA4.

  1. Click Explore, then Blank.
  2. Next to Dimensions, click +, open the Custom tab, tick the dimensions you registered, and click Import. Do the same next to Metrics.
  3. Drag dimensions into Rows and metrics into Values.
  4. Under Filters, add Event name where the report needs one event.

Google's custom metric guidesupport.google.com shows the same import steps with screenshots.

Which campaign first found the people who became leads, and which one brought them back?

Rows
first_session_campaign, then last_session_campaign
Columns
None
Values
Event count
Filter
Event name exactly matches generate_lead

Which Typeform form gets finished?

Rows
form_id
Columns
Event name
Values
Event count
Filter
Event name contains tf_form

Do first-time buyers spend more than returning ones?

Rows
new_customer
Columns
None
Values
Purchase revenue, Ecommerce purchases
Filter
None

Which discount codes cost the most?

Rows
Order coupon
Columns
None
Values
Ecommerce purchases, Purchase revenue, discount_amount
Filter
None

Which AI sources accompany leads and purchases?

Rows
user_ai_name
Columns
Event name
Values
Event count
Filter
user_ai exactly matches true; after collection is verified

Which received events have ad-blocker detection?

Rows
Event name
Columns
user_adblocker
Values
Event count
Filter
None; after collection is verified
Six explorations from the starter set. Pick the dimension or metric you registered for each parameter.

For the form question, a Funnel exploration with tf_form_loaded, tf_form_started and tf_form_submitted as steps and form_id as the breakdown shows where each form loses people.

Why do I see (not set), blanks or (other)?

Almost always because the event didn't carry the field. The common causes:

  • The event never carries it. form_id on a purchase, or cart_total on a page_view.
  • The visitor never arrived on a tagged link. The first and last campaign fields stay empty until they do.
  • The dimension is less than a day old. Google says a new custom parameter can show (not set) for the first 24 hourssupport.google.com.
  • You're looking at `session_start` or `first_visit`. Those keep only the parameters of the session's first event, per Googlesupport.google.com.
  • The date range starts before you registered. Earlier events don't gain the dimension.
  • (other) instead of (not set). The table hit its row limit; Google calls a dimension with more than 500 values high cardinalitysupport.google.com. IDs cause this, which is why they stay unregistered.

When do you not need Crisper for GA4?

If all you need is GA4's standard reports, Google's own tag is enough: GA4 already reports sessions, sources and store revenue. Crisper is built for advertisers whose domain Meta has restricted, and the GA4 fields are a useful extra on the same events, not a reason to switch on their own.

Conversions your CRM sends to Crisper by webhook are set up for your ad platforms, not for GA4, so GA4 won't show a sale your team closes later in the CRM. If your site runs its own Tag Manager container instead of Crisper's standard install, the fields above can differ; check Realtime before you register.

Questions people ask about Crisper and GA4

Do bot-like visits still count in my GA4 conversions?

Crisper continues forwarding bot-like traffic; these labels are for measurement. GA4 applies its own collection and processing rules, so forwarding is not a guarantee that every event appears in reports. Once the fields arrive, use device_bot in an exploration to compare received key events.

Is a visit from ChatGPT counted as a bot?

An AI referral does not automatically mean a bot visit. user_ai and device_bot are separate signals: a person can follow a link from an AI assistant. After collection is verified, read the fields together; detection is not proof of who visited, and a missing flag is not false.

Why can't I register `gclid` or `user_id`?

Google reserves those names, along with currency, customer_id and otherssupport.google.com. You can't create a custom dimension with them, and you don't need to.

Why does `session_session_source` differ from GA4's Session source?

They're worked out separately. Crisper uses UTM tags first, then the referring site, then (direct), and starts a new visit after 30 minutes without activity or when the source changes. GA4 applies its own rules, so small differences are normal.

Are custom dimensions retroactive?

No. GA4 shows a custom dimension only for events collected after you register it, and new definitions take 24 to 48 hourssupport.google.com to appear.

How many custom dimensions can I create?

On a standard property, 50 event-scoped and 25 user-scoped custom dimensions, 10 item-scoped ones and 50 custom metricssupport.google.com. GA4 360 allows more.

Should you use Crisper for GA4 and Meta?

If Meta has restricted your domain and you also want GA4 to show where each lead first came from, which form it used and which order details apply, we recommend Crisper. It recovers usable Lead and Purchase events on the domain you already have, and its GA4 integration forwards supported events with the applicable fields described here. Verify the fields you need before building reports; the traffic-signal delivery caveat above still applies.

Sources

14 sources
  1. 1Google's overview of custom dimensions and metrics↩
  2. 2collects with every web event↩
  3. 3fields each store event uses↩
  4. 4item-scoped custom dimension↩
  5. 5caps individual cookie expiry at 400 days↩
  6. 6tracking-prevention rules↩
  7. 7first acquired the user↩
  8. 8does not let you change a saved definition's event parameter or scope↩
  9. 9Google's guidance↩
  10. 10can't be used↩
  11. 11custom metric steps↩
  12. 12for the first 24 hours↩
  13. 13registration is not retroactive↩
  14. 14the (other) row↩