Tracking and pixels: Meta, GA4, TikTok and LinkedIn
Arino One holds every advertising pixel for the workspace in one place: Settings, Tracking and pixels. Paste the IDs once and every public surface — landing pages, forms, the hosted checkout, short links — picks them up. There is no per-page setup to forget about, and nothing loads at all while the master switch is off.
Browser pixels
The supported browser pixels are Meta, GA4, TikTok and LinkedIn. Add only the IDs you use; blank fields inject nothing.
On each enabled surface, the standard snippet is injected and a page view fires. From there the surface's own events flow normally — a form submission, a checkout completion, a redirect through a short link.
Consent comes first
When the GDPR module is on, no snippet loads until the visitor accepts cookies in the consent banner. Accepting loads them immediately, without a page reload, so you do not lose the pageview of someone who consents on arrival.
This is the behaviour that makes the setup defensible under ePrivacy: analytics and advertising cookies are not "necessary", and loading them before consent is the most commonly enforced violation in the EU. Leave the GDPR module on unless you have specific legal advice not to.
Server-side conversions
Ad blockers, iOS privacy settings and browser tracking protection drop a large share of browser pixel events — commonly a third or more of them. Arino One therefore also reports three conversions server-side, directly from your instance to Meta's Conversions API:
| Event | Reported as | Fires on |
|---|---|---|
| Short-link click | ViewContent | A tracked short link is opened |
| Form submission | Lead | A public form is submitted |
| Paid order | Purchase | An order reaches paid |
Email and phone are SHA-256 hashed before they leave the server, so Meta receives a match key rather than the raw identifier. Every event carries a stable event ID, which is how the browser copy and the server copy of the same conversion deduplicate instead of inflating your numbers.
Setting it up
Create a Conversions API access token for your pixel in Meta Events Manager, paste it into the Meta Conversions API card and save. It goes into the workspace secret store and is never displayed again — treat it like any other credential and rotate it if it leaks.
Add a test event code if you want events to appear in Meta's Test Events tab, then click Send test event and confirm Meta accepts it.
Proving it works
The Recent conversions list on the same settings page shows the last events your instance sent, with the Meta event name, the delivery status, and the error text when a send failed.
If a conversion never appears at all, it is one of three things and the status column tells you which: the surface toggle is off, the pixel ID is blank, or no access token is stored.
It cannot break anything
Tracking is fire-and-forget by design. A failed pixel call or a Meta outage cannot slow a redirect, break a form submission, or stop an order being marked paid. Marketing instrumentation should never be able to take down the thing it is measuring.
Steps at a glance
- Open the tracking settingsGo to Settings, Tracking and pixels, and turn Enable tracking on. Nothing loads and nothing is reported while the master switch is off.
- Paste your pixel IDsAdd the IDs you actually use: Meta Pixel ID, GA4 Measurement ID, TikTok Pixel ID, LinkedIn Partner ID. Leave the rest blank.
- Choose the surfacesSelect which public surfaces track: landing pages, forms, hosted checkout and short links. There is no per-page setup.
- Add the Conversions API tokenCreate a Conversions API access token for your pixel in Meta Events Manager and paste it into the Meta Conversions API card. It is stored in the workspace secret store and never shown again.
- Send a test eventOptionally add a test event code, click Send test event, and confirm Meta accepts it in the Test Events tab.
- Verify real trafficCheck the Recent conversions list on the same page — it shows the last events sent, the Meta event name, delivery status and the error text when a send failed.
Frequently asked
Where do I add tracking pixels in Arino One?
In Settings, Tracking and pixels. It is workspace-wide: you paste each ID once and every public surface picks it up. There is no per-landing-page or per-form pixel configuration to maintain.
Which pixels are supported?
Meta Pixel, GA4, TikTok Pixel and LinkedIn Insight (Partner ID) as browser pixels, plus the Meta Conversions API for server-side reporting.
Do pixels respect cookie consent?
Yes. When the GDPR module is on, the browser snippets only load after a visitor accepts cookies in the consent banner. Accepting loads them immediately with no page reload required.
Why use the Meta Conversions API as well as the browser pixel?
Ad blockers and iOS privacy settings drop a large share of browser pixel events. Three conversions are therefore also reported server-side straight from your instance: short-link clicks as ViewContent, form submissions as Lead and paid orders as Purchase. Each carries a stable event ID so the browser and server copies deduplicate rather than double-count.
Does Meta receive customer email addresses and phone numbers?
No. Email and phone are SHA-256 hashed before they leave the server, so Meta receives a match key and never the raw identifier.
Can a tracking failure break my landing page or checkout?
No. Tracking never blocks the app — a failed pixel call or a Meta outage cannot slow a redirect, break a form submission, or stop an order being marked paid.
A conversion is not showing up. What should I check?
Three things, in order: the surface toggle is off, the pixel ID is blank, or no access token is stored. The status column in Recent conversions names which one it was.
Apply this to your own deployment
This guide describes decisions we make on live instances. Tell us your channels, systems and region and we will map it to an architecture outline, a provisioning plan and an indicative commercial model — usually within one business day.