# First-Party Attribution RC | TrackAny.Click

Last reviewed: 30 August 2026

[HTML](https://trackany.click/) · [Documentation](https://docs.markengroup.cloud/trackany)

The first-party event and Ads-mirroring layer designed to connect provider-owned campaigns, sessions, conversions and revenue.

## Current status

A local release candidate prepares https://trackany.click/v1/t.js, https://connect.trackany.click, event reporting and Meta/Google OAuth mirroring. There is no public collector deployment, and neither provider connection has production acceptance.

## A platform click and a product conversion are not the same event.

Attribution fails when campaign identity disappears at the landing page, sessions are added instead of ordered, or browser and server claims are treated as equally trusted.

- **Campaigns get copied instead of mirrored:** Manual shadow campaigns drift. OAuth should preserve the provider's stable campaign, ad-group and ad IDs without asking customers to recreate them.
- **Events lose their sequence:** Counts cannot explain a journey unless events stay ordered inside the session that produced them.
- **Incomplete data looks definitive:** Provider metrics, browser events and verified customer outcomes have different coverage; ROAS and CAC must stay unavailable until their inputs are comparable.

## Preserve the context before you calculate the credit.

TrackAny.Click keeps provider ownership, acquisition, session and customer outcomes separate, then calculates only metrics whose inputs and coverage are explicit.

- **Preview — Start denied:** Load the prepared queue-safe embed with consent denied; no identifier, storage access or event request occurs before the site's consent flow grants tracking.
- **Preview — Mirror Ads:** Read authorized Meta and Google campaign → ad group → ad hierarchies and daily metrics without creating or editing provider campaigns.
- **Preview — Order outcomes:** Preserve UTM/click context and build observed journeys from event order within real sessions rather than unrelated totals.
- **Preview — Guard calculations:** Calculate CTR, CPC and CPM from provider facts; expose ROAS and CAC only when revenue or newly acquired customer coverage is complete and explicit.

### Prepared consent-denied embed

```json
<script>
  window.trackany = window.trackany || function () {
    (window.trackany.q = window.trackany.q || []).push(arguments);
  };
  window.trackany("consent", "denied");
</script>
<script
  async
  src="https://trackany.click/v1/t.js"
  data-project="<public project key>"
  data-consent="denied"
  data-endpoint="https://connect.trackany.click"
></script>
```

This is a local release-candidate embed, not a live installation instruction. Use https://trackany.click/v1/t.js and https://connect.trackany.click only after both are deployed and your project has a valid public key; grant consent later through the site's CMP.

## Measure the decision, not just the activity around it.

- **Which provider object created this signup?:** Join stable campaign, ad-group and ad IDs to UTM and session context without duplicating the provider hierarchy.
- **What do CTR, CPC and CPM say?:** Calculate provider-defined ratios from mirrored impressions, clicks and spend for completed account-local days.
- **Are ROAS and CAC complete enough to show?:** Keep ROAS unavailable without complete comparable revenue; divide spend only by explicitly defined newly acquired customers for CAC.

## Give your agent one event vocabulary before it instruments ten screens.

Stable events, an explicit denied-first consent state and documented provider ownership help coding agents generate reviewable analytics code. Prepared addresses do not make the service usable before deployment.

- `Prepare a denied-first TrackAny embed for our CMP.` — The agent can queue consent before loading the prepared script while marking both release addresses as deployment-gated.
- `Mirror our Meta and Google hierarchy without duplicate campaigns.` — The agent can preserve provider-owned campaign, ad-group and ad IDs and keep OAuth secrets server-side.
- `Define ROAS and CAC for this acquisition report.` — The agent can require complete comparable revenue for ROAS and an explicit newly acquired customer denominator for CAC.

## The model is concrete. Production availability is not.

- **Preview — Consent-denied embed:** The prepared script is queue-safe and silent before consent, but its public URL and collector are usable only after deployment.
- **Preview — OAuth Ads mirror:** Meta and Google data remains provider-owned while campaign, ad-group and ad IDs plus daily metrics are mirrored into the project.
- **Preview — Explicit metric semantics:** CTR, CPC and CPM use provider facts; ROAS and CAC remain coverage-bound instead of silently treating missing data as zero.
- **Preview — Production gates:** The rolling seven-day Ads resync flag is disabled; provider approval, secrets, abuse controls, retention, deletion and monitoring remain blockers.

## Provider campaigns stay authoritative. TrackAny.Click adds the first-party outcome layer.

Meta and Google OAuth read and mirror campaign → ad group → ad data; TrackAny.Click does not ask customers to rebuild campaigns or edit them at the provider.

Provider Ads account → Mirrored hierarchy and daily metrics → Consent-aware session → Explicit customer outcome → Guarded ROAS and CAC

This flow is a local release candidate. Provider approval, production secrets, deployment and real-account acceptance are still pending.

## Attribution is only useful when its trust limits stay visible.

The release-candidate architecture separates collection authority, provider ownership, consent, project context and reporting coverage instead of hiding them behind one score.

- **Consent starts denied:** The browser SDK creates no tracking identifiers or requests before an explicit grant and stops future SDK events after revocation.
- **OAuth remains server-side:** Provider tokens and secrets never belong in the embed; mirrored data does not grant permission to edit campaigns.
- **No direct customer Firebase writes:** The collector resolves organization, project, origin and trust before product storage is reached.
- **Retention and coverage stay explicit:** ROAS/CAC coverage, retention, deletion/export and token lifecycle need production acceptance. Privacy guidance is technical, not legal advice.

## Do not mistake a clear model for a public endpoint.

### Can I send production events to TrackAny.Click today?

No. https://trackany.click/v1/t.js and https://connect.trackany.click are prepared release-candidate addresses, not deployed customer services. Use them only after deployment and project-key issuance. Do not guess a script URL or endpoint.
### Must I recreate Meta or Google campaigns?

No. After provider approval, an authorized OAuth connection reads and mirrors campaign, ad-group and ad objects. TrackAny.Click is not a second campaign editor.
### Does consent-aware tracking make my implementation legally compliant?

No. The technical model can start disabled and minimize data, but purpose, legal basis, consent design, retention and deletion require your own legal and operational assessment.