Mettriccloud

Cookie Policy

Last updated: October 15, 2026

Cookies are small files stored in your browser. Here we explain which ones mettric.cloud uses, why, for how long, and how you control each category.

ChatGPT ad measurement

With marketing consent, the OpenAI pixel measures page views and server-accepted contacts for ChatGPT ad attribution. The SDK may automatically match normalized and hashed contact information. Cookies __oppref (up to 30 days) and __obref (up to 365 days) support measurement and are removed on consent withdrawal. mtc_lead_receipt is a session lasting up to 10 minutes, created with analytics or marketing consent to confirm an accepted contact once. Google Analytics receives the event only with analytics consent; advertising pixels only with marketing consent. You can refuse or withdraw consent in the footer.

1. Categories we use

  • Required — site security and core functionality, including the record of your consent decision. Always on.
  • Analytics — metrics, heatmaps and session recordings (Google Analytics and Microsoft Clarity). Only with your consent.
  • Marketing — measurement and remarketing (Google Ads, OpenAI, Meta and LinkedIn), source attribution, Mettric Identity and native Web Push (VAPID). Only with your consent; push also requires separate browser permission.
  • Preferences — reserved category with no active feature or tracker at present. If that changes, we will update this policy and ask for a new decision.

2. First-party cookies (set by us)

  • mtc_consent — stores full acceptance and the policy version. Category: required. Duration: 12 months.
  • mtc_consent_session — stores refusals and custom preferences for the current session only. Category: required. It is removed when the browser session ends.
  • __Host-mtc_experiment — random signed identifier used to allocate A/B tests and deduplicate conversions; it contains no name, email address or other data submitted through a form. Category: marketing; created only with marketing consent and removed when that consent is withdrawn. Duration: 30 days.
  • mtc_attrib — campaign source (UTMs, gclid/gbraid/wbraid/fbclid/msclkid, referrer), first and last touch. Category: marketing; only written with marketing consent and deleted if you refuse. Duration: 90 days.
  • mtc_push_adiado and mtc_push_decisao (local storage) — remember that the notification invitation was dismissed or completed so it is not repeatedly shown. Category: marketing; created only after marketing consent. Duration: 12 months.

3. Third-party cookies

  • Google Analytics (_ga, _ga_*) — audience metrics. Category: analytics. Duration: up to 24 months. Loaded only after consent (Consent Mode v2, default denied).
  • Google Ads — conversions, remarketing and customer lists using hashed email addresses. Category: marketing. Used only after marketing consent.
  • Mettric Identity — opaque identifiers, pages, campaigns, active-time and scroll bands, CTAs, downloads, media and form states are kept in our own infrastructure to measure the journey without typed field content. CRM linking happens only after deterministic identification. Category: marketing; active only after consent.
  • Microsoft Clarity (_clck, _clsk and related identifiers) — heatmaps and session recordings. Category: analytics. Loaded only after consent.
  • Meta Pixel (_fbp, _fbc) and LinkedIn Insight (li_gc, bcookie, lidc and related identifiers) — measurement and remarketing. Category: marketing. Loaded only after consent.
  • OpenAI Ads (__oppref, __obref) — ChatGPT ad attribution and deduplication between the Pixel and Conversions API. Category: marketing. Loaded only after consent.
  • Native Web Push (VAPID) — sets no third-party cookie; the subscription and its public keys are stored on Mettric's own infrastructure. Category: marketing. Requires consent and separate browser permission; withdrawing marketing revokes that grant. The physical subscription remains only when another purpose was separately authorized, such as service updates.

4. How to control

On your first visit, the banner asks for your decision — nothing optional runs before it. You can change your mind at any time via “Manage cookies” in the footer. On withdrawal, we issue opt-out commands, delete applicable local identifiers and cancel the push subscription.

Beyond our panel, your browser lets you block or delete cookies in its privacy settings.

5. Questions

Controller: Mettric Data Technology LTDA, CNPJ 53.179.077/0001-37, Av. Paulista, 1471 — Bela Vista — São Paulo/SP — CEP 01311-927. Data Protection Officer: privacidade@mettric.com.br. See also our Privacy Policy.