Install the Relator pixel on the client’s website, verify the domain, choose where each event goes (Meta Conversions API and Google Ads enhanced conversions) and follow the health of what is sent.
Tracking installs Relator’s own pixel on the client’s website. It records visits and website events (purchase, lead, cart and others) and, from Relator’s server, forwards each event to the Meta Conversions API and to Google Ads enhanced conversions. Events sent by the server don’t depend on the visitor’s browser, so blockers and cookie restrictions lose fewer conversions.
Before you start
The pixel belongs to each client. Enter the client first; in the agency view, the screen asks you to Choose a client.
To forward events, connect the client’s Meta Ads and/or Google Ads. Without the connection, the platform column shows Connect Meta to forward or Connect Google Ads to forward. See Connect Meta Ads and Connect Google Ads.
Access to the website (code, Google Tag Manager, Shopify or WordPress) and, for the recommended mode, to the domain’s DNS.
Setup is done by whoever can edit the client (agency team, or the client’s admins and editors). The client invited to the portal only sees the Health step, with the notice Your agency sets up tracking. Here you follow the health of the events.
Step by step
Open Sources in the sidebar and, on the Data sources screen, click the Tracking tab. Setup has four steps: Install, Verify domain, Forward events and Health. You can go back to any step you’ve already done, but you can’t skip ahead.
1
Step 1
Enter the domain and where the pixel is served from
In Website domain, type just the address, without https:// and without a path (for example, yoursite.com). If the client has a website on file, it comes suggested. Then choose where the pixel is served from:
Your website’s subdomain (recommended): the pixel runs on t.yoursite.com, as part of the website itself, and avoids most blockers. It needs one DNS record (step 2).
Relator’s domain (quick): works right away, no DNS changes. Ad blockers may stop part of the events. You can switch to the subdomain later.
Illustrative screen
Korra/Connections
Ask RelatorAIPT
TrackingRelator pixel on Korra’s website
Connections
Tracking1
1. InstallCurrent
2. Verify domain
3. Forward events
4. Health
2
Start with the website
Website domainkorra.comJust the address, without https:// and without a path.
3
Where the pixel is served fromYour website’s subdomain (recommended)Relator’s domain (quick)
4
1The Tracking tab sits next to Connections, in Data sources.
2The four setup steps.
3The website domain, without https://.
4Website subdomain (recommended) or Relator’s domain.
2
Step 2
Install the code on the website
Under How to install, choose Code, Google Tag Manager, Shopify or WordPress and follow the on-screen instructions. The code already carries the website identifier; use Copy code.
Code: paste it before the closing </head> on every page.
Google Tag Manager: create a Custom HTML tag, paste the code, choose the All Pages trigger and publish the container.
Shopify: in Online Store › Themes › Edit code, open theme.liquid, paste before </head> and save.
WordPress: in Appearance › Theme Editor (or the header plugin you already use), paste before </head> and save.
3
Step 3
Verify the domain
In subdomain mode, create in the domain’s DNS the record the screen shows: type CNAME, name t and the value unique to this website (use Copy). Relator checks automatically every 5 minutes; Verify now forces a check. When Domain verified shows, move on to forwarding. In Relator’s domain mode, this step asks for nothing.
4
Step 4
Choose where each event goes
Pick the Meta dataset and the Google Ads account in the searchable selectors. The table lists each Website event with its volume in the Last 24h and, for each platform, the destination: the Meta event and the Google conversion action, or Don’t send. RelatorAI suggests destinations (marked suggested) with the reason, for example the primary conversion already optimizing the account’s campaigns. Review and click Save and go to Health.
5
Step 5
Follow the health
The Event health step shows the last 24 hours: Events 24h against yesterday, Accepted by platforms (of those sent) and a table per event with Received, what Meta and Google accepted and the Status.
Buyer data and consent
Send hashed email and phone: email and phone leave the website already turned into SHA-256, a code that can’t be reversed. Relator never stores the raw data. With them, Meta and Google match more conversions to the people who saw the ad.
Respect the cookie banner consent: the pixel reads the consent from the website’s banner (Google consent mode, IAB TCF v2 or rd('consent', …)). Without ads consent, the event isn’t forwarded; without user data consent, email and phone don’t go along; without analytics consent, the visitor gets no cookie. If the website has no banner, events are counted and forwarded without personal data.
The visitor’s IP and browser are used only when sending to Meta and Google and aren’t stored.
Statuses in the health table
Healthy
What it means
The event is arriving and the platforms are accepting it.
Meta rejected / Google rejected
What it means
More than half of the sends were rejected. The row gives the reason, for example Conversion action is inactive or The event arrived without the order id. When the problem is the conversion action, use Choose another action.
Stopped
What it means
The event usually arrives at least once an hour and, in the last 3 hours, less than 30% of the usual came in. The "[event]" without events for [N] hours banner shows, and the notice also goes to the bell.
No events
What it means
The event hasn’t arrived in the period yet.
Status
What it means
Healthy
The event is arriving and the platforms are accepting it.
Meta rejected / Google rejected
More than half of the sends were rejected. The row gives the reason, for example Conversion action is inactive or The event arrived without the order id. When the problem is the conversion action, use Choose another action.
Stopped
The event usually arrives at least once an hour and, in the last 3 hours, less than 30% of the usual came in. The "[event]" without events for [N] hours banner shows, and the notice also goes to the bell.
No events
The event hasn’t arrived in the period yet.
Common problems
"The record wasn’t found in the DNS yet." Propagation can take a while. Check the name t and the copied value and wait for the next check.
"The CNAME points elsewhere." If the website’s DNS is on Cloudflare, set the record to DNS only (grey cloud).
"DNS is right; the certificate is being issued…" The record is correct. The subdomain certificate may take a few minutes.
"72 hours passed without the DNS record." The domain claim expired. Create the CNAME and click Verify now.
"This domain is already in use by another client." Another website has already proven ownership of this domain. If it’s yours, contact support.
"No events received yet" after installing: check that the code is on every page and that the Google Tag Manager tag was published. The screen updates on its own.
"No gclid or buyer data for Google to match the event": Google needs the ad click or hashed email/phone to attribute the conversion. Turn on Send hashed email and phone and send that data in the event.
Frequently asked questions
Do I need to remove the Meta pixel or the Google tag from the website?
No. The Relator pixel works alongside them. In Meta, the browser event and the server event are deduplicated by the same event_id.
Does Relator change anything in the ad account?
No. It only sends events to the Meta dataset and the Google conversion actions you chose. Campaigns, budgets and account settings don’t change.
Can I type the pixel ID or the conversion action ID?
No need. Dataset, account and conversion action show by name, from the client’s connections. Google lists only active conversion actions.
Does the end client see tracking?
They see the Health step, without being able to change anything. Install, domain and forwarding stay with whoever edits the client.
TrackingRelator pixel on Korra’s websiteConnectionsTracking