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.
First-party event and attribution layer
Local release candidate · no public collector deploymentKnow what caused the conversion—not just what happened before it.
TrackAny.Click locally mirrors authorized Meta and Google campaign → ad group → ad data and joins it to consent-aware first-party events. The release candidate is not production-deployed, and neither provider connection has passed real-account acceptance.
01Campaign→
02Session→
03Event→
04Conversion→
05Revenue
Why dashboards disagree
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.
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.
First-party attribution model
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.
<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.
Questions worth answering
Measure the decision, not just the activity around it.
These use cases exist in the local release candidate but remain unavailable until collector deployment, provider acceptance and operational release gates are complete.
Which provider object created this signup?
Join stable campaign, ad-group and ad IDs to UTM and session context without duplicating the provider hierarchy.
Read the technical guideWhat do CTR, CPC and CPM say?
Calculate provider-defined ratios from mirrored impressions, clicks and spend for completed account-local days.
Read the technical guideAre 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.
Read the technical guideBuilt for developers who ship with AI
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.
Technical preview scope
The model is concrete. Production availability is not.
Each capability exists in local code and tests, but still needs deployment, provider acceptance, production secrets, distributed controls, retention and operational monitoring.
Consent-denied embed
The prepared script is queue-safe and silent before consent, but its public URL and collector are usable only after deployment.
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.
Explicit metric semantics
CTR, CPC and CPM use provider facts; ROAS and CAC remain coverage-bound instead of silently treating missing data as zero.
Production gates
The rolling seven-day Ads resync flag is disabled; provider approval, secrets, abuse controls, retention, deletion and monitoring remain blockers.
One mirror, no shadow campaign manager
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.
01Provider Ads account→
02Mirrored hierarchy and daily metrics→
03Consent-aware session→
04Explicit customer outcome→
05Guarded ROAS and CAC
Concrete data boundaries
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.
Related guideOAuth remains server-side
Provider tokens and secrets never belong in the embed; mirrored data does not grant permission to edit campaigns.
Related guideNo direct customer Firebase writes
The collector resolves organization, project, origin and trust before product storage is reached.
Related guideRetention and coverage stay explicit
ROAS/CAC coverage, retention, deletion/export and token lifecycle need production acceptance. Privacy guidance is technical, not legal advice.
Related guideBefore you instrument
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.
Design the attribution model before you ship the tracking code.
Define events, provider IDs, customer acquisition and consent now. Send customer data only after the prepared script and collector are deployed and provider, retention and security gates are accepted.