Branding -> Tracking in your admin sidebar.
Your own measurement and advertising accounts, measuring your own traffic. Paste the id a tool gives you and the platform loads that tool on every page of your domain: the public pages, sign-in, the checkout and the trader dashboard. Nothing loads before a visitor accepts the cookie banner, and a visitor who declines loads nothing and sends nothing.
The form runs down the left. The column beside it says, as you type, what each tool will receive and who the tags reach, with a line for anything that cannot work as the form stands. It stays in view while you scroll, and on a narrow screen each part sits under the part of the form it is about. The line above the title says what is saved right now: how many tools are connected, and whether your team is left out.
One save bar saves whatever you changed, and only that. A colleague who
connected another tool while you had the screen open keeps it. Cmd+S or
Ctrl+S saves, and Discard puts the form back to what is saved.
Who can change what
| Permission | What it allows |
|---|---|
view_settings | Open the screen and read every id, switch and what they reach |
manage_settings | Change them |
view_activity_logs | See the last changes at the bottom, each a link to its entry |
view_team | See how many people your team is, in the column and beside the switch |
view_legal | Open your privacy policy from the column and from its warning |
Somebody who may only read gets no save bar, every field disabled, and a line saying which permission changing them takes.
The tools
| Tool | What to paste | Where to find it |
|---|---|---|
| Google Analytics | The measurement id, G- and letters and digits | Admin, Data streams, your web stream |
| Google Tag Manager | The container id, GTM- and letters and digits | At the top of your workspace |
| Microsoft Clarity | The project id, 6 to 16 lowercase letters and digits | Settings, Overview |
| Google Ads | The conversion id, AW- and digits | Goals, Conversions, Settings, Google tag |
| Meta | The pixel id, 10 to 20 digits | Events Manager, next to your dataset |
| TikTok | The pixel id, 10 to 32 letters and digits | Events Manager, Web events |
| X | The pixel id, the short id in twq('config', ...) | Ads, Tools, Events Manager |
The pixel id, starting with a2_ or t2_ | Ads, Events Manager |
Paste the whole snippet a tool gives you if that is easier: the field keeps only the id and says it took it from the snippet. Case does not matter, the field writes the id the way its vendor does. An id that does not have its tool's shape is pointed out under the field while you type. Saving then stops before anything is sent: the field turns red with what the id should look like, and the screen scrolls to it. Nothing is saved until every id has the right shape, and editing the field clears the message.
Under each field you see whether it is connected, or what a save will do with it: connect it, replace the id that is there, or disconnect it. Disconnect empties a connected field, and Keep puts the saved id back.
Google Analytics and Google Ads share one Google tag, so connecting both loads it once.
Conversion labels and event ids
Google Ads and X only count a sign-up or a purchase against a conversion action you made in their own dashboard. Once an Ads id or an X pixel id is in the form, two more fields appear under it:
- Google Ads: the conversion label of your sign-up action and of your
purchase action. Paste the part after the slash in
AW-123456789/label, or the whole thing. When the Ads id is still empty, pasting the whole thing fills that in too. - X: the event id of your sign-up event and of your purchase event, starting
with
tw-. The part aftertw-is the pixel the event belongs to, so pasting an event id while the X pixel id is still empty fills that in too.
Without them those tools see visits but count no conversion, and the column says so. Taking the tool off keeps its labels, so connecting it again finds them back.
Conversions
Two switches decide what your tools hear about besides page views. Both are on unless you turn them off.
- Sign-ups: when somebody makes an account on your domain.
- Purchases: when a challenge is paid for, with the amount, the currency and the challenge. A challenge claimed free with a coupon of 100% counts as a purchase of 0.
Each tool gets the event under its own name, which the column shows:
| Tool | Sign-up | Purchase |
|---|---|---|
| Google Analytics | sign_up | purchase |
| Google Tag Manager | sign_up in the data layer | purchase in the data layer |
| Microsoft Clarity | the custom event sign_up | the custom event purchase |
| Google Ads | your sign-up conversion | your purchase conversion |
| Meta | CompleteRegistration | Purchase |
| TikTok | CompleteRegistration | CompletePayment |
| X | your sign-up event | your purchase event |
SignUp | Purchase |
A purchase carries the payment's id as its order number in every tool, so a purchase that is reported twice counts once. With Tag Manager the data layer events are there for your own tags to pick up: the container decides what happens with them.
The tools run in the trader's browser, so an event is handed over on the next page the trader opens. It waits two days for that page, so a purchase Stripe confirms after the trader closed the tab still counts when they come back within two days. A trader who has not answered the cookie banner yet keeps the event in that tab until they accept, and a trader who declines sends nothing.
Your team
Measure your team is off unless you turn it on. While it is off, the owner and everybody with a role see no cookie banner and load no tag, so your own visits never count as traffic, and a test purchase never as a sale. A tab that loaded the tags before somebody of your team signed in reloads once to drop them. The admin panel shows your traders' names, which is one more reason to keep it off. Beside the switch you see how many people that is.
What the column says
On your domain lists every tool that is on, or that a save turns on or off, with what it receives. Who it reaches says that the cookie banner asks first, that every page is covered, whether your team is measured, and which privacy policy the banner links to: the standard text, or your own and in which languages.
It warns when:
- Google Analytics and Tag Manager are both connected, because a Google Analytics tag inside your container would count every page view and purchase twice.
- Google Ads or X is connected without the label or event id for an event that is switched on.
- An X event id belongs to another pixel than the X pixel id above it, which would count nothing.
- Both switches are off while an advertising tool is connected.
- Your privacy policy is the standard text, which names no cookies and none of these tools, or your own text does not mention cookies. The warning opens Legal on the privacy policy.
- Your team is measured.
A warning that a field fixes takes you to that field.
History
At the bottom are the last changes to this screen, from either design and whoever made them: which tool was connected, changed or removed, and which switch went on or off. Each opens its entry in the activity log, and a right click copies its id or a link to it. Changes by Propper's own staff are left out, as they are in the log.
In the older designs
On Propper - OG and Tactical the screen keeps its earlier form: five fields for Google Analytics, Tag Manager, Google Ads, Meta and TikTok, and a note about the cookie banner. Saving there changes only those five. Clarity, X, Reddit, the conversion labels and the switches set on the new design stay as they are, and they work in every design, because the tags load the same way whatever design a firm runs.