PartnerConsole Pixel
One script tag that fills the whole Behavior section on its own.
The PartnerConsole Pixel is the fastest way to see what customers do inside your app. It's one script tag: paste it into your app's admin UI and page views, sessions, and custom events start flowing, each one attributed to the right shop automatically. No analytics stack, no cookie banner, nothing to instrument for the basics.
Once it's in, the whole Behavior section fills on its own: usage events stream live, web analytics charts itself, funnels get their steps, and session recordings become available.
Set up the Pixel
-
Open your app in the console, click Settings in the top right, and find the PartnerConsole Pixel card.
-
Click Enable tracking. This generates the app's Pixel token for you.
-
Copy the snippet and paste it into your app so it loads on every page. The token is already inside it (
px.js?token=pcpx_...), so there's nothing else to fetch or configure.
That's it. The card shows "Receiving data" the moment the first event arrives, with the last event time and a 7-day count, so you always know the Pixel is alive.
What it sends
Out of the box, a page_view for every screen a customer opens and a user_session_start when they begin a session. Every event carries the page, a normalized route (so /orders/123 and /orders/456 count as one screen), the session, and the customer's country, resolved privately on our servers from the connection, never by a third party.
Your developers can also report custom events (a first sync, a report exported) with one line of code. See Usage events for the details.
Safe by default
The Pixel token is created when you enable tracking and lives inside the snippet you copied; the card always shows the current one. It's publishable by design: it can only send events, never read anything. If it ever ends up somewhere you didn't intend, click Regenerate token on the card and every deployed tag goes dead instantly. Turning the Pixel off works the same way.
With the Pixel flowing, you can see which features get used, where onboarding stalls, and which customers are drifting away, all without asking your developers for a single report.