Sites And Tracking

Sites define where Orbital Audience is allowed to collect data and how that data should be enriched.

What A Site Controls

Field What It Does
Name Label used in dashboards, filters, and reports.
Domain Public website domain used to attribute pages and sessions.
Timezone Local day boundary for dashboards and daily exports.
Navegg Adds Navegg audience profile signals when enabled.
Tail Adds Tail profile signals when enabled.
Advertiser Floodlight Adds a second advertiser-owned Floodlight dispatch when configured.
Google Ads Sends optional orb_* audience parameters to the configured AW- ID when explicitly enabled.

Main Tracking Tag

The generated Install Code tag is the base DMP tag for the site. It collects:

  • Page URL, path, host, title, canonical URL, metadata, headings, and text excerpt.
  • Anonymous visitor ID and first-party orbital_id.
  • Session ID.
  • Referrer and UTM parameters.
  • Optional logged-in site_user_id.
  • Product context when available.
  • Navegg and Tail profile signals when enabled.
  • Activation payloads used by Floodlight and audience workflows.
  • Optional Google Ads audience parameters when Google Ads is explicitly enabled for the site.

Install this tag on every page where audience and journey data should be available.

Installing With Google Tag Manager

  1. Open the site container in GTM.
  2. Create a Custom HTML tag.
  3. Paste the Orbital Install Code snippet.
  4. Enable Support document.write when GTM shows the option.
  5. Use a trigger restricted to the real production hostname.
  6. Exclude preview, render, staging, and server-side helper hosts unless they are intentionally tracked.
  7. Publish and validate in Orbital Audience.

Recommended trigger rule:

Page Hostname equals example.com

Avoid firing on hosts such as gtm-msr.appspot.com, because those are GTM render/preview contexts and can create artificial pages like /render.

Logged-In User ID

When the site can expose a stable customer identifier, enable Include site user ID and replace the sample value with the actual logged-in user ID.

Use this only for IDs owned by the advertiser site. Do not put email, phone, CPF, or raw personal data in the field.

The ID helps connect anonymous behavior to a known site account when the user logs in.

Single-Page Applications

For SPAs, install the main tag on the application shell. The first page view is collected on load.

If the app changes routes without a full page load, ensure the route-change implementation triggers a new page collection or reloads the DMP tracker intentionally. Validate that:

  • window.location.pathname reflects the public route.
  • The canonical URL points to the user-facing page.
  • Technical routes such as /render are not collected as real pages.

Canonical Handling

When a render or preview path is collected but the page exposes a valid same-domain canonical URL, Orbital Audience can normalize the page to the canonical URL.

Example:

Collected URL:  https://orbital.company/render
Canonical URL:  https://orbital.company/
Stored URL:     https://orbital.company/

Quality Checklist

  • Domain is saved without https:// and without paths.
  • Main tag fires only on allowed hostnames.
  • Conversion tags are installed separately from the main tag.
  • Canonical URLs are correct.
  • UTMs remain available on landing pages.
  • Consent rules used by the advertiser are respected.
  • Google Ads is enabled only for sites that have an approved AW- ID.