ApivomApivom
Get Demo

Features

Everything Apivom Orbit can do: the full feature catalog, with what each feature does and how it fits into the Apivom platform.

Overview: traffic, pages and users

See daily visits and page views, top pages, events and identified users for the last 7, 30 or 90 days, with breakdowns by device, browser, country and traffic source.

The Overview is the first screen in Orbit. It shows daily visits and page views as a chart, then the pages with the most views, the custom events your sites and apps send, and the users who have been active in the period.

Breakdowns split the same period by device, browser, country and traffic source, with each row shown as a share of visits. Switch the date range between 7, 30 and 90 days and every panel follows.

The numbers come from the events your sites and apps send to Orbit, so there is no export to build and no spreadsheet to refresh.

Websites: referrers and campaigns

Every connected website gets daily visitors and page views, with referrers, campaigns, campaign sources and mediums, devices, browsers, operating systems and languages.

The Websites view lists the websites Apivom has connected for your account, with domain, visitors, page views and last update. Open one to see its daily visitors and page views, its top pages and its events.

The referrer and campaign breakdowns show where traffic comes from. Campaigns are read from the campaign tags on your links, so you can compare campaigns, campaign sources and campaign mediums side by side. Devices, browsers, operating systems and languages show who is visiting.

Apivom connects your websites for you, so a new site appears in the list with no step on your side beyond adding the tracking library.

Ads: spend and conversations

Follow spend, conversations started, cost per conversation, qualified leads, sales and return on ad spend for the Meta ad account you connect in Mars, with alerts when a figure passes its limit.

The Ads view shows the spend and results of the Meta ad account you connect in Apivom Mars. A daily chart plots spend against conversations started, and a campaign table ranks campaigns by spend with conversations, cost per conversation, qualified leads, sales and revenue.

The view also reports return on ad spend, and an alerts panel lists the days when daily spend or cost per conversation went above the limit.

If access to the ad account has to be renewed, Orbit says so and points you to Mars to reconnect it.

Social: followers and post engagement

Follow the audience and post results of the Facebook, Threads and LinkedIn accounts you connect in Mars: followers per account, and impressions, likes, comments and shares per post.

Connect a Facebook, Threads or LinkedIn account in Apivom Mars and Orbit shows it under Social. The view lists each connected account with its follower count and the time of the latest snapshot.

Below it, recent posts are listed with impressions, likes, comments and shares, so you can see which posts earned engagement.

Because publishing happens in Mars and reporting in Orbit, you do not copy numbers from one tool to the other.

One tracking library

Add one library to your site or app and send page views, events and identified users to Orbit, instead of a separate script for every analytics or marketing tool.

Everything in Orbit starts as an event. You add one tracking library for the browser and one for your servers, and call it for page views, screen views, custom events, identifying a user and grouping users.

The browser library is served from Apivom, with its plugins mirrored there, so your pages make no calls to an outside CDN for it. Events reach a gateway first, and the gateway forwards them from the server to the destinations set up for the source: web analytics, marketing automation, Google Analytics 4 and LinkedIn Insight Tag.

Because every tool is fed from the same stream, you instrument once and Apivom changes destinations later without touching your site.

A warehouse schema per source

Each source gets its own schema in the warehouse with pages, tracks and identifies tables, synced on a 30-minute cycle.

Behind the dashboard, events are written into a warehouse database that keeps one schema per source. A website gets a schema of its own, and so does each customer of Apivom Iris and Apivom Atlas, created automatically.

Every schema has the same standard tables: pages, tracks and identifies. That gives each source a consistent structure for the Overview and Websites views to read from.

The warehouse syncs on a 30-minute cycle. Orbit also copies analytics aggregates into each customer account’s own space every hour, which feeds its views.

First-party identity and consent

Visitors are recognised by a first-party identifier that lasts 1 year, identify joins their events under one user, and the library sends consent choices with every event.

Each visitor gets an anonymous identifier, kept in a first-party cookie for 1 year. Orbit re-issues that cookie from the server for the domains Apivom has allow-listed for your account. When a visitor signs in, call identify with your own user id and their events are reported under that user.

The browser library attaches the visitor’s consent choices to every event: which categories are allowed and which are denied. A destination can be given a consent rule, and when the visitor has denied that category the gateway drops the destination for that event.

First-party destinations, such as Apivom Opus and the warehouse, receive all events. Consent is read from your own consent manager, so what visitors choose on your site is what Orbit follows.

More about Orbit