T
Tracking
Attribution & performance for this deployment
Overview
Engagement
Total Leads
—
 
 
Total IC
—
 
Checkouts reached · from signature
Sales
—
 
Reported by the checkout
Cost per Lead
—
Meta spend / leads
 
Gross Revenue
—
 
Sales
—
 
Average Order
—
per sale in this window
Leads over time
Daily lead count (non-bot)
Cost per Lead over time
Daily Meta spend ÷ daily leads.
Revenue over time
Daily gross revenue from confirmed purchases
Products
Loading…
Sales per product over time
Origem e confiança
De onde veio cada checkout e cada compra, e o quanto se pode confiar na resposta. Regra em functions/api/_attribution.js; parcerias em config/attribution.js. Investimento da Meta sincronizado pela Marketing API .
Meta Ads
Vendas
—
Receita
—
Investimento
—
CPA
—
ROAS
—
Investimento sincronizado no nível de campanha, então o ROAS é por campanha, não por anúncio ou conjunto. Venda com fbc mas com UTM de parceria conta para a parceria, não aqui.
Por origem
Compras
Checkouts
Origem Confiança Base Compras Receita
Alta: a origem foi declarada no link (UTM) ou carimbada pela plataforma (fbc, gclid). Média: inferida do referrer, que diz o site e não diz o link nem a campanha. Baixa: sem sinal nenhum, lido como direto — é aqui que se esconde o anúncio que perdeu o fbc no caminho. Nenhuma: a visita nem chegou a ser identificada.
Leads by hour of day
Local time
Leads by day of week
Local time
IC · checkouts started
Quem abriu /finalizar-compra/, de onde veio e com o quê no carrinho. O valor é intenção: quanto o carrinho valia quando o checkout começou, sem nada dizer se a compra aconteceu.
 
By plan
Plan Checkouts Intent Share
By cart size
How many items were in the cart when the checkout opened. One item is the one-off buy; a large cart is a professional assembling material. They have different tickets and respond to ads differently.
Orders · reported by the store
O pedido no momento em que ele é criado na loja, reportado por duas pontas independentes — a tag da página de obrigado e o woocommerce_thankyou do servidor — e encaminhado para Meta e GA4. É pedido gerado, não pagamento confirmado. Pix e boleto criam o pedido antes de alguém pagar, e parte deles nunca é paga: a quebra por meio de pagamento abaixo mostra o tamanho disso. Contar só pagamento confirmado exige o webhook order.updated, que este deploy não liga por decisão.
 
By category
Category Sales Charged Share
By payment method
Arrival to sale
 
UTM breakdown
 
source
placement
campaign
adset
ad
Value Leads Share Meta OK Sales Revenue AOV
Loading…
Recent leads
Click a row to inspect the exact payload sent to Meta / GA4 / Google Ads and the response
When Campaign Adset Ad Device Meta GA4
Loading…
/ 1
Recent IC
Um checkout por linha, com as mesmas colunas de campanha da tabela de leads — a leitura que interessa é comparar as duas. A origem vem da linha de sessions da própria visita, pelo session_id; no link quer dizer que o elo não fechou, não que a pessoa veio sem campanha.
When Link Campaign Adset Ad Plan Items Device
Loading…
/ 1
Recent sales
Which campaign, adset and ad each sale came from, the category it closed on and what the store charged. Click a row for the full record, including what went to Meta. Origin is joined from sessions on session_id, so a row marked no link has empty UTM columns meaning “unknown”, not “no campaign”.
When Link Campaign Adset Ad Plan Items Charged Meta
Loading…
/ 1
Recent purchases
Click a row to inspect the exact payload sent to Meta / GA4 / Google Ads and the response
When Email Product Value Meta GA4 Google Ads
Loading…
/ 1
Recent bots
Events flagged as bot/fraud and excluded from leads & metrics. Click a row to inspect why.
When Reason Campaign Adset Ad
Loading…
/ 1
Tracking health
First-party capture vs pixel. Shows how many lead events you would have lost without server-side tracking.
Real events
—
Duplicates removed
—
ITP recovered
—
Adblock recovered
—
Bots filtered
—
fbp source breakdown
On-page behavior
 
Paid
All
Organic
 
Time on page
Active time only: the clock pauses while the tab is in the background.
Band Visits Share
Scroll depth
Cumulative: "reached 75%" includes everyone who went deeper.
Reached Visits Share
How far down the page
Deepest section that entered the viewport. The row for the plans is the one to watch: leaving before it and leaving with the price on screen are two different problems.
Section Visits Share
Reading level vs. WhatsApp lead
How much of the page the people who asked for a conversation had read.
Group Visits Median time Median scroll Reached plans
Reading level vs. checkout click
Same cut against the checkout clicks. A visitor can appear on the engaged side of both tables; these are two readings, not a funnel split.
Group Visits Median time Median scroll Reached plans
By device
Read from the user-agent of the visit, the same coarse split the leads table uses.
Device Visits Median time Median scroll Reached plans
Tracking Stack · self-hosted on Cloudflare Pages
Dashboard key required
Paste the DASH_KEY you set in Cloudflare environment variables.
Invalid key.
Event details