Analytics, tracking links and consent

Built-in Analytics

Open Analytics for the selected website. It reports visitors, page views, leads, customers, revenue and conversion rates, compares the previous period and shows daily trends, top pages, sources, countries, devices and the product funnel. The live visitor counter refreshes periodically; it is not a list of named people.

Choose the date range using the website timezone, or a valid custom range, and use the CSV export for the current report. Aggregated visitor estimates, order totals and email statistics answer different questions. Bots, team activity, browser privacy behavior and reporting timing can explain differences; do not assume every page view is a unique buyer.

Create a tracking link

Open Tracking links, create a descriptive name and source code and choose a destination path. Associate a YouTube video when appropriate. Share the generated link containing ?src= in the matching description, campaign or QR code.

Rename the label or change the destination later if needed; the source code stays stable because it may already be printed or shared. Deleting a tracking-link record does not erase the source text already retained on subscribers. Automatic source-link creation has a cap, so check the screen if a new source is not appearing as a new managed link.

External analytics and pixels

Use the Analytics connection guide for GA4, Plausible and the supported advertising-pixel IDs. These are separate from built-in Analytics and can produce different totals. Use your own provider IDs and verify the correct website before saving.

Configure the cookie banner and policy wording for your actual setup. External tracking requires the applicable consent behavior; built-in measurement is designed separately and does not mean you can bypass consent for third-party scripts. A banner is not a legal compliance guarantee.

Outgoing integrations

Use Outgoing notifications to connect a receiver to supported events. Configure an endpoint you control, select the events and use the provided test and delivery history. Treat the signing secret as a credential. A successful HTTP delivery proves the receiver accepted a request, not that its downstream business action finished.

Troubleshooting

Check range, timezone, website selection and source URL first. Test external tools with the relevant consent choice. For missing notifications inspect the delivery result and receiver rather than creating duplicate endpoints blindly.