TikTok

08/10/2026

With the TikTok pixel your TikTok campaigns see visits, course views, checkouts, requests, sign-ups and purchases on the academy site, to optimise and build audiences. Aladia loads the official pixel code with your Pixel ID and sends TikTok standard events.

TikTok loads only after Marketing consent in the cookie banner. Cookies, consent and the pages where it runs apply to every tool: see Tracking and cookies.

Where to find the ID

1. In TikTok Ads Manager open Tools › Events Manager (TikTok: Events Manager).
2. Open the site's web pixel. None yet? Connect data source › Web, and choose manual setup (code) as the method, not a partner (TikTok: set up and verify the pixel).
3. The Pixel ID is below the pixel name: uppercase letters and digits, about 20 characters (e.g. C4ABCDEFGH12345678IJ).

You don't need to copy the pixel code: Aladia loads it.

Connect it in Aladia

1. Settings › Integrations, Marketing category, TikTok card.
2. In the Connection section enter the Pixel ID and turn the switch on.
3. Press Save: the Active badge appears.

You need the Owner or Admin role. With the wrong format the field shows Expected format and it won't save.

Events we send

Names are TikTok standard events.

contents holds the course: content_id (course ID), content_name, content_type (product), quantity and price if public. Every event has an event_id (for purchases purchase.<checkout session ID>) for deduplication with the server-side Events API (TikTok: event deduplication). No personal data: no email, phone or name.

How to check

1. Turn TikTok on and save.
2. In Events Manager › your pixel › Test Events, open the site from the QR code or the address (TikTok: Test Events).
3. On the site press Accept in the cookie banner and browse: the page view shows up, ViewContent on a course, SubmitForm after a request…
4. Or use the TikTok Pixel Helper Chrome extension on the site (TikTok Pixel Helper).
5. From Cookie preferences in the footer try Reject: TikTok must receive nothing more (Aladia calls ttq.revokeConsent()).

Server-side sending

Besides the pixel, Aladia sends InitiateCheckout, SubmitForm, CompleteRegistration and CompletePayment to TikTok with the Events API, with the same event_id as the browser (TikTok: deduplication) and, as SHA-256 hashes, email and phone. What we send, deduplication and privacy: Server-side sending.

1. Open TikTok Ads Manager › Tools › Events Manager › your web pixel › Settings.
2. In the Events API section choose Generate access token and copy it (TikTok: Events API, developer docs).
3. In Aladia, on this page, Server-side sending section: paste the token, Save, then turn the switch on.
4. Check: Events Manager › your pixel › Test Events, copy the test code and paste it into Test event code; server events show up there (TikTok: Test Events). Remove it after testing.

Common issues

• Pixel Helper doesn't find the pixel. The visitor didn't give Marketing consent: without it TikTok doesn't load. Use an incognito window and press Accept.
• "Expected format" below the field. You copied the ad account ID or code with extra characters: you need the Pixel ID (uppercase letters and digits).
• The pixel shows "Inactive". No event has arrived since saving: open the site, accept cookies and browse.
• Purchases made after signing in don't arrive. From the browser the purchase fires from the checkout without sign-in; the others (after sign-in, instalments) are counted by server-side sending, for visitors who accepted cookies.

Double counting

See also: Meta, Google Tag Manager.