Ads

Common tasks

• A media buyer who has a login (a staff member with the Media buyer role) sees only their own campaigns, creatives, spend and CSV imports: the ones linked to them on the Media buyers tab. They can add and change those, and nothing else: not another buyer's campaigns, not the overview, performance, fatigue, audiences, projection or settings pages. A CSV that touches someone else's campaign is refused whole. A media buyer can also change only the spend figures they entered themselves: a figure the owner typed in or imported (or any figure from before this rule) is protected, and a file that would replace one is refused whole. The owner and admins see everything and can change any figure. Spend a media buyer typed in is self-reported, and every change keeps the old amount in the Activity page. A person who is ONLY a media buyer gets no shop-wide ad alerts in their bell. Roles add up: someone who is a media buyer AND another role (a Data analyst, say) reads what that role reads, including every campaign's spend and the shop-wide ads pages, but can still add and change only their own campaigns.

• Linking a media buyer's login to their profile. A media buyer with a login can only add pixels, campaigns and ad spend once the owner (or an admin or Manager) has linked their login to their media buyer profile. Until then every Ads page tells them: "Ask the business owner to link you to your media buyer profile." To link: open the profile on the Media buyers tab, find the "Linked login" card, pick the person (only active people with the Media buyer role who aren't linked to another profile are listed) and press Link. One profile per person. "Change" moves it to someone else and "Unlink" ends their access; either one removes the pixels that person added to the profile (and their tokens). If someone has the Media buyer role but no profile at all, the Media buyers tab lists them at the top with a "Make their profile" button that creates theirs and links it in one step. The owner and admins open Ads > Pixels to see every media buyer's pixels with their state (Allowed, Waiting for your OK, or Switched off by the buyer) and a link to each buyer's page; they never see a pixel ID or token.
• Letting a buyer's tracking code run on pages with a sign-up form (owner or admin switch, per media buyer). On a media buyer's page the owner or an admin sees "Let this buyer's tracking code run on pages with a sign-up form", off by default. A pixel is a tracking code: it tells the buyer's ad account which visitors saw a page, so their ads work better. By default it is off on every page where visitors type their details. Turning this on (after ticking that the owner understands and accepts the risk) lets that one buyer's pixel also run on the funnel's landing and opt-in pages that only hold a sign-up form or lead capture. The risk: on those pages the buyer's ad account may receive what visitors type, such as their name, email and phone number. What it collects is set in the buyer's own ad account, so neither the owner nor Lazycom can control it, and under privacy law that is the shop owner's responsibility. Checkout, payment, upsell, downsell and custom HTML pages are always blocked, whatever is chosen. It is recorded with who and when (and which wording was agreed to), can be taken away at any time, and goes away on its own if the buyer is switched off or archived or loses their login.
• Where a buyer's pixel runs. A buyer's pixel loads only for a visitor that buyer's own tracking link brought, only after the visitor allowed marketing, and only on a funnel's landing step that has no form on it (never on opt-in, checkout, upsell or thank-you steps, or on a landing page with a sign-up, checkout or HTML block), unless the owner turned on "Let this buyer's tracking code run on pages with a sign-up form" for that buyer, which also allows the opt-in step and pages with a sign-up form. It also loads on the shop's own pages, the home page included (the default tracking link goes there), as long as the page has no sign-up, checkout or HTML block. The "Let this buyer's tracking code run on pages with a sign-up form" switch does not apply to shop pages: a shop page with any form never loads a buyer's pixel. The cookie policy page never does. In the visitor's browser it receives page views and content views only. The shop's own pixel keeps working as before.
• Checkout pages: server events only. A buyer's pixel never runs in the visitor's browser on a checkout step, so Pixel Helper shows nothing there and that is expected. When the buyer has saved an access token on the pixel, our server sends that buyer's Meta pixel a page view, a content view and a checkout start when a visitor their link brought opens a checkout step (and the purchase and sign-up events as before), a few minutes later. These carry only the visitor's own Meta cookies, browser name and IP address, never a name, email or phone number, and they follow the same rules as everything else: the visitor allowed marketing, the buyer is live and the owner allowed the pixel. With no token saved, nothing is sent from checkout pages.
• Pixel status and test events (the buyer's own Ads > Pixels page). Server events do not show in Pixel Helper, so each Meta pixel has a Pixel status panel: how many page views, content views, checkout starts, purchases and sign-ups were sent to Meta in the last 24 hours and the last 7 days, when something was last sent, and Meta's last answer in plain words (for example that the access token was not accepted, or the pixel could not be found). Events that were not sent (waiting, failed, or skipped, with the reason) are listed too. They appear in Events Manager under the pixel with the connection method Conversions API. "Send a test event" lets the buyer paste the Test Event Code from Events Manager, Test events: we send one page view with that code so it shows live there, and it is never counted as real traffic. It needs a saved access token, the owner's OK on the pixel, and is limited to 5 a pixel an hour. Only Meta pixels have server events. Visitors who did not allow marketing cookies are never sent, so there is no count for them.
• Sales, checkouts and sign-ups sent from the server. For a buyer who saved an access token and whom the business allowed, the shop also sends three events to that buyer's own Meta pixel, only for visitors the buyer's own link brought and who allowed marketing: a Purchase (when a card order is paid, or for cash on delivery when Operations confirms delivery, never twice for one order), an Initiate checkout (a visitor opened a checkout step) and a Lead (a visitor signed up). A Purchase carries the order's value (goods after discount, no delivery fee). The customer's email and phone go with it, in scrambled (hashed) form, only when that media buyer may see customer details (In-house, or "Show customer details" switched on for them in Settings > Staff); otherwise the Purchase carries no contact data at all. Initiate checkout and Lead never carry a name, email, phone or amount. Imported orders, refunded, cancelled or returned orders, and anything older than 60 days are never sent. The shop keeps the visitor's IP address, browser name and Meta cookies for 60 days so these events can be matched, then deletes them. Sending can be switched off for the whole platform; while it is off the events just wait.
• The shop's own sales sent from the server (Meta Conversions API, Settings > Tracking & SEO, directly under the Meta Pixel ID field). Separate from the media buyer events above. A shop that saved its Meta Pixel ID can also paste its Meta access token there (it is stored encrypted and can never be shown again; Replace and Remove are the only ways to change it). Our servers then also tell the shop's own pixel about each Purchase, with the same order number the browser uses, so Meta counts a sale once and still sees it when a browser or ad blocker hides the pixel. A card or bank-transfer sale is sent when it is paid. A cash on delivery sale is sent when the order is confirmed (not when it is placed, not when it is delivered), after a short wait so a confirmation that is taken back stops it; while this is on, the shop's own browser pixel no longer counts a cash on delivery sale at placement, so it is not counted twice. The value is the order total including delivery. Only the first order of a purchase is sent, never an upsell on its own, and only for customers who allowed marketing cookies when they ordered (an order placed before the token was saved is never sent). Orders typed in by hand, chats, and imported orders are never sent, nor refunded, cancelled or returned ones that were not sent yet, nor anything older than 60 days. The customer's email and phone go in scrambled (hashed) form with the browser details Meta uses to match (kept 60 days, then deleted). Removing the token stops it and cancels what was waiting. Sending stays off until Lazycom switches it on after a test with the owner's own token; saving the token before that sends nothing. The owner gets a bell notice when the token is saved, replaced or removed, or when the Meta Pixel ID changes while a token is saved. A cash on delivery sale placed while this was on is not counted in the browser; if the token is removed or sending is switched off before the order is confirmed, that sale reaches the shop's Meta pixel from neither side.

Limits and plan gating

Ads is gated on the crm_media (Growth track) entitlement — fail-closed: without it, spend and attribution screens don't open. Requires See ad spend (who has it: Owner, Admin, Manager, Accountant, Data analyst, Media buyer) (or Manage ad spend (who has it: Owner, Admin, Manager, Media buyer) for editing).