Analytics

Sidebar: Analytics

Analytics answers one question: where does my traffic come from, and what does it turn into? Everything FlyB hosts for you — landing pages, blogs, blog posts, forms, booking calendars, tracked URLs and pricing tables — reports into the same explorer.

It is its own permission, and every role can read it by default: the report covers the whole capture side of the account, so it is not tied to owning a landing page. An admin can take it away per person on Settings → Team.

What is recorded

Each visit is aggregated into a daily bucket carrying:

FlyB stores aggregated daily counts, not an individual event log with a per-visitor identifier. Analytics data belongs to your organization and is never shared with other customers.

Where a visit’s campaign comes from

The three campaign columns are filled from the first of these that the visit carries:

1. The UTM tags on the link — utm_source, utm_medium, utm_campaign. Whatever you wrote always wins, and each field is treated on its own, so tagging only the source still leaves the other two free to be filled by the steps below.
2. A referral code — the ?ref= on a FlyB short link.
3. The advertising click identifier, described next.
4. The site the visitor came from — youtube.com, instagram.com and so on. Only a site that is genuinely somewhere else: moving between two FlyB addresses (your landing page and your blog, say) is not a visit from outside, and neither is coming back from a Google sign-in or a Stripe checkout we sent the visitor to.

If none of them is present the visit is recorded as direct.

A lead captured on that visit — a form, a booking or a sign-up — is given the same three values, so a contact and the traffic report never disagree about where it came from. See Contacts → Marketing & origin.

Ads without UTM tags

Ad platforms tag their own clicks. Google Ads adds ?gclid=... to the landing page address, Microsoft Advertising adds ?msclkid=..., and so on — automatically, with auto-tagging on by default, while adding UTM tags is something you have to remember to do. FlyB reads those identifiers, so paid traffic is still reported as paid traffic when the link was never tagged by hand:

Four of these are not reported as advertising. Facebook, Instagram and Pinterest add their identifier to every link opened from the app, and Google Shopping adds srsltid to free listings as well as paid ones — so those visits are labelled with the platform that sent them, which is true whether or not you paid for the click.

Campaign is filled from a real campaign name when the link carries one: your own utm_campaign, or utm_id, or the gad_campaignid that Google Ads adds next to the gclid. When there is none, the campaign repeats the medium — ads / google-ads / google-ads. It is never the click identifier: that value is unique to a single click, so using it here would give every visitor a row of their own and turn the campaign report into a list of opaque strings.

So keep tagging your links if you already do. Auto-tagging tells FlyB which platform sent the visit; only your own utm_campaign tells it which campaign.

The ad click on a lead

The click identifier is not discarded — it is kept on the contact, in a field of its own called Ad click ID, whenever a visit that arrived from an ad goes on to produce a lead: a FlyB sign-up, a form capture or a booking. One lead, one click.

That is the value Google Ads and Meta match on when you upload an offline conversion — it is how you tell them that the lead their ad produced became a sale — so it is shown with a copy button on the contact’s record. See Contacts → Marketing & origin.

It is stored for the same reason and under the same rules as the campaign parameters: it travels in the flyb_clid cookie, it waits for consent where consent is required, and it identifies an ad click rather than a person.

What is not counted

Analytics reports people, so three kinds of visit are left out. This is why the numbers here are usually lower than the raw request counts in a server log or in Google Search Console, and that difference is expected.

• Automated traffic. Search-engine crawlers (Googlebot, Bingbot and the rest), AI crawlers, SEO and uptime tools, speed audits and automated browsers are identified and discarded. On a site with a lot of indexed addresses they can easily outnumber the real visitors.
• The editor preview. Looking at your own page inside the FlyB editor never counts.
• Reloads. The same visitor reopening the same address counts once per 24 hours, not once per refresh.

Filtering

Filter traffic from lets you narrow to any combination of pages, blogs, forms, calendars, tracked URLs and pricing tables — or select all of one kind at once. A date range sets the window. The list offers the kinds whose module is active; the totals with nothing selected still count every visit your organization recorded.

A pricing table counts visits to its own public page only. A table embedded in a landing page or in an external site records nothing of its own — the page it sits in is already counting that visit.

For a page that is running an A/B test, the Include A/B variants switch decides whether the page’s numbers cover every version in the test or only the one you selected.

Grouping

Group by builds the table. You may combine dimensions, with one rule: only one time dimension at a time (Day, Day of Week, Day of Month, Month or Year).

Each row of the resulting table shows the hits, the row’s share of total hits, and — with Show Conversions on — the leads, qualified leads and completed payments attributable to it.

Above the table, a ranking by hits and an evolution over time chart summarise the same data. Rows past the top ones are grouped into “Others” so a long tail cannot hide the shape.

The conversion funnel

Vision of your Funnel reduces the selected period to four numbers:

Total Access → Total Leads → Total Qualified → Total Payments

Each step shows its share of the step above it. This is the fastest read of whether your problem is traffic, capture, qualification or closing.

The daily summary by e-mail

Once a day, FlyB e-mails your organization a short report of the last full day, measured against the day before it. It goes to the account owner, with the organization’s admins in copy.

What the day produced

The report opens with the two figures that say whether the day worked:

When bookings landed on more than one calendar, the three calendars with the most bookings are listed underneath, with how many they took; if there were more, the report says how many it left out.

A figure only appears when there was something to show. A day with no captures does not print a zero beside a red percentage.

The traffic

Underneath, the five most visited items of each kind:

Only content that received visits that day is listed. Something that was visited the day before and not since is left out of the report entirely, rather than shown at -100%.

Every line shows the visits and how that compares with the previous day. The section line totals all of your items of that kind, not just the five listed, so a section with more says how many it left out. Where there is nothing to compare against — no visits at all the day before — the change column shows a dash.

When it is sent

Overnight, between 00:01 and 06:00 UTC. The report covers the day that has just closed, so it is sent while it is still fresh and lands in the inbox before the working day starts; outside those hours nothing goes out. Each organization receives one report per night, at most.

It is sent when the day produced at least one of the three: a visit, a captured contact or a booking. A day made entirely of bookings still arrives; a day with nothing in any of them is not e-mailed at all.

To stop it, turn Daily summary by e-mail off under Settings → Company. The switch applies to the whole organization, and turning it back on restarts it the next day.

How a lead is attributed to a visit

When a visitor fills in a form, FlyB records which visit produced the contact. That is why the contact record carries the country, city, browser, page path and UTM parameters of its first visit, and why the Contacts filters can query on them — see Contacts → Filters.

Your own Google tags

Analytics inside FlyB is always on for content FlyB hosts. Independently of it, you can add your own Google Analytics measurement ID and Google Tag Manager container to a landing page or a tracked URL, and the data will flow into your own Google account as well. See Landing Pages and URLs & QR Codes.